Remittance Advice Remark Code (RARC)

Remittance Advice Remark Codes (RARCs) are supplemental codes that appear alongside CARC codes on an Explanation of Benefits or Electronic Remittance Advice. While a CARC code tells you the category of an adjustment (for example, "this claim lacks required information"), a RARC code drills into the specifics: which information is missing, what the provider needs to do next, or what the payer's policy is on the issue.

Not every claim adjustment includes a RARC, but when one appears, it is often the most actionable piece of information on the remittance. Billing staff who skip RARC codes in favor of working from CARC codes alone will frequently pursue the wrong resolution path.

What are the two types of RARC codes?

RARCs fall into two categories, each serving a distinct purpose:

Informational RARCs (often prefixed with "N") convey supplemental explanations or instructions. For example, N30 indicates "patient has a Medicare Supplemental Policy" and N96 signals "patient is covered by a managed care plan." These codes add context but do not necessarily indicate a problem that requires action.

Alert RARCs (often prefixed with "MA" or "M") signal that the provider must take a specific action or that the notice has compliance implications. MA130 ("your claim contains incomplete and/or invalid information") and M76 ("missing/incomplete/invalid diagnosis or condition") are common examples that require the provider to correct and resubmit.

How do RARC codes work with CARC codes in practice?

The most effective way to read a remittance is to treat the CARC and RARC as a pair. Consider a few real-world combinations:

• CO-16 + N56: The claim lacks required information (CO-16), and specifically, the procedure is not covered when performed by this provider's specialty (N56). The action is to verify whether the procedure is within the provider's scope or to obtain a referral.
• CO-4 + M76: The claim has billing errors (CO-4), and specifically, the diagnosis code is missing or invalid (M76). The action is to review and correct the diagnosis code and resubmit.
• CO-97 + N95: The service was already adjudicated (CO-97), and specifically, this is a duplicate of a previously processed claim (N95). The action is to verify whether this was an intentional resubmission or a duplicate submission error.

Reading these pairs together saves significant time in the rework process and prevents incorrect actions, such as sending a reconsideration letter when the actual issue is a correctable billing error.

Why do RARC codes matter for denial prevention?

RARC codes are underutilized for pattern analysis. Most denial management programs track CARC code frequency, but tracking RARC code frequency across high-volume denial categories reveals granular root causes that CARC codes alone obscure.

For example, a practice might see a 10% denial rate on a specific procedure code and attribute it broadly to CO-4 (modifier issue). But analyzing the accompanying RARCs might reveal that 80% of those denials carry M44 ("incomplete/invalid place of service"), meaning the actual fix is standardizing place-of-service codes in the billing template, not re-educating coders on modifiers.

Where are RARC codes published?

Like CARC codes, RARCs are maintained by the Washington Publishing Company and updated periodically. The full list is publicly available and referenced in most practice management and clearinghouse software. There are currently over 900 active RARC codes, reflecting the wide variety of specific denial circumstances payers need to communicate.

How do they relate to denial automation?

When AI systems process remittance data to categorize and route denials automatically, RARC codes are essential inputs. A system that reads only the CARC code will achieve coarse-grained categorization; one that reads the CARC-RARC pair can route with enough precision to generate a specific resolution action: the right letter template, the correct missing field, or the specific payer policy to cite in an appeal.