Detect Missing ABA Charges Without Treating Schedules as Proof

Define Yara's missing-charge detection without schedule substitution control

Yara's ledger records the source that raised the gap and the evidence needed to resolve it. It distinguishes missing record, missing claim, delayed interface, nonbillable activity, bundled service, canceled event, duplicate alert, and unsupported claim.

Build the charge-gap exception ledger

Record gap ID; source system; planned event; actual service; record; claim; interface time; billability; code and units; authorization; provider; payer; filing clock; exclusion; duplicate alert; hold; expected amount source; action; owner; retest; and close. Structured fields preserve identity, authority, source, version, clock, evidence, calculation, money movement, action, hold, retest, and closure. Narrative captures clinical meaning, uncertainty, disagreement, accessibility, family communication, legal deferral, and each accountable owner's rationale.

Run Yara's workflow

Yara runs both directional comparisons, applies a waiting window for expected latency, and investigates remaining exceptions. The reviewer checks current source evidence before creating or correcting any claim.

Assign decisions to qualified owners

Charge capture is a completeness control, not authorization to bill. Expected revenue estimates are separate from submitted charges, allowed amounts, adjudication, payment, and cash.

Work through Yara's fictional example

Yara reviews 32 fictional gaps. Eleven are timing lag, seven are valid missing claims, five are cancellations, three are nonbillable activities, two are bundled, two are duplicate alerts, one is a missing record, and one is an unsupported existing claim. Thirty reach dispositions. Two stay open. This synthetic cohort tests control logic and arithmetic only. It creates no coding, coverage, authorization, payment, client-balance, refund, recovery, overpayment, accounting, disclosure, or legal conclusion for a real person, provider, payer, claim, contract, or account.

Calculate Yara's measures

Gap-disposition completeness is 30 of 32, or 93.8%. Verified missing-claim incidence is 7 of 30 reviewed gaps, or 23.3%. Gaps, services, records, claims, and dollars remain separate.

Address the main missing-charge detection without schedule substitution risk

A dashboard labeled missed revenue can pressure staff to bill every exception. Ignoring false positives can also hide integration failures that deserve repair.

Test the charge-gap exception ledger against exceptions

Yara tests interface lag, late note, missing claim, cancellation, nonbillable work, bundled service, duplicate alert, payer hold, unsupported claim, and clock expiry. Each fixture retains source version, expected state, actual state, affected unit, safeguard, owner, repair, retest, and disposition. Failed, unknown, quarantined, pending, excluded, and held items remain in the predeclared cohort.

Document the stop condition

Block automatic claim creation and unsupported expected revenue when service, record, billability, payer, or timing evidence is incomplete.

Hand off open work with evidence

Yara's handoff includes the gap source, waiting-window result, service and record evidence, claim search, disposition, estimate basis, filing clock, and owner.

Communicate the current state accurately

Reports use potential gap until review confirms a missing claim. Clinician questions identify exact evidence without presenting the schedule as truth.

Verify Yara's acceptance evidence

A reviewer selects each disposition and reconstructs it from both comparisons. The ledger must also expose claims that lack a supporting service record.

Maintain Yara's control over time

Yara recalibrates latency rules after integration changes and retains before-and-after false-positive rates. Rule changes receive fixtures and rollback.

Monitor Yara's operational results

Monthly analysis separates workflow delay, system delay, true missing claims, valid exclusions, and unsupported claims. Counts are segmented by service date and maturity. The practice pairs completeness with claim quality, client impact, staff burden, and filing risk so reducing one gap category does not create another hidden defect.

Build the detector from comparisons, never from a billing instruction. A schedule-to-record mismatch signals that staff must determine what happened. A completed-record-to-claim mismatch signals that a qualified billing reviewer must determine whether a claim is due. The queue should retain canceled visits, incomplete records, nonbillable services, already bundled work, coordination-of-benefits holds, and true omissions as distinct outcomes. That structure lets the practice calculate detection precision and missed-charge recovery without using appointment status as evidence that a reimbursable service occurred.

Run Yara's independent review

Yara assigns a reviewer who did not build the charge-gap exception ledger. The reviewer reconstructs the missing-charge detection without schedule substitution source, state, calculation, money movement, action, and close. Earlier versions, failed tests, unknowns, credits, exclusions, pending items, and holds remain available. Hidden exceptions, missing authority, unexplained amounts, overwritten history, or unsupported financial action fail review.

Anchor released claims to the adopted standard

Current 45 CFR 162.1102 identifies the adopted professional-claim standard. Yara preserves exact service and claim identities throughout the charge-gap exception ledger. A financial estimate, schedule, or rate table never substitutes for the transaction or source record.

Separate front-end claims evidence from adjudication

The CMS electronic-claims page describes a Medicare route with batch and claim edits. The CMS remittance page separates claim, line, provider adjustment, and payment information. Yara keeps those Medicare examples scoped while verifying each payer's current route for missing-charge detection without schedule substitution.

Use fee schedules within their stated scope

The CMS PFS overview says its tool provides Medicare payment information and directs users to the MAC for official definitive files. The 2026 national payment file page exposes versioned Medicare files. Yara does not treat either source as a commercial contract or universal ABA rate.

Keep credit-balance pathways program-specific

The CMS-838 instructions define a Medicare credit-balance reporting mechanism and explicitly distinguish amounts due to Medicare, another insurer, or a patient. Yara uses that lesson to classify recipients while verifying actual entity, program, payer, contract, state, and account duties.

Escalate potential overpayments through current authority

Current 42 CFR 401.305 governs specified Medicare overpayments and includes identification, investigation, deadline, reporting, and lookback provisions. Yara does not generalize that rule to every credit, refund, payer, or client account and routes legal conclusions to qualified owners.

Interpret adjustment codes with the complete remittance

The X12 external-code-list index defines code-list scopes. Yara reads group codes, CARCs, RARCs, provider adjustments, and payment evidence with the full claim and payer context before deciding missing-charge detection without schedule substitution.

Protect payment and account information

HHS payment guidance and minimum-necessary guidance apply when their HIPAA conditions are met. Yara limits access and disclosure to the approved purpose and recipient while preserving evidence for the charge-gap exception ledger.

Keep clinical and compliance authority visible

The CASP public summary and BACB Ethics Code retain their stated scopes. The voluntary OIG GCPG is a compliance framework rather than a payer or accounting rule. Yara keeps clinical, billing, contract, payer, accounting, privacy, compliance, and legal decisions with qualified owners.

Related resources

• Investigate an ABA Payer Underpayment.
• Prevent Canceled or Unperformed ABA Visits From Becoming Claims.
• Build an ABA Contract Rate Version Register.
• Investigate an Unbilled ABA Service Without Auto-Creating a Claim.

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, Electronic Health Care Claims.
• Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice.
• Centers for Medicare and Medicaid Services, Physician Fee Schedule Look-up Tool Overview.
• Centers for Medicare and Medicaid Services, Physician Fee Schedule National Payment Amount File.
• Centers for Medicare and Medicaid Services, Medicare Credit Balance Report, Form CMS-838 instructions.
• Electronic Code of Federal Regulations, 42 CFR 401.305, reporting and returning overpayments.
• X12, External Code Lists.
• 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.