Remittance Advice Remark Codes (RARCs) Explained: What They Mean and How to Act on Them

If you work in healthcare billing, you’ve seen them: those cryptic two-to-four character codes that show up in remittance files alongside denied or adjusted claims. Remittance Advice Remark Codes (RARCs) are one of the most overlooked tools in revenue cycle management — and misunderstanding them costs practices real money.

This guide breaks down what RARCs are, where they live in an EDI 835 file, what the most common ones mean, and — most importantly — what you should do with them.

What Are Remittance Advice Remark Codes (RARCs)?

RARCs are standardized codes published by the Centers for Medicare & Medicaid Services (CMS) that accompany Electronic Remittance Advice (ERA) transactions. They appear alongside Claim Adjustment Reason Codes (CARCs) and provide additional context about why a claim line was adjusted, denied, or paid differently than billed.

Where CARCs tell you what happened (e.g., “not covered”), RARCs often tell you why or what to do next (e.g., “submit a corrected claim” or “see your provider manual”).

There are two categories:

Informational RARCs — provide detail or context without necessarily triggering action
Alert RARCs (MA or N prefix) — provide guidance that may require follow-up

CMS maintains the complete RARC list and updates it periodically. As of 2026, there are over 900 active RARCs.

Where Do RARCs Live in an 835 File?

RARCs appear in the CAS segment (Claim Adjustment) and MOA segment (Medicare Outpatient Adjudication) of an 835 ERA transaction. More specifically, they show up in the LQ segment under Service Payment Information.

Here’s how a claim service line adjustment looks in raw X12:

CLP*1234567890*2*150.00*100.00**MC*1234567890101~
SVC*HC:99213*150.00*100.00**1~
DTM*472*20260701~
CAS*CO*45*50.00~
AMT*B6*100.00~
LQ*HE*N30~

Breaking this down:

CLP — Claim-level segment. The second element (2) means the claim was paid (partially).
SVC — Service line. Billed $150, paid $100.
CAS — Adjustment. CO (Contractual Obligation), CARC 45 (charges exceed contracted amount), amount $50.00.
LQHE — Remark code qualifier. HE means “HIPAA Claim Adjustment Reason Code.”
N30 — The RARC itself.

N30 means: “Patient cannot be identified as our insured.”

So in this example, the claim was adjusted by $50 under contract (CARC 45), but there’s also a remark that the patient couldn’t be confirmed as a member — which is a serious signal worth following up on.

RARC Anatomy: Understanding the Code Structure

RARCs typically follow two naming conventions:

Prefix	Category	Example
`MA`	Medicare Administrative	MA01, MA130
`N`	Informational/Alert	N30, N115, N657
`M`	Older Medicare remark codes	M15, M79

Most modern payers use the N series. Medicare remittances often include MA codes in addition to N codes.

The 15 Most Common RARCs You’ll See (and What to Do)

N1 — Alert: You may appeal this decision.

This is an informational remark indicating the provider has appeal rights. It appears frequently alongside denials. Action: Review the CARC on the same line to understand the denial reason, then determine if the denial is worth appealing.

N30 — Patient cannot be identified as our insured.

The member could not be matched. This is often a data entry issue — wrong member ID, name mismatch, date of birth error — or a lapsed policy. Action: Verify eligibility at the date of service using a 270/271 transaction. Resubmit with corrected patient demographics.

N56 — Procedure code billed is not correct/valid for date of service.

The code used wasn’t valid for that service date under the applicable code set. Could be a code that was retired, added after the date, or billed under the wrong year’s code set. Action: Check the CPT/HCPCS code effective dates. Submit a corrected claim with the accurate procedure code.

N115 — This decision was based on a Local Coverage Determination (LCD).

Medicare denied or adjusted based on an LCD policy. Action: Review the relevant LCD to determine if the diagnosis supports coverage. If documentation supports medical necessity, gather it and appeal.

N130 — Consult your provider manual.

Generic remark that the payer’s internal policy governs the adjustment. Action: Pull the payer’s provider manual for the relevant service category. This is often paired with a CO denial and needs policy-specific follow-up.

N180 — This claim has been identified as a duplicate.

The payer considers this a duplicate submission. Action: Check your claim log. If it truly is a duplicate, no action is needed. If not, resubmit with a corrected claim (loop 2300, CLM05-3 = 7) with documentation that this is not a duplicate.

N211 — You may not appeal this decision.

The adjustment is final and not subject to appeal. Common on contractual write-offs. Action: Adjust off the balance. No further action required.

N270 — Claim/service not covered by this payer/contractor. You must send the claim to the correct payer/contractor.

