Reconcile Partial, Zero, and Suspended ABA Claim Payments

Define Kiran's partial, zero, and suspended payment states control

Kiran's decision record uses payer-reported state instead of treating every unpaid amount as a denial. A zero-dollar 835 can report final adjudication, reversal, or information. A suspended claim may still await action. A partial payment can contain multiple line outcomes. Each state receives its own clock and owner.

Build the claim payment-state decision record

Record payer and product; claim version; submission and acknowledgment; claim-status response; ERA; claim and line status; billed, allowed, paid, and adjusted amounts; group code; CARC; RARC; PLB; BPR amount; trace; denial; suspension reason; request for information; secondary route; patient responsibility; correction or appeal; recoupment; owner; due date; and final disposition. 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 Kiran's workflow

Kiran starts from the latest authenticated payer artifact and compares it with earlier responses. He assigns a state at claim and line level, checks whether money was expected, and identifies the source-directed next action. Status inquiries, corrected claims, appeals, records, secondary claims, and treasury research remain separate routes with separate evidence.

Keep decision rights with qualified owners

A zero payment does not always mean denial, and an accepted claim does not mean adjudication or payment. A partial payment does not authorize collection of the remaining amount. A suspense message does not establish that no action is due. The payer, contract, program, and deadline sources determine follow-up.

Work through Kiran's fictional example

Kiran reviews 25 fictional claim episodes: eight paid in full, six partially paid, four zero-payment adjudications, three suspended, two provider-level offsets, one missing deposit, and one rejected before adjudication. Seventeen have correct states and routes on first review. Six repair. Two remain escalated. 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 Kiran's measures

Initial state accuracy is 17 of 25 episodes, or 68.0%. Twenty-three reach a verified next action or final disposition, or 92.0%. Episodes, claims, lines, payer artifacts, dollars, deposits, and tasks stay separate.

Address the main partial, zero, and suspended payment states risk

A single unpaid work queue can send a suspended claim into appeal, a zero-dollar informational remittance into rebilling, or a provider-level offset into a family balance. Each mistake creates additional transactions and obscures the original state.

Test the claim payment-state decision record against exceptions

Kiran tests zero-payment ERA, partial line payment, suspended claim, records request, provider-level offset, reversal, recoupment, missing EFT, secondary payer, patient responsibility, pre-adjudication rejection, and conflicting portal state. 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 outbound action when the latest payer artifact, claim version, adjustment level, payment expectation, deadline, or route is unclear. Preserve all states and ask the payer or trading partner for written clarification when available rather than repeatedly resubmitting.

Hand off open work clearly

Kiran's handoff names the claim and line states, evidence time, money expected, remittance or status codes, open question, route, deadline, owner, and next verification. The receiver confirms the artifact and avoids changing patient or ledger balances until the selected route supplies sufficient evidence.

Maintain Kiran's control over time

Kiran samples partial, zero, suspended, offset, and missing-payment cases after payer or system changes. He compares portal, 277, ERA, and bank states, records resolution time from defined events, and keeps pending cases visible. Repeated state mismatches trigger an interface or payer-rule investigation.

Run Kiran's independent check

Kiran assigns a reviewer who did not build the claim payment-state decision record. The reviewer reconstructs the partial, zero, and suspended payment states 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. Kiran checks the actual transaction, service date, payer, product, and receiver before applying any partial, zero, and suspended payment states 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. Kiran records which source and receiver produced each state in the claim payment-state decision record.

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. Kiran 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. Kiran uses trace, amount, payee, date, and bank evidence for the claim payment-state decision record.

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. Kiran 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. Kiran records entity status, purpose, recipient, workforce role, and scoped data access for the claim payment-state decision record, 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. Kiran uses these sources for control design without presenting them as a universal partial, zero, and suspended payment states mandate or payment guarantee.

Related resources

• Age Open ABA Claims Without Hiding Holds or Appeals.
• Build an ABA Payment-Posting Exception Queue.
• Reopen a Closed ABA Claim When New Evidence Arrives.
• Validate Patient Responsibility Before an ABA Statement.

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.