Top

CO-197: Precertification, authorization, or notification absent

The service required precertification or authorization that was not obtained, so the payer denies it as a contractual provider responsibility.

What it means

CO-197 means a required precertification, authorization, or notification was not on file when the service was rendered. The payer's benefit rules made prior authorization a condition of payment and that condition was not met. As a CO code the balance falls on the provider.

Mechanically this is an authorization edit that checks for a valid auth matching the service, dates, units, and provider. A missing auth, an expired auth, an auth for the wrong level of care, or units exceeding what was authorized will all trigger it.

What the code says

X12 defines code 197 as "Precertification/authorization/notification/pre-treatment absent" (X12). The word doing the work is absent. The payer is not saying the service was unnecessary or not covered, only that a required approval step did not happen before it was delivered. The definition covers four distinct requirements with different rules. A payer requiring notification within 48 hours is imposing something quite different from one requiring approval before the first session; read the contract for which applies.

How often it is overturned

Authorization denials are overturned far more often than practices assume. As a general healthcare baseline, Medicare Advantage insurers fully or partially denied 7.7% of nearly 53 million prior authorization requests in 2024. Just 11.5% of those denials were appealed, and 80.7% of appeals were partially or fully overturned. Those figures cover prior authorization requests rather than claims denied with CO-197 after the fact. The direction is still hard to argue with: a large volume of appealable denials is absorbed without anyone testing them. In HealthCare.gov marketplace plans in 2021, 8% of in-network denials were attributed to lack of preauthorization or referral. Consumers appealed less than two-tenths of 1% of in-network denials.

Sources: X12 Claim Adjustment Reason Codes · KFF, Medicare Advantage Insurers Made Nearly 53 Million Prior Authorization Determinations in 2024 · KFF, Claims Denials and Appeals in ACA Marketplace Plans in 2021

Why it happens in behavioral health

CO-197 is a costly behavioral health denial because it attaches to the expensive services. IOP, PHP, and residential admissions typically need prior auth, and continued stays require concurrent review to extend the authorized days. A gap between authorized units and delivered units is a classic trigger.

SUD programs are especially exposed when a client steps up or down a level of care and the authorization does not follow. A weekend admission that outruns the auth obtained after the fact is the other classic case. Match every delivered day and unit to a valid authorization for the exact level of care, and keep concurrent reviews ahead of the delivered dates.

Why session counts make it recur

In behavioral health, authorization often attaches to session counts rather than to a single approved episode. A medical procedure typically needs one authorization. A course of therapy may need an initial authorization, a concurrent review at a set number of sessions, then another. Each is a separate opportunity to miss a deadline, and missing the second one denies every session after it.

The failure mode is specific. The initial authorization is obtained carefully because someone owns it. The concurrent review is missed because nobody tracked sessions against the approved number. The denial then arrives, in an illustrative case, for sessions eleven through eighteen all at once. See prior authorization in behavioral health for the workflow.

How to fix it

  • Work it in this order, upstream fix first:
    1. Close the tracking gap before touching the claim. Name who owns authorization tracking for this patient, and request the next concurrent review today so the sessions still to be delivered do not deny as well.
    2. Check whether an authorization exists and whether it covers the exact dates, units and level of care. If it exists but was mis-keyed or never transmitted, correct the claim to match it and resubmit. That case overlaps with CO-16.
    3. Request retroactive authorization. Many payers allow it inside a defined window, and it is the step most often skipped.
    4. Check whether authorization was genuinely required. Requirements change in both directions.
    5. Appeal with clinical documentation when the service met criteria but the authorization was missed.
    6. Write off only after all of that.
  • Treat a denial citing an absent authorization for a service that no longer requires one as worth challenging. A requirement list verified a year ago is not reliable.

