RARC — Remittance Advice Remark Codes

How to read a RARC on a remit

A Remittance Advice Remark Code never stands alone on the 835 electronic remittance. It appears in the LQ segment attached to a claim-line adjustment whose financial reason is the paired Claim Adjustment Reason Code (CARC) in the CAS segment. The biller works the denial by pulling both codes together: the CARC explains whether the payer bundled, denied for medical necessity, rejected for prior-auth, or carved out the balance to patient responsibility, and the RARC narrows the specific data element, documentation piece, or policy reference that caused the outcome. Missing either half of the pair means a rebill or appeal works off incomplete information and usually cycles back into the A/R queue a second time.

Three letter-series frame the RARC set and explain why a particular remit draws from one range and not another. The M-series is historically Medicare-authored and still skews toward fee-for-service Medicare remits: modifier combinations, LCD and NCD references, beneficiary liability rules, and the Advance Beneficiary Notice (ABN) interactions live here. The MA-series is the Medicare Part A remark inventory — inpatient, hospice, home-health, and other institutional touch-points where the 837I carries data that can generate a remark the 837P never would. The N-series is the general all-payer inventory that commercial insurers, Medicaid MCOs, Blue Cross licensees, and workers' compensation carriers draw from when CMS has not published a specific M or MA code for the situation. Every leaf page in this sub-hub cites the X12 master description verbatim and shows which CARCs the code pairs with in the real-world remits our editorial team has reviewed.

When a RARC appears on more than one denial family — for example N130, which surfaces on both medical-necessity denials (paired with CARC 50) and coverage denials (paired with CARC 96) — the leaf page expands the scenario matrix so you can choose the right remediation without guessing. Work RARCs the same way you work CARCs: identify the pair, confirm the documentation gap, and choose between a corrected claim (the usual answer for modifier, diagnosis, and demographic remarks) or a formal appeal (the answer for medical necessity, benefit exclusions, and prior- authorization remarks where the underlying decision is clinical). Most RARC-flagged denials resolve with a corrected 837, not a first-level appeal, which is why the CARC and RARC leaves each ship a prevention checklist in addition to the appeal template.