Reading a Denial: Codes, Group Codes, and the Remittance
A payer does not explain a denial in a sentence. It returns standardized codes on the remittance advice, and those codes are the whole of its account of the decision. Reading them accurately — the adjustment reason, the group code beside it, and the remark that narrows it — is what separates a denial you can act on today from one that goes back into a queue.
Updated 8 min read
On this page
Key takeaways
- Denials are read at the claim line, not the claim. A payer can pay most of a claim and deny one line, and money arriving is not evidence that nothing was denied.
- Three pieces travel together: a group code (who bears the amount), a CARC (why it was adjusted), and often a RARC (the detail that makes it actionable).
- The group code is the one that decides whether a balance may be billed to the patient. Reading the reason without it is how patients get billed for amounts they do not owe.
- The codes state the payer's reason. They do not state your root cause — and they are not a verdict on whether the decision was right.
Where a denial actually arrives
Denials come back on the electronic remittance advice — the transaction a payer sends to report what it did with a claim and why. It is the payer's account of its own adjudication, and it is the only place a denial is formally stated. A rejection never appears here at all, because a rejected claim was never adjudicated; it comes back in an acknowledgement report instead, which is precisely why rejections are easier to lose.
Read the line, not the payment
The three pieces on a denied line
Every adjustment on a claim line carries a group code and an adjustment reason code, and often one or more remark codes. They do different jobs, and reading only one of them is the source of most misreadings.
| Piece | The question it answers | What it does not tell you |
|---|---|---|
| Group code | Who bears this amount — the provider by contract, the patient, or the payer. | Why the adjustment was made. It assigns responsibility, not reason. |
| CARC | Why the payer adjusted the line — the stated adjustment reason, from a national code set. | Your root cause, or which specific item was at fault. It is the payer's reason, not your diagnosis. |
| RARC | The detail that narrows the reason — often which information was missing or which policy applied. | Which kind it is, until you look. Most RARCs supplement an adjustment reason — but an informational RARC (prefaced “Alert:”) carries no adjustment at all. |
The code sets themselves are maintained by X12 (opens in a new tab) and are not reproduced here — the current list is always the one X12 publishes. What is worth learning is the structure above, because it lets you read a code you have never seen before.
The group code decides who pays
Of the three, the group code carries the most immediate financial consequence, and it is the one most often skipped. It answers a single question: now that the payer has adjusted this amount, who bears it? There are four, and they are stable across payers.
- CO — Contractual Obligation
- The provider bears the amount because the contract says so. This is the group code on a contractual adjustment — the routine difference between the billed charge and the contracted rate — and it is written off. It must not be billed to the patient.
- PR — Patient Responsibility
- The patient bears the amount: a deductible, a copay, coinsurance, or a non-covered service the patient is responsible for. This is the group code that produces a patient statement.
- OA — Other Adjustment
- The catch-all, used when none of the other group codes applies — commonly where another payer is involved, as in coordination of benefits. It tells you who does NOT bear the amount more clearly than who does, so what happens next comes from the reason code beside it rather than from the group code alone.
- PI — Payer Initiated Reduction
- The payer is reducing payment for a reason it considers its own, rather than one the contract assigns to the provider. Worth reading closely: unlike CO, it is not a write-off the agreement anticipated, so a PI adjustment should be understood before it is accepted as one.
The same reason under CO and PR means opposite things
Reading a denied line, in order
The order matters, because each step changes what the next one means. Working a denial by reacting to the first code you see is how claims get appealed that should have been corrected.
Confirm it is a denial at all
A zero payment is not automatically a denial. It can be a contractual adjustment on a line the payer processed exactly as contracted, or an amount applied to a patient deductible. The group code answers this before anything else does.Read the group code
Establish who bears the amount. This decides whether the balance is a write-off, a patient statement, or work — and it is the answer that has to be right before any patient is billed.Read the adjustment reason
Now the reason means something. Map it to a category — eligibility, authorization, medical necessity, coding, filing — using the recurring categories.Read every remark on the line
A line can carry several remark codes, and the actionable detail is usually in one of them rather than in the reason. An adjustment reason may say information is missing; a remark is what identifies which — and that is the difference between a fix today and a research task.Decide the response before you touch the claim
Correct and resubmit if the claim was wrong. Appeal if the decision was wrong. Write off if neither is warranted. The codes you have just read are what decide which of the three this is.
What the codes will not tell you
Reason codes are a shared language for stating decisions, which makes them enormously useful and gives them two limits worth naming.
The first is that a code is the payer's reason, not your cause. Two claims denied under the same eligibility code can fail for entirely different upstream reasons — one practice never verified, another verified at scheduling and never re-checked before the visit. The code is identical; the fix is not. Tracing a code back to the step that produced it is analysis the remittance cannot do for you.
The second is that a code is not a verdict. It states what the payer decided, not whether the decision was correct. A denial can be wrong — the record can support the necessity the payer says is unsupported, the claim can have arrived inside a window the payer says it missed. That the reason is standardized says nothing about whether it was applied rightly, which is the entire premise of an appeal, and the reason the appeal overturn rate is a metric worth watching at all.
Codes are worth grouping, not memorizing
Common questions
What is the difference between a CARC and a RARC?
A CARC — Claim Adjustment Reason Code — states why the payer adjusted a claim line, and travels with a group code that says who bears the amount. A RARC — Remittance Advice Remark Code — adds detail: in practice the CARC gives you the category and the RARC often gives you the specific, actionable item. Most RARCs are supplemental and accompany a CARC, but informational RARCs — prefaced “Alert:” — stand alone and explain no adjustment. The two code sets also have different maintainers: CARCs are maintained through the X12 committee process, while CMS maintains the RARC list as X12’s recognized maintainer.
Why does the group code matter so much?
Because it decides who bears the adjusted amount, and the same adjustment reason means opposite things under different group codes. Under CO — contractual obligation — the amount is the provider's and is written off. Under PR — patient responsibility — it is the patient's and produces a statement. Reading the reason without the group code is how a patient gets billed for an amount they do not owe.
Where can I look up a specific reason code?
X12 maintains the CARC and RARC code sets nationally and publishes the current lists, which is the authoritative place to look one up. We do not reproduce the code descriptors here: the lists change, and a copy on a third-party site is a copy that can be out of date at the moment you rely on it.
Does a zero payment always mean a denial?
No. A line can be paid at zero because the entire amount was a contractual adjustment, or because it was applied to the patient's deductible — in both cases the payer processed the claim exactly as expected. The group code is what distinguishes an adjustment the contract anticipated from a refusal to pay, which is why it is read first.
Key terms in this article
Defined once, on their own pages.
Continue learning
Where to go next on denials.
Appealing a Denial
What to do once the codes tell you the decision, not the claim, was wrong.
Why Claims Get Denied
The categories these codes roll up into, and the step each points back to.
The Denial Appeal Process
The ordered steps for challenging a payer's decision.
Appeal overturn rate
The metric that measures how often a challenged denial is reversed.
Authoritative sources
- X12 — Claim Adjustment Reason Codes and Remittance Advice Remark Codes (opens in a new tab)
Maintains and publishes the national code sets used on the remittance advice. The authoritative source for any specific code.
- Centers for Medicare & Medicaid Services (CMS) (opens in a new tab)
Publishes Medicare remittance and claims-processing guidance for providers.