That’s the CO 226 denial code in a nutshell. It’s one of the most frustrating denials in medical billing because the underlying service is rarely the problem. The paperwork is. And according to Experian Health’s 2025 State of Claims survey, 41% of healthcare providers now face denial rates above 10%, with missing information and documentation errors ranking among the top preventable causes.
The good news? CO 226 is a soft denial. It doesn’t mean your claim is dead. It means the payer pressed pause and you still have a window to fix it.
This guide walks through exactly what the CO 226 denial code means, why it happens, how to resolve it efficiently, and how to keep it from disrupting your revenue cycle again.
CO 226 Denial Code – Description
The official Claim Adjustment Reason Code (CARC) definition for CO 226 reads:
“Information requested from the billing/rendering provider was not provided or not provided timely or was insufficient/incomplete.”
In simpler terms, the payer asked your practice for something clinical documentation, prior authorization details, updated patient records, or supporting attachments — and either didn’t receive it at all, received it past their deadline, or found what you sent inadequate for adjudication.
The “CO” prefix stands for Contractual Obligation. That classification matters because it means the financial responsibility for this denial falls on the provider, not the patient. You can’t pass a CO 226 charge to the patient’s balance. The obligation to correct and resubmit sits entirely with your billing team.
What Makes CO 226 Different from a Hard Denial
Here’s a distinction many billing teams overlook. CO 226 is a temporary denial sometimes called a soft denial. The payer isn’t rejecting the service as non-covered or medically unnecessary. They’re saying they can’t finish processing the claim without additional information.
That’s an important difference. A hard denial (like CO 50 for non-covered services) often requires a formal appeal with medical necessity arguments. CO 226, by contrast, typically resolves through straightforward document submission provided you act within the payer’s response window.
Remark Codes That Accompany CO 226
Payers never issue CO 226 in isolation. Per CARC guidelines, at least one Remittance Advice Remark Code (RARC) must accompany it. These remark codes tell you specifically what’s missing or insufficient.
For medical claims, the RARC pinpoints the exact documentation gap whether it’s an absent operative report, a missing prior authorization number, or incomplete clinical notes. For pharmacy claims, payers may use an NCPDP Reject Reason Code instead, serving the same purpose but formatted for pharmacy billing workflows.
Reading the remark code carefully is essential. It tells you precisely what the payer needs, which saves your team from guessing or worse, resubmitting with the same gaps and triggering another denial.
Reasons for Receiving Denial Code CO 226
The CO 226 denial code doesn’t appear randomly. It traces back to specific breakdowns in communication, documentation, or workflow. Understanding these root causes helps you target the right fix instead of chasing symptoms.
Failure to Respond to Payer Information Requests
Insurance companies routinely request additional details before finalizing a claim. They might need operative reports for a complex surgical procedure, clinical notes justifying medical necessity, or updated referral documentation. When your practice misses these requests entirely often buried in fax queues or overlooked in payer portals the claim stalls and eventually denies with CO 226.
This happens more often than most practices realize. A request sent via the payer’s electronic portal might not trigger a notification in your practice management system. Without a consistent process for monitoring these requests, they slip through the cracks.
Incomplete or Insufficient Documentation Submitted
Sometimes the practice does respond but the payer considers the submission inadequate. Perhaps the clinical notes lacked the specificity required to support the billed procedure. Maybe the operative report was uploaded but the relevant pages were missing. Or the documentation didn’t clearly establish medical necessity for the service rendered.
Payers evaluate documentation against their own adjudication criteria. What feels “complete” from the provider’s perspective may fall short of what the insurer requires to release payment.
Missing Prior Authorization Details
For services that require prior authorization, forgetting to include the authorization number on the claim is a common CO 226 trigger. On the CMS-1500 form, that number belongs in Box 23. When it’s absent, the payer can’t verify that the service was pre-approved — and they’ll request it before proceeding.
The same issue occurs when a prior authorization was obtained but expired before the service date, or when the authorization covered a different procedure than what was ultimately performed.
Outdated or Incorrect Patient Information
Stale data in your practice management system creates a cascade of problems. An old insurance ID number, a misspelled patient name, or an outdated date of birth can all prompt the payer to request corrections. When those corrections don’t arrive within the payer’s window, the claim denies under CO 226.
This is especially common with patients who visit infrequently. Their insurance details may have changed since the last encounter, and if your front desk doesn’t reverify coverage, the outdated information flows straight into the claim.
Delayed Response to Payer Deadlines
Timing matters as much as accuracy. Most payers set strict response windows often 30 to 60 days for submitting requested information. Even if you eventually provide everything they need, missing that deadline triggers CO 226 automatically. The payer’s system doesn’t evaluate the quality of a late response; it simply closes the request.
CO 226 Denial Code – Management & Resolution
A CO 226 denial code on your remittance advice isn’t the end of the road. This denial is designed to be resolved but speed and precision determine whether you recover the revenue or lose it to a timely filing expiration.
Analyze the Denial and Remark Code Together
Don’t look at CO 226 in isolation. The accompanying RARC tells you exactly what the payer found missing or insufficient. Read both codes together to understand the full picture before taking action. A denial paired with a remark code referencing clinical documentation requires a different response than one flagging a missing authorization number.
Verify the Patient’s Current Information
Before resubmitting anything, confirm that the patient’s demographics, insurance details, and policy status are accurate and current. Cross-check the information in your practice management system against the patient’s insurance card and the payer’s eligibility portal. Outdated records cause repeat denials even after you address the original documentation gap.
Gather and Organize the Missing Documentation
Once you’ve identified what’s missing, compile everything the payer requested. That might include clinical notes, operative reports, prior authorization confirmations, referral letters, or proof of medical necessity. Organize these documents clearly — label them, include the claim reference number, and ensure they meet the payer’s formatting requirements.
Resubmit Within the Payer’s Response Window
Attach the corrected or additional information and resubmit the claim. Pay close attention to the payer’s specific deadline. Most insurers give providers 30–60 days from the date of the initial request, though some contracts allow longer. Missing this window converts a resolvable soft denial into a permanent revenue loss.
Double-check that every required field on the claim form is complete before resubmitting. A second CO 226 denial on the same claim wastes time your team doesn’t have.
Track the Resubmitted Claim Through Adjudication
Resubmission isn’t the finish line. Monitor the claim’s status through your clearinghouse or payer portal. Confirm that the payer received the corrected submission and that adjudication is progressing. Proactive follow-up catches processing delays before they become problems.
File an Appeal When Necessary
In some cases, the payer may deny the resubmitted claim again either because they deem the documentation still insufficient or because the response arrived past their deadline. When that happens, a formal appeal is your next step. Include a detailed cover letter explaining the timeline, attach the original CO 226 remittance notice as evidence, and provide all supporting documentation in a single organized package.
Appeals succeed most often when they demonstrate that the provider acted in good faith, responded within a reasonable timeframe, and supplied all requested information.
How to Prevent Denial Code CO 226
Resolving a CO 226 denial takes time, labor, and attention that your team could spend on productive work. Prevention eliminates that drag entirely. These strategies address the root causes that trigger the denial in the first place.
Build a Reliable System for Monitoring Payer Requests
Most CO 226 denials start with a missed request. Payers send information requests through portals, electronic remittance files, faxes, and sometimes physical mail. If your practice doesn’t have a centralized system for capturing and tracking these requests, they get lost.
Assign ownership of payer correspondence to a specific team member or role. Set up alerts in your practice management system for incoming requests. Create a tracking log with deadlines so nothing falls through the cracks. The goal is simple: every payer request gets seen, assigned, and resolved before its expiration date.
Verify and Update Patient Information at Every Visit
Insurance details change. Patients switch employers, age into Medicare, add dependents, or lose coverage — often without informing your office. Running electronic eligibility verification before every encounter catches these changes before they contaminate the claim.
Make verification a non-negotiable part of your intake workflow. Confirm the patient’s name, date of birth, insurance ID, group number, and plan type at every visit. Thirty seconds at check-in prevents days of rework in your billing department.
Submit Complete Documentation with the Initial Claim
The most effective way to prevent CO 226 is to give the payer everything they need the first time. Attach operative reports for surgical claims. Include clinical notes that clearly establish medical necessity. Enter the prior authorization number in Box 23 of the CMS-1500. Complete every required field on the claim form.
When your initial submission is thorough, the payer has no reason to request additional information and CO 226 never fires.
Train Your Team on Payer-Specific Requirements
Different insurance companies have different documentation standards. What satisfies one payer might fall short for another. Your billing and coding staff needs to understand the specific requirements of each major payer in your mix — including their preferred documentation formats, submission deadlines, and authorization protocols.
Regular training sessions keep your team current on policy changes and new payer requirements. The cost of a monthly training hour is negligible compared to the revenue lost from preventable denials.
Conduct Pre-Submission Claim Audits
Before any claim leaves your office, run it through a quality check. Verify that all required fields are populated, supporting documents are attached, authorization numbers are present, and patient demographics match the payer’s records. Automated claim scrubbing tools can flag common gaps, but a human review adds an extra layer of protection for high-value claims.
Practices that implement pre-submission audits consistently report lower denial rates and faster reimbursement cycles. It’s a small investment of time that pays for itself many times over.
Bottom Line
The CO 226 denial code represents revenue that’s paused, not lost. The payer isn’t questioning whether your service was legitimate or covered. They’re simply waiting for information they need to finish processing the claim. That makes CO 226 one of the most fixable denials in medical billing — but only if your team responds quickly, completely, and within the payer’s deadline.
The pattern behind most CO 226 denials is predictable: missed payer requests, incomplete documentation on initial submissions, or outdated patient information flowing into claims unchecked. Every one of those causes is preventable with the right systems in place.
Practices that build reliable tracking for payer correspondence, verify insurance at every encounter, and submit thorough documentation from the start see CO 226 denials drop dramatically. Those that don’t end up spending far more time on rework than prevention would ever require.
If your practice is seeing CO 226 denials pile up or if denial management in general is consuming more of your team’s bandwidth than it should partnering with a specialized denial management services team can take that weight off your staff. Experienced denial specialists know exactly what each payer expects, track every request against its deadline, and resolve denials before they age into lost revenue.
The bottom line is straightforward: respond fast, respond completely, and build workflows that prevent the request from being necessary in the first place.
Frequently Asked Questions
Is CO 226 a hard denial or a soft denial?
CO 226 is a soft (temporary) denial. The payer isn’t saying the service is non-covered or unnecessary. They’re saying they can’t finish processing the claim without additional information. Once you provide what’s missing, the claim can be adjudicated.
Can I bill the patient for a CO 226 denial?
No. The “CO” group code designates this as a Contractual Obligation. The financial responsibility for resolving it sits with the provider, not the patient.
How long do I have to respond to a CO 226 denial?
Response windows vary by payer, but most insurers allow 30–60 days from the date of the information request. Always check the specific payer’s deadline on the remittance advice to avoid missing it.
What remark codes appear with CO 226?
CO 226 always comes paired with at least one Remittance Advice Remark Code (RARC) for medical claims or an NCPDP Reject Reason Code for pharmacy claims. These remark codes specify exactly what documentation or information the payer found missing or insufficient.
How is CO 226 different from CO 16?
CO 16 indicates that a claim lacks information needed for adjudication — typically missing data fields on the claim form itself. CO 226 is specifically about information the payer requested after initial submission that the provider failed to provide. CO 16 is a front-end error; CO 226 is a follow-up failure.
