Fast answer: Missing documentation.
How to use RARC N706
RARC N706 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
Recommended workflow
- Identify the document requested by the RARC, letter, or portal task.
- Confirm the submission channel, attachment control number, and deadline.
- Send an indexed packet with claim number, patient ID, DOS, provider, and line item clearly labeled.
- If the payer says it never received the records, attach proof of submission and resubmit through the required channel.
- 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 N706 mean?
Missing documentation.
Is N706 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 N706?
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.