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

RARC N20 Remark Code: Service not payable with other service rendered on the same date

Reviewed by QuickIntell RCM Editorial Team · Last reviewed

Updated

Not an ICD-10 code. RARC N20 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 N20 (X12 Service not payable with other service rendered on the same date). Commonly paired with CARC 4, CARC 97. RARC N20 commonly accompanies a bundling or same-day edit (often CARC 97).

Official X12 description

“Service not payable with other service rendered on the same date.”

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 N20 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 4The procedure code is inconsistent with the modifier used or a required modifier is missing.
CARC 97The benefit for this service is included in the payment/allowance for another service/procedure that has already been adjudicated.
CARC 231Mutually exclusive procedures cannot be done in the same day/setting.

What RARC N20 actually means

RARC N20 commonly accompanies a bundling or same-day edit (often CARC 97). It states that the service cannot be paid in combination with another service billed on the same date. If the two services were genuinely distinct, the fix is a corrected claim with the correct distinct-procedural-service modifier and supporting documentation.

Common root causes

  • Same-day bundling edit between two procedures.
  • Two services that the payer treats as mutually exclusive on the same date.

Prevention checklist

  • NCCI PTP and MUE edits at charge entry; payer-specific same-day rules in the scrubber.

Resolution & appeal strategy — step by step

Because RARC N20 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. 1Work the underlying CARC (usually 97 or 231).
  2. 2Apply the correct distinct-procedural-service modifier and submit a corrected claim with documentation.
Sample reconsideration language referencing RARC N20
[Provider letterhead] Re: Reconsideration — Claim #{claim_number}, CARC 4 / RARC N20 Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} The 835 remittance on {remittance_date} carried RARC N20: "Service not payable with other service rendered on the same date." 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 N20?

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 N20

QuickRCM reads RARC N20 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 N20

What does RARC N20 mean?

RARC N20 is an X12 Remittance Advice Remark Code. The official X12 definition is: "Service not payable with other service rendered on the same date." It is supplemental to a Claim Adjustment Reason Code (CARC) on the same 835 line.

Which CARC is paired with RARC N20?

RARC N20 is most commonly paired with CARC 4, CARC 97, CARC 231. 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 N20 remark on a remit?

Start from the root cause: Same-day bundling edit between two procedures. First step: Work the underlying CARC (usually 97 or 231). Because RARCs are supplemental, the resolution is almost always to address the paired CARC rather than appeal the RARC alone.

Where does RARC N20 appear on the 835 ERA?

RARC N20 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 N20 the same as ICD-10 code N20?

No. RARC N20 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.