Why CO-226 Denials Are Silently Writing Off Your Practice’s Revenue

1. The payer request went to the wrong place

A payer may have an outdated correspondence address, fax number, contact, or portal workflow.

The billing office may honestly believe that no request was received.

But from the payer’s perspective, the request was sent.

What goes wrong: The practice never sees the request.

Why it happens: Payer contact information is outdated or correspondence is not centrally monitored.

How to prevent it: Maintain a payer correspondence log and verify where medical-record and documentation requests are delivered.

2. The request was received but nobody owned it

This is one of the most dangerous workflow gaps.

A fax comes in. An electronic request comes through on a payer website. A letter is entered into the EHR.

Everyone takes it for granted that someone else will do it.

No one does.

Problem: The deadline is missed.

Consequences: The claim is put into denied status after being flagged “waiting for information.”

How to prevent it: Every payer request should have an owner, deadline, status, and documented submission.

3. The records were submitted late

Sometimes the practice knows exactly what the payer wants but cannot collect the records quickly enough.

This can happen when documentation must come from multiple departments or providers.

Where something that should have been responded to within a few days turns into a two-week process.

Prevention: Develop an escalation policy for urgent matters relating to payers.

4. The answer was incomplete

Submitting “something” does not mean responding to the inquiry.

For example, a payer may request documentation covering a specific date range, but the practice sends only one progress note.

The staff member may mark the denial as worked.

The payer may still consider the response incomplete.

That can produce another denial or delay adjudication.

5. The wrong documents were submitted

A payer request can be specific.

If the payer requests clinical documentation supporting a billed service and the billing team sends a generic claim form, the response may not solve the underlying issue.

The question should always be:

Does the documentation directly answer the payer’s request?

6. The request was sent to the wrong payer department

Some payer requests have a specific submission destination.

A practice may send records to a general claims address when the request directs them to a medical-review unit, portal, fax number, or other designated channel.

The documents may technically have been sent, but not to the place responsible for processing them.

7. There was no confirmation trail

A fax confirmation, portal receipt, mailing record, or electronic transmission confirmation can become extremely important if the payer later says the records were never received.

Without proof, the practice may have difficulty demonstrating that it responded within the required timeframe.

Best practice: Save the submission evidence with the claim or denial record.

CO-226 vs. CO-16 vs. CO-252: Don’t Treat Them as the Same Denial

One of the most useful ways to improve denial management is to stop grouping every documentation-related denial into one bucket.

X12’s official code list distinguishes 226 from these other reason codes.

That distinction is operationally useful.

If your dashboard lumps CO-16, CO-226, and CO-252 together as “missing information,” management loses the ability to see which process is actually failing.

Why CO-226 Denials Are More Expensive Than They Look

The amount shown on the denial is only one part of the cost.

Suppose a practice receives a $350 CO-226 denial.

The financial exposure may include:

• $350 delayed or potentially lost reimbursement
• Research time spent by employees on the request
• Time spent retrieving the medical record
• Follow-up by billing employees
• Appeal/reopening effort.
• Phone calls to payer.
• A/R aging.
• Management review.
• Write-off potential if the problem cannot be fixed.

Now multiply that by dozens or hundreds of claims.

A denial that appears small at the individual claim level can become significant at the practice level.

Example of revenue leakage

Let us look at an example that has the following features:

Total claims of 2,000 per month

2% of the total are CO-226

The average allowed amount per claim is $300

This results in:

40 claims × $300 = $12,000 per month in potential reimbursement

$12,000 × 12 = $144,000

Keep in mind that this is just an example and does not represent the benchmark. Revenue exposure will vary based on many factors.

The important point is the math:

Few denials x lots of claims x slow follow up = Revenue leakage.

What the Latest Denial Data Says About the Bigger Problem

CO-226 should not be viewed in isolation.

The broader healthcare revenue cycle is already dealing with substantial denial pressure.

The HFMA has observed that initial claim denial rates have increased to 12% in 2024 using the statistics provided by Kodiak Solutions in their 2025/2026 report. The HFMA also points out that an increase in denials reduces the efficiency in payment process.

