DFDenialFix Desk

RARC remark code guide

BCBS RARC N705 — Incomplete or invalid documentation

What RARC N705 means with BCBS denials, common paired CARCs, evidence checklist, and provider next steps.

Fast answer: Incomplete or invalid documentation.

How to use RARC N705

RARC N705 should be read with the CARC and group code on the same claim or service line. For BCBS denials, the remark often tells you whether the next move is a corrected claim, attachment response, COB update, authorization proof, or appeal packet.

Common paired CARCs

CO-251CO-226

Recommended workflow

  1. Identify the document requested by the RARC, letter, or portal task.
  2. Confirm the submission channel, attachment control number, and deadline.
  3. Send an indexed packet with claim number, patient ID, DOS, provider, and line item clearly labeled.
  4. If the payer says it never received the records, attach proof of submission and resubmit through the required channel.
  5. If records were complete and timely, appeal with proof of receipt and a concise document map.

Evidence checklist

  • Requested records
  • Attachment control number
  • Proof of submission
  • Denial/RFI letter
  • Claim image
  • Document index

FAQ

What does RARC N705 mean?

Incomplete or invalid documentation.

Is N705 enough to appeal a BCBS denial?

No. Pair the RARC with the CARC, group code, EOB text, claim line, and plan rule. The RARC explains the missing detail or context; the CARC explains the adjustment reason.

What should I attach for N705?

Start with Requested records, Attachment control number, Proof of submission, Denial/RFI letter. Add only the records that answer the specific remark code and denial reason.