EOBs and ERAs Explained: Making Sense of Your Remittance

When a payer sends money, it also sends a story explaining exactly how it arrived at that number. Learn to read that story and you stop leaving revenue on the table.

A person reviewing financial statements and an insurance remittance document while using a calculator at a desk.
Every remittance is a line-by-line accounting of what the payer allowed, adjusted, and paid.

The check a payer sends rarely matches what you billed, and the difference isn't random. Every payment carries a remittance explaining, line by line, how the payer decided what to pay — in two forms, the EOB and the ERA. This is the exact step where underpayments and quiet denials either get caught or get written off.

EOB vs. ERA: what they are and how they differ

Both answer the same question — "here's what we did with your claim" — but in very different forms.

  • EOB (Explanation of Benefits) is the human-readable version: a paper or PDF statement summarizing how a claim was adjudicated — what was billed, allowed, and paid, and what the patient owes. Patients get their own copy (often stamped "this is not a bill"); the practice receives a provider-facing remittance advice.
  • ERA (Electronic Remittance Advice) is the same information as a structured file on the HIPAA-standard 835 transaction. Built to be read by your billing software, it can post payments automatically and at scale.

In short: an EOB is for reading, an ERA/835 is for processing. Enroll to receive ERAs from every payer that offers them, paired with EFT so the money and the explanation arrive together — paper EOBs should be the exception.

How to read a remittance, field by field

On an EOB or a decoded 835, the same numbers tell the whole story for each service line:

  • Billed (charged) amount — your full fee, exactly as submitted.
  • Allowed amount — the maximum the payer recognizes under your contract; the real ceiling on payment.
  • Contractual adjustment — the write-off between billed and allowed. For in-network claims it's expected and non-collectible. It is not a denial.
  • Patient responsibility — deductible, copay, and coinsurance owed out of the allowed amount.
  • Paid amount — what the payer actually sent: allowed minus patient responsibility and any other valid adjustments.

A quick sanity check: allowed = paid + patient responsibility, and billed = allowed + contractual adjustment. When those don't balance, something was adjusted that warrants a look at the reason codes.

CARC and RARC codes: the "why" behind every adjustment

No payer reduces or denies a line without attaching a reason. On an 835 those reasons are standardized codes, and two families let you triage a remittance fast:

  • CARC — Claim Adjustment Reason Codes say why an amount changed. Routine ones include CO-45 (charge exceeds the allowed amount), PR-1 (deductible), PR-2 (coinsurance), and PR-3 (copay). Problem codes include CO-97 (bundled), CO-16 (claim lacks information), and CO-50 (not medically necessary).
  • RARC — Remittance Advice Remark Codes add detail to a CARC — a missing modifier, an authorization requirement, a timely-filing issue — usually telling you exactly what to fix.
  • Group codes are the CARC prefix: CO (Contractual Obligation) is a write-off you can't bill anyone for, PR (Patient Responsibility) moves the balance to the patient, and OA/PI often flag a second look.

The discipline that protects revenue: never assume a CO adjustment is correct. CO-45 is legitimate only if the allowed amount matches your contracted rate — if the payer "allowed" less, that CO-45 is hiding an underpayment.

How payment posting works — and why accuracy matters

Payment posting records each remittance against the right claim and line — payment, contractual adjustment, patient responsibility, and reason codes. Done well it gives a clean picture of every account; done sloppily it corrupts your receivables file. It matters because posting:

  • Drives patient billing — a wrong patient-responsibility line bills patients for money they don't owe, or misses money they do.
  • Triggers secondary claims — coordination of benefits depends on accurate primary posting.
  • Exposes denials — it turns a zero-pay line with a CO-16 or CO-50 into a workable denial instead of a silent write-off.
  • Keeps your A/R honest — misclassifying a denial as a contractual adjustment makes a problem claim vanish from your aging report, along with its revenue.

Spotting underpayments and contractual adjustments

This is where reading a remittance turns into recovered dollars. A contractual adjustment should bring your charge down to the agreed rate — no more — so verify the allowed amount is correct:

  • Compare allowed vs. contracted rate. Load your fee schedules so software flags any line where the payer allowed less than your contract requires.
  • Watch for silent bundling. A CO-97 that wrongly bundles a separately payable service — often fixable with the right modifier — is lost revenue dressed as routine.
  • Re-check downcoding. If the payer paid a lower-level code than you billed, the allowed amount drops quietly; confirm the adjudicated code matches what you submitted.
  • Track payer patterns. A payer or CPT code that's routinely short is a contract or configuration issue worth escalating.

Caught at posting, an underpayment becomes an appeal or corrected claim. Missed, it's a permanent write-off no one ever sees.

Auto-posting, reconciliation, and the revenue it protects

Because the 835 is structured data, ERAs can post automatically — software matches each line to its claim and records the payment, adjustment, and codes with no keystrokes. That's fast and accurate for clean, full-pay claims, but it's not "set it and forget it":

  • Reconcile the deposit — tie every ERA to its EFT or check so posted dollars equal deposited dollars; short deposits get flagged, not buried.
  • Route exceptions to humans — hold denials, partial payments, and unusual codes for manual review rather than auto-posting them as adjustments.
  • Audit the adjustment rules — auto-posting logic decides which CARCs become write-offs, and a misconfigured rule can write off thousands before anyone notices.

Automation for the routine, human eyes on the exceptions — that's what makes this step both efficient and a real revenue safeguard.

How Bill The Max helps

We treat the remittance as a revenue checkpoint, not a clerical chore. We enroll your practice in ERA and EFT with every payer, post payments accurately, and decode CARC/RARC codes so denials and underpayments surface right away. We load your contracted fee schedules to catch any payer that allows less than it owes, route exceptions to a human reviewer, and reconcile each deposit — so the money you earned is the money you keep.

Key takeaways

  • An EOB is the human-readable explanation of a claim; an ERA (the 835 file) is the same information in machine-readable form for automated posting.
  • Read each line in order — billed, allowed, contractual adjustment, patient responsibility, paid — and make sure the numbers balance.
  • CARC codes explain why an amount changed and RARC codes add detail; the CO/PR/OA group prefix tells you who, if anyone, can be billed.
  • Accurate posting keeps your A/R honest and turns silent zero-pays into workable denials.
  • Verify allowed amounts against contracted rates — underpayments are recoverable only if caught at posting.
  • Auto-post the routine, but reconcile deposits and send denials and partial payments to a human reviewer.

Back to all articles

Maximize Every Claim

Stop writing off money you actually earned.

Underpayments and silent denials hide in your remittances. Let Bill The Max post payments accurately, decode every reason code, and recover the revenue your current process misses. Start with a free practice consultation.