Skip to main content
Call
RARC M66 · Remittance Advice Remark Code

RARC M66 Remark Code: Our records indicate that we should be the third payer for this claim. We canno…

Reviewed by QuickIntell RCM Editorial Team · Last reviewed

Updated

Not an ICD-10 code. RARC M66 is a remittance-advice remark code published by X12 and carried on the 835 LQ segment. Any ICD-10 code with the same letters and digits (e.g., ICD-10 M15 osteoarthritis, N130 other urinary tract disorders) is a separate, unrelated code set used in diagnoses on the 837. Confirm the context before acting on this page.

TL;DR

RARC M66 (X12 Our records indicate that we should be the third payer for this claim. We cannot process this claim…). Commonly paired with CARC 22, CARC 23. RARC M66 requires COB chain completion before tertiary adjudication.

Official X12 description

“Our records indicate that we should be the third payer for this claim. We cannot process this claim until we have received payment information from the primary and secondary payers.”

Source: X12 Remittance Advice Remark Codes. X12 publishes and maintains the RARC set; always verify against the current release before building a claim workflow.

Paired CARC codes

RARC M66 almost never appears alone — it accompanies one of the CARCs below on the same 835 remittance line. Fix the CARC and the RARC typically clears; the RARC alone is informational.

Paired CARCWhat the CARC means
CARC 22This care may be covered by another payer per coordination of benefits.
CARC 23The impact of prior payer(s) adjudication including payments and/or adjustments.

What RARC M66 actually means

RARC M66 requires COB chain completion before tertiary adjudication. Submit primary and secondary EOBs.

Common root causes

  • Tertiary submission without prior EOBs.

Prevention checklist

  • COB-chain workflow enforces EOB sequencing.

Resolution & appeal strategy — step by step

Because RARC M66 is supplemental to a CARC, the resolution path usually starts by fixing the underlying adjustment reason. A formal appeal of the RARC alone is rarely necessary.

  1. 1Submit prior EOBs and resubmit.
Sample reconsideration language referencing RARC M66
[Provider letterhead] Re: Reconsideration — Claim #{claim_number}, CARC 22 / RARC M66 Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} The 835 remittance on {remittance_date} carried RARC M66: "Our records indicate that we should be the third payer for this claim. We cannot process this claim until we have received payment information from the primary and secondary payer…" We request reconsideration. The attached documentation rebuts the remark code: 1. [State the fact that rebuts the remark — authorization number, primary 835, modifier rationale, LCD citation, etc.] 2. [Reference the paired CARC and the corresponding fix] 3. [Attach the supporting document listed in step 1] Attached: {list supporting documents} Please process this line under the member's benefits. Contact the billing office at {provider_phone} for questions. Sincerely, {billing_manager_name}, {credentials}

Edit the bracketed fields before sending. Payer-specific reconsideration forms are often required — check the provider portal first.

How common is RARC M66?

Platform frequency
Pending ETL

Platform frequency ranks publish once the anonymized denial-rate pipeline reaches the publication threshold (strategy §12 Phase 2).

How QuickRCM handles RARC M66

QuickRCM reads RARC M66 alongside its paired CARC in the 835 LQ segment and routes the line to the correct worker queue with the right documentation already attached:

  • Denial routing rules tuned to the CARC+RARC pair — the paired combination tells QuickRCM which documentation the payer will accept.
  • Reconsideration template for this exact remark code pulls the supporting facts from the claim automatically.
  • Pre-submission scrubs that catch the preventable drivers surfaced on this page before the 837 leaves the clearinghouse.
See QuickRCM →Book a demo

Frequently asked questions — RARC M66

What does RARC M66 mean?

RARC M66 is an X12 Remittance Advice Remark Code. The official X12 definition is: "Our records indicate that we should be the third payer for this claim. We cannot process this claim until we have received payment information from the primary and secondary payers." It is supplemental to a Claim Adjustment Reason Code (CARC) on the same 835 line.

Which CARC is paired with RARC M66?

RARC M66 is most commonly paired with CARC 22, CARC 23. The CARC is the financial adjustment reason; the RARC is the informational remark. Fix the paired CARC first — the RARC usually clears with the corrected claim.

How do I resolve a RARC M66 remark on a remit?

Start from the root cause: Tertiary submission without prior EOBs. First step: Submit prior EOBs and resubmit. Because RARCs are supplemental, the resolution is almost always to address the paired CARC rather than appeal the RARC alone.

Where does RARC M66 appear on the 835 ERA?

RARC M66 is carried on the 835 Loop 2110 LQ segment alongside the CARC in the CAS segment of the same service line. The code and its X12 description also print on the paper EOB in the "Remark Code" or "Remark" column next to the corresponding denial or adjustment reason.

Is RARC M66 the same as ICD-10 code M66?

No. RARC M66 is a remittance-advice remark code published by X12 and carried on the 835. Any ICD-10 code with the same letters and digits is a diagnosis code on the 837 HI segment — a completely different code set maintained by the WHO/CMS. Use the transaction context (835 = RARC; 837 = ICD-10) to disambiguate.

Disclaimer

This page is operational reference for medical-billing professionals. It is not legal, clinical, or contractual advice. X12 code descriptors are maintained by the X12 External Code Lists; always verify against the current X12 release and the payer's own published policy before submitting or appealing a claim.