OakClaim

How to read an ERA: CARC + RARC codes together

The electronic remittance advice (the 835) is where payers explain every dollar they didn't pay. Most billing teams read it shallowly — they see a denial code, guess, and rebill. Reading it properly takes about ninety seconds per claim and cuts rework dramatically, because the ERA almost always tells you exactly what's wrong. You just need all three layers.

Layer 1: the group code — who absorbs the dollars

  • CO (Contractual Obligation) — the provider absorbs it. Write-offs, bundling, fee schedule reductions. Never billable to the patient.
  • PR (Patient Responsibility) — deductible, coinsurance, copay, non-covered-by-choice. Billable to the patient.
  • OA (Other Adjustment) — neither party definitively; COB bookkeeping, pends, transfers.
  • PI (Payer Initiated) — payer-driven reductions, often audit- or program-related.
The single most expensive posting error in billing is treating CO amounts as patient responsibility. Remark code MA13 is the payer warning you: balance-billing CO amounts violates your contract and, for Medicare, federal rules.

Layer 2: the CARC — what happened

The Claim Adjustment Reason Code gives the category of the adjustment: 45 means fee-schedule reduction, 16 means missing information, 197 means no authorization. There are ~300 active codes — our denial code librarycovers every one with causes and fixes. But the CARC alone is often too vague to act on. CO-16 tells you something is missing. It doesn't tell you what.

Layer 3: the RARC — the actionable detail

Remark codes ride along the CARC and carry the specifics: CO-16 + N290 = missing rendering NPI. CO-16 + M76 = missing diagnosis. CO-16 + MA120 = missing CLIA number. Same CARC, three completely different fixes. Working denials without reading the remark codes is why claims get rebilled three times instead of once — search any code in our remark code lookup.

Reading a real denial line

Take this service line from an 835:

CAS*CO*197 · REF: Auth required — paired remark N351 (service date outside approved treatment plan dates)

Shallow read: "no auth, request retro-auth." Full read: an auth existsbut the service date fell outside its window — you need an auth extension and an appeal citing the reschedule, a completely different (and faster) path. That's the value of layer three; our CO-197 appeal guide walks the full playbook.

Don't skip the PLB segment

Provider-Level Balance adjustments sit at the bottom of the 835 and hit your deposit without touching any claim: recoupments, interest, sequestrationoffsets, advance reconciliations. When your deposit doesn't match your posted claims, the PLB is almost always why. Post PLB items to their own GL buckets — burying recoupments inside claim adjustments destroys your denial analytics.

The triage system

Route every remitted line into one of four queues, in priority order:

  1. Fix-and-rebill (same day) — missing/invalid data: CO-16 family, NPI remarks, MA130 unprocessable claims. Fast, high-recovery, deadline-sensitive.
  2. Appeal (deadline-calendared) — auth denials, medical necessity (CO-50), timely filing with proof (CO-29). Calendar the appeal deadline the day the denial posts.
  3. Route elsewhere — COB issues (CO-22), plan-routing codes (254/270/280/297/301), misdirected claims (N418).
  4. Post-and-analyze — legitimate contractual adjustments (CO-45, bundling). No claim action, but trend them: rising CO-97 means a coding pattern; rising CO-45 percentages mean a fee schedule problem.

The metric that matters: first-pass resolution — the share of denials fixed correctly on the first touch. Reading all three layers is how it goes up.

Want remits read like this on every claim?

Our team triages every ERA line the day it lands. The free audit shows what your current process is leaving behind.

Get a Free Audit