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

RARC N381 Remark Code: Alert: Consult our contractual agreement for restrictions/billing/payment infor…

Reviewed by QuickIntell RCM Editorial Team · Last reviewed

Updated

Not an ICD-10 code. RARC N381 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 N381 (X12 Alert: Consult our contractual agreement for restrictions/billing/payment information related to th…). Commonly paired with CARC 45, CARC 96. RARC N381 is an informational alert pointing the provider back to the contractual agreement for the specific restriction or payment rule that triggered the CARC.

Official X12 description

“Alert: Consult our contractual agreement for restrictions/billing/payment information related to these charges.”

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 N381 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 45Charge exceeds fee schedule/maximum allowable or contracted/legislated fee arrangement.
CARC 96Non-covered charge(s).
CARC 97The benefit for this service is included in the payment/allowance for another service/procedure that has already been adjudicated.

What RARC N381 actually means

RARC N381 is an informational alert pointing the provider back to the contractual agreement for the specific restriction or payment rule that triggered the CARC. Identify the contract clause and confirm claim compliance; the answer is in the contract, not in the payer's portal.

Common root causes

  • Contract clause governs this service's billing or payment.
  • Non-standard contract terms apply.

Prevention checklist

  • Contract-library access for billing teams; clause-level summaries.

Resolution & appeal strategy — step by step

Because RARC N381 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. 1Pull the contract clause cited and reconcile with the billed service.
  2. 2Dispute only if the clause was misapplied.
Sample reconsideration language referencing RARC N381
[Provider letterhead] Re: Reconsideration — Claim #{claim_number}, CARC 45 / RARC N381 Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} The 835 remittance on {remittance_date} carried RARC N381: "Alert: Consult our contractual agreement for restrictions/billing/payment information related to these charges." 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 N381?

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 N381

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

What does RARC N381 mean?

RARC N381 is an X12 Remittance Advice Remark Code. The official X12 definition is: "Alert: Consult our contractual agreement for restrictions/billing/payment information related to these charges." It is supplemental to a Claim Adjustment Reason Code (CARC) on the same 835 line.

Which CARC is paired with RARC N381?

RARC N381 is most commonly paired with CARC 45, CARC 96, CARC 97. 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 N381 remark on a remit?

Start from the root cause: Contract clause governs this service's billing or payment. First step: Pull the contract clause cited and reconcile with the billed service. Because RARCs are supplemental, the resolution is almost always to address the paired CARC rather than appeal the RARC alone.

Where does RARC N381 appear on the 835 ERA?

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

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