MGMA Stat poll held in January 2026 according to the survey by the MGMA revealed that denials and appeals constituted the largest revenue cycle leakage in health care institutions with 48% followed by front-end process (23%), billing and collection (14%) and coding (13%).

There is another important data point from CMS.

For FY 2025, CMS reported a 6.55% estimated improper payment rate for Medicare Fee-for-Service, representing approximately $28.83 billion in estimated improper payments. The Part B provider category had an estimated improper payment rate of 8.44%, or about $9.62 billion.

These figures do not mean that all improper payments are CO-226 denials. They are different measurements.

But together, they demonstrate why documentation, claim accuracy, and payment integrity deserve active management rather than passive monitoring.

The CO-226 Issue: Your Denial Rate Is Just the Tip of the Iceberg

A process may have a satisfactory denial rate while suffering from a CO-226 issue at the same time.

Why is that?

Because denial statistics can conceal:

• Specific payer problems
• Specific providers
• Specific locations
• Specific CPT categories
• Documentation-related patterns
• High-dollar claims
• Repeat requests
• Aging denials
• Unworked payer correspondence

For example:

This is a much stronger management view than simply reporting:

“We had 37 denials this month.”

How to Prevent CO-226 Denials Before They Happen

The best CO-226 denial is the one that never reaches the denial queue.

I. Payer Request Owner

Every request must have the following information:

• Owner
• Date Received
• Due Date
• Payer
• Claim Number
• Documents Requested
• Method of Transmission
• Date of Transmission
• Reference Number
• Follow-Up Date
• No request must be an orphan in its inbox.

2. Set up the documentation request tracking system

Use a spreadsheet, RCM software, worklist, or tickets.

Must at least include:

Received -> Assigned -> In process -> Records ready -> Submitted -> Confirmed -> Reprocessed -> Resolved

This helps to track aging.

3. Monitor payer portals

Not every important payer communication will necessarily arrive through the same channel.

Depending on the payer, requests may appear through:

• Portal notifications
• Electronic correspondence
• Fax
• Mail
• Clearinghouse workflows

Your practice needs a defined process for checking the channels it uses.

4. Establish an escalation rule

For example:

• Day 0: Request received

• Day 1: Assigned
• Day 2–3: Records gathered
• Day 4: Quality check
• Day 5: Submission
• Follow-up: Based on payer instructions
• Actual timelines must accommodate the payer’s deadline.

The philosophy is clear:

• Do not find out too late at the deadline that there is a missing record.

5. Audit documentation completeness

Medical record response needs to be verified prior to submission.

Questions:

• Are all requested dates included?
• Are all requested providers included?
• Are signatures where appropriate?
• Have diagnostic results been provided where appropriate?
• Is the documentation legible?
• Does the documentation respond to the payer’s request?
• Has the claim number or reference been provided correctly?

Under What Circumstances Should a Practice Consider Outsourcing Denial Management?

• If the denial management is constantly taking up capacity or if it is difficult to track payer requests to closure, then outsourcing should be considered.

These red flags should make you think twice:

• Month over month increase in CO-226 denials.
• Requests from payers sitting and not being worked.
• Increasing A/R > 90 days.
• Unable to determine the status of denied claims.
• Lack of ownership in document request process.
• Appeal deadline requirements not met.
• Same denial reasons kept resurfacing.
• Management has denial reports but no root cause analysis.
• Billing personnel take up too much time on old A/R.
• Providers are repeatedly asked for the same documentation.

The goal should not be outsourcing for the sake of outsourcing.

The goal is to create a more controlled revenue cycle.

A structured Medical Billing and Coding Services workflow can include denial follow-up, documentation tracking, payer communication, and A/R management when those capabilities are part of the service arrangement.

What a Strong CO-226 Denial Management Process Looks Like

A mature workflow connects denial management with the rest of the revenue cycle.

• Front end→ Accurate patient and insurance information

• Clinical documentation→ Complete documentation

• Coding→ Correct coding based on documentation

• Claim submission→ Clean claim

• Correspondence from payer→ Captured and addressed

