Investigate Unapplied ABA Payer Cash

Define Hana's unapplied payer cash investigation control

Hana's trace file keeps money movement separate from remittance meaning. One deposit may cover several remittances, and one remittance may settle many claims. A claim payment can also be offset by provider-level adjustments.

Build the unapplied cash trace file

Record bank account; deposit date; amount; sender; trace number; EFT; ERA or other remittance; payer and product; entity; tax and NPI configuration; claim and line; adjustment; recoupment; client; applied amount; unapplied remainder; communication; hold account; authority; owner; and close. Structured fields preserve identity, source, version, authority, state, clock, 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 Hana's workflow

Hana confirms the deposit, searches remittance and payer evidence, matches stable identifiers and totals, then allocates only supported amounts. Treasury owns bank facts, billing interprets remittance and claim links, accounting owns ledger treatment, and privacy staff govern disclosure routes.

Assign each decision to its proper authority

A payer name in bank text is a clue. It does not prove the affected client, claim, legal entity, overpayment, or refund recipient. A matching dollar amount also needs transaction evidence.

Work through Hana's fictional example

Hana investigates a fictional 18,450 dollar deposit. One ERA supports 16 claims totaling 17,900 dollars and includes a 250 dollar provider adjustment. A second 300 dollar amount lacks a matched remittance. The supported application is 17,900 dollars to claims plus the separately classified 250 dollar adjustment; 300 dollars remains unapplied with an owner and payer inquiry. This synthetic scenario tests control logic and arithmetic only. It creates no coding, coverage, authorization, payment, client-balance, refund, reserve, accounting, disclosure, contract, or legal conclusion for a real person, provider, payer, claim, or entity.

Calculate Hana's measures

Amount reconciliation is 18,150 of 18,450 dollars, or 98.4%. Claim matching is 16 of 16 ERA claims. The 300 dollar remainder stays in the denominator until supported application, return, transfer, or other approved disposition.

Address the main unapplied payer cash investigation risk

Applying cash to the oldest balance can change the wrong client's account and conceal an overpayment. Returning money to an unverified destination creates fraud and privacy risk.

Test the unapplied cash trace file against exceptions

Hana tests single EFT and ERA, one EFT with multiple remittances, missing ERA, split deposit, provider adjustment, recoupment offset, wrong entity, duplicate payment, client payment mislabeled as payer cash, and returned funds. Every fixture retains the 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

Hold application or refund when sender, entity, amount, remittance, claim, recipient, or authority remains uncertain. Escalate suspected overpayment and fraud indicators through the current process.

Hand off open work with evidence

Hana's handoff provides bank evidence, safe sender details, trace identifiers, remittance search, candidate claims, reconciled amount, unapplied remainder, approved outreach, owner, and next review date.

Communicate the current state accurately

Payer inquiries use verified channels and the minimum information needed for tracing. Internal reports distinguish received, identified, remitted, applied, deposited, refunded, transferred, and unresolved money.

Verify Hana's acceptance evidence

A reviewer starts with the bank deposit and independently reaches the same remittance, claim, adjustment, and remainder results. Every posting and return links to authorization.

Maintain Hana's control over time

Hana reviews unapplied cash daily or at the risk-based cadence and tests bank, clearinghouse, ERA, and ledger integrations after change. Aging never substitutes for evidence.

Monitor Hana's operational results

Report count and dollars by age, payer, entity, missing artifact, root cause, resolution type, and recurrence. Track time from deposit to identification and from identification to final ledger application as separate durations.

Make the unapplied cash trace file implementation-ready

Create a suspense route that preserves the original deposit and prevents unverified client statements or collection actions. Reconcile at three levels: bank deposit to EFT, EFT to remittance, and remittance to claims plus provider adjustments. Store the expected amount at every level. If the payer sends replacement remittance evidence, retain both versions and record which one controls the final posting.

Run Hana's independent review

Hana assigns a reviewer who did not build the unapplied cash trace file. The reviewer reconstructs the unapplied payer cash investigation source, state, calculation, money movement, action, and close. Earlier versions, failed tests, unknowns, credits, exclusions, pending items, and holds remain available. Missing authority, unexplained amounts, overwritten history, concealed exceptions, or unsupported action fail review.

Anchor claim transactions to the adopted standard

Current 45 CFR 162.1102 identifies the adopted professional-claim standard. Hana preserves the relevant claim identities and versions throughout the unapplied cash trace file. Internal financial, migration, or ownership labels never replace the actual transaction and source evidence.

Separate claim processing, remittance, and money

The CMS electronic-claims page illustrates front-end Medicare claim processing, while the CMS remittance page separates claim, line, adjustment, and payment information. Hana uses those examples within their scope and verifies every payer's current route before deciding unapplied payer cash investigation.

Use published rates 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 provides versioned Medicare files. Hana does not treat either source as a commercial contract, accounting rule, or universal ABA rate.

Classify credit recipients before financial action

The CMS-838 instructions define a Medicare credit-balance reporting mechanism and distinguish amounts due to Medicare, another insurer, or a patient. Hana carries that classification discipline into the unapplied cash trace file while verifying the actual program, contract, entity, state, recipient, and accounting 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. Hana keeps that Medicare scope visible and routes other payer, client, credit, refund, and accounting conclusions through their own controlling sources.

Interpret adjustment codes with complete context

The X12 external-code-list index defines code-list scopes. Hana reads group codes, CARCs, RARCs, provider adjustments, payer messages, claim history, and payment evidence together before assigning a financial or operational meaning in the unapplied cash trace file.

Protect payment and account information

HHS payment guidance and minimum-necessary guidance apply when their HIPAA conditions are met. Hana limits access and disclosure to approved purposes and recipients while preserving the evidence needed for unapplied payer cash investigation.

Keep professional and compliance authority visible

The CASP public summary and BACB Ethics Code retain their stated scopes. The voluntary OIG GCPG supplies a compliance framework rather than a payer, contract, coding, or accounting rule. Hana routes clinical, billing, payer, finance, privacy, compliance, and legal decisions to qualified owners.

Related resources

• Resolve Small ABA Claim Balances Without Hiding Root Causes.
• Build an ABA Contract Variance Reserve Without Hiding Claim Work.
• Preserve ABA Claim Evidence During a Billing System Migration.
• Reconcile ABA Accounts Receivable to the General Ledger.

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.