Official X12 description
“Requested additional information was not received.”
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 N85 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 16 | Claim/service lacks information or has submission/billing error(s). |
| CARC 226 | Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete. |
| CARC 227 | Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete. |
What RARC N85 actually means
RARC N85 pairs with CARCs 16/226/227 where records requests were unanswered. Submit records and resubmit.
Common root causes
- Records request went unanswered.
Prevention checklist
- Central ADR inbox with SLA enforcement.
Resolution & appeal strategy — step by step
Because RARC N85 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.
- 1Submit records and resubmit.
Sample reconsideration language referencing RARC N85
Edit the bracketed fields before sending. Payer-specific reconsideration forms are often required — check the provider portal first.
How common is RARC N85?
Platform frequency ranks publish once the anonymized denial-rate pipeline reaches the publication threshold (strategy §12 Phase 2).
How QuickRCM handles RARC N85
QuickRCM reads RARC N85 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.
Frequently asked questions — RARC N85
What does RARC N85 mean?
RARC N85 is an X12 Remittance Advice Remark Code. The official X12 definition is: "Requested additional information was not received." It is supplemental to a Claim Adjustment Reason Code (CARC) on the same 835 line.
Which CARC is paired with RARC N85?
RARC N85 is most commonly paired with CARC 16, CARC 226, CARC 227. 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 N85 remark on a remit?
Start from the root cause: Records request went unanswered. First step: Submit records 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 N85 appear on the 835 ERA?
RARC N85 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 N85 the same as ICD-10 code N85?
No. RARC N85 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.