EOB vs. ERA

An Explanation of Benefits goes to the patient; an Electronic Remittance Advice goes to the provider. They describe the same adjudication — the same claim, the same allowed amount, the same split between plan and patient — but they are written for different audiences, delivered on different documents, and used for different jobs. Confusing them is mostly a matter of expecting one to do the other's work.

Updated July 20, 20267 min read

On this page

Key takeaways

The EOB is patient-facing. It explains to the member what was billed, what the plan allowed, what the plan paid, and what they owe — and it is not a bill.
The ERA is provider-facing. It is the electronic transaction a billing system reads to post payment, with the claim- and line-level detail that requires.
Both describe the same adjudication. The payer decided the claim once; the EOB and the ERA are two renderings of that one decision for two audiences.
The ERA drives payment posting; the EOB answers patient questions. A practice that cannot reconcile the two cannot post its own payments or explain a patient's balance.

What an EOB is

An Explanation of Benefits is the document a health plan sends to its member after a claim has been processed. It is written for the person who received the care, not the practice that billed for it, and its job is to explain — in the member's terms — what the plan did with the claim and what, if anything, the member now owes.

A typical EOB shows what the provider billed, the allowed amount the plan recognized, the contractual adjustment written off, the plan's payment, and the patient responsibility — the deductible, copay, or coinsurance the member owes as their cost sharing. It may also show why something was not paid, in language aimed at a member rather than a biller.

An EOB is not a bill

The line that causes the most confusion is the one a patient reads as “you owe.” The EOB states a patient responsibility; it does not collect it. The provider's own statement — the bill — arrives separately, and is built from the practice's records of what was posted, not from the EOB the patient happens to be holding. Medicare calls its version a Medicare Summary Notice, or MSN; reading one is covered in Reading the Medicare Remittance and MSN.

What an ERA is

An Electronic Remittance Advice — the remittance advice a provider actually uses — is the transaction a payer sends to the practice to explain how one or more claims were adjudicated and paid. In the United States it is almost always the X12 835 transaction, delivered electronically, with or shortly before the payment it describes.

Where the EOB summarizes for a member, the ERA itemizes for a billing system. It carries claim-level and line-level detail — the plan payment, every adjustment and its reason code, the patient responsibility transferred back to the provider, and whether each service line was paid, reduced, or denied. That detail is what makes automated payment posting possible at all.

The ERA is the input to posting

Payment posting reads the ERA, not the EOB. The 835's structured adjustments and reason codes are what let a billing system match a payment to the right claim, apply the contractual adjustment, and leave the correct patient balance — and flag anything that did not pay as expected for follow-up. How that mechanical step works is the subject of How Payment Posting Works.

The same adjudication, two documents

The thing to hold onto is that the payer decided the claim once. There was one adjudication — one comparison of the claim to the member's benefits, the provider's contract, and the plan's edits — and it produced one set of numbers. The EOB and the ERA are two renderings of that one decision, aimed at the two parties who need to see it.

The same adjudication, rendered for two audiences. The numbers underneath are the same; the document each party receives is not.

The same adjudication, rendered for two audiences. The numbers underneath are the same; the document each party receives is not.
Dimension	EOB (to the patient)	ERA (to the provider)
Audience	The member, or the patient who received the care.	The provider or billing entity that submitted the claim.
What it explains	How the claim was processed for the member — what was allowed, what the plan paid, what the member owes.	How the claim was adjudicated and paid — the plan payment, adjustments, reason codes, and patient balance transferred back.
Delivery	Mail or the member portal, on the member's schedule.	An electronic transaction (the X12 835), received with or shortly before the payment.
Level of detail	Summary, member-friendly, one claim per page or row.	Claim- and service-line-level, with adjustment and denial reason codes a system can act on.
Primary use	Explains the member's responsibility and answers their questions.	Drives payment posting and flags claims for follow-up.

Read the last row as the practical summary. The EOB is an explanation a person reads; the ERA is a transaction a system reads. A practice that treats the EOB as its posting source — or the ERA as its patient-facing statement — is using the wrong document for the job, and the two are not interchangeable.

The numbers should agree because they come from the same decision. The allowed amount, the contractual adjustment, the plan payment, and the patient responsibility on a correctly posted claim should match what the member sees on their EOB for the same service. When they do not, one of the two documents has been read wrong, posted wrong, or describes a different adjudication than the practice thinks it does — and that is worth finding before the patient calls about it.

Using them together

The two documents are for different jobs, and a working practice uses both. The ERA is the operational source: it is what gets posted, what flags a denial for follow-up, and what feeds the reconciliation between what was submitted and what was collected. The EOB is the explanatory source: it is what the patient is looking at when they call, and what their question is usually about.

Which is why the right answer to a patient who calls about their EOB is almost never read from the EOB itself. The practice's record of that claim is the posted ERA — the authoritative version of what was adjudicated, what was paid, and what the patient actually owes on the practice's books. The EOB the patient holds is one rendering of the same adjudication; the posted ERA is the one the practice has already acted on. A discrepancy between the two is a finding, not a feature, and it is resolved by tracing back to the adjudication both describe — which sits inside The Claim Lifecycle.

Don't bill the patient from the EOB

A clean claim that adjudicated correctly produces an EOB and an ERA that agree. If the patient's EOB shows a responsibility different from what the practice posted, do not bill the EOB's figure to close the gap — find out why the two differ first. Billing a number the practice did not post is how a patient gets charged for an adjustment that was already written off, and how a discrepancy that had one cause becomes a dispute that has two.

Common questions

Is an EOB a bill?

No. An Explanation of Benefits states what the plan adjudicated — including the patient responsibility the member owes as their cost sharing — but it does not collect it. The bill, if any, comes separately from the provider, and it is built from the practice's posted records rather than from the EOB the patient is reading. Treating the EOB as a bill is the most common source of patient confusion about what they actually owe.

Does the ERA come with the payment?

Usually together, but not always and not necessarily at the same moment. An electronic remittance advice may arrive with the payment, shortly before it, or shortly after; the relationship between the 835 and the funds transfer is set by the payer and the practice's bank. What is reliable is that the ERA is the document that explains the payment, and posting waits for it rather than guessing from the deposit alone.

Why don't the EOB and ERA always match?

For a correctly adjudicated and posted claim they should match, because they describe the same decision. When they do not, the usual causes are a posting error on the practice's side, an EOB the patient is reading for a different claim or date of service than they think, or — less commonly — a payer processing error. The answer is to trace both back to the underlying adjudication rather than assuming either document is the right one.

What is the X12 835?

It is the electronic remittance advice transaction standard used in the United States — the structured transaction a payer sends a provider to explain how claims were adjudicated and paid. The 835 carries the claim- and line-level detail, including adjustment and denial reason codes, that a billing system reads to post payments automatically. It is the provider-facing counterpart to the patient-facing EOB, for the same adjudication.

Key terms in this article

Defined once, on their own pages.

Continue learning

Where to go next.

Authoritative sources

Centers for Medicare & Medicaid Services (CMS) (opens in a new tab)
Administers Medicare, which issues the Medicare Summary Notice (the EOB equivalent) and the electronic remittance advice, and publishes the X12 835 implementation guidance providers post from.
Healthcare Financial Management Association (HFMA) (opens in a new tab)
Publishes guidance on revenue cycle operations, including payment posting and remittance reconciliation, that reflects how provider finance teams actually use the ERA and EOB together.