30-day free trial with no obligation 90-day money-back guarantee on RCM Free practice audit — call 630-708-0271

EOB vs. ERA: what's the difference?

Two documents explain how your claims were paid — one written for patients, one built for your practice. Here's how EOBs and ERAs differ, and why ERAs matter for cash flow.

EOB and ERA, defined

Both an EOB and an ERA explain the same event — how a payer processed a claim — but they're written for different audiences and used in different ways.

  • EOB (Explanation of Benefits) is the human-readable statement a health plan sends to the patient after a claim is processed. It shows what was billed, what the plan allowed and paid, and what the patient may owe. In bold letters it usually says “This is not a bill.”
  • ERA (Electronic Remittance Advice) is the electronic remittance a payer sends to the provider. It's the standardized HIPAA 835 transaction, designed to be read by software and posted automatically into your practice-management or billing system.

Put simply: the EOB explains the claim to the patient; the ERA explains the same claim to your billing team — in a format a computer can post.

The core difference: audience and format

The distinction comes down to who receives it and what form it takes. An EOB is a document (often mailed, sometimes viewable in the member portal) meant for a person to read. An ERA is a structured data file delivered electronically through a clearinghouse or payer portal, meant for a system to consume.

Because the ERA is standardized, your software can match each line to the right claim and patient, post the payment and adjustments, and flag anything that didn't pay in full — without someone keying it in by hand. That's the practical reason practices care about the difference.

What's on them (the fields that matter)

Whether you're reading a patient's EOB or working an ERA, the same key figures appear for each service line:

  • Billed amount — what the provider charged.
  • Allowed amount — the contracted rate the payer recognizes for that service.
  • Paid amount — what the plan actually paid.
  • Patient responsibility — copay, coinsurance and deductible amounts the patient owes.
  • Adjustments and reason codes — why the paid amount differs from the billed amount, expressed as CARCs (Claim Adjustment Reason Codes) and RARCs (Remittance Advice Remark Codes).

Those reason codes are where denials and underpayments hide. Reading them correctly is the difference between catching an underpayment and quietly writing it off.

Why ERAs matter for your practice

Moving from paper EOBs to ERAs isn't just tidier — it changes how fast and how accurately you get paid:

  • Auto-posting. Payments and adjustments post to the right accounts automatically, cutting manual data entry and the errors that come with it.
  • Faster reconciliation. ERAs arrive electronically, often days before a paper EOB would, so your books close sooner.
  • Denial and underpayment visibility. Because every reason code is captured as data, denials and short-pays surface immediately instead of being buried in a stack of paper.
  • Cleaner reporting. Structured remittance data feeds accurate A/R, denial and collections reporting.

ERA, EFT and the 835: how they fit together

Three terms travel together and are easy to confuse:

  • The ERA (835) is the explanation — how the claim was paid and adjusted.
  • The EFT (electronic funds transfer) is the money — the deposit of the actual payment into your bank account.
  • The EOB is the patient-facing version of that same explanation.

Providers usually enroll in ERA and EFT together with each payer. A crucial back-office step is reconciling the ERA against the EFT deposit so the remittance and the money agree. When they don't, that's a signal to investigate — a missing payment, a takeback, or a posting error.

Common points of confusion

A few things trip practices and patients up:

  • An EOB is not a bill. It shows estimated patient responsibility; the actual bill comes from the provider.
  • The numbers should tie out, but the audiences differ. The patient's EOB and your ERA describe the same adjudication — one just isn't machine-readable.
  • “Why doesn't the deposit match the remit?” Because one ERA can span many claims, and one EFT can bundle several ERAs. Reconciliation is what makes it all line up.

If you want the bigger picture of where these documents sit in the workflow, see our walkthrough of the medical billing process, step by step.

How Synergy uses ERAs

Synergy posts payments from ERAs and reconciles them against EFT deposits, targeting 99% posting accuracy so the numbers you act on are correct. Because we capture every reason code as data, denials and underpayments surface right away — and we work denials within 48 hours rather than letting them age. You see it all in monthly Practice Performance Reports. If your posting is behind or your remits aren't being reconciled, get a free practice audit and we'll show you what's slipping through.


Good to know

Frequently asked questions

What is the difference between an EOB and an ERA?

An EOB (Explanation of Benefits) is the human-readable statement a health plan sends the patient explaining how a claim was processed. An ERA (Electronic Remittance Advice) is the standardized electronic version — the HIPAA 835 transaction — sent to the provider so payments and adjustments can post automatically into the billing system. Same information, different audience and format.

What is the difference between an ERA and an EFT?

An ERA (835) is the electronic explanation of how a claim was paid and adjusted; an EFT (electronic funds transfer) is the actual deposit of the money into the provider's bank account. Practices enroll in both with each payer and reconcile the ERA against the EFT deposit to confirm the remittance and the payment agree.

Start today

Ready to collect more and stress less?

Get a free, no-obligation practice audit and see exactly where your revenue is leaking — and how Synergy plugs it.

No long-term contracts • Cancel anytime with 30 days' notice • HIPAA compliant