Payment posting

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Posting connects remittance, cash, and claim records

The required CMS electronic billing page is Medicare fee-for-service-specific. Broader CMS EFT and ERA guidance distinguishes the transactions: EFT orders a funds transfer, ERA explains claim adjudication, and payment posting applies remittance results to billing records and matches related funds when any exist. Practices also call it cash posting or remittance posting, although cash posting can understate zero-payment work.

X12's 835 description says an 835 can carry a payment, remittance advice, or both. Keep four layers distinct:

• deposit or check evidence
• the immutable X12 835 file, paper remittance, or payer report
• claim, service-line, patient-account, and A/R subledger entries
• any accountant-approved general-ledger batch

A matched deposit does not show every claim paid, and a zero-payment 835 can still change A/R. General-ledger entries follow separate accounting policy. IRS Publication 538 distinguishes federal tax cash and accrual timing; the remittance neither selects a tax method nor dictates general-ledger treatment.

Give each payment, adjudication, and recovery state its own rule

Use approved rules for:

• payer payment or partial payment
• contractual adjustment supported by the applicable agreement
• patient responsibility held for billing review
• zero-payment adjudication awaiting classification
• denial or noncovered result after full code and payer-policy review
• payer-reported provider-level withholding, interest, offset, or recoupment
• provider refund or repayment supported by approved disbursement evidence
• reversal or correction linked to the prior entry
• secondary-payer or coordination-of-benefits state
• unidentified cash, unmatched remittance, variance, or duplicate transaction

Each rule records source fields, subledger effect, queue, approver, and exception. Retain the payer code and internal reason. Never merge zero payment with denial, contractual adjustment, patient responsibility, or discretionary write-off. Posting staff apply rules and route exceptions; RCM approves write-offs and balance transfers, treasury reconciles deposits, accounting controls GL entries, and a designated compliance or legal reviewer confirms the authorized overpayment or refund route.

The CMS EFT and ERA operating-rules page explains that CARCs and RARCs communicate adjustments across health plans. Read the complete claim or line code combination with the contract and payer policy; no single code alone authorizes a write-off or patient bill.

Reassociate funds before closing the batch

For ACH health-care EFTs, the CMS reassociation guide says payment initiation and the associated ERA use matching TRN data and may arrive separately. HHS has not standardized the provider's bank deposit notification, so the practice may need data from its bank. Checks and other methods use applicable remittance and check identifiers, not an assumed ACH TRN.

Before closing a posting batch, confirm:

• payment evidence and remittance agree on payer, payee, method, amount, date, and unique identifier
• each claim and service line maps once to the correct claim version
• each provider-level adjustment has a code, sign, reason, and approved destination
• claim amounts satisfy applicable balancing rules, and claim payments plus signed provider-level adjustments equal the transaction net
• reversals and corrections link to prior entries rather than overwrite them
• every exception has an owner and due date
• the billing subledger reconciles to the remittance, payment evidence to the transaction net, and any general-ledger batch to both under accountant-approved rules

For Medicare, the current CMS payment-and-remittance page says one check or EFT represents benefits for claims itemized in the ERA or standard paper remittance. Treat that as a Medicare example rather than a universal payer batching rule.

Automation should propose reversible entries

Auto-post only when the payer, payee, remittance control, applicable claim, line, or provider-level adjustment, amount, trace, and approved subledger rule match. Route ambiguous patient responsibility, unknown codes, negative balances, duplicates, recoupments, offsets, reversals, and variances.

Keep the immutable raw source, transaction identifier, proposed, approved, and reversed states, rule version, operator, approver, timestamps, balances, and reversal link. A reviewer must reconstruct each change from the remittance and, when payment exists, deposit evidence. Posting staff should not approve their own manual write-off or refund where role separation is feasible.

Clinical records remain under the authorized clinical correction process. Posting staff can flag an apparent conflict; they should not change service times, providers, units, goals, or clinical content to make a remittance fit.

A 24-outcome example separates gross and net payment

A fictional ERA contains 24 outcomes: 23 current-claim adjudications and one $500 recoupment tied to a prior claim. Of the current claims, 19 paid $17,200, two partially paid $900, and two were denied at $0. Gross positive payment is $17,200 + $900 = $18,100; net remittance payment is $18,100 - $500 = $17,600.

The system proposes 21 positive-payment entries, a reviewer links the recoupment, and two denials receive zero-payment entries and tasks. Outcome disposition completeness is 24/24 = 100%. Positive-payment rate among current claims is 21/23 = 91.3%; the prior-claim recoupment is outside that denominator.

Reassociation requires the correct payee and TRN plus a zero amount difference: $17,600 - $17,600 = $0. The example omits billed, allowed, patient-responsibility, and contractual-adjustment detail, so it tests net cash and routing, not full claim or line balance. It cannot establish whether the recoupment is correct, a denial should be appealed, or a patient may be billed.

Potential overpayments need qualified routing

A duplicate payment or credit balance triggers review; it is not a final overpayment conclusion. 42 CFR 401.301 limits this subpart to Medicare Part A and Part B providers and suppliers. Section 401.305 uses the federal "knowingly" standard and sets timing, suspension, contractor-reporting, and six-year-lookback rules. It does not govern Medicaid, Medicare Advantage, Part D, or commercial payers; verify each program and contract.

A payer recoupment or offset is not a provider refund. Record a refund only from approved disbursement evidence, and link corrections instead of overwriting entries. Automation may flag facts but should not decide legal identification or disclosure.

Measure completeness and accuracy together

Useful measures include:

• outcome disposition completeness: eligible outcomes posted or routed divided by eligible outcomes on fully ingested remittances, calculated separately for claim, service-line, and provider-level units
• first-pass posting rate: outcomes auto-posted and unreversed through the observation window divided by automation-eligible outcomes at the same unit
• reassociation rate: unique payment-remittance matches on payer, payee, amount, and identifier divided by eligible payment-bearing transactions after the wait window
• correction rate: entries reversed or corrected divided by posted entries in a matured cohort
• two aging clocks: remittance receipt to posting or routing, and deposit receipt to application or routing
• denial routing SLA: denied claims with an owned action by due time divided by denied claims requiring action
• unapplied funds: amount and oldest age

Use one unit per ratio; do not mix batches, claims, and lines. Publish the numerator, denominator, period, exclusions, maturity window, source, and owner. Report each adjudication and recovery state separately.