Reconcile Returned EFT and Voided Payer Checks for ABA Claims

Define Valerie's returned EFT and voided-check reconciliation control

Valerie's incident record connects treasury evidence with RCM evidence without assuming they change together. It shows whether money settled, was returned, was never deposited, or was replaced, and whether the payer also changed claim adjudication. Each state has its own owner and next action.

Build the returned-payment incident record

Record payer; payee; ERA; BPR; trace or check number; payment date and amount; bank account alias; deposit; return code and date; void or stop notice; replacement payment; related claims; remittance reversal; claim balances; ledger entry; security review; payer contact; owner; deadline; correction; retest; and closure. Structured fields preserve identity, version, source, clock, comparison, access, decision, hold, calculation, correction, retest, and close. Narrative captures clinical meaning, uncertainty, disagreement, family communication, privacy, legal deferral, and the authorized owner's rationale.

Run Valerie's workflow

Valerie authenticates the bank or payer event, confirms the authorized payee account, and locates the exact remittance and claims. Treasury determines cash treatment. RCM checks whether adjudication changed or only payment delivery failed. A replacement receives a new linked payment state and is matched before the incident closes.

Assign each decision to the responsible role

A returned EFT does not necessarily reverse claim adjudication. A remittance reversal does not prove the bank retrieved funds. A voided check can occur before or after deposit. Claims, remittance, payment, deposit, and ledger states must therefore remain separate.

Work through Valerie's fictional example

Valerie reviews 14 fictional incidents: five returned EFTs, four voided checks, three stopped payments, and two replacements. Nine have verified payer, trace, bank state, remittance, claims, ledger treatment, and follow-up. One points to an old account, one lacks a return code, one has no replacement, one includes a reversal, and one check was already deposited. Three repair. Two remain open. This synthetic cohort tests controls and arithmetic only. It creates no coding, coverage, authorization, payment, patient-balance, privacy, accounting, recovery, or legal conclusion for a real person, provider, plan, claim, remittance, or deposit.

Calculate Valerie's measures

Initial incident readiness is 9 of 14 records, or 64.3%. Twelve reach verified cash and claim disposition or documented escalation, or 85.7%. Incidents, payments, deposits, claims, remittances, and dollars remain separate.

Address the main returned EFT and voided-check reconciliation risk

Automatically reopening all claims after a returned payment can create duplicate submissions. Leaving cash posted after a confirmed return overstates assets and can make the practice treat an unavailable balance as collected.

Test the returned-payment incident record against exceptions

Valerie tests invalid account, closed account, payer stop, duplicate replacement, deposited check, remittance reversal, no claim change, wrong payee, bank fee, trace mismatch, and suspected account-change fraud. Each fixture retains source version, expected state, actual state, affected unit, safeguard, owner, repair, retest, and disposition. Failed and held cases remain inside the predeclared cohort.

Document the stop condition

Freeze the affected cash entry and investigate immediately when the payee, account, trace, return, or replacement is unclear. Security owners review unexpected account changes; claims stay on their verified payer path until adjudication evidence changes.

Hand off open work with evidence

Valerie's handoff contains the remittance, payment trace, bank event, claim state, ledger treatment, security finding, payer contact, replacement status, deadline, and owner. The receiver verifies the bank and RCM sides before closure.

Maintain Valerie's control

Valerie reviews returned-payment causes after bank, payer, enrollment, account, or treasury changes. She reconciles all open incidents to cash and claim records and tests replacement-payment matching in each close cycle.

Verify Valerie's release evidence

Valerie closes an incident only after treasury verifies the money state and RCM verifies the adjudication state. A replacement payment receives its own trace and deposit evidence; it never overwrites the returned or voided payment that explains the interruption.

Run Valerie's independent review

Valerie assigns a reviewer who did not build the returned-payment incident record. That reviewer reconstructs the returned EFT and voided-check reconciliation source, state, calculation, decision, entry, and close from retained evidence. Earlier versions, failed tests, and holds remain available. Hidden exceptions, unexplained amounts, overwritten history, missing population, or unauthorized decisions fail review.

Anchor the claim side to the adopted standard

Current 45 CFR 162.1102 identifies the adopted professional-claim standard. CMS's professional-claim page provides Medicare electronic and paper context, and its Medicare FFS companion guides supplement the X12 TR3 only for their named routes. Valerie records the actual payer, product, transaction version, receiver, and service date for the returned-payment incident record.

Use current ERA and EFT distinctions

The CMS ERA and EFT page describes the adopted payment and remittance standards and reassociation through matching TRN content. Medicare's remittance page separates claim, line, and provider-level adjustments. The Medicare EFT page describes direct deposit and bank reconciliation in Medicare scope. Valerie preserves each artifact and level.

Apply reversal and correction guidance precisely

X12 RFI 2060 explains that a standard withdrawal or void of a previously adjudicated claim requires the prior payer control number and that finalized recovery is represented through the 835 reversal-and-correction process. Valerie uses this X12 interpretation for transaction meaning while payer, contract, appeal, refund, and legal decisions remain separate.

Match each 835 to its payment mechanism

X12 RFI 2075 explains the 835 TR3's one-to-one relationship between an 835 and its check or EFT, with a nonpayment 835 as the stated exception. Valerie records the trace, amount, payer, payee, bank event, and raw remittance rather than matching the returned EFT and voided-check reconciliation by amount alone.

Keep PLB and recovery at the right level

X12 RFI 2809 illustrates how a claim reversal and PLB can coexist without a current funds reduction in its specific subrogation scenario. RFI 1324 says PLB reports nonclaim-specific payment adjustments and excludes a zero-dollar PLB. RFI 1114 emphasizes scenario-specific PLB reference instructions. Valerie retains these scopes in the returned-payment incident record.

Preserve payer-order and privacy boundaries

The CMS coordination-of-benefits page describes the covered-entity COB transaction and Version 5010. HHS payment guidance and minimum-necessary guidance govern only when their HIPAA conditions apply. Valerie verifies payer order, entity status, purpose, recipient, and role-based data scope before sharing or using claim information.

Keep clinical and compliance roles scoped

The CASP public summary and BACB Ethics Code provide clinical and covered-professional context without governing every billing transaction. The OIG GCPG is voluntary and nonbinding. Valerie keeps clinical authorship, payer adjudication, accounting treatment, privacy access, and legal decisions with their qualified owners throughout the returned EFT and voided-check reconciliation workflow.

Related resources

• Control Manual ABA Payment-Posting Adjustments and Overrides.
• Validate ABA Remittance Parser and Mapping Changes.
• Build End-to-End ABA 837P-to-835 Traceability.
• Post Paper ABA Remittance Without Losing Source Evidence.

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.
• Centers for Medicare and Medicaid Services, Medicare Fee-for-Service Companion Guides.
• 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 2060, Withdrawal or Void Claim and Response.
• X12, RFI 2075, 835 Relationship to Payment.
• X12, RFI 2809, Subrogation Claim Adjustments on 835.
• X12, RFI 1324, Interest and PLB on 5010 835.
• X12, RFI 1114, 835 PLB Reference IDs.
• Centers for Medicare and Medicaid Services, Coordination of Benefits transaction.
• 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.