ERA, EOB, and EFT: Reconcile the Decision, Posting, and Deposit
Understand ERA versus EOB and EFT, match remittances to deposits, and investigate reversals, adjustments, and unposted balances.
Direct answer
ERA EFT reconciliation: what operators need to know
Understand ERA versus EOB and EFT, match remittances to deposits, and investigate reversals, adjustments, and unposted balances. Do not treat remittance receipt as proof that money reached the bank. Link reversals and corrections to the original event instead of deleting history.
Five recent denials · Drafts back in 7 days · A de-identified worksheet, not the charts
See the workflow: Medical billing workflows.
On this page: Direct answer

An ERA describes payer adjudication in an electronic remittance. An EOB communicates benefit and payment information in the payer's explanation format, often directed to the member. An EFT moves funds. Reconciliation connects the applicable remittance, the practice ledger, and the bank evidence; none should silently stand in for the others.
When expected revenue and collections disagree, start with the path of one payment. Preserve the source files, trace references, posting event, adjustment basis, and deposit match. A large spreadsheet that merges these stages into one 'paid' column can hide where the difference began.
Key takeaways
The short version
- Do not treat remittance receipt as proof that money reached the bank.
- Link reversals and corrections to the original event instead of deleting history.
- Separate contractual adjustments, denials, patient responsibility, and unexplained differences.
- An unresolved reconciliation item needs an owner even when automated posting completed.
Take the template with you
Free to copy · no email required
ERA-to-deposit exception log
A blank exception worksheet for approved internal use.
Process reference,Remittance reference,Payment trace reference,Ledger event,Exception type,Owner,Next check,Reviewed resolution DEMO-001,,,,Unmatched deposit,,,
Saves as era-deposit-reconciliation.csv
Use three records, with one reconciliation owner
The remittance explains the payer decision; the practice-management ledger records how that decision was posted; the bank record establishes the deposit. Define who reconciles across all three. Dividing posting and treasury between teams is workable only if the handoff includes sufficient matching evidence and a clear exception route.
Keep bank-sensitive data and actual remittance records in approved systems. A public template needs only blank fields and fictional references. A reconciliation dashboard should link to controlled evidence rather than become another uncontrolled copy of financial or patient information.
Match trace information before comparing totals
Use the applicable payer, payee, payment method, trace reference, amount, and settlement context to associate remittance and payment. Batch structures vary: a deposit may cover many services, and offsets may explain why expected gross payment differs from the net transfer. Investigate the relationship rather than assuming every remittance has a simple one-to-one match.
A fictional practice receives a remittance showing payment but cannot find the deposit in its expected account. The posting owner should not create a balancing write-off. The next action is to verify payment destination and trace evidence through the approved financial channel, with a dated follow-up.
Read adjustments as explanations requiring a basis
Keep the original adjustment group and reason information alongside the ledger action. A contractual adjustment, a denial, a deductible amount, and an overpayment offset lead to different follow-up. Verify the contract and applicable payer instructions before treating an adjustment as correct or transferring a balance to the patient.
Do not let a generic mapping turn every unfamiliar reason into a write-off. Maintain a reviewed mapping register with a version, effective date, owner, and exception behavior. When the incoming reason or amount does not match the mapping assumptions, route it for review.
Keep original, reversal, and replacement linked
A later remittance may reverse or revise an earlier decision. Preserve all events and identify which ledger entries they changed. Record whether a replacement payment arrived and how any patient balance changed. Deleting the original event makes it harder to explain historical collections, reconcile an auditor's question, or repair an erroneous statement.
For example, a payer reverses a prior payment and issues a corrected remittance with a different responsibility allocation. The case remains open until the posting and deposit effects are understood. 'Replacement received' and 'reconciliation complete' should be separate statuses when money is still unmatched.

Use an exception queue that explains the next action
Useful exception categories include missing remittance, unmatched deposit, remittance not posted, duplicate posting, unsupported adjustment, unexplained offset, and unresolved reversal. Each category should identify the evidence needed, the receiving role, and an internal next check. Avoid a single miscellaneous bucket that cannot be prioritized.
Prioritize by amount at risk, age, deadlines, and impact on patient balances. The daily total of unmatched money is useful, but a row-level explanation matters more than a dashboard number that nobody can resolve. A named reviewer approves material ledger corrections under the organization's financial controls.
Define when the item is actually reconciled
An item is ready to close when the remittance decision, posted entries, and payment evidence agree or a supported exception has been approved and recorded. Retain the reviewer, source references, and remaining dependency if the result is partial. Do not count an item as collected simply because staff finished researching it.
Review recurring differences by payer, payment method, posting rule, and originating system. Fixing a repeated mapping defect can matter more than increasing posting speed. Compare a stable period before and after the change and verify that patient balances did not become less accurate.
Common questions
Answers before you build.
Is an ERA the same as an EFT?
No. An ERA communicates adjudication information; an EFT transfers money. Reassociation connects the related records using applicable trace information and payment context.
Should every adjustment become a write-off?
No. Determine the adjustment's meaning and contractual or other basis. Denials, patient responsibility, offsets, and contractual adjustments require different handling.
How should a corrected payment be recorded?
Keep the original decision, reversal, and replacement linked, then reconcile their ledger and bank effects. The authorized financial owner approves corrections.
Practical closeout
Use this operator checklist.
- Do not treat remittance receipt as proof that money reached the bank.
- Link reversals and corrections to the original event instead of deleting history.
- Separate contractual adjustments, denials, patient responsibility, and unexplained differences.
- An unresolved reconciliation item needs an owner even when automated posting completed.
Continue through the cluster
Verified customer case studies are added only with customer permission and supporting evidence; none is implied by these operational examples.
Sources & methodology
Trace the operational claims.
Marsa Health Editorial reviewed the primary and research sources below on November 5, 2026. We translate them into workflow controls, distinguish proposals from final rules, and flag where plan, program, state, contract, or clinical requirements vary.
- 01Health care payment and remittance advice CMSExplains remittance advice and payment information. A remittance and a bank deposit are different evidence.Accessed or rechecked November 5, 2026
- 02EFT and ERA reassociation basics CMSPrimary background for matching payment and remittance records using trace information.Accessed or rechecked November 5, 2026
- 03HIPAA transactions and code sets CMSTransaction standards background; verify trading-partner implementation and payer-specific requirements.Accessed or rechecked November 5, 2026
- 04Minimum necessary requirement HHSPrivacy guidance with defined scope and exceptions; organizations establish approved information handling.Accessed or rechecked November 5, 2026
Organizational author. Editorial review covers source accuracy, search intent, workflow boundaries, and human-oversight requirements. This material is educational and does not provide clinical, legal, coding, or coverage advice.
No named clinical or legal expert reviewer is attributed to this version. Marsa Health does not invent reviewer credentials.
Read our editorial methodRevision history
What changed and when
November 5, 2026
Initial publication, source review, and operational editing.