Quick answer
Reconcile an SNF remittance at service-line, claim and provider levels before matching it to a bank receipt. Preserve the original amounts and adjustment references; a provider-level difference should not be forced onto an arbitrary resident. Check event counts as well as dollars so duplicates, reversals and partial imports cannot disappear inside a balanced net total.
Reconcile five thousand dollars without distorting the accounts
Here is an original fictional posting specimen. Dollar amounts are not Medicare rates. The purpose is to test whether a financial record can explain both adjudication and cash; qualified finance staff determine actual accounting treatment.
| Claim | Submitted charge | Fictional claim-level contractual reduction | Claim payment |
|---|---|---|---|
| A | $3,000 | $500 | $2,500 |
| B | $2,000 | $200 | $1,800 |
| C | $1,000 | $300 | $700 |
| Total | $6,000 | $1,000 | $5,000 |
For this specimen, assume the actual remittance supports all three claim-level contractual reductions and none transfers a balance to the resident. The line and claim detail balances: $6,000 − $1,000 = $5,000.
The same remittance contains a $250 provider-level deduction and a $10 provider-level addition. Therefore:
$5,000 − $250 + $10 = $4,760 expected transfer.
A matching $4,760 bank receipt closes this payment-reference reconciliation only when identity and timing also agree. It does not mean that every underlying issue associated with the provider-level items has been resolved.
CMS payment and remittance guidance explains why these levels must remain distinct. If an employee reduces Claim A's payment to $2,260 to force the deposit total, the bank still matches, but Claim A is understated by $240. A bank-only check would pass the wrong allocation.
Follow the difference to the right evidence
| Observed difference | First inspection | What should remain open |
|---|---|---|
| Claim subtotal differs from remittance detail | Missing lines, duplicate events, wrong claim version | Specific posting discrepancy |
| Claim subtotal matches but transfer differs | Provider-level additions/deductions and payment reference | Unexplained provider item or reference mismatch |
| Transfer amount matches but bank entry is absent | Settlement evidence and timing | Bank reconciliation, not claim adjudication |
| Bank shows $4,710 for the specimen | Reference match, split receipts, fees or other actual evidence | $50 unexplained; no invented balancing allocation |
| Response says pending but no remittance exists | Claim-status stage and response date | Adjudication or follow-up work |
CMS claim-status request and response describes claim-status inquiry channels. A status response is useful for locating work; it is not a substitute for the remittance or bank entry in this bridge.
Keep an unidentified provider adjustment in a separate review register with original reason, reference, entity, period and next action. Requiring a resident identifier for every adjustment invites a false association. A central posting team also needs the correct provider and accounting-entity context; a common bank-import folder does not establish which facility owns an item.
A reversal specimen catches migration errors
Use a second fictional sequence to test reconstruction:
| Event | Amount | Required relationship |
|---|---|---|
| Original posting E1 | + $400 | Original remittance/claim reference |
| Reversal E2 | − $400 | Explicitly reverses E1 |
| Corrected repost E3 | + $350 | Correction evidence and new reference |
| Duplicate import of E1 | $0 additional effect | Attempt retained, original not posted twice |
Expected net is $350, gross positive postings are $750, reversal magnitude is $400, and there are three financial events. A fourth posted event fails even if another error happens to offset it. Importing only one $350 balance passes the net check but fails transaction-history reconstruction.
If historical detail will remain in a controlled archive, state that scope explicitly and test retrieval from the new account. A balance conversion can be acceptable for a reviewed implementation design; it must not be represented as a full event-history conversion.
Release the batch with evidence, not a success message
For the first specimen, compare the original file control totals with posted detail, retained provider-level items and the bank match. A partial import of only Claims A and B produces $4,300 in claim payments, not $5,000. It remains incomplete even if the import job reports success.
A useful batch signoff records the three claim references, $5,000 claim subtotal, the two provider items, $4,760 expected transfer, the matching receipt and any open investigation. On rerun, the financial totals should not double. If a manual correction changes a line, preserve the before/after batch totals and reason.
Resident statements need a separate responsibility review. An unpaid amount or a convenient balancing entry does not establish what a person owes. The completed reconciliation should explain where each dollar belongs before any downstream communication is generated.
Questions & answers
Why can claim payments differ from the bank deposit?
Provider-level additions or deductions can change the net transfer. Reconcile the actual remittance references and bank evidence before changing claim allocations.
What should a duplicate ERA import do?
It should retain the import attempt without adding duplicate financial events. Compare event identity and control totals, not the filename alone.
Is a matching balance enough to approve a migration?
No. Reversal links, source references, gross amounts and event counts must also reconcile. A net-only import can lose the history needed to explain the balance.
Primary sources
Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.