How to prevent it

  • Obtain prior authorization before admission for IOP, PHP, and residential care.
  • Run concurrent review ahead of authorized end dates so continued stays never lapse.
  • Reconcile delivered units against authorized units before billing each episode.
  • Check at scheduling whether this payer requires authorization for this service, across every appointment, since it is a knowable fact at booking.
  • Track sessions delivered against sessions approved for every active authorization, with a trigger before the limit rather than a denial after it. An illustrative tracker line: Auth A123, 12 sessions approved, 9 delivered, renewal request due at session 10, expires 03/31.
  • Separate arriving CO-197 denials by path (corrected claim, retroactive request, appeal) so nothing defaults to write-off.

How AI can help with CO-197

CO-197 is helped on both sides, prevention and recovery, which makes it the code where automation pays back most. Prevention cuts the volume at the source, and routing recovers a share of what remains.

  • Requirement checking at scheduling. Whether this payer requires authorization for this service is a knowable fact at booking. Checking it then, across every appointment, is the intervention that prevents the denial outright.
  • Session count tracking against the authorization. The concurrent review failure is purely a counting problem. A system holding the approved number and the sessions delivered can raise the flag before the limit rather than after. That is the difference between a renewal and, in an illustrative case, eight denied sessions.
  • Routing denials to the right path. A CO-197 where the authorization existed is a corrected claim. One where it did not may be a retroactive request or an appeal. Those are different workflows, and separating them automatically stops everything defaulting to write-off.

Supabill automates benefits verification across payers and manages denials with routing and appeals. That is aimed squarely at the gap the KFF numbers describe: denials that were appealable and never got appealed.

The limit is real and worth naming. Automation cannot obtain an authorization a payer refuses to grant, and it cannot manufacture medical necessity. Where a service genuinely was not authorized and the payer will not grant it retroactively, the write-off is correct. What automation changes is that you reach that conclusion after testing it rather than instead of testing it.

FAQ

Can I bill the patient when I forgot to get authorization?

Generally no. CO-197 carries the contractual obligation group code, so the amount is absorbed by the provider. Billing a patient for your own administrative omission also creates a strong complaint risk, whatever the contract says.

Is it worth appealing a CO-197 denial?

The data suggests yes, far more often than practices assume. As a general healthcare baseline, 80.7% of appealed Medicare Advantage prior authorization denials were overturned in 2024, while only 11.5% of denials were appealed at all.

Can I get authorization after the service was provided?

Many payers allow retroactive authorization inside a defined window, particularly for urgent services or where eligibility was unclear. It is worth attempting before writing off, and it is the step most commonly skipped.

What is the difference between CO-197 and CO-16?

CO-197 means the authorization was never obtained. CO-16 means required information was missing from the claim, which can include an authorization number that exists but was not transmitted. Check which situation you are in before choosing a corrected claim or an appeal.

Why do I get denials for later sessions when the first ones were approved?

Because your authorization likely covered a set number of sessions and the concurrent review was missed. Track sessions delivered against sessions approved, and trigger the renewal before the limit rather than discovering it through a denial.

Do authorization requirements change?

Frequently, in both directions. Payers add and remove requirements, so a requirement list verified a year ago is not reliable. This cuts both ways: a denial citing a requirement that no longer exists is worth challenging.

What is the difference between CO-197 and CO-50?

CO-197 says a required approval step was absent; the payer has not judged the service itself. CO-50 says the payer judged the service not medically necessary. One is fixed with process and paperwork, the other with clinical documentation and an appeal.

Does a level of care change need a new authorization?

Usually yes. An authorization is for a specific level of care, so when a client steps up or down, the existing auth does not follow. Request the new authorization before the first day at the new level, or the whole stretch denies.

What should I do about a weekend admission with no authorization?

Notify the payer on the first business day and request authorization covering the admission date. Many contracts allow a defined notification window for urgent or after-hours admissions. Check the contract for the window, because a weekend admission that outruns it is a classic CO-197 trigger.

AI agents that run your billing.

Denials like CO-197 are rarely a one-off. They trace back upstream to eligibility, coding, documentation, or a payer rule that changed. Supabill's agents work the whole revenue cycle to stop them at the source. See our guide on why behavioral health denials keep rising, or book a demo.

Book a live demo