If you work in medical billing, you already know the pain of a denial that should have been avoidable. The CO 97 Denial Code is one of those claim issues that can quietly stall payments, increase rework, and drain time from your billing team. It is frustrating because it often points to a preventable process problem, not just a payer decision.

The good news is that the CO 97 Denial Code is manageable when you understand what it means, why it happens, and how to fix it fast. This guide breaks it down in a practical way so healthcare providers, billing specialists, and claims administrators can take immediate action and reduce repeat denials.

What Is CO 97 Denial Code?

The CO 97 Denial Code generally means the benefit for the billed service is included in the payment or allowance for another service or procedure that has already been adjudicated. In plain English, the payer is saying the denied charge is considered bundled, inclusive, or not separately payable.

This usually happens when:

• Two or more services are billed together, but one is considered part of another service

• A payer applies National Correct Coding Initiative logic or its own bundling edits

• The denied line item is viewed as incidental to the primary procedure

That is why the CO 97 denial is often tied to claim bundling, unbundling, modifier misuse, or code pairing errors.

Why the CO 97 Denial Code Matters

A lot of teams treat this denial as routine and simply write it off. That is a mistake.

A recurring CO 97 Denial Code problem can lead to:

• Delayed reimbursement

• Higher denial volume

• Unnecessary appeals

• Missed revenue opportunities

• Staff burnout from repetitive rework

More importantly, repeated CO 97 denials usually reveal a weakness in coding review, claim scrubber setup, or denial prevention workflow. Fixing the root issue can improve your clean claim rate across far more than one denial category.

What Causes CO 97 Denial Code?

There is no single cause. The CO 97 Denial Code usually appears because of one of several common billing failures.

1. Unbundled Services

This is one of the biggest triggers.

A practice bills components of a service separately when the payer expects them to be included in a more comprehensive code. The claim is then reduced because one line is not separately payable.

2. Incorrect Modifier Use

Some bundled services may be separately payable only when supported by a valid modifier. If the modifier is missing, incorrect, or unsupported by documentation, the payer may deny the line with CO 97.

Common examples involve modifiers used to indicate distinct procedural services or separate encounters.

3. NCCI Edit Violations

Payers often rely on coding edits that flag code pairs which should not be billed together. If your claim includes a code combination that conflicts with these edits, the secondary code may be denied.

4. Duplicate or Overlapping Services

Sometimes the issue is not true duplication, but the payer reads it that way. If two line items appear to overlap in scope, one may be denied as inclusive.

5. Documentation Does Not Support Separate Payment

Even if a service could be billed separately, the chart may not clearly support why it was distinct. In those cases, the denial is harder to overturn.

Quick Answer: What Does CO 97 Mean?

CO 97 means the payer considers the denied service included in another paid service and not separately reimbursable.

That is the short version. The real work is figuring out whether the payer is right.

How to Fix CO 97 Denial Code

This is where most teams either recover revenue or waste time. Use a disciplined process.

Step 1: Read the Full Remittance Carefully

Do not stop at the code itself. Review:

• Remittance advice message details

• Associated remark codes

• Which line item was denied

• Which paid service the payer likely considers inclusive

The denial code alone is not enough. The supporting messages often tell you what the payer is objecting to.

Step 2: Review the Code Pairing

Check whether the denied CPT or HCPCS code is commonly bundled with the paid service. Look at:

• NCCI edits if relevant

• Payer-specific policy

• Internal coding reference tools

• Contract or billing guidance for that payer

This tells you whether the denial is valid on its face.

Step 3: Check Modifier Logic

If the service was truly separate, determine whether a modifier should have been used. Then ask the harder question: was the modifier actually justified?

This is where sloppy billing teams lose credibility. Adding modifiers blindly is not a strategy. It is a liability.

Step 4: Audit the Documentation

Confirm the medical record supports separate reimbursement. Look for:

• Separate anatomical site

• Separate encounter

• Separate lesion, procedure, or session

• Distinct medical necessity

• Time separation when relevant

If the chart does not support distinction, your appeal is weak.

Step 5: Correct and Resubmit or Appeal

Once you know the real cause, choose the right path:

• Corrected claim if coding or modifier omission caused the problem

• Appeal if the payer misapplied bundling logic

• Write-off if the denial is valid and the service truly is inclusive

Not every CO 97 denial should be fought. Smart denial management means knowing when recovery is realistic.

Proven Fixes for CO 97 Denial Code

These are the highest-value corrections billing teams can implement right away.

Tighten Claim Scrubber Rules

Your claim scrubber should catch likely bundling conflicts before submission. If it is not flagging common CO 97 scenarios, your front-end editing is too weak.

