Skip to main content
Remittance Advice Remark Codes (RARCs) provide additional explanation for an adjustment, or convey information that doesn’t fit a CARC. They appear in the LQ segment of the 835. RARCs are maintained by CMS on behalf of the industry and the list is updated periodically. This page covers the high-frequency working set. The authoritative list is published at x12.org/codes/remittance-advice-remark-codes — check it for codes not listed here and for current definitions.

What RARCs do

Two types: The RARC is what makes a vague CARC actionable. CARC 16, “claim lacks information”, is a scavenger hunt on its own. CARC 16 with a RARC telling you which information is missing is a five-minute fix.
Train billers to read the RARC before working a CARC 16, 96, 125, or 252. Those CARCs are deliberately generic; the RARC carries the specifics.

High-frequency N-series

High-frequency M-series

MA130 is important and misread constantly. It means the claim was rejected as incomplete with no appeal rights — submit a new claim rather than an appeal. Practices that appeal MA130 waste the effort and may run out the filing window.MA13 is a warning that billing the patient for a non-PR amount can carry penalties. If you see it, check your group code mapping.

Appeal rights signals

Two RARCs tell you directly whether an appeal is available: Reading these first saves filing appeals that cannot succeed.

Working with RARCs

1

Always read the RARC before working a generic CARC

CARC 16, 96, 125, and 252 are generic by design.
2

Check for appeal-rights RARCs

N210, N211, MA130 determine whether an appeal is even available.
3

Include the RARC in your denial root-cause tagging

“CARC 16” is not a root cause. “CARC 16 / N290, missing rendering provider NPI” is.
4

Look up anything unfamiliar before posting

Do not guess at a RARC’s meaning. The authoritative list is public.