Payment Reconciliation: Proving the Cash
Reconciliation asks one question posting is structurally incapable of answering about itself: is anything missing? Posting records the remittances it was given. Only an independent source — the bank — can reveal the ones it never got.
Updated 6 min read
On this page
Key takeaways
- Posting is self-referential. It cannot know about a remittance it never received, so a check on posting's own record proves nothing about completeness.
- The failure it catches is a deposit with no posted remittance: cash in the bank that no claim has been credited for, while those claims still look unpaid.
- The reverse matters too — a posted remittance with no deposit means a payment was explained and never arrived, or arrived reduced by a recoupment.
- Neither failure produces an alarm. The money is there, or the balance is closed, and the ledger looks calm in both cases.
Why this is a control, not a second look
There is a specific reason reconciliation cannot be replaced by posting more carefully, and it is not about diligence. Posting works from remittances. Careful posting means every remittance you received was recorded correctly — and that says nothing whatsoever about a remittance that never arrived, or one that arrived and was set aside.
Checking posting against itself will always come back clean, because it is checking a record against the same source that produced it. Reconciliation compares that record against something posting has no influence over: what the bank actually received. That independence is the entire point — it is what makes it a control rather than a review.
The same reason the acknowledgment step exists
The two exceptions
Because the money and the accounting travel separately — funds by EFT, the explanation by remittance — they can fail to meet in two directions, and the two mean completely different things.
| Exception | What it means | Why nobody notices |
|---|---|---|
| Deposit with no posted remittance | Money is in the account and no claim has been credited. The claims it paid still show as open. | The cash is there, so every check that looks at the bank passes. The A/R is simply wrong, and nothing about being wrong is visible. |
| Posted remittance with no deposit | A payment was explained and did not arrive — or arrived reduced, because a recoupment took part of it against an older claim. | The balance is closed and the claim looks paid. The ledger says the money came in; only the bank disagrees. |
The first is the more damaging, because it compounds. Claims that are already paid keep getting worked: followed up, refiled as duplicates, argued with payers who correctly say they paid, and eventually written off — all of it effort spent on money that was collected weeks ago.
An unposted deposit is worse than an unpaid claim
What makes the match tractable
Matching a deposit to its remittance sounds like a search problem and does not have to be one. Payers place a reassociation identifier on both the funds transfer and the remittance, precisely so the two can be paired mechanically rather than by hunting for an amount that looks about right.
When that identifier is present and used, reconciliation is a lookup. When it is missing, ignored, or the two arrive far enough apart that nobody connects them, it becomes a manual search against amounts and dates — and manual searches against amounts are where deposits stop being matched at all, because the work expands until it is no longer worth doing today.
A mismatch is a question, not a verdict
Why cadence is the whole design
Reconciliation gets harder with age, and not gently. A deposit questioned the week it landed is a quick lookup. The same deposit questioned a quarter later means reconstructing which claims it might have covered, against claims that have since been followed up, possibly refiled, possibly written off — and the people who would have recognized it have moved on to other things.
This is why reconciliation is a scheduled task with an owner rather than a project someone runs when the numbers look strange. By the time the numbers look strange, the cheap version of the work is gone. It is the last step of The Payment Posting Process for exactly that reason: not because it is the least important, but because it is the step that proves the others actually happened.
It also protects the metrics
Common questions
If we post carefully, do we still need to reconcile?
Yes, and careful posting is not a substitute for a specific reason: posting can only account for the remittances it received. Checking posting against itself compares a record with the source that produced it, so it will always come back clean — including when a remittance never arrived at all. Reconciliation compares the record against the bank, which posting has no influence over. The independence is what makes it a control rather than a review.
Which direction of mismatch is more urgent?
A deposit with no posted remittance, without much question. A posted remittance with no deposit is a known gap in a known claim — somebody can go and ask the payer about it. An unposted deposit is money already received against claims that still look open, so it generates work in the wrong direction: those claims get followed up, possibly refiled, argued with a payer who correctly says it paid, and potentially written off. One is a question waiting for an answer; the other is a wrong picture being acted on.
Why is an unposted deposit worse than an unpaid claim?
Because an unpaid claim is a known problem with an owner, and an unposted deposit generates false work. The claims it paid still look open, so they get followed up, potentially refiled as duplicates, argued with a payer who correctly says it already paid, and possibly written off — while a patient may receive a statement for a balance that was settled weeks ago. The practice is not merely out of date; it is acting confidently on a picture that is wrong.
How often should reconciliation happen?
We do not publish an interval, because the right cadence depends on volume and on how many payers and deposit channels are involved. What is not cadence-dependent is the direction of the cost: reconciliation gets sharply harder with age. A deposit questioned the week it lands is a lookup; the same deposit a quarter later means reconstructing which claims it covered, against claims that have since been worked, refiled, or written off. Whatever the cadence, the argument for making it shorter is that the cheap version of the work expires.
Key terms in this article
Defined once, on their own pages.
Continue learning
Where to go next.
The Payment Posting Process
The ordered steps this is the last of.
Underpayments and Overpayments
The variances reconciliation surfaces, and what to do with them.
Days in A/R calculator
The metric an unposted deposit quietly overstates.
Tracking a Claim
The follow-up work an unposted deposit sends chasing money already collected.
Authoritative sources
- X12 — EDI standards (opens in a new tab)
Maintains the 835 remittance transaction and the reassociation identifiers that link a payment to its explanation.
- Centers for Medicare & Medicaid Services (CMS) (opens in a new tab)
Publishes Medicare electronic funds transfer and remittance guidance, including overpayment recovery.
- Healthcare Financial Management Association (HFMA) (opens in a new tab)
Publishes standard definitions for the revenue-cycle metrics computed from posted and reconciled data.