RARC N61 Remark Code: Meaning & Resolution

Official X12 description

“Rebill services on separate claims.”

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 N61 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 CARC	What the CARC means
CARC 238	Claim spans eligible and ineligible periods of coverage.
CARC 239	Claim spans eligible and ineligible periods of coverage. Rebill separate claims.

CARCs CAQH CORE pairs with RARC N61

Under the CAQH CORE Payment and Remittance Uniform Use rule, a health plan that reports remark code N61 on an 835 should pair it with one of the 4 claim adjustment reason codes below, with the listed group code, for the business scenarios 2 (Missing, invalid or incomplete data from the submitted claim); 3 (Billed service not covered by the health plan). A remark paired outside this list is itself a compliance question to raise with the payer.

CORE-required CARC and group code combinations that include RARC N61
CARC	Group code	Scenario
16	CO or PI	2: Missing, invalid or incomplete data from the submitted claim
96	CO, PI or PR	3: Billed service not covered by the health plan
239	CO, PI or PR	3: Billed service not covered by the health plan
267	CO or PI	2: Missing, invalid or incomplete data from the submitted claim

Source: CAQH CORE-required Code Combinations v3.10.0 (2026-02), published by CAQH CORE (operating rules).

What RARC N61 actually means

RARC N61 instructs splitting services onto separate claims. Rebill per payer rules.

Common root causes

Payer requires service separation on distinct claims.

Prevention checklist

Claim-splitting rules per payer.

Resolution & appeal strategy — step by step

Because RARC N61 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.

1Split services and resubmit.

Sample reconsideration language referencing RARC N61

[Provider letterhead] Re: Reconsideration — Claim #{claim_number}, CARC 238 / RARC N61 Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} The 835 remittance on {remittance_date} carried RARC N61: "Rebill services on separate claims." 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 N61?

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 N61

QuickRCM reads RARC N61 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.

Prevent denials before submission →Manage RARC-driven denials Book a demo

Frequently asked questions — RARC N61

What does RARC N61 mean?

RARC N61 is an X12 Remittance Advice Remark Code. The official X12 definition is: "Rebill services on separate claims." It is supplemental to a Claim Adjustment Reason Code (CARC) on the same 835 line.

Which CARC is paired with RARC N61?

RARC N61 is most commonly paired with CARC 238, CARC 239. 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 N61 remark on a remit?

Start from the root cause: Payer requires service separation on distinct claims. First step: Split services 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 N61 appear on the 835 ERA?

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

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

RARC N61 Remark Code: Rebill services on separate claims

TL;DR