Explanation of benefits

An explanation of benefits is the output a member sees after their plan has already decided what to pay — it documents a completed adjudication decision, not a request for money. Every EOB traces back to a specific claim that ran through eligibility, benefit matching, pricing, and cost-sharing, and the EOB is the human-readable record of what happened at each of those steps for that member.

What an EOB actually contains

A complete EOB shows, at minimum: the provider and date of service, what was billed, the plan’s allowed amount (the fee schedule or usual-and-customary rate the claim actually priced against, which is often lower than what was billed), what the plan paid, and what’s left as member responsibility — broken into deductible, coinsurance, copay, and any non-covered amount, each labeled as its own line rather than lumped into one number. A denied or pended line item shows a reason, not just a zero-dollar payment, because a member reading “$0 paid” with no explanation is the single most common driver of an appeal call.

A worked example

A member sees an in-network provider for CPT 99214, billed at $200. The plan’s contracted fee schedule rate for that code is $150 — the allowed amount. The member has already met their deductible and owes 20% coinsurance. The EOB shows:

The member owes $30 — not the $50 gap between billed and allowed, since that’s the provider’s contracted write-off, and not the full $200. An EOB that doesn’t show the allowed amount as its own line leaves a member unable to tell the difference between “the plan negotiated a lower rate” and “the plan is shortchanging me,” which is exactly the confusion an EOB exists to prevent.

Not a bill, and not the 835

Two distinctions matter here, and people conflate both regularly. First: an EOB is not a bill. The provider (or the plan, for member-owed amounts) bills separately; the EOB only explains what was decided. Second, and more specific to how the data actually moves: the EOB is not the same document as the 835 remittance advice, even though both come out of the same adjudication event. The 835 is a standardized X12 EDI transaction that flows from payer to provider, in a structured, machine-readable format built for practice management systems to post automatically. The EOB is the plain-language version that goes to the member. Same underlying payment decision, two different audiences and two different formats — for the full mechanics of the 835 and where it fits with the 837 claim and 834 enrollment transactions, see 834, 835, 837 EDI explained.

Why this matters operationally

An EOB that doesn’t clearly separate allowed amount, plan payment, and member responsibility generates support calls and appeals regardless of whether the underlying adjudication was correct — the document is the member’s only window into a decision they didn’t see happen. A claims adjudication engine that generates the EOB directly from the same pricing and cost-sharing calculation used to adjudicate the claim — rather than a separate system reconstructing it after the fact — keeps the two in sync by construction, which matters for a self-funded employer plan whose members are calling HR, not a claims department, when the numbers don’t add up.

← All glossary terms