To investigate a missing ABA remittance after adjudication, verify the exact claim, payer, payee, adjudication state, and expected delivery route. Search clearinghouse, direct EDI, portal, vendor, and paper channels using authenticated identifiers. Check for zero-payment remittance and access failures, then reconcile any payment or deposit. Avoid claim resubmission or manual posting until the missing artifact and payer state are understood.
Define Daria's missing-remittance investigation control
Daria's investigation record begins with evidence that adjudication occurred and a remittance should exist. It distinguishes a missing file, delivery failure, inaccessible file, wrong receiver, wrong payee, paper remittance, zero-payment advice, and missing payment. Each condition has a different owner and next step.
Build the missing-remittance investigation record
Record payer and product; payee; claim and version; payer control; adjudication source and date; expected ERA or paper route; trading partner; receiver ID; mailbox; delivery time; file control; trace; zero-payment status; portal; vendor ticket; access role; payment; deposit; resend or retrieval request; privacy issue; owner; deadline; evidence; and closure. Structured fields preserve identity, source, level, version, clock, comparison, access, action, hold, calculation, correction, retest, and closure. Narrative captures clinical meaning, uncertainty, disagreement, family communication, privacy, legal deferral, and the responsible owner's rationale.
Run Daria's workflow
Daria validates adjudication, checks every authorized delivery endpoint, and asks the trading partner or payer for a file-level trace. She confirms whether the remittance was sent, received, rejected, archived, or routed elsewhere. Any related money stays unapplied or on hold until claim-level detail is recovered.
Assign decisions to qualified owners
A portal paid status cannot supply all line adjustments or patient responsibility. A deposit cannot replace remittance detail. A missing remittance does not mean the claim is missing, and a repeated claim submission can create a duplicate after adjudication.
Work through Daria's fictional example
Daria reviews 16 fictional investigations. Ten locate the remittance in the correct mailbox, two find paper advice, one finds a zero-payment ERA, one identifies a wrong receiver ID, one finds a vendor-access failure, and one remains untraced. Fourteen reach a verified artifact or delivery cause. Two remain escalated. This synthetic cohort tests control logic and arithmetic only. It creates no coding, coverage, clean-claim, authorization, payment, patient-balance, disclosure, appeal, privacy, or legal conclusion for a real person, provider, plan, claim, or remittance.
Calculate Daria's measures
Initial artifact recovery is 13 of 16 cases, or 81.3%. Verified remittance or documented route-cause completion is 14 of 16, or 87.5%. Cases, files, claims, payments, deposits, and access incidents remain separate units.
Address the main missing-remittance investigation risk
Resubmitting a claim because its remittance is absent can create duplicate adjudication. Posting from a deposit amount can allocate adjustments and responsibility to the wrong claims.
Test the missing-remittance investigation record against exceptions
Daria tests wrong receiver ID, paper route, zero-payment ERA, portal archive, vendor outage, access revocation, duplicate file name, wrong payee, deposit without ERA, and payer resend. Each fixture retains source version, expected state, actual state, affected unit, safeguard, owner, repair, retest, and disposition. Failed, unknown, and held items remain inside the predeclared cohort.
Document the stop condition
Hold resubmission, manual posting, statement, and close when adjudication and remittance evidence conflict. Restrict any wrong-payee or wrong-person file and route privacy review if exposure may have occurred.
Hand off open work with evidence
Daria's handoff contains adjudication proof, expected and checked routes, identifiers, vendor or payer contacts, payment state, access issue, next deadline, and owner. The receiver verifies the endpoint before requesting another file.
Maintain Daria's control
Daria reviews missing-remittance causes after receiver, clearinghouse, payer, vendor, mailbox, or access changes. Recurring failures create a route-level corrective action and a test of retrieval continuity.
Verify Daria's release evidence
Daria closes the investigation after the retrieved artifact is stored in the approved location, its claim inventory reconciles, and any related cash is matched. She also records whether historical remittances remain accessible after the route or vendor correction.
Run Daria's independent review
Daria assigns a reviewer who did not build the missing-remittance investigation record. The reviewer reconstructs the missing-remittance investigation source, state, calculation, action, and close from retained evidence. Earlier versions, failed tests, unknowns, and holds remain available. Hidden exceptions, unexplained values, overwritten history, missing population, or unauthorized decisions fail review.
Start with the adopted claim and status standards
Current 45 CFR 162.1102 identifies the adopted professional-claim standard. The CMS claims-status page identifies the 276 request and 277 response. Daria still records the actual payer, product, route, transaction version, receiver, and artifact before applying either source to the missing-remittance investigation record.
Keep the Medicare stage example inside Medicare
The March 2026 CMS Medicare claim-status guide distinguishes 999 front-end processing, 277CA claim-level acknowledgment, payer control assignment, clean-claim payment-status timing, and duplicate risk during editing. Daria uses those facts only for the applicable Medicare route; other payers and contracts require their own evidence for missing-remittance investigation.
Read remittance codes with their level and context
CMS's Medicare remittance page separates claim, service-line, and provider-level adjustments and explains group codes, CARCs, RARCs, and PLB in Medicare scope. Daria links the code combination to the raw remittance, original claim, payer source, and qualified decision rather than treating one code as a complete outcome.
Use current X12 code-list status
The X12 external-code-list index defines the scopes of CARCs, RARCs, claim status, and related lists. The current CARC list explains why a claim or line was paid differently than billed. The current RARC list separates supplemental remarks from informational alerts. Daria stores these meanings in the missing-remittance investigation record.
Version updates instead of overwriting history
The X12 code-update listing shows a July 1, 2026 update and notes a corrected RARC N922 effective date on August 3, 2026. Daria retains start, modification, and stop dates, source-check time, and historical mappings so an older remittance is evaluated against the relevant code-set state.
Distinguish receipt and correction identifiers
X12 RFI 2099 says 999 acceptance does not necessarily establish carrier receipt date. X12 RFI 2060 explains the payer-control-number requirement for the standard replacement or void path after adjudication and notes that pending routes can differ. Daria preserves transaction, claim, payer, and version identities separately.
Protect payer order and payment data
The CMS coordination-of-benefits page describes the covered-entity COB transaction. HHS payment guidance and minimum-necessary guidance apply only when their HIPAA conditions are met. Daria verifies payer order, entity status, purpose, recipient, role-based access, and the narrow data needed for the missing-remittance investigation work.
Keep clinical and compliance authority scoped
The CASP public summary and BACB Ethics Code supply limited clinical and professional context. The OIG GCPG is voluntary and nonbinding. Daria keeps clinical authorship, coding decisions, payer actions, disclosure authority, financial entries, and legal conclusions with their qualified owners throughout the missing-remittance investigation record.
Related resources
- Reconcile Corrected ABA Claim Versions to Payer Status.
- Separate ABA First-Pass Transmission, Adjudication, and Payment Yield.
- Prevent Duplicate ABA Claims During Ambiguous Payer Responses.
- Validate Payer-Specific Clean-Claim Status for ABA Reporting.
Sources
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary.
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
- Electronic Code of Federal Regulations, 45 CFR 162.1102, standard for health care claims.
- Centers for Medicare and Medicaid Services, Health Care Claims Status.
- Centers for Medicare and Medicaid Services, Checking Medicare Claim Status, March 2026.
- Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice.
- X12, External Code Lists.
- X12, Claim Adjustment Reason Codes.
- X12, Remittance Advice Remark Codes.
- X12, Code Updates Listing.
- X12, RFI 2099, 999 Confirming Claim Receipt.
- X12, RFI 2060, Withdrawal or Void Claim and Response.
- Centers for Medicare and Medicaid Services, Coordination of Benefits transaction.
- U.S. Department of Health and Human Services, Uses and Disclosures for Treatment, Payment, and Health Care Operations.
- U.S. Department of Health and Human Services, Minimum Necessary Requirement.
- U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.
