N706 remark code: missing documentation, claim review and resubmission

The N706 remark code tells a billing team that required documentation is missing. It does not, by itself, identify which record is absent or explain the entire payment decision. The claim’s group code, Claim Adjustment Reason Code (CARC), other Remittance Advice Remark Codes (RARCs), and payer message provide the context needed to determine what happened.

Do not automatically rebill the same claim. Identify the requested record, confirm whether it existed for the date of service, and check the payer’s submission instructions. The correct action may be a document response, corrected claim, reconsideration, or appeal.

What does the N706 remark code mean?

The official RARC list defines N706 as “Missing documentation.” A RARC supplements a CARC or communicates information about remittance processing. Although billing teams may call N706 a denial code, technically it is a remark code rather than a standalone denial reason.

CMS instructs Medicare contractors to maintain current CARC and RARC lists using the official ASC X12 code set. The CMS remittance-code update also explains that these codes supply adjustment or policy information on remittance advice transactions. Read N706 with the rest of the ERA or EOB before deciding how to work the account.

Read the complete remittance before requesting records

Start at the affected service line. Confirm the group code, CARC, N706, other RARCs, adjustment, claim status, and payer narrative. Check for a separate letter, portal notice, fax, or documentation request.

The same remark can appear with different claim outcomes. The payer may need records to complete review, may have denied payment after no response, or may expect a document with the claim. N706 alone does not establish the appeal route, deadline, or patient responsibility.

What documentation may be missing?

The absent material depends on the service and payer policy. Common examples include:

• A signed progress note or encounter note supporting the service billed
• An order, referral, certification, recertification, or plan of care
• An operative, procedure, imaging, laboratory, pathology, or therapy report
• A treatment plan, medication record, test result, or medical-necessity support
• Proof of delivery, equipment records, supplier documentation, or a completed form
• Records from a referring clinician, facility, or other entity involved in the service

Do not send a generic chart dump unless requested. Match the submission to the patient, claim, service line, and date of service, and include the records needed to support the billed care and relevant coverage conditions.

CMS guidance on medical record documentation requirements explains that Medicare may deny payment when records are absent, incomplete, illegible, or insufficient to verify coverage, coding, billing, or the level of care. Commercial and Medicaid plans can have different documentation rules, so use the policy that applies to the payer and date of service.

Why N706 appears on a remittance

Some N706 cases begin before submission. A required report may not be attached, a document may remain unsigned, or the record may sit outside the billing queue. Payer notices can also reach an outdated correspondence address.

Other cases are response failures: the notice was missed, the submission was late or unreadable, or the payer could not match it to the claim. A record in the EHR is still missing to the payer if it never reaches the correct review channel.

How to resolve an N706 remark code

Use a documented workflow rather than resubmitting from the denial queue without review:

1. Read the full ERA or EOB. Capture the CARC, group code, N706, other RARCs, affected lines, adjustment, and payer instructions.
2. Locate the request. Check the payer portal, correspondence queue, fax logs, mail, clearinghouse attachments, and account notes for a documentation notice.
3. Identify the exact record. Confirm the document type, service line, date of service, submission deadline, accepted channel, and any required reference number or coversheet.
4. Verify the documentation. Make sure the record belongs to the patient and encounter, is complete and legible, supports the billed service, and contains required signatures or authentication.
5. Reconcile the claim. Compare the documentation with the procedure, diagnosis, modifiers, units, provider, and service location. Do not alter codes unless the record and applicable rules support the change.
6. Choose the payer’s correct pathway. Submit requested records, send a corrected or replacement claim, request reconsideration, or appeal based on the remittance and payer instructions.
7. Preserve proof and follow up. Save the confirmation number, transmission report, submitted packet, date, and next follow-up point. Record the root cause for prevention.

RCMGen’s medical billing services apply the same claim-level reconciliation before another transaction is sent.

Submit documents, correct the claim, or appeal?

Submit records when the payer provides a channel for medical-review material. Follow the notice exactly. A documentation response is not the same as a corrected claim, and attaching records to a duplicate may not satisfy the request.

Use a corrected or replacement claim when the original data were inaccurate and the record supports the change, such as a wrong procedure, modifier, units, or provider. Follow the payer’s replacement process and link it to the original claim. RCMGen’s medical coding services emphasize documentation-supported code selection rather than changing data solely to obtain payment.

Request reconsideration or file an appeal when the original claim was accurate, the required documentation was submitted or is now available, and the payer’s determination appears inconsistent with its policy. Check the denial notice for the permitted route and deadline. Do not assume N706 itself authorizes resubmission or prohibits an appeal.

Medicare additional documentation requests need prompt routing

For Medicare Fee-for-Service medical review, an Additional Documentation Request seeks records needed to support payment. CMS’s ADR guidance tells providers to submit the necessary documentation and explains that response periods vary by review type and contractor.

That guidance currently describes 45-calendar-day response periods for specified MAC, SMRC, and RAC reviews and 30-calendar-day periods for specified UPIC reviews. Do not apply them to other plans or every Medicare communication; use the actual request and current rules.

How to prevent repeat N706 issues

Route requests into a monitored queue with an owner, due date, payer reference, and escalation path. Keep correspondence addresses current, monitor portals, and connect each request to the correct patient and claim.

Before billing, confirm that required orders, reports, signatures, certifications, and attachments are present. Trend N706 by payer, service, missing-record type, and root cause. Denial management services are most useful when findings produce specific workflow changes.

How RCMGen approaches N706 resolution

RCMGen begins with the complete payer response and claim history, identifies the missing item, and checks the record for completeness, signatures, service support, and consistency with the claim before choosing the response channel.

Each outcome is classified as a record submission, correction, reconsideration, appeal, or valid adjustment. Recurring causes are routed to the team that can prevent the same gap.

Frequently asked questions about the N706 remark code

Send the right record through the right channel

N706 is a prompt to find the missing evidence, not a reason to resend the same transaction blindly. Identify what the payer requested, verify that the record supports the service, and use the stated response path.

Once the gap is clear, submit the records, correct supported claim errors, or challenge an incorrect determination. Keeping proof of submission and documenting the root cause makes the resolution defensible and reduces repeat documentation denials.