CO-226 Denial Code: How to Fix Missing Provider Information

A CO-226 adjustment tells the billing team that the payer did not receive usable information owed by the billing or rendering provider. That identifies who owed the response, not what kind of information is missing. It does not prove a provider name or NPI was wrong, prove the claim was wrong, or tell the team how to respond.

Start with the complete remittance and its required remark code. Then compare the payer's request with the claim that was actually sent and the verified provider record. That sequence prevents a vague adjustment from turning into an inaccurate correction.

What CO-226 means

X12 defines CARC 226 as information requested from the billing or rendering provider that was not provided, was late, or was insufficient or incomplete. X12 also requires at least one non-alert remark or reject reason code with CARC 226. That companion code matters because CO-226 does not name the missing information.

Read the group code, CARC, RARC, adjustment amount, and payer message together. The claim remit-code guide explains how those parts fit. CMS notes that a CO group code assigns the unpaid amount to the provider, while a RARC can add the detail needed to fix the request. Do not move a provider-information adjustment to the patient.

CO-226 is different from PR-227

CO-226 concerns information requested from the billing or rendering provider. PR-227 concerns information requested from the patient, insured person, or another responsible party. Use the PR-227 member-information workflow when the payer needs an insurance, employment, accident, or other member-side detail. If the owner of the information is unclear, ask the payer to clarify before contacting anyone.

The missing item may not be a single claim field

CMS's professional-claim training shows how many provider details can appear on a CMS-1500 or 837P, including billing, rendering, ordering or referring, service-facility, tax-ID, and NPI information. The payer's remark code and written request must identify which detail matters. The payer may instead be asking for documentation, an enrollment or affiliation correction, a provider-file match, or another separately submitted response.

Payer-specific examples show that breadth. Ohio Medicaid describes CO-226 with N767 for enrollment and affiliation denials, while Louisiana Medicaid describes CO-226 with N831 for incomplete provider revalidation affecting pharmacy, prescriber, billing, rendering, referring, and ordering records. Those examples govern those programs; they do not establish a universal CO-226 pairing.

Real remittances can also be incomplete. MassHealth training shows a CO-226 example without a RARC when one NPI maps to multiple service locations and the payer cannot route the claim. A missing companion message does not make the cause guessable. Get the payer's exact edit text and correction instructions.

Route the response by the companion message

Use the current X12 RARC list and the named payer's instructions to choose the response lane.

• Documentation message: assemble only the requested record, confirm it is complete and tied to the claim, and use the payer's stated delivery method.
• N516 or N521: reconcile the submitted identifier or provider information with the payer's provider file before changing the claim.
• N767, N831, or explicit enrollment text: resolve enrollment, affiliation, or revalidation under that payer's rules before rebilling.
• N517: submit a new claim with the requested information, as the current message directs.
• No usable non-alert RARC or reject reason: obtain the exact request, response deadline, accepted delivery path, and payer reference number before changing anything.

The six-step recovery workflow

Step 1: Reconstruct the adjustment from the full remittance

Open the claim and remittance details the billing team can see. Record the patient, payer and plan, claim number, service date, adjusted line, billed and paid amounts, group code, CARC 226, every RARC, and any claim-level message. If a needed detail is missing, obtain the complete 835 or paper remittance before choosing an action.

Step 2: Recover the payer's exact request

Use the remark code, payer message, portal correspondence, and prior request to write the gap in plain language. If the request remains vague, ask five questions: What exact information is missing? Which provider role does it concern? Was the original information missing, invalid, or inconsistent? Where must the response be sent? What deadline and correction method apply?

• Save the payer's answer, reference number, date, and representative or portal source.
• Ask whether the response is claim data, a separate document, an enrollment update, or another payer process.

Step 3: Identify the provider role and source record

Separate the billing provider from the professional who rendered, ordered, referred, or supervised the service and from the service facility. CMS places the rendering-provider NPI and ordering or referring provider information in distinct claim locations. Verify the value against the pharmacy's current provider, enrollment, and service-location records before changing the claim.

Step 4: Compare the submitted claim with the verified record

Inspect the claim image or 837P data that the payer received. Compare the requested field with the verified source record and note whether it was blank, formatted incorrectly, assigned to the wrong provider role, inconsistent with the service location, or correct as submitted. A valid source record does not prove the transmitted claim matched it.

Step 5: Use the payer's supported response path

Choose the path that matches the verified cause and payer instructions. Correct a claim-data error through the payer's corrected-claim process. Send separately requested material through the stated portal, fax, or other approved route. Fix an enrollment or provider-file mismatch before rebilling. Appeal with the original claim and source evidence when the payer's request conflicts with its own record or policy.

Providing the missing information does not guarantee payment. Coverage, eligibility, coding, authorization, documentation, provider enrollment, and timely-filing rules can still affect the claim.

Step 6: Verify the next remittance and close the loop

Track the payer's confirmation or corrected claim number, then inspect the next remittance. Confirm whether CO-226 cleared, whether another adjustment replaced it, and whether the submitted provider information remained intact. If the same gap repeats, fix the source workflow rather than correcting claims one at a time.

The CO-226 repair record

Answer these eight questions in the claim note or billing work queue. Another team member should be able to reproduce the decision without repeating the investigation.

1. Which claim, service line, payer, plan, and service date received CO-226?
2. What was the original request date, exact requested item, RARC or reject reason, and payer edit text?
3. Which provider role, identifier, location, document, or enrollment record did the payer request?
4. What did the submitted claim contain, and what did the verified source record show?
5. Was the cause claim data, separately requested material, enrollment, or a payer-record mismatch?
6. Which payer response path, submission channel, deadline, and payer reference number applied?
7. What was sent or changed, how many pages or records were included, and which confirmation or correspondence ID proves receipt?
8. What is the follow-up date, owner, next-remittance result, and prevention change?

How to prevent repeat adjustments

Use the pharmacist credentialing and enrollment guide to keep provider records current, then connect repeat CO-226 findings to the claim field, template, integration, or payer file that created the mismatch.

• Maintain one verified source for each billing, rendering, ordering, referring, and service-facility record used on claims.
• Review provider enrollment and payer-file changes before the effective date reaches claim templates.
• Track CO-226 by payer, remark code, provider role, location, and source system so the team can fix the recurring handoff.

DocStation supports claim customization for billing and rendering providers, ordering providers, and service facilities, plus claim-level notes and a timeline of changes. Keep the CO-226 repair record with the broader pharmacy revenue cycle management workflow so the verified provider record stays connected to the correction and its outcome.