Guide

CARC and RARC: the payer's reason-code grammar

Summary

CARC and RARC are the two code sets on every remittance: the Claim Adjustment Reason Code says why a line paid differently than billed, and the Remittance Advice Remark Code supplies the specific detail the CARC alone doesn't give. In front of both sits a group code — CO for a contractual write-off, PR for patient responsibility — which decides whether the amount is yours to absorb or the patient's to pay.

By Gale Editorial · Updated 2026-07-26. Every figure cited to a dated source. How we write.

What do CARC and RARC codes mean on a remit?

A Claim Adjustment Reason Code, or CARC, is the standard, X12-maintained code explaining why a service line was paid differently than billed or not paid at all 1. A Remittance Advice Remark Code, or RARC, rides alongside it to supply the additional detail the CARC alone is too broad to give — which field was wrong, which policy applied, what to do next 2.

Read in isolation, a CARC tells you the category of the problem; read together with its RARC, it tells you the actual fix. A CARC that means the claim lacks information paired with a RARC naming the exact missing field is the difference between guessing and correcting a claim in one pass.

The group code comes first: CO vs PR, and the others

Before the CARC number itself, every adjustment carries a two-letter group code that decides who is responsible for the amount. CO, contractual obligation, is a write-off you agreed to under your network contract and cannot bill the patient. PR, patient responsibility, is an amount you can and should move to the patient's statement — a deductible, coinsurance, or copay 1.

The most common CO line on any in-network remittance isn't actually a denial at all: co-45 is not a denial, it's the ordinary contractual adjustment between what you billed and what the contract allows, and treating it as something to appeal is wasted effort. Two less frequent group codes, OA for other adjustments and PI for payer-initiated reductions, round out the set but appear far less often than CO and PR.

Why the CARC alone often isn't enough to act on

Some CARCs are specific enough to act on immediately — a duplicate-claim code, for instance, tells you exactly what happened. Others are deliberately broad, covering a whole family of possible problems, and that's precisely where the RARC earns its keep by narrowing a vague category down to one fixable fact 2.

The habit worth building is reading the RARC every time a CARC is anything less than crystal clear, rather than treating the reason code as the whole answer. A missing-information CARC without reading its paired remark code just tells you something is wrong; the remark code tells you what to actually change before you resend.

Where these codes actually live: the standardized remittance

CARC and RARC codes arrive on the electronic remittance advice, and CAQH CORE operating rules require payers to deliver that remittance in a standardized, rule-governed format — the same standardization that covers eligibility checks and claim-status inquiries 3. That consistency is why reading remits from one payer transfers directly to reading remits from the next; the code lists and the group-code logic don't change payer to payer, even though the specific reasons behind any one line will.

That standard format is also what makes automated remittance posting possible at all: practice management systems can parse the CARC and group code without a human reading every line, reserving your attention for the lines that actually need a decision.

When a CARC points to a payer's own coverage policy

Some CARCs, particularly medical-necessity or non-covered-service denials, trace back to a specific coverage policy the payer has published rather than a universal industry rule. UnitedHealthcare, for example, publishes its own medical and reimbursement policies on its provider portal, stating exactly what it will and won't consider covered for a given service 4.

The discipline this creates is specific to the payer on the remittance, not a general industry assumption: read that payer's own published policy before writing an appeal, since your contract with that payer controls, and a policy pulled from a different plan doesn't apply just because the reasoning sounds similar. A denial code that references a coverage policy is telling you exactly where to go read, not inviting you to guess.

Self-funded plans read a little differently: ERISA

Not every remittance sits under the same rulebook. A self-funded employer plan is governed by federal ERISA law rather than state insurance law, which is why state prompt-pay and assignment protections often don't reach it — and ERISA sets its own claims-and-appeals framework and deadlines for those plans instead 5.

The practical effect is that the same CARC, on two different remittances, can carry different appeal rights and different clocks depending on whether the plan behind it is state-regulated or self-funded. Confirming which kind of plan you're dealing with, before you calendar an appeal deadline, tells you which set of rules and windows actually apply.

A simple reading routine for every remittance line

Read the group code first — CO or PR decides who owes the money before you even look at the number. Read the CARC second, for the category of what happened. Read the RARC third, whenever the CARC alone doesn't tell you exactly what to fix or where the money goes.

That three-step read sorts every line into one of three lanes: a correctable resubmission, a patient-responsibility balance to bill, or a genuine dispute that belongs in denials-appeals territory. Lines involving pr codes route to the patient statement; lines flagged for coordination of benefits route to a coordination check before anything else, since the group code and reason code together are already telling you which lane a line belongs in before you've made a single phone call.

Common questions

A CARC (Claim Adjustment Reason Code) explains why a claim or line paid differently than billed or didn't pay at all — the category of the problem. A RARC (Remittance Advice Remark Code) supplies the specific additional detail the CARC alone doesn't give, such as exactly which field was missing. Reading both together turns a vague reason into an actionable fix.

CO stands for contractual obligation — a write-off you agreed to under your network contract, which you cannot bill the patient. PR stands for patient responsibility — an amount that belongs on the patient's statement, such as a deductible, coinsurance, or copay. Reading the group code before the reason code tells you immediately who owes the money.

No. CO-45 typically represents the ordinary contractual write-off between your billed charge and the payer's allowed amount — it's expected on nearly every in-network claim, not a decision to dispute. Appealing it wastes time better spent on lines with a genuine medical-necessity or coverage disagreement behind them.

Because coverage and medical-necessity CARCs often trace back to that specific payer's published clinical or reimbursement policy, not a universal rule. Reading the named payer's own policy before appealing tells you the exact criteria the denial rests on, since your contract with that payer controls and another plan's policy doesn't transfer.

The codes themselves are the same standardized lists, but the rules behind them can differ. A self-funded employer plan is governed by ERISA rather than state insurance law, which sets its own claims-and-appeals deadlines and framework — so the appeal window and process behind a code can vary depending on whether the plan is state-regulated or self-funded.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

  1. 1.X12 (2026). Claim Adjustment Reason Codes. X12. linkThat CARCs are the standard code list explaining why a claim or service line was paid differently than billed, and that the group code (CO, PR, OA, PI) in front of the reason code sorts each adjustment by who is responsible for it.
  2. 2.X12 (2026). Remittance Advice Remark Codes. X12. linkThat RARCs supply the supplemental explanation on a remittance beyond the CARC, maintained by X12 with a public list, narrowing a broad reason code down to a specific, fixable detail.
  3. 3.CAQH (2026). CAQH CORE Operating Rules. CAQH CORE. linkThat CAQH CORE operating rules standardize the electronic remittance transaction that carries CARC and RARC codes, the same rule set that governs eligibility and claim-status transactions, making the code format consistent across payers.
  4. 4.UnitedHealthcare (2026). UnitedHealthcare Policies and Protocols. UnitedHealthcare provider portal. linkThat UnitedHealthcare publishes its own medical and reimbursement policies on its provider portal, cited only as a named example of where a payer states the coverage criteria behind a medical-necessity or non-covered-service CARC — never as what all payers do.
  5. 5.U.S. Department of Labor (2026). ERISA. U.S. Department of Labor. linkThat self-funded employer plans are governed by ERISA rather than state insurance law, with their own claims-and-appeals framework and deadlines, so the same CARC can carry different appeal rights depending on the plan type.

https://www.gale.care/for-providers/cm-carc-rarc-basics · 5 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

Findability, by specialty

How practices like yours get found in local search and AI answers — the honest playbook, per specialty.

SEO for private practices · SEO for AI search / answer engines (all verticals)