Reading a remittance: turning a CARC and RARC pair into a corrective action

Every adjustment on a remittance advice is reported as a claim adjustment reason code, a CARC, usually paired with a group code and one or more remittance advice remark codes, RARCs. Read correctly, that pair tells you why the money moved, who is now responsible for it, and what to do next. Read as an opaque number, it just looks like a denial.

The group code answers one question: who owes it

The group code prefixed to a CARC on the remittance (CO, PR, OA or PI) is a separate fact from the CARC itself, and it answers a specific question: can this amount be billed to the patient.

• CO, Contractual Obligation. The provider is responsible for the amount under the payer contract. It cannot be billed to the patient.
• PR, Patient Responsibility. The amount may be billed to the patient, such as a deductible, coinsurance or copay.
• OA, Other Adjustment. Used when neither CO nor PR applies, commonly coordination-of-benefits scenarios.
• PI, Payer Initiated Reduction. The payer treats the adjustment as its own decision rather than a term of the contract.

The same CARC can appear under more than one group code depending on the payer and the circumstances. CARC 96, Non-covered charges, is a good example: it is reported as PR when the patient owes it and as CO when the provider does under the contract terms. Do not assume the group code from the CARC number alone, read what is actually printed on the remittance.

The CARC explains the mechanism

The CARC itself is the reason the adjustment happened. Some examples from our own dataset show how differently that mechanism plays out:

• CO-45, charge exceeds the fee schedule or contracted rate. This is a routine contractual write-off in most cases: the payer paid the contracted amount and the difference is adjusted off, not evidence of an error. It is only worth appealing if you can show the payer used the wrong fee schedule, the wrong contract year, or that the code is not actually subject to that schedule.
• CO-97, the service is bundled into another procedure already paid on the claim. This is where an NCCI PTP edit or a global surgical period usually sits behind the denial. It is worth appealing with documentation when the service was genuinely separately identifiable but was submitted without the modifier that would have said so.
• CO-16, the claim or service lacks information, or has a submission or billing error. This is a correctable claim, not a coverage dispute: identify the missing or invalid field, most often named in the accompanying RARC, correct it, and resubmit.
• PR-204, the service or equipment is not covered under the patient's current benefit plan. This is a genuine patient-responsibility scenario in most cases, not a billing mistake, though it is worth confirming the plan and dates of coverage were read correctly before writing it off as uncollectable.

The RARC is the detail behind the CARC

A CARC by itself is often generic. CO-16 alone just says information is missing or invalid, it does not say which field. That is what the accompanying RARC is for: a remittance advice remark code that names the specific missing item, whether that is a referring provider NPI, a rendering provider taxonomy code, or a required attachment. Two claims can both deny as CO-16 for completely different reasons, and the RARC is what distinguishes them.

RARCs come in two flavors: informational RARCs add detail to an already-explained adjustment, and alert RARCs (the M and N series in the official list, among others) often carry an instruction of their own, such as a specific resubmission requirement. Treat an alert RARC as something to act on directly, not just as color on the CARC.

Turning the pair into a ranked corrective action

Our denial explainer takes the CARC's own corrective actions first, then adds anything from the RARCs that is not already covered, and removes duplicates so the biller sees one ranked list rather than the same instruction twice. Appeal worthiness is read directly off the CARC record, since that is the fact that actually governs whether reconsideration is likely to succeed. Where a payer is known, its published appeal deadline is attached to the same result, so the worthiness judgment and the clock you are working against sit next to each other instead of in two different references.

What to do with an unfamiliar RARC

Our RARC dataset is still being built out, so not every remark code on your remittance will have a page here yet. Where that is the case, check the code directly against the official X12 remittance advice remark code list rather than guessing at its meaning from the CARC alone, since two different RARCs paired with the same CARC can point to genuinely different fixes.