Revenue Cycle Management 6 min read
The Deposit Arrived but the Payment Is Still Unposted

The bank shows a payer deposit. The payment-posting queue still shows work waiting for a remittance. An AR colleague opens the payer portal, sees paid, and wonders why the balance remains open.
In this hypothetical example, each person has a useful piece of evidence. Nobody has connected the pieces. A payment can be received while the billing team is still resolving how it belongs in the ledger.
EFT and ERA reconciliation should make that gap visible. The immediate task is to match the funds, the remittance, and the posting record before treating the account as resolved.
Identify the missing part of the payment record
For ACH health care payments, the electronic funds transfer carries the funds and the electronic remittance advice explains the payment. CMS’s payment remittance reassociation guide explains that these transmissions can reach the provider at different times. Reassociation connects the ERA to the payment it describes.
At the start of the review, write down what is actually available: a payer status response, a bank deposit record, an ERA, and a posting batch are different records. A paid status can help direct research, but it does not prove that the deposit has been matched and posted correctly.
This workflow concerns ACH payments and their associated remittances. Use the relevant process for paper checks, virtual cards, zero-payment remittances, or other payment arrangements.
Use the reassociation detail rather than a similar amount
CMS’s EFT and ERA operating-rules guidance explains that the TRN segment in the ACH CCD+ addenda should match the TRN segment in the corresponding ERA. Those matching details support reassociation.
Before comparing references, confirm what each system’s field represents. A bank transaction identifier may not be the same field as the remittance reassociation information. Ask the person responsible for banking access to identify the relevant addenda detail; do not guess from a column labeled reference.
The CMS reassociation guide also explains that providers need to arrange with their financial institutions to receive the required reassociation data. If the bank export omits it, investigate the export or delivery arrangement with the authorized finance contact.
Compare the payer and payee context, the reassociation details, the payment amount, and the relevant dates together. A matching amount alone is a weak basis for a posting decision, especially when several payments have similar values.
Route the exception to the person who can resolve it
Use a small set of internal labels to show which evidence is missing. These are suggested work categories, not official transaction codes.
- Deposit found and ERA missing: check the expected remittance delivery channel, then follow the payer’s missing-ERA process.
- ERA found and deposit not confirmed: ask the authorized finance contact to check the relevant payment record before treating the funds as received.
- Both records found but the match is unclear: compare identifiers and amounts, then route the discrepancy to the appropriate reviewer.
- Matched payment awaiting posting: assign the posting task and confirm the batch result before closing the exception.
Keep the exception open until its specific question has been resolved. A note saying sent to posting does not establish that posting succeeded. Equally, the posting team should not be expected to investigate a bank record it cannot access.
Reconcile differences without forcing the total
For Medicare remittances, CMS’s payment and remittance guidance explains that adjustments can occur at the line, claim, or provider level. Provider-level adjustments can include interest or recovery of a prior overpayment, so a reviewer may need more than the individual claim payment amounts to understand the total.
If the numbers do not reconcile, preserve the unexplained difference and the supporting records. Route it for review under your payment-posting and accounting procedures. Avoid assigning a difference to an unrelated patient account or using an unsupported adjustment simply to balance the batch.
Check for an existing posting before importing a replacement remittance or manually entering a payment. An ERA that was delivered twice should not become two postings. Record what was checked so the next person does not repeat the same investigation.
Make missing-remittance follow-up specific
CMS’s reassociation guide describes written payer procedures for resolving late or missing EFT and ERA transactions. Obtain the applicable instructions and use the correct contact route. Keep the reference supplied by the payer and the expected next action with the exception.
For a billing company, agree in advance who can obtain banking evidence from each client. Give the client a precise request for the payment detail needed, using an approved secure channel. Do not ask colleagues to circulate bank credentials or unrestricted statements just to resolve one payment.
Use a payment exception note that survives handoffs
A concise note can follow this structure. Store actual financial and account identifiers only in the approved system.
- Evidence available: deposit record, ERA, payer response, and any existing posting batch.
- Matching details: payer and payee, reassociation reference, relevant dates, and amount.
- Unresolved question: the exact missing record or unexplained difference.
- Assigned action: the person obtaining the record or reviewing the discrepancy, with a next review date.
- Closure evidence: the verified match, posting reference, and result of the reconciliation review.
A supervisor can review a small sample of unresolved payments each week. Track their age, the amount still awaiting resolution, and the repeated causes. Separate time waiting for an ERA from time waiting for posting; otherwise the same total can hide two different problems. Use consistent definitions when comparing periods.
Connect claim follow-up to payment posting
RCM Edge’s Claim Status Automation can support payer-status research where the required connection and response details are available. Treat a paid response as information for the next team, not evidence that bank reconciliation or posting has been completed. Confirm the current platform scope when evaluating any automation.
The practical improvement is a complete payment handoff. Finance knows which deposit is being researched, posting knows which remittance belongs to it, and AR can see what remains unresolved without starting over.
Sources
- CMS EFT and ERA Payment Remittance Reassociation Basics. June 2022; reviewed October 27, 2026.
- CMS Operating Rules EFT and Remittance Advice. Reviewed October 27, 2026.
- CMS Health Care Payment and Remittance Advice. Reviewed October 27, 2026.
The exception labels, review measures, and handoff note are editorial workflow recommendations. Apply the payer’s instructions and your organization’s accounting controls to the actual payment.