• Denials Management→ CO-226 identified and handled

• A/R follow-up→ Payment tracked

• Analytics→ Root cause identified

• Process improvement→ Repeat denial reduced

This is why CO-226 should not be assigned exclusively to “the billing department.”

The denial may originate somewhere else in the workflow.

CO-226 Denial Check List for Billers

When you get a CO-226 in your workflow, use this check list:

Claim Review:

• Patient Name & Claim Number
• Date of Service
• Payer
• CARC 226
• Read all remark codes
• Check denied amount

Request review

• Locate original payer request
• Identify request date
• Identify response deadline
• Identify exact requested information
• Confirm where the response must be sent

Documentation review

• Collect all documents required
• Services dates verification
• Check signatures/proof of evidence
• Check legibility
• Check against the request

Resolution

• Send through proper portal
• Get proof of receipt
• Apply payer’s correction/reopening/appeals process
• Set follow up
• Monitor reprocessing
• Process post-payment properly

Prevention

• Note the cause of the issue
• Payer or workflow issue categorization
• Recognition of repeat patterns
• Increased frequency of recurring issues

Example for CO-226: Why a Claim for $500 is Really Worth More than $500

Hypothetical outpatient facility.

The doctor provides treatment which is covered and documented.

The claim is submitted correctly.

Later, the payer requests additional records.

The request enters a shared fax inbox but is not assigned.

The deadline passes.

The claim receives CO-226.

The billing team discovers the denial 25 days later.

They locate the records, submit them, and request reprocessing.

Now the practice has incurred:

• Delayed reimbursement
• Multiple billing touches
• Medical-record retrieval time
• Denial follow-up time
• Additional A/R aging
• Management supervision

The practice can recoup the initial payment if it is eventually paid by the payor.

However, the process still didn’t work properly.

This is why only recovery is not enough.

A well-designed denial management system will consider:

“Did we get paid?”

A better one also asks:

“Why did we need to fight for payment in the first place?

How CO-226 Affects Revenue Cycle Management

CO-226 can influence several core RCM metrics.

Clean claim rate

Documentation and information issues that recur may suggest deficiencies prior to or during claims processing.

Denial rate

CO-226 should be tracked separately rather than being included in an “other” category.

Days in A/R

Every delayed claim has the potential to extend the collection cycle.

A/R over 90 days

Older CO-226 claims deserve special attention because recovery becomes more difficult as deadlines approach.

Net collection rate

Repeated unresolved denials can affect how much of the collectible revenue is actually realized.

Timely filing and appeal performance

Missed payer requests can eventually create additional deadline risk.

Underpayment trends

A documentation-related denial may also obscure broader payer behavior if denial and payment variance data are not analyzed together.

HFMA recommends standardized denial metrics because organizations need consistent data to identify the operational causes behind denials. Its guidance specifically highlights initial denial volume and charges as useful claim-integrity indicators.

The Most Important CO-226 Metric Isn’t Just the Denial Rate

Consider two practices.

Practice A

• 100 CO-226 denials
• 90 recovered
• 10 permanently lost

Practice B

• 40 CO-226 denials
• 20 recovered
• 20 permanently lost

Practice B has the lower denial count.

But Practice A may have the better process.

That is why practices should measure:

Denial volume + denial dollars + recovery rate + time to resolution + repeat rate

A simple dashboard could look like this:

That gives management a much clearer picture of revenue leakage.

Don’t Automatically Write Off a CO-226

The presence of a CO group code should not lead staff to blindly post a write-off without reviewing the claim and payer instructions.

The first question is:

Can the requested information still be supplied and the claim appropriately reprocessed?

If yes, pursue the appropriate payer process.

If the practice failed to respond and the payer’s applicable rules no longer permit recovery, the financial adjustment may ultimately become a write-off.

But that should be the result of a documented resolution process not the default response to seeing CO-226.

What If the Payer Says the Records Were Never Received?

This is where documentation of your own billing workflow becomes critical.

If your team has:

• Fax confirmation
• Portal confirmation
• Submission ID
• Date/time stamp
• Copy of submitted records
• Payer correspondence
• Reference number

