To audit ABA remittance posting and financial close, lock a complete cohort and trace every submitted claim through payer acknowledgment, adjudication, remittance, posting, payment, deposit, adjustment, patient balance, and exception disposition. Reconcile opening plus activity to the ending ledger, retain unresolved items, and have an independent reviewer reproduce selected ordinary and exception paths. Report counts and dollars with separate denominators.

Define Nadia's remittance posting and financial close control

Nadia's audit file joins operational evidence without collapsing its states. It contains the outbound claim inventory, raw ERAs, payment records, bank evidence, posting batches, adjustments, patient balances, exception queue, journal entries, and close approvals. Each link shows the identifier, version, amount, and owner used.

Build the remittance close audit file

Record audit period and cutoff; entity; payer; opening claims and balances; submissions; acknowledgments; adjudications; ERAs; claims and lines; paid, allowed, adjusted, and patient amounts; PLB; reversals; EFT or check; bank deposits; posting batches; credits; refunds; exceptions; reopenings; ending claims and balances; ledger accounts; access; sample; tester; defect; correction; retest; and close approval. 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 Nadia's workflow

Nadia defines the population before testing, reconciles control totals, and selects risk-based plus random samples. She traces forward from claim to ledger and backward from deposit and balance to source. Every difference receives an exception owner and remains in the close package. Independent review reproduces calculations from raw evidence.

Keep decision rights with qualified owners

A balanced bank account does not prove claim or patient-balance accuracy. A clean posting batch does not prove every expected remittance arrived. Audit evidence can identify a control failure, while qualified clinical, coding, accounting, privacy, payer, and legal owners decide the resulting action.

Work through Nadia's fictional example

Nadia locks a fictional month with 120 first-submitted claims, 112 adjudicated claims, nine ERAs, eight payment mechanisms, and 117 bank or zero-payment dispositions. The file contains six exceptions: two unmatched claims, one PLB variance, one returned EFT, one patient credit error, and one reopened reversal. Four resolve before close. Two carry with approval. 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 Nadia's measures

Adjudication reach is 112 of 120 first submissions, or 93.3%. Payment-or-zero-remittance disposition is 117 of 120 claims, or 97.5%. Exception resolution by close is 4 of 6, or 66.7%. Claims, ERAs, payments, deposits, dollars, exceptions, and journal entries retain separate denominators.

Address the main remittance posting and financial close risk

A close process can force unresolved differences into generic adjustments and erase their operational cause. Sampling only paid claims omits rejections, suspended work, zero-payment adjudications, and missing remittances from the population.

Test the remittance close audit file against exceptions

Nadia tests missing ERA, duplicate posting, wrong claim version, PLB, zero payment, returned EFT, bank fee, patient credit, secondary balance, reversal, reopened claim, stale exception, and unauthorized close entry. 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

Withhold close approval for a material unexplained difference, wrong entity or person, unverified bank change, incomplete population, missing evidence, unauthorized adjustment, or failed retest. Document carried items, risk acceptance authority, restrictions, owner, and due date under the governing policy.

Hand off open work clearly

Nadia's close handoff contains population rules, control totals, samples, raw evidence links, differences, corrected entries, unresolved items, risk decisions, owners, and approvals. The next period receives carried exceptions with their original age and source. Reviewers can reproduce the published metrics without relying on hidden filters.

Maintain Nadia's control over time

Nadia refreshes the audit after payer, bank, clearinghouse, ledger, parser, policy, or organizational changes. Trend review separates claim defects, posting defects, deposit differences, patient-balance issues, and close failures. It records recurrence by exposed workflow version and verifies that corrective actions reduce the identified error in a later locked cohort.

Run Nadia's independent check

Nadia assigns a reviewer who did not build the remittance close audit file. The reviewer reconstructs the remittance posting and financial close 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. Nadia checks the actual transaction, service date, payer, product, and receiver before applying any remittance posting and financial close 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. Nadia records which source and receiver produced each state in the remittance close audit file.

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. Nadia 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. Nadia uses trace, amount, payee, date, and bank evidence for the remittance close audit file.

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. Nadia 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. Nadia records entity status, purpose, recipient, workforce role, and scoped data access for the remittance close audit file, 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. Nadia uses these sources for control design without presenting them as a universal remittance posting and financial close mandate or payment guarantee.

Related resources

Sources