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

RARC N706 Remark Code: Missing documentation

Reviewed by QuickIntell RCM Editorial Team · Last reviewed

Updated

Not an ICD-10 code. RARC N706 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 N706 (X12 Missing documentation). Commonly paired with CARC 16, CARC 125. RARC N706 accompanies documentation-required denials (often CARC 252, 227, or 251) and signals that the required documentation was not received.

Official X12 description

“Missing documentation.”

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 N706 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 16Claim/service lacks information or has submission/billing error(s).
CARC 125Submission/billing error(s). Usage: Refer to the 835 Healthcare Policy Identification Segment (loop 2110 Service Payment Information REF), if present.
CARC 227Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete.
CARC 251The attachment/other documentation that was received was incomplete or deficient.
CARC 252An attachment/other documentation is required to adjudicate this claim/service.

What RARC N706 actually means

RARC N706 accompanies documentation-required denials (often CARC 252, 227, or 251) and signals that the required documentation was not received. Resubmit via the payer's designated attachment channel (ADR portal, fax, PWK) with the correct claim reference.

Common root causes

  • ADR response not received by deadline.
  • Documentation sent to wrong address/fax/portal.

Prevention checklist

  • Central ADR inbox with SLA tracking.
  • Payer-specific attachment-channel matrix.

Resolution & appeal strategy — step by step

Because RARC N706 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. 1Resubmit documentation via the correct channel with the claim and control numbers.
  2. 2Appeal if documentation was submitted timely — include proof of submission.
Sample reconsideration language referencing RARC N706
[Provider letterhead] Re: Reconsideration — Claim #{claim_number}, CARC 16 / RARC N706 Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} The 835 remittance on {remittance_date} carried RARC N706: "Missing documentation." 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 N706?

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 N706

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

What does RARC N706 mean?

RARC N706 is an X12 Remittance Advice Remark Code. The official X12 definition is: "Missing documentation." It is supplemental to a Claim Adjustment Reason Code (CARC) on the same 835 line.

Which CARC is paired with RARC N706?

RARC N706 is most commonly paired with CARC 16, CARC 125, CARC 227, CARC 251, CARC 252. 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 N706 remark on a remit?

Start from the root cause: ADR response not received by deadline. First step: Resubmit documentation via the correct channel with the claim and control numbers. Because RARCs are supplemental, the resolution is almost always to address the paired CARC rather than appeal the RARC alone.

Where does RARC N706 appear on the 835 ERA?

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

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