you have an evidence trail.

For Medicare, CMS states that supporting documentation should be included with a redetermination request when it supports the appeal, and the first-level redetermination generally has a 120-day filing window from receipt of the initial determination.

For commercial payers, follow the specific payer’s rules.

Never assume that a Medicare deadline automatically applies to a commercial plan.

How Technology Can Reduce CO-226 Risk

Technology can help, but software alone does not fix a broken workflow.

Some of the helpful capabilities would be:

• Automatic work queues
• Payer portal watch
• Assignment of tasks
• Deadline reminders
• Document indexing
• Attachment of documents electronically
• Submission tracking
• Monitoring of claim status
• Denial codes
• A/R dashboards
• Root cause reporting

What is really crucial is accountability.

An alerting system without assignment of accountability just creates more alerts.

The correct flow is:

Request received – automatically assigned – deadline visible – document gathering – submission – follow-up planned

What Practices Should Audit Every Month

A monthly CO-226 review can be surprisingly revealing.

Take a sample of denied claims and ask:

1. How many had an actual payer request?
2. How many requests were received by the practice?
3. How many were assigned?
4. How many were answered before the deadline?
5. How many responses were incomplete?
6. How many had proof of submission?
7. How many were successfully reprocessed?
8. How many became write-offs?
9. Which payer produced the most CO-226 claims?
10. What was the most common root cause?

After three months, patterns should begin to emerge.

Maybe one payer produces most of the denials.

Maybe one provider’s documentation is repeatedly requested.

Maybe the problem is a fax number.

Maybe requests are sitting in a shared inbox.

Maybe the medical records department needs a defined turnaround process.

That is the difference between denial reporting and denial prevention.

The Bottom Line on CO-226 Denials

The CO-226 Denial Code is easy to underestimate because its description sounds administrative.

It isn’t.

Every unanswered payer request creates a potential break in the revenue cycle.

This solution does not merely entail sending the records after the claim denies. It entails creating a process that will allow for capturing payer requests, ownership, deadline, verification of documentation, proof of submission, tracking the claims through adjudication, and identifying root cause analysis.

The process involves the following steps:

Capture the request → understand the request → respond comprehensively → submit properly → prove submission → follow up → stop repetition.

In such a scenario, CO-226 will not be a difficult problem, but a part of the revenue cycle that needs to be managed effectively.

For practices considering revenue cycle management solutions, professional medical billing service can provide centralized billing, claim follow-up, and reporting among other revenue cycle processes.

And when the objective is to evaluate the broader organization behind those services, I-Med Claims Medical Billing Company provides information about its billing and RCM capabilities, including its stated focus on reducing billing errors and improving claim processing.

Frequently Asked Questions About CO-226 Denial Code

1. What does the CO-226 Denial Code mean?

CO-226 means information requested from the billing or rendering provider was not provided, was not provided timely, or was insufficient or incomplete. X12 also requires at least one remark code to accompany CARC 226.

2. Is CO-226 a coding denial?

Not necessarily.

CO-226 specifically concerns information requested from the billing/rendering provider. The underlying issue may involve documentation, records, provider information, or another item requested by the payer. The accompanying remark code and original payer request should be reviewed before deciding how to correct the claim.

3. Can a CO-226 denial be appealed?

Potentially, yes, but the correct action depends on the payer and the reason for the adjustment.

For Original Medicare, CMS provides a formal redetermination process and generally allows 120 days from receipt of the initial claim determination to request a first-level redetermination. CMS also distinguishes claim corrections involving minor errors and omissions from the formal appeals process.

4. What should I do first when I receive CO-226?

Read the complete ERA/EOB and accompanying remark code first. Then locate the original payer request and determine what information was requested, when it was due, whether anything was submitted, and whether the submission can be documented.

5. How can practices prevent CO-226 denials?

Design a system for payer request handling that includes designated ownership, deadlines, documentation checklists, submission verification, follow-up dates, and root cause reporting on a monthly basis. Prevention is not so much about dealing with the denial but ensuring payer requests cannot get lost in the untracked workflow process.