Skip to main content
Call
CARC 226 · CO-226

CARC 226 Denial: Information requested from the Billing/Rendering Provider was not provided or w… — How to Fix and Appeal

Reviewed by QuickIntell RCM Editorial Team · Last reviewed

Updated

TL;DR

CARC 226 (X12 Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete). CARC 226 means the payer requested additional records from the provider (via a letter, fax, or portal message) and either did not receive them, received them late, or received an incomplete response.

Official X12 description

“Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete.”

Source: X12 Claim Adjustment Reason Codes. The X12 External Code Lists are the single authoritative source for every CARC descriptor — always verify against the current release before building a claim-scrub rule.

What CARC 226 actually means

CARC 226 means the payer requested additional records from the provider (via a letter, fax, or portal message) and either did not receive them, received them late, or received an incomplete response. The fix is to send the requested records before the deadline or, if the deadline has passed, appeal with proof of timely submission. Speed matters — many payers give only 30–45 days before converting the pend into a final denial.

Common root causes

  • Records request letter sent to the wrong address (practice moved, new billing agent, etc.).
  • Records were sent but the payer claims non-receipt.
  • Records were sent but did not include the specific items the payer requested.
  • Records-request queue not worked promptly and deadline passed.

Prevention checklist

  • Central records-request workqueue with SLA tracking (respond within 50% of the payer's deadline).
  • Verify the records submission address and method (fax, portal, PWK attachment on the 837) every quarter.
  • Include a cover sheet enumerating each requested item so the reviewer can confirm completeness.
  • Maintain proof of submission (fax confirmation, portal upload receipt) for every records response.

Appeal strategy — step by step

Most CARC 226 denials clear faster with the right remediation than with a formal appeal. Work the steps in order and escalate only when a lower-effort path has been ruled out.

  1. 1If records were submitted on time and the payer claims non-receipt, appeal with the submission receipt / fax confirmation / portal screenshot.
  2. 2If records were not submitted, send them now with an appeal letter referencing the original request and any mitigating circumstances.
  3. 3When a payer routinely loses records submissions, escalate to provider relations and move that payer to certified-mail for records responses.
Sample appeal-letter language for CARC 226
[Provider letterhead] Re: Appeal of CARC 226 — Claim #{claim_number} Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} On {remittance_date} this claim was adjusted with CARC 226: "Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete." We respectfully request reconsideration. The X12 External Code List definition of CARC 226 does not apply to this claim for the following reasons: 1. [Cite the clinical / coding / policy fact that rebuts the adjustment] 2. [Cite the supporting documentation attached — op note, EOB, LCD/NCD citation, NCCI edit indicator, modifier rationale] 3. [Cite the payer's own policy where applicable] Attached: {list supporting documents} Please process payment under the member's benefits. If additional information is required, contact the billing office at {provider_phone} or {provider_email}. Sincerely, {billing_manager_name}, {credentials}

Edit the bracketed fields before sending. This template is a starting point; a payer-specific appeal form may still be required — check the provider portal first.

Payer-specific notes

Payer-specific behavior for CARC 226 publishes here as the QuickIntell anonymized denial ETL ingests sufficient volume. In the meantime, consult the payer directory for the relevant provider manual and appeal form.

How common is CARC 226?

Search demand rank
#22

Out of 306 seeded CARCs, ranked by combined US monthly search volume for "CARC 226", "CO-226 denial", and "denial code 226".

Platform frequency
Pending ETL

Platform frequency ranks publish once the anonymized denial-rate pipeline reaches the publication threshold (strategy §12 Phase 2).

How QuickRCM prevents CARC 226

QuickRCM catches the root causes above before the 837 leaves the clearinghouse:

  • Claim-scrub rules fire on every root cause listed above — the scrub references the same X12 CAS segment logic that drives the denial, so what the payer checks, QuickRCM checks first.
  • When a denial lands, QuickRCM routes it to the correct worker with the documentation bundle already attached (op note, LCD citation, modifier rationale, EOB, primary 835).
  • Appeal templates tuned to each CARC (including this one) pull the supporting facts from the claim and fill the bracketed fields automatically.
See QuickRCM →Book a demo

Frequently asked questions — CARC 226

What does CARC 226 mean?

CARC 226 is an X12 Claim Adjustment Reason Code. The official definition is: "Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete." In plain English, the payer is telling you cARC 226 means the payer requested additional records from the provider (via a letter, fax, or portal message) and either did not receive them, received them late, or received an incomplete response. The fix is to send the requested records before the deadline or, if the deadline has passed, appeal with proof of timely submission. Speed matters — many payers give only 30–45 days before converting the pend into a final denial.

How do I resolve a CARC 226 (CO-226) denial?

Start with the most common root cause: Records request letter sent to the wrong address (practice moved, new billing agent, etc.). First step: If records were submitted on time and the payer claims non-receipt, appeal with the submission receipt / fax confirmation / portal screenshot. See the full remediation and appeal checklist on this page before filing a formal appeal.

Is CARC 226 patient responsibility?

No — CARC 226 is typically carried under CO (Contractual Obligation) or OA (Other Adjustment), which means it is the provider's responsibility, not the patient's. Do not bill the patient unless the 835 CAS group code is PR.

What does CARC 226 look like on an EOB or 835 remittance?

On the 835 ERA, CARC 226 appears in Loop 2110 CAS segment as "CAS*CO*226*{amount}". On a paper EOB the same code prints in the Adjustment/Denial Reason column with the X12 description: "Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete." — usually paired with one or more RARC remark codes in the same remittance line for additional context.

Which RARC is paired with CARC 226?

CARC 226 is commonly observed with RARC N4, N11, MA130. The RARC narrows the reason — for example, pointing at a missing modifier, an LCD citation, or a specific policy. Fix the underlying CARC first; the RARC usually clears with the corrected claim.

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.