Validate ABA Claim Service Dates and Multi-Date Spans

Define Elena's service-date and date-span validation control

Elena begins with the actual date on which each service occurred. She preserves the timezone, midnight boundary, start and stop evidence, late-entry timing, and the exact claim version. A date span becomes a claim representation only after a qualified reviewer confirms that the applicable format and payer route permit it for those services.

Build the service-date release worksheet

Record person; encounter ID; local date and timezone; raw start and stop; service; provider and role; setting and modality; authorization period; code candidate; unit method; claim format; span start and end; source record; payer and product; companion guide; filing deadline; late entry; correction history; reviewer; discrepancy; hold; and release version. 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 Elena's workflow

Elena groups records by person, payer, provider, and actual date, then compares them with the proposed claim. She checks every change within a span and every event that crosses midnight. A late signature keeps its own timestamp. Only the service date supported by the record moves to the claim after current format, code, and receiver rules reconcile.

Keep decision rights with qualified owners

The date field cannot cure a missing service record or convert travel, preparation, supervision, or another activity into a covered service. Clinical authors own the service facts. Coding and billing reviewers select the claim representation from those facts. Payer acceptance remains separate from documentation accuracy and coverage.

Work through Elena's fictional example

Elena locks 24 fictional encounters. Seventeen have matching service dates, providers, settings, authorization periods, source records, and claim representations. Two use signature dates, one crosses midnight, one combines a provider change, one uses an expired authorization date, one has an unsupported span, and one has a timezone conflict. Five repair. Two stay 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 Elena's measures

Initial date readiness is 17 of 24 encounters, or 70.8%. Twenty-two reach verified release or documented final hold, or 91.7%. Encounters, calendar dates, spans, minutes, claim lines, signature timestamps, and submissions remain different units.

Address the main service-date and date-span validation risk

A system default can silently copy the scheduled date or note-entry date into the claim. Multi-date billing can hide a provider, setting, code, or authorization change that requires separate evidence and possibly separate lines.

Test the service-date release worksheet against exceptions

Elena tests midnight crossing, daylight-saving change, late signature, corrected service date, provider handoff, setting change, authorization expiration, weekend span, payer transition, and duplicate encounter. 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 release when the actual service date, timezone, provider, setting, authorization period, span authority, or line allocation cannot be reconstructed. Preserve the source and proposed claim versions while the clinical, coding, payer, or system owner resolves the specific conflict.

Hand off open work clearly

Elena's handoff names each raw encounter, proposed date or span, changed fact, rule source, filing clock, open discrepancy, owner, and retest. The receiver recalculates one ordinary event and one midnight or change event before accepting the queue. Any family-facing update explains the administrative hold without implying a change to care or coverage.

Maintain Elena's control over time

Elena samples span and single-date claims after scheduling, timezone, EHR, payer, code, authorization, or interface changes. She compares the service record with the transmitted version and the payer acknowledgment, ages every hold, and records which source version governed the decision. The review keeps corrected claims in a separate cohort from first transmissions.

Run Elena's independent check

Elena assigns a reviewer who did not build the service-date release worksheet. The reviewer reconstructs the service-date and date-span validation 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. Elena checks the actual transaction, service date, payer, product, and receiver before applying any service-date and date-span validation 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. Elena records which source and receiver produced each state in the service-date release worksheet.

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. Elena 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. Elena uses trace, amount, payee, date, and bank evidence for the service-date release worksheet.

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. Elena 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. Elena records entity status, purpose, recipient, workforce role, and scoped data access for the service-date release worksheet, 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. Elena uses these sources for control design without presenting them as a universal service-date and date-span validation mandate or payment guarantee.

Related resources

• Reconcile Same-Day ABA Claim Lines Before Release.
• Audit ABA Remittance Posting and Financial Close.
• Reconcile an ABA ERA to Original Claims and Service Lines.
• Reopen a Closed ABA Claim When New Evidence Arrives.

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.