CARC vs RARC: what the difference actually means
A claim adjustment reason code and a remittance advice remark code answer different questions on the same remittance. Here is what each one is for, and why you need both to actually fix a denial.
Ask five billers to explain the difference between a CARC and a RARC and you will often get an answer that is roughly right but not quite precise enough to act on. Both are printed on the same 835 remittance transaction, both are maintained by X12, and both show up alongside a denial. What they each actually communicate is genuinely different, and mixing them up is a common reason a corrective action gets built around the wrong fact.
TL;DR. A CARC (claim adjustment reason code) says why the amount was adjusted, standardised across every payer. A RARC (remittance advice remark code) adds detail a CARC alone does not carry, or delivers an instruction of its own. A claim can carry one CARC and several RARCs, but not the reverse.
The core difference: reason versus detail
A claim adjustment reason code (CARC) is the code that explains why an adjustment happened at all, financially. It is always required whenever an amount was changed, denied or shifted to a different party. A remittance advice remark code (RARC) is optional supplementary information, sometimes narrowing a generic CARC down to a specific fact, sometimes carrying an instruction that stands on its own.
| CARC | RARC | |
|---|---|---|
| What it answers | Why the payment amount changed | The specific detail behind that reason, or a separate instruction |
| Required on every adjustment? | Yes | No, though many CARCs are practically unreadable without one |
| Can appear alone? | Yes | No, always accompanies at least one CARC |
| Two-letter prefix in the official list | None; three-digit numeric codes (CARC 1 through several hundred) | M for many informational codes, N for many alert-style codes, among others |
Why a CARC alone is often not enough
CO-16, "Claim/service lacks information or has submission/billing error(s)", is the clearest example of why the pairing matters. The CARC alone tells you something is wrong with the submission. It does not tell you what. Two different claims can both carry CO-16 for two completely unrelated reasons, a missing NPI on one and an invalid diagnosis pointer on the other, and only the paired RARC distinguishes them. Treating a CO-16 denial as fully explained by the CARC number, without reading the remark code, is the single most common reason a resubmission fails a second time.
Informational RARCs versus alert RARCs
Not every RARC does the same job. Some simply add colour to an already-understood adjustment, confirming or clarifying a fact the CARC already established. Others, often in the alert category, carry an instruction of their own, such as a specific resubmission requirement or a notice the biller needs to act on directly, independent of whatever the CARC already said. Treat an alert-type RARC as a task, not as background detail.
A useful mental model: the CARC is the verdict, the RARC is the reasoning. You can sometimes guess at a fix from the verdict alone, but you are far more likely to get it right, and to write a reconsideration a reviewer can act on, when you can cite both.
How our own denial explainer uses the pair
Our engine takes the CARC's own corrective actions as the primary list, then layers in anything the paired RARCs add that is not already covered, and removes duplicates so a biller sees one ranked set of next steps instead of the same instruction twice. Appeal-worthiness is read from the CARC record specifically, since the CARC is what actually governs whether a reconsideration has a realistic chance, while the RARC narrows down exactly what evidence that reconsideration needs to cite.
Look up the CARC on your remittance and see the corrective action ranked against its paired remark codes.
Look up a denial codeA quick reference for reading your own remittance
- Read the group code first. CO, PR, OA or PI tells you who is financially responsible before you even get to the mechanism.
- Read the CARC. This is the reason the adjustment happened, and it is standardised, so its meaning does not change from payer to payer.
- Read every paired RARC, not just the first one. A claim can carry several remark codes attached to a single CARC, and each can add a different piece of the picture.
- Decide whether it is a correction or a dispute. A data-error CARC like CO-16 needs a corrected claim; a payment-methodology CARC like CO-97 or CO-45 may need a reconsideration instead, and our full guide to that pair walks through the decision in more depth.
Frequently asked questions
Can a claim have a RARC without a CARC?
No. A RARC is always supplementary to a CARC; it never appears on its own, since it exists to add detail to, or an instruction alongside, an adjustment the CARC has already explained.
Do CARC and RARC meanings vary by payer?
No, both code sets are standardised and maintained centrally by X12 for use in the 835 remittance transaction, so a given code's published meaning is the same regardless of which payer issued the remittance. What varies by payer is how frequently a given code is used and which RARCs it commonly pairs with.
How many RARCs can be attached to a single CARC?
There is no fixed limit; a single adjustment can carry multiple remark codes if more than one detail or instruction applies. Reading only the first RARC listed and assuming it is the only relevant one is a common way to miss a second, equally important detail.
Where can I look up an unfamiliar CARC or RARC directly?
The authoritative published lists are maintained by X12 at their claim adjustment reason codes and remittance advice remark codes pages. Our denial code lookup covers the CARCs and RARCs we have verified and added corrective actions to, and flags plainly where a code is not yet in our dataset rather than guessing.
This guide is billing and administrative guidance, not medical advice, a coverage determination or a guarantee of payment. To see the cited entry for your own denial code, use the denial code lookup, or see how the same engine works from your own code or an AI agent.
More guides
Put this into practice on your own claim
Scrub a claim free in your browser, or look up the specific CARC or RARC on your remittance.