Detect Duplicate ABA Remittance Files and Payment Postings

Define Sandeep's duplicate remittance and posting detection control

Sandeep's register computes several duplicate signals and records their evidence. An exact file hash, repeated control number, repeated payment trace, overlapping claim set, or equal amount can each trigger review, yet no single signal proves every duplicate. Corrected remittances remain distinct versions.

Build the remittance deduplication register

Record sender and receiver; file name; received time; envelope and transaction controls; raw hash; payer; payee; BPR amount; TRN trace; claim count; claim controls; content signature; import batch; prior file; similarity; retransmission flag; correction or reversal evidence; posting entries; deposit; quarantine; owner; decision; reversal; retest; and close. 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 Sandeep's workflow

Sandeep checks file-level identity before parsing, then transaction and claim-level overlap before posting. Exact retransmissions link to the accepted original and stop. Potential corrections proceed to adjudication-state review. Suspected duplicate ledger entries are traced back to raw files and reversed through the approved accounting path.

Assign each decision to the responsible role

A repeated dollar amount can be legitimate, and a new file name can carry identical content. A payer correction may reuse some identifiers while changing adjudication. Deduplication logic organizes evidence; authorized RCM and accounting reviewers decide whether an entry is duplicate and how it is reversed.

Work through Sandeep's fictional example

Sandeep locks 26 fictional incoming ERA files. Nineteen are unique, three are exact retransmissions, two are corrected adjudications, one repeats a trace with different content, and one is imported twice under new names. Twenty-three classify correctly on first pass. Three require manual review; two resolve and one remains quarantined. 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 Sandeep's measures

Initial classification is 23 of 26 files, or 88.5%. Twenty-five reach verified unique, retransmission, correction, duplicate, or final hold, or 96.2%. Files, transactions, claims, payments, imports, and postings remain separate denominators.

Address the main duplicate remittance and posting detection risk

A permissive importer can double claim payments and family credits. An aggressive duplicate filter can discard a valid correction or reversal and leave outdated balances in production.

Test the remittance deduplication register against exceptions

Sandeep tests same hash, renamed file, repeated control, repeated trace, same amount, changed claim set, corrected adjudication, reversal, zero-payment ERA, split file, and repeated manual import. 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

Quarantine when the relationship between prior and incoming remittance cannot be established. Stop automated posting for the affected file while unrelated verified files continue under the release policy.

Hand off open work with evidence

Sandeep's handoff includes both raw files, hashes, controls, traces, content comparison, prior posting, deposit, classification, owner, and next test. The receiver opens each file and confirms the adjudication difference before releasing or discarding it.

Maintain Sandeep's control

Sandeep regression-tests duplicate rules after payer, clearinghouse, parser, storage, or import changes. He reports duplicates and false-positive holds by exposed file population, then samples discarded retransmissions to confirm that no corrected content was lost.

Verify Sandeep's release evidence

The deduplication decision records which keys matched, which content differed, and whether a payment or posting already occurred. Sandeep retains the quarantined file and the accepted original so a later payer correction can be distinguished from an earlier retransmission.

Run Sandeep's independent review

Sandeep assigns a reviewer who did not build the remittance deduplication register. That reviewer reconstructs the duplicate remittance and posting detection 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. Sandeep records the actual payer, product, transaction version, receiver, and service date for the remittance deduplication register.

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. Sandeep 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. Sandeep 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. Sandeep records the trace, amount, payer, payee, bank event, and raw remittance rather than matching the duplicate remittance and posting detection 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. Sandeep retains these scopes in the remittance deduplication register.

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. Sandeep 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. Sandeep keeps clinical authorship, payer adjudication, accounting treatment, privacy access, and legal decisions with their qualified owners throughout the duplicate remittance and posting detection workflow.

Related resources

• Post Paper ABA Remittance Without Losing Source Evidence.
• Reconcile ABA Payer Recoupments and Payment Offsets.
• Validate ABA Remittance Parser and Mapping Changes.
• Post Secondary-Payer ABA Adjudication After Primary Payment.

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.