CO 97 denial code: bundled, or wrongly bundled?

By Kathryn Thompson, RCM Expert, Supa

TL;DR: The CO 97 denial code means the payer considers this service already paid for inside another service on the claim. Sometimes that is correct and the line is a legitimate write-off. Sometimes the services were genuinely separate and a modifier would have prevented it. Telling those apart before you appeal is the whole skill.

Key takeaways

• X12 defines code 97 as a benefit included in the payment for another adjudicated service.
• The group code is CO, so the amount is not billable to the patient.
• Correct bundling and incorrect bundling produce the same code on the remittance.
• Modifiers are the mechanism for signaling a genuinely separate service.
• Appealing without documentation that the services were distinct is wasted effort.

Two services on one claim. One gets paid, the other comes back CO 97. The question your biller has about ninety seconds to answer is whether the payer is right.

Most of the time it is. The cases where it is not are worth real money, and they look identical on the remittance.

What does the CO 97 denial code mean?

X12 defines code 97 as "The benefit for this service is included in the payment/allowance for another service/procedure that has already been adjudicated" (X12).

Read that carefully. It is not saying the service was not performed, not covered, or not medically necessary. It is saying the payment for it is already inside a payment you received for something else. The service is recognized. It is just not separately payable.

The CO prefix again means Contractual Obligation, so the amount is written off rather than billed to the patient (X12).

What is bundling? Bundling is a payer treating two services as one payable unit because one is considered a component of the other. Edits that define these relationships are published and updated regularly.

The reason CO 97 causes more argument than CO 45 is that the underlying judgment is contestable. A pricing adjustment is arithmetic. A bundling decision is a claim about clinical relationships between services, and clinical relationships have exceptions.

When is CO 97 correct, and when is it not?

It is correct when the second service genuinely is a component of the first. It is wrong when the services were separate in time, in site, or in clinical purpose, and the claim failed to say so.

The distinction in practice:

Correctly bundled. The component service is part of the primary service by definition. There is no separate work, no separate session, and no clinical basis for separate payment. Post the adjustment.

Incorrectly bundled. The services were distinct. Different sessions, a separate clinical purpose, or an unrelated problem addressed in the same encounter. Here the payer's edit fired on the code pair without knowing the circumstances, because nothing on the claim told it.

The mechanism for telling it is the modifier. Modifiers exist precisely to signal that a code pair which usually bundles should not bundle in this instance, and applying them correctly is a skill worth building on your team. Our guide to modifiers 25 and 59 in behavioral health covers the two that matter most here.

One caution that will save you grief. A modifier appended to force payment on services that were not genuinely distinct is a compliance problem, not a billing tactic. The documentation has to support the separation before the modifier goes on the claim.

What should you check before appealing a CO 97?

Four things, in this order, and the whole check should take under five minutes.

1. Were the services actually distinct? Read the note, not the claim. If the documentation does not establish separate work, the appeal fails and should.
2. Was a modifier appropriate and missing? If yes, this is usually a corrected claim rather than an appeal, which is faster and cleaner.
3. Is the bundling edit correct for this code pair? Payer policy and national edits both apply, and they are not always aligned.
4. Is this a pattern? One CO 97 is an incident. Forty on the same code pair is a claim build problem in your system, and fixing it upstream beats appealing each one.

Step four is where most of the recoverable value sits. Practices that work CO 97 line by line stay busy and stay flat. Practices that trace the code pair back to how their claims are built stop generating the denial.

For where this fits in your broader denial workflow, why behavioral health claim denials keep rising covers the upstream prevention approach.

[Image: A decision tree showing a CO 97 line splitting into correctly bundled, missing modifier, and incorrect edit paths, with the resolution for each, clean editorial flowchart, accent teal on warm neutral - alt='A four step check for whether a CO 97 line is correctly bundled or worth challenging']

Does appealing actually work?

More often than the effort levels suggest, which is the recurring finding across denial data.

In ACA marketplace plans, KFF found that enrollees "appealed less than two-tenths of 1% of denied in-network claims," and that insurers "upheld most (59%) denials on appeal" (KFF). That leaves 41% overturned.

Sit with that pair for a second. Almost nobody appeals, and roughly two in five appeals succeed. Those two facts together describe a large amount of money left on the table across the system.

The honest caveat for CO 97 specifically: that 41% is across all denial types, and bundling appeals are not the easiest category. A bundling appeal without documentation establishing separate services will lose, and it should. The overturn rate rewards appeals with evidence behind them, not appeals in volume.

Where automation actually helps with CO 97

The return here is upstream, before the claim goes out. Working CO 97 after the fact is slow and mostly unproductive. Preventing the ones that were preventable is where the return is.

Pre submission scrubbing against code pair edits. A claim carrying a pair that will bundle can be caught before submission, when adding the modifier is a small edit rather than a corrected claim and a thirty day wait.

Documentation checked against the modifier. This is the part that protects you. A modifier signaling separate services should be supported by a note establishing them, and that link is checkable at claim build rather than at audit.

Pattern surfacing across the book. The same code pair bundling repeatedly is a fixable build issue. That only becomes visible when something is watching across claims rather than working a queue.

Supabill scrubs claims pre submission against payer and state rules and handles denial routing when something does get through, with documentation guardrails supplied by Supanote on the clinical side. The design intent is that the CO 97 lines reaching a human are the ones needing clinical judgment about whether the services were genuinely distinct.

Where it will not help you: it cannot decide that two services were clinically separate. That determination lives in the documentation and in the clinician's judgment about what happened in the room. A system that appended modifiers on its own to clear bundling edits would be generating compliance risk at machine speed, which is the opposite of useful.

Want your bundling edits caught before submission instead of after? Book a demo.

FAQ

Q: Can I bill the patient for a CO 97 amount?

A: No. The CO group code makes it a contractual obligation absorbed by the provider. The service was recognized and paid for inside another service, so there is no patient liability attached to the line.

Q: Will adding a modifier fix a CO 97 denial?

A: Only when the services genuinely were distinct and the documentation shows it. A modifier is a statement about the clinical circumstances, so applying one to clear an edit without supporting documentation creates compliance exposure rather than revenue.

Q: Should I appeal or submit a corrected claim?

A: If a modifier was appropriate and missing, a corrected claim is usually faster and cleaner. Appeal when you believe the bundling edit itself was applied incorrectly to services that should be separately payable.

Q: What is the difference between CO 97 and CO 45?

A: CO 97 says the service is not separately payable because it is included in another payment. CO 45 says the service is payable but your charge exceeded the contracted rate. Different problems with different resolutions.

Q: Why does the same code pair keep bundling?

A: Because something in how your claims are built keeps producing that pair without the appropriate modifier or sequencing. Repeated CO 97 on one pair is a process signal, and fixing the build stops the denial rather than working it.

Q: Does CO 97 mean the service was not covered?

A: No. Non coverage is a different determination with different codes. CO 97 specifically means the benefit is included in the payment for another service that has already been adjudicated, which means the service was recognized.