Wrong payer. The claim needs to be sent elsewhere — usually to a primary or secondary payer. Action: Identify the correct payer using eligibility verification. Cross-over claims may handle this automatically for Medicare/Medicaid.

N381 — Consult your provider manual for additional information about this service.

Similar to N130 but more specific to a service type. Action: Review the payer’s clinical coverage policies for the specific procedure billed.

N479 — Please resubmit with the appropriate revenue code.

Common on institutional (837I) claims. The submitted revenue code doesn’t match what the payer expects. Action: Verify the correct revenue code mapping for the service and submit a corrected claim.

N522 — Duplicate of a claim processed, or to be processed, as a crossover claim.

The claim crossed over from primary Medicare and will be processed automatically. Action: Wait for the secondary remittance. No action needed unless it doesn’t arrive within expected timeframe.

N600 — Completion of a prior administrative action may be needed.

There’s a pending administrative process (credentialing, contract update, prior auth) that needs to be resolved first. Action: Contact your provider relations or credentialing team to resolve the upstream issue.

MA01 — Alert: If you do not agree with what we approved for these services, you may appeal our decision.

Standard Medicare appeal notice. Action: Evaluate the adjustment reason. If you believe the service warrants additional reimbursement, initiate the Medicare appeals process within the required timeframe.

MA130 — Your claim contains incomplete and/or invalid information, and no appeal rights are afforded because the claim is unprocessable.

The claim had data issues that prevented it from processing at all. Action: Review the claim for missing or invalid required elements. Resubmit as a new claim (not a corrected claim) once fixed.

N657 — The rendering provider is not eligible to perform the service billed.

Credentialing or scope-of-practice issue. Action: Verify that the rendering provider is credentialed with this payer and that their NPI is active and correctly linked. May require a corrected claim with a different rendering provider NPI.

Reading RARCs in Context: CARCs + RARCs Together

RARCs are almost never interpreted in isolation. They work alongside CARCs. Here’s a real-world example of a 835 SVC/CAS/LQ block with both codes:

SVC*HC:93000*85.00*0.00**1~
DTM*472*20260715~
CAS*PR*1*85.00~
LQ*HE*N115~

CARC PR-1 = “Deductible amount” — patient owes $85 (responsibility shifted to patient)
RARC N115 = “This decision was based on a Local Coverage Determination”

Together, this tells you: The EKG (93000) was applied to the patient’s deductible, AND Medicare used an LCD to make that determination. The remark code gives you an angle to document medical necessity more thoroughly if you want to fight the deductible assignment through a coverage review.

Without the RARC, you’d just see “patient deductible” and move on. With it, you know there’s an LCD policy at play.

Workflow: What to Do When You See an Unfamiliar RARC

Look it up — CMS publishes the full RARC list at Washington Publishing Company. New codes are added quarterly.
Find the paired CARC — The RARC adds context to the CARC. Don’t read one without the other.
Identify the responsibility — Is this a payer adjustment, patient responsibility, or provider write-off? The CAS segment qualifier tells you (CO, PR, OA, PI).
Determine if action is required — Informational RARCs often need no action. Alert RARCs (especially MA codes) usually do.
Set a follow-up flag if open-ended — Codes like N600 require upstream resolution. Track them in your AR workflow so they don’t fall through the cracks.
Document your action — When you resubmit or appeal based on a RARC, note the original RARC and your response in your claim notes. Payer audits and disputes go better with clear documentation.

RARCs vs. CARCs: Quick Reference

	CARC	RARC
Purpose	Reason for adjustment	Additional context/instruction
Required on ERA?	Yes, when adjustment exists	No, but common
Segments used	CAS	LQ (under SVC or CLP)
Published by	WPC / CMS	CMS
Action trigger?	Often	Sometimes

Tools That Help

Reading RARCs in raw 835 files is tedious — especially when a remittance file has hundreds of service lines. A dedicated EDI viewer makes it significantly easier to:

Parse the LQ segment and display the RARC description inline
Group denials by CARC + RARC combination to spot systemic issues
Export denial detail for AR follow-up

If you’re reviewing 835 files manually or want to investigate a specific remittance, a browser-based tool that parses the raw X12 without requiring a clearinghouse login is worth having in your toolkit.

Summary

RARCs are not just noise in your remittance files — they’re instructions. When you learn to read them alongside CARCs, you stop treating denials as binary (paid/denied) and start treating them as diagnostic data. That shift is what separates reactive billing teams from ones that systematically recover revenue.

The key habits:

Always read RARC + CARC together
Act on alert RARCs promptly — they often have appeal or resubmission deadlines
Track recurring RARC patterns as indicators of upstream workflow problems
Never let a RARC like N600 or MA130 sit without a follow-up task

Ready to work with EDI files in your browser? Try EDI Paisan free — no install required.