Improve Coding Review Before Submission

Do not let complex procedural claims go out without code pairing review. High-risk specialties should have stronger pre-bill quality checks.

Stop Modifier Overuse

A modifier is not a magic trick. Overusing modifiers may increase short-term payments but raises audit risk and weakens your appeal position.

Build Denial Pattern Reports

Track:

• Which CPT pairs trigger CO 97 most often

• Which payers apply the denial most aggressively

• Which providers or departments generate the most CO 97 volume

Patterns matter. If you do not measure them, you will keep fixing the same denial forever.

Train Staff on Bundling Rules

Billing staff, coders, and charge entry teams need practical training on:

• Inclusive services

• Comprehensive vs component coding

• Distinct service criteria

• Payer variation

This is one of the most profitable forms of training you can do because it prevents denials before they happen.

Real-World Example

A provider performs a primary procedure and also bills a supporting service that is commonly considered part of that procedure. The claim goes out with both codes and no valid modifier. The payer reimburses the primary line and denies the second with CO 97 Denial Code.

What should happen next?

1. Review whether the second service is always bundled or only bundled in certain circumstances

2. Check whether the procedure was actually distinct

3. Confirm whether documentation supports separate reporting

4. If justified, submit corrected claim or appeal with clear explanation

5. If not justified, adjust and update internal billing rules so it does not happen again

That last step matters. Recovery is good. Prevention is better.

When Should You Appeal CO 97?

Appeal only when you have a real argument.

A CO 97 appeal makes sense when:

• The services were truly distinct

• Documentation supports separate billing

• The correct modifier applies and was omitted or ignored

• The payer misapplied its own bundling rule

Do not appeal when:

• The denied code is clearly inclusive

• The documentation is weak

• The claim was coded incorrectly

• You are guessing rather than proving

Weak appeals waste staff time and slow down meaningful recovery work.

How to Prevent CO 97 Denial Code Going Forward

The fastest way to improve denial performance is to stop this denial before it happens.

Build a Pre-Bill Checklist

For high-risk claims, verify:

• Code pair compatibility

• Modifier necessity

• Documentation support

• Payer-specific bundling rules

Use Specialty-Specific Denial Controls

Different specialties have different bundling risks. A generic denial prevention process is not enough.

Audit High-Volume Denial Sources

Focus first on the departments, providers, and CPT combinations producing the most CO 97 hits.

Create Feedback Loops

If billing finds a recurring coding issue, that information must go back to coders, providers, and operations. Otherwise the denial repeats.

Standardize Appeal Templates

When CO 97 denials are appealable, use consistent, evidence-based letters tied directly to documentation and policy.

Common Mistakes to Avoid

These are the habits that keep practices stuck.

Writing Off Every CO 97 Automatically

Some are valid. Some are recoverable. Treating all of them the same is lazy billing.

Appealing Without Documentation

No evidence, no leverage.

Adding Modifiers After the Fact Without Support

That is not denial management. That is gambling.

Ignoring Payer Policy Differences

The same code combination may not behave the same way across all payers.

Failing to Track Recurrence

If the same error happens 50 times, you do not have 50 denials. You have one broken process.

Why This Denial Keeps Coming Back

Because most organizations address the symptom, not the system.

They:

• Work denials one by one

• Fail to fix root causes

• Train too broadly instead of precisely

• Do not monitor code pair trends

• Leave scrubber edits outdated

That is why a strong denial program matters. It reduces repeat work, protects cash flow, and improves coding discipline across the board.

How HMS Group Inc Helps

At HMS Group Inc, denial management is not just about posting adjustments and sending appeals. It is about identifying root causes, tightening workflows, and reducing repeat claim failure.

That includes:

• Reviewing denial trends

• Strengthening front-end claim edits

• Improving coding and modifier accuracy

• Building payer-specific denial workflows

• Helping practices reduce preventable revenue loss

That is how you stop treating denials as routine and start treating them as solvable operational problems.

Final Takeaway

The CO 97 Denial Code is not just a payment issue. It is a signal.

It tells you your billing team may be dealing with:

• Bundling errors

• Modifier misuse

• Weak claim edits

• Poor documentation alignment

• Broken denial prevention processes

The essential fix is not just to work the denial. It is to understand why it happened, decide if recovery is justified, and build a system that prevents it next time.

Next Step

If your team is dealing with recurring CO 97 Denial Code issues, the smartest move is to audit the pattern, not just the individual claim. Use the denial to expose what is weak in your workflow, then fix that permanently.

HMS Group Inc can help you identify the root causes, tighten your billing processes, and reduce costly denial volume across your revenue cycle.