Cash is not posted until it balances.

Module 01 · the diagnosisThe remittance arrived. That is not the same as reconciled.

Electronic remittance is no longer the constraint. Adoption of the ASC X12N 835 across the medical industry reached 89 percent in the 2024 CAQH Index, up one percentage point after a five point jump the year before, with only 5 percent of remittance advice still fully manual. Electronic funds transfer reached 77 percent of medical claim payment, up four points. The files arrive, the money moves, and the standard works.

What has not kept pace is the control layer on top of the file. A remittance that parses is not a remittance that reconciles. The same CAQH Index notes a pattern that anyone who has worked a posting queue will recognise: providers pull the same payment information twice, once through the ERA and again from the plan portal, because the portal view is easier to read. ERA volume rose 9 percent while portal volume fell 27 percent, but the duplication is still there, and duplicate posting is one of the quieter ways a ledger goes out of balance.

The failure mode is rarely dramatic. It is a partial payment absorbed into a contractual write-off. It is a takeback that landed against a claim nobody connected to the payment it recouped. It is $1,400 of unapplied cash that sits in a suspense account because the patient account number on the remit did not match anything, and stays there until a month-end hunt. Each one is small. Together they are the reason the bank statement and the practice management system tell two different stories about the same week.

Adoption figures: 2024 CAQH Index Report, remittance advice and claim payment sections. Auto-post and tolerance figures are ASP-RCM production measurements published on our 835 reconciliation engine and payment posting automation pages.

Module 03 · the matchHeader matching is a rounding error with a business plan.

The single highest leverage change in most posting operations is moving the match from the claim header to the service line. Header matching asks one question: did the paid amount look reasonable against the charged amount. Line matching asks the only question that generates work: for every line we submitted on the 837, what came back on the 835, and does it agree with the contract.

The example below is anonymized from a behavioral health practice. Five lines went out on one claim. At the header the payer reports a charge of $712.00 and a payment of $181.20. A header-level poster records the payment, applies the contractual difference, and closes the claim. Nothing looks wrong, because at the header nothing is visible.

The claim closed at the header is not wrong in a way an auditor would catch. It is wrong in a way that compounds. $103.60 on one claim is noise. The same pattern across a year of behavioral health volume is a measurable share of net revenue, which is why our published measurement puts recoverable underpayment at roughly 1.4 percent of total billed dollars once line-level reconciliation is running. Header-level posting does not find that 1.4 percent because header-level posting cannot see it.

Matching has to be done on the composite key that actually identifies a line: procedure code plus modifiers plus revenue code, with units and date of service as tiebreakers. Modifiers matter because 97153 HM and 97153 HN are different rates under most behavioral health contracts. Units matter because a payer that pays three of four authorized units has short paid, not denied, and short pays carry no reason code to alert anyone.

Module 05 · the PLB segmentThe segment that breaks every naive tie-out.

Ask a posting team why the deposit does not equal the sum of the claim payments and the answer, nine times in ten, is the PLB segment. Provider level adjustments live in Table 3 of the 835. They are not attached to any claim, they can reference a claim from a completely different period, and they are the mechanism by which a payer recoups an old overpayment out of today's money.

The sign convention is where careers go quietly wrong. In X12 syntax, a positive PLB amount reduces the payment to the provider and a negative PLB amount increases it. That reads backwards to anyone with an accounting background, where a positive number usually means more money. A team that posts PLB with the intuitive sign will produce a tie-out that is off by exactly twice the adjustment, every time, and will spend a week looking for a $1,548.58 error that is really a $774.29 error doubled.

Two PLB codes deserve standing procedures rather than case-by-case judgment. WO, overpayment recovery, is the payer taking money back, and it must be tied to the original payment before it is posted, otherwise the recouped claim silently returns to open AR with no explanation attached. FB, forwarding balance, is the payer carrying an amount into the next remittance, and it must be tracked as a receivable against that future file, otherwise it looks like a permanent loss and gets written off.

PLB03-1 provider adjustment identifier values per the ASC X12N 835 TR3, 005010X221A1. Posting actions are ASP-RCM standing procedures, not regulatory requirements. Sign convention: a positive PLB amount decreases the payment, a negative amount increases it.

Module 08 · the back endA credit balance is not a reserve.

Overpayments accumulate in every operation. Coordination of benefits pays twice, a patient prepays and insurance then pays, a payer reprocesses without recouping. The dollars sit as credit balances, and because they look like a cushion on the balance sheet, they are the single most commonly neglected item in payment posting. They are not a cushion. They are somebody else's money, and the clock on returning it is legal, not managerial.

For Medicare, section 1128J(d) of the Social Security Act, added by section 6402(a) of the Affordable Care Act and implemented for Parts A and B at 42 CFR 401.305, requires an identified overpayment to be reported and returned within 60 days of identification. Retaining it past that window can create False Claims Act exposure, which is why the 60 day clock is a compliance control and not an AR metric.

Patient credit balances follow a different path with the same urgency. A credit the patient is owed must be refunded, and where the patient cannot be located, the balance eventually escheats to the state as unclaimed property under that state's dormancy rules. Two practices cause the most damage here. The first is netting, using a patient credit on one account to quietly offset a debit on another, which destroys the audit trail and can convert an ordinary refund obligation into a finding. The second is aging without classification, letting a credit sit for a year before anyone asks whether it belongs to a payer, a patient, or nobody because the posting was wrong in the first place.

The clean operating rule is that every credit balance is classified within fifteen days of appearing and dispositioned within thirty. Classification is the hard part and it is cheap only when done early, because it depends on remittance detail, deposit records, and patient statements that are all easier to retrieve in the same month they were created. That is the connection back to Module 04: an operation running a daily three-point tie-out generates credit balance detection as a by-product, while an operation reconciling monthly discovers credit balances as an archaeology project.

Sources: section 6402(a) of the Affordable Care Act adding section 1128J(d) to the Social Security Act; 42 CFR 401.305, reporting and returning of overpayments; CMS Medicare Financial Management Manual, chapter 12, credit balance report activities. This is operational guidance, not legal advice; confirm state unclaimed property obligations with counsel.