To reconcile an ABA ERA to original claims and service lines, identify the payer, receiver, remittance, payment trace, claim control numbers, and exact submitted version. Match each adjudicated claim and line, then post paid, allowed, adjustment, patient responsibility, denial, reversal, and provider-level states to separate fields. Preserve the original claim, ERA, mapping decision, exception, and later correction as distinct evidence.
Define Gideon's ERA-to-claim reconciliation control
Gideon's crosswalk begins with the transmitted claim inventory and the raw remittance. It records whether matching used a payer control number, provider control number, service date, line identity, amount, or approved combination. Ambiguous matches enter an exception queue; they never post to the most convenient account.
Build the remittance-to-claim crosswalk
Record payer; product; receiver; ERA file and control; receipt time; payment trace; BPR amount and status; claim control numbers; submitted claim version; person; service date; line; billed amount; allowed amount; paid amount; group code; CARC; RARC; PLB; patient responsibility; reversal; correction; match method; confidence; exception; poster; reviewer; and close. Structured fields support identity, versioning, clocks, comparison, access, routing, holds, measurement, correction, retesting, and close. Narrative preserves clinical meaning, uncertainty, disagreement, family communication, privacy, legal deferral, and why the authorized owner chose the final path.
Run Gideon's workflow
Gideon validates the ERA envelope and payment context, then matches claims and service lines to the locked outbound inventory. He balances claim and line amounts, isolates provider-level adjustments, and routes unclear identifiers for research. Automated posting requires the same evidence and balance rules as manual posting, plus a retained mapping and override history.
Keep decision rights with qualified owners
An ERA explains payer adjudication; it does not rewrite the clinical record, authorization, or submitted claim. A paid amount does not prove correct coding or coverage. A zero-payment ERA can still contain meaningful adjudication, and a bank deposit without remittance detail cannot support line-level posting.
Work through Gideon's fictional example
Gideon receives a fictional ERA containing 31 claims and 69 service lines. Twenty-five claims match exactly. Two have reused provider control numbers, one references a corrected version, one has a line-count mismatch, one carries a provider-level adjustment, and one belongs to another entity. Four repair. Two remain quarantined. This synthetic cohort tests workflow and arithmetic only. It creates no coding, coverage, authorization, payment, patient-balance, privacy, accounting, or legal conclusion for a real person, provider, plan, claim, or deposit.
Calculate Gideon's measures
Initial claim-level match is 25 of 31 claims, or 80.6%. Sixty-six of 69 service lines reach a verified posting or documented hold, or 95.7%. ERA files, payments, claims, lines, adjustments, and ledger entries remain distinct denominators.
Address the main ERA-to-claim reconciliation risk
A loose match can post another person's adjudication or apply a reversal to the wrong claim version. Treating PLB amounts as claim-level adjustments can make every claim appear balanced while the deposit remains wrong.
Test the remittance-to-claim crosswalk against exceptions
Gideon tests duplicate control number, corrected claim, reversal and correction, zero payment, split line, bundled line, payer reassigned ID, PLB, another entity, missing original claim, and repeated ERA file. Each test retains the initial evidence, source version, expected result, actual result, affected unit, safeguard, owner, correction, retest, and disposition. Failed and held cases stay inside the predeclared cohort.
Document the stop condition
Quarantine a remittance item when payer, entity, claim version, service line, amount, group code, or adjustment level cannot be verified. Restrict wrong-person or wrong-entity evidence and route privacy review when exposure may have occurred.
Hand off open work clearly
Gideon's handoff includes the raw ERA, payment context, outbound claim version, match keys, unmatched fields, balance, adjustment level, posting result, owner, and deadline. The receiver independently rebuilds one paid, one adjusted, and one exception item before accepting the crosswalk. Overrides include rationale and approval.
Maintain Gideon's control over time
Gideon tests remittance parsers and mapping tables after payer, clearinghouse, software, code-set, or account changes. His close review compares raw ERA totals, posted transactions, unresolved exceptions, and deposit evidence. Reprocessed claims, reversals, and duplicate files receive their own test cases and stay visible through final disposition.
Run Gideon's independent check
Gideon assigns a reviewer who did not build the remittance-to-claim crosswalk. The reviewer reconstructs the ERA-to-claim reconciliation state, source, decision, calculation, correction, and close from retained evidence. Earlier versions, failed records, and holds remain available. A missing population, hidden exception, unexplained value, overwritten history, or decision by an unauthorized role fails the check.
Use the adopted claim standard as the starting boundary
Current 45 CFR 162.1102 identifies the adopted professional-claim standard. CMS's professional-claim page provides Medicare electronic and paper context, while the NUCC Version 13.0 manual governs its paper-form scope. Gideon checks the actual transaction, service date, payer, product, and receiver before applying any ERA-to-claim reconciliation rule.
Keep companion and claim-status evidence route specific
CMS says its Medicare FFS companion guides supplement the X12 TR3 for named Medicare routes. The administrative-simplification claim-status page identifies 276 and 277 status transactions, and the March 2026 Medicare status guide illustrates Medicare-specific stages. Gideon records which source and receiver produced each state in the remittance-to-claim crosswalk.
Read ERA adjustments at the correct level
The current CMS ERA and EFT page describes an ERA as a health plan's explanation of claim payment and explains CARC and RARC use. The Medicare remittance page separates claim, service-line, and provider-level adjustments and explains PR, CO, and PLB in Medicare scope. Gideon retains those levels instead of moving an unexplained amount into another account.
Reassociate remittance and payment with evidence
The CMS EFT page describes Medicare direct deposit and reconciliation with bank statements. X12 RFI 2075 explains the 835 TR3's one-to-one relationship between a payment mechanism and an 835, with a zero-payment 835 as the stated exception. Gideon uses trace, amount, payee, date, and bank evidence for the remittance-to-claim crosswalk.
Treat responsibility codes as adjudication evidence
X12 RFI 2048 explains that an adjustment assigned to the patient uses PR and an adjustment arising from a provider contractual or regulatory obligation uses CO within the 835 guide. CMS's Medicare remittance guidance says Medicare beneficiaries may be billed only for adjustments carrying PR. Gideon also verifies the actual program, contract, secondary coverage, notices, and protections before a balance action.
Limit payment data to authorized use
HHS treatment, payment, and health-care-operations guidance describes HIPAA pathways for covered entities. Its minimum-necessary guidance generally applies to payment uses, disclosures, and requests. Gideon records entity status, purpose, recipient, workforce role, and scoped data access for the remittance-to-claim crosswalk, with more protective law or contract requirements evaluated separately.
Preserve clinical and compliance authority
The CASP public summary and BACB Ethics Code provide scoped clinical and covered-professional context. Clinical record authorship and care decisions stay with qualified roles. The OIG GCPG is voluntary and nonbinding general guidance. Gideon uses these sources for control design without presenting them as a universal ERA-to-claim reconciliation mandate or payment guarantee.
Related resources
- Match ABA ERA, EFT, and Bank Deposit Evidence.
- Reconcile Same-Day ABA Claim Lines Before Release.
- Validate Patient Responsibility Before an ABA Statement.
- Validate ABA Claim Service Dates and Multi-Date Spans.
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, Professional Paper Claim Form CMS-1500.
- National Uniform Claim Committee, 1500 Claim Form Reference Instruction Manual Version 13.0.
- Centers for Medicare and Medicaid Services, Medicare Fee-for-Service Companion Guides.
- 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 and Electronic Funds Transfer.
- Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice.
- Centers for Medicare and Medicaid Services, Electronic Funds Transfer.
- X12, RFI 2075, 835 Relationship to Payment.
- X12, RFI 2048, Claim Adjustment Group Code CO With Coinsurance.
- 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.