Reconcile Same-Day ABA Claim Lines Before Release

Define Farah's same-day line reconciliation control

Farah treats the calendar day as a reconciliation container rather than a billable unit. Her map shows clinical service intervals, excluded time, provider handoffs, setting changes, simultaneous participants, and proposed lines. It preserves each line's source and prevents one interval from appearing under multiple codes or providers.

Build the same-day interval and line map

Record person; service date; timezone; event and record IDs; raw intervals; pauses; provider and role; participant; group size when relevant; setting; modality; code candidate; modifier; authorization bucket; unit rule; aggregation order; proposed line; duplicate key; overlap result; total supported time; excluded time; reviewer; hold; and release. 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 Farah's workflow

Farah imports raw intervals, sorts them chronologically, and marks factual transitions. She tests overlap at the person, provider, service, and setting levels. The coding reviewer applies current licensed material and payer rules after the facts are stable. Units are calculated once at the allowed level, and totals reconcile back to the complete day.

Keep decision rights with qualified owners

Two different claim lines can represent distinct supported services on the same date. Separate labels alone cannot establish that distinction. One provider's documentation cannot support another provider's line, and a payer edit or clearinghouse acceptance cannot establish that simultaneous activity was clinically delivered or separately reportable.

Work through Farah's fictional example

Farah reviews 18 fictional service days containing 43 proposed lines. Twelve days reconcile on the first pass. One duplicates a transition, one overlaps two individual services, one attributes time to the wrong provider, one rounds each fragment separately, one exceeds an authorization bucket, and one uses the wrong setting. Four repair. Two remain held. 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 Farah's measures

Initial day readiness is 12 of 18 days, or 66.7%. Forty of 43 proposed lines have supported, unique intervals after repair, or 93.0%. Days, events, intervals, providers, minutes, authorization units, and claim lines retain separate denominators.

Address the main same-day line reconciliation risk

Daily totals can balance while individual lines duplicate time or misstate providers. Fragment-level rounding can also create units that do not exist when the rule requires aggregation before conversion.

Test the same-day interval and line map against exceptions

Farah tests provider handoff, concurrent caregiver work, group service, travel gap, meal break, location change, telehealth fallback, modifier change, authorization split, corrected record, and repeated batch import. 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

Hold the affected day when raw intervals, provider attribution, simultaneous-service treatment, aggregation rule, authorization allocation, or duplicate status is unresolved. Keep unaffected days and clearly separable lines moving under the documented release policy.

Hand off open work clearly

Farah's handoff includes the sorted timeline, excluded intervals, transition facts, code and modifier source, unit calculation, overlap test, proposed lines, authorization comparison, and unresolved exception. The receiver reconstructs the day from raw records instead of relying on the system total. Every correction keeps the earlier proposal and review reason.

Maintain Farah's control over time

Farah reruns same-day tests after code-table, rounding, interface, scheduling, staffing, or payer changes. Her monthly review samples high-line-count days, provider handoffs, and days with both direct and caregiver services. It reports first-pass defects separately from repaired lines and preserves every held day in the due cohort.

Run Farah's independent check

Farah assigns a reviewer who did not build the same-day interval and line map. The reviewer reconstructs the same-day line 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. Farah checks the actual transaction, service date, payer, product, and receiver before applying any same-day line 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. Farah records which source and receiver produced each state in the same-day interval and line map.

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. Farah 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. Farah uses trace, amount, payee, date, and bank evidence for the same-day interval and line map.

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. Farah 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. Farah records entity status, purpose, recipient, workforce role, and scoped data access for the same-day interval and line map, 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. Farah uses these sources for control design without presenting them as a universal same-day line reconciliation mandate or payment guarantee.

Related resources

• Reconcile an ABA ERA to Original Claims and Service Lines.
• Validate ABA Claim Service Dates and Multi-Date Spans.
• Match ABA ERA, EFT, and Bank Deposit Evidence.
• Audit ABA Remittance Posting and Financial Close.

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.