CO-197 Denial Code: Precertification/Authorization/Notification Absent
CO-197 is a claim adjustment reason code meaning precertification, authorization, notification, or pre-treatment requirements were absent: the required approval was never obtained before the service. It is one of the costliest preventable denials. Retro-authorization requests and appeals with good-cause evidence are the main recovery paths.
- Group
- CO (Contractual Obligation)
- Category
- Authorization not obtained
- Appealable?
- Yes; retro-auth or good-cause appeal, success varies by payer
- Typical fix
- Request retro-authorization fast, then appeal with clinical urgency evidence
What does denial code CO-197 mean?
CO-197 means "precertification/authorization/notification/pre-treatment absent." The payer required an approval before the service, checked its system on adjudication, and found nothing: no auth, no precert, no notification on file. This is the "we never asked" denial, distinct from CO-15, where an auth exists but does not match the claim.
Example: a surgery center performs an arthroscopic knee repair, 29881, billed at $4,850.00. The scheduler assumed the surgeon's office obtained the auth; the surgeon's office assumed the facility did. ERA: billed $4,850.00, allowed $0.00, CO-197 $4,850.00, paid $0.00. Two offices, one skipped step, and nearly five thousand dollars now depends on the payer's retro-auth policy.
Why did the claim get a CO-197?
- Ownership confusion: the referring office, rendering office, and facility each assumed someone else was getting the auth. This is the number one root cause in multi-provider services.
- Nobody knew it was required. Auth lists change constantly; a code that needed no approval last quarter needs one now.
- Plan changed between scheduling and service, so the auth rules changed with it.
- Add-on services during the encounter that were not on the original request, common in surgery and imaging.
- Urgent care delivered before approval when the situation did not allow waiting, which is exactly what good-cause appeal language exists for.
How do you fix a CO-197 denial?
- Call utilization management the day the denial posts and ask two questions: does this plan accept retro-authorization requests, and what is the window? Get the answer with a reference number.
- If retro-auth is possible, submit clinical documentation immediately: order, notes, and why the service was needed. Approval converts the denial to a payable claim on resubmission.
- If retro-auth is refused, escalate to a formal appeal on good-cause grounds: urgency, misinformation from the payer, eligibility system outage, or the payer's own published list not requiring auth at the time.
- Log the root cause on every CO-197 (who should have obtained it and why they did not); this data is what actually fixes the process.
How do you prevent CO-197 denials?
Assign auth ownership by service line so exactly one role is accountable per case, and require an auth status field on the schedule that must be "verified" before the patient is seen. Recheck authorization requirements at scheduling and again 48 hours before service, since plans update lists mid-year. For surgical cases, verify the auth covers all likely add-on codes. Track CO-197 as its own line in your denial rate dashboard; it is close to 100 percent preventable, so any recurring volume points at a broken handoff.
Can you appeal a CO-197 denial?
Yes. Retro-auth is the first lane; the formal appeal is the second, and it wins with evidence, not apology: proof of urgency (ED records, same-day orders), proof of payer misinformation (call references), or proof the payer's own auth list did not include the code on the date of service (screenshot with date). File inside the window, verified with the appeal deadline calculator, and structure the argument in the appeal letter generator. Confirm remark codes in the denial code lookup first so you appeal the right defect.
Frequently asked questions
The service required precertification, prior authorization, or advance notification, and the payer has no record that any was obtained. Unlike CO-15, where an auth exists but does not match, CO-197 means the approval step was skipped entirely. Recovery depends on retro-authorization policies and good-cause appeals.
Sometimes. Many payers allow retro-auth requests within a short window, commonly 2 to 30 days after the service, especially for urgent or emergent care, eligibility that could not be verified, or newborn claims. Call utilization management immediately; the window is the whole game.
Almost never. Obtaining authorization is the provider's contractual duty for in-network care, and the CO group code assigns the loss to the practice. Balance-billing a patient because your office skipped the auth violates most network contracts and, for Medicare Advantage, federal rules.
Sources & further reading
Reviewed by the ImmediCare Solutions RCM team
Certified billers and coders handling claims across 50+ specialties nationwide. This entry is reviewed against current payer policy and CMS rules. Last review: Jul 5, 2026.
Stop losing revenue to problems like this.
A free billing audit shows exactly where your practice is leaking money — no cost, no commitment.
