Guide

CO-197: retro-auth requests and when they work

Summary

A CO-197 denial means the service required prior authorization that wasn't obtained before it happened. Getting paid afterward usually means a retro-authorization request, and payers grant those only within specific, narrow criteria they publish themselves — an emergency, a coverage eligibility nobody could have confirmed in time, a documented notification error. An elective service where authorization was simply missed rarely qualifies. Read the payer's own retro-auth policy before assuming this claim is salvageable, and consider whether a peer-to-peer review is actually the tool needed instead.

By Gale Editorial · Updated 2026-07-26. Every figure cited to a dated source. How we write.

Can I get paid after a CO-197 no-authorization denial?

Sometimes, but only through a formal retro-authorization request, and only when the circumstances fit criteria the payer sets for itself — not simply because the claim already happened 1Ref 1X12 (2026).Claim Adjustment Reason Codes.That CARCs, including CO-197, are the standard X12 code list explaining why a claim paid differently than billed — used here as the definition of what a CO-197 actually signals: authorization not obtained before the service.. A CO-197 signals that a service requiring prior authorization went forward without it, and the default outcome is that the claim stays denied.

Whether it's worth pursuing depends entirely on why the authorization was never obtained. A genuine emergency, an eligibility question nobody could have resolved in time, or a documented error in how the notification was submitted are the situations payers actually reopen. A scheduled, elective service where the authorization step was simply skipped is a much harder case, and often not one worth spending appeal effort on.

CO-197 is a different problem than an authorized claim getting denied anyway

CO-197 specifically means no authorization was on file at all before the service happened — a distinct problem from a claim that gets denied even though the authorization was obtained and confirmed in advance. That second situation, sometimes described as authorized but denied, usually traces to a different issue entirely: a mismatch between what was authorized and what was billed, or a separate medical-necessity determination made after the fact.

Confusing the two wastes time on the wrong fix. If authorization genuinely exists on file for this date and service, the path forward is confirming what it actually covered and why the claim didn't match it — not requesting a retro-authorization for something already authorized. Reading the RARC riding alongside the CO-197 often narrows down which of the two situations applies, since it can name the specific requirement that wasn't met or the specific mismatch behind the denial 2Ref 2X12 (2026).Remittance Advice Remark Codes.That RARCs supply the supplemental detail beyond the CARC on a remittance, maintained by X12 as a public list, used here to distinguish a true no-authorization denial from an authorized claim denied for a separate reason..

When a retro-authorization request can actually work

Payers publish their own criteria for accepting an authorization request after the fact, and those criteria are narrow by design — Aetna, for one example, states its medical and reimbursement policies, including how it handles authorization exceptions, on its own provider portal 3Ref 3Aetna (2026).Aetna Clinical Policy Bulletins.That Aetna publishes its own medical and reimbursement policies on its provider portal, cited only as a named example of where a specific payer's retro-authorization criteria live — never as what all payers require.. Reading that specific policy before submitting a retro-auth request tells you whether this claim actually fits, since your contract with that payer controls, not a rule of thumb carried over from a different plan.

The situations that tend to qualify share a common thread: something outside routine scheduling caused the authorization step to be skipped or delayed — an emergency admission, a patient's eligibility that wasn't confirmable until after the visit, or a documented system or notification failure on the submission itself.

When it almost certainly won't work

A scheduled, elective service where the authorization step was simply missed — nobody called it in, nobody checked the payer's requirement before the appointment — is the hardest case to reverse. Most payers treat this as a process failure on the provider's side rather than a circumstance beyond anyone's control, and a retro-authorization request built on missed routine follow-through is unlikely to succeed.

That doesn't make the appeal worthless to attempt if the clinical case is strong, but it changes the odds and the framing: the request needs to explain what made this instance different from ordinary scheduling, not simply ask the payer to overlook a missed step. Denials overall are common and worked appeals rare — appeals are filed on well under one percent of denied claims even as denial rates run in the high teens across marketplace plans 4Ref 4Kaiser Family Foundation (2025).Claims Denials and Appeals in ACA Marketplace Plans.That in-network claim denial rates in ACA marketplace plans average in the high teens with wide insurer variation, and that appeals are filed on well under one percent of denied claims, per KFF's analysis of federal transparency data. — and a CO-197 built on a missed routine step starts from an already low base rate.

The peer-to-peer is a different tool for a different problem

A retro-authorization request and a peer-to-peer review solve different problems, and confusing them wastes the one that might actually work. The peer-to-peer is a direct conversation between the treating clinician and the payer's medical reviewer, aimed at arguing medical necessity — not at getting a missed authorization step waived after the fact.

When a CO-197 sits on top of a case where the real dispute is whether the service was medically necessary at all, requesting the peer-to-peer alongside the retro-authorization gives the clinical argument a direct channel it wouldn't otherwise have. When the dispute is purely procedural — authorization was owed and nobody obtained it — a peer-to-peer conversation about necessity doesn't address the actual reason for the denial.

Building the prior-auth workflow that prevents the next CO-197

Every CO-197 is, in some sense, a workflow gap: a service went forward before someone confirmed whether the payer required authorization for it. Running prior auth as a solo means that check has to happen at scheduling, not after the visit, since there is no separate department to catch it later.

The habit worth building is simple and repeatable: verify authorization requirements against the specific plan on file before the appointment is confirmed, not after, and log the authorization number alongside the visit so it's on hand when the claim goes out. A missed step caught before the service happens costs a phone call; the same gap caught after the service happens costs an uncertain appeal.

Know which rulebook governs the appeal

Before deciding how hard to push, confirm which framework governs this specific plan, because it changes both the process and the odds. A self-funded employer plan is governed by federal ERISA law rather than state insurance law, and ERISA sets its own claims-and-appeals structure and deadlines for those plans 5Ref 5U.S. Department of Labor (2026).ERISA.That self-funded employer plans are governed by ERISA rather than state insurance law, with their own claims-and-appeals framework and deadlines, so a CO-197 appeal can follow a different process depending on the plan type..

That distinction matters for a CO-197 specifically because retro-authorization policies and appeal windows are set by the plan itself, not by a uniform national rule — so the same clinical situation can have a real shot at reversal under one plan's rules and almost none under another's. Reading the specific plan's language, not a general assumption about how authorization denials usually work, is what actually determines the outcome.

Common questions

Sometimes, through a formal retro-authorization request, but only when the payer's own published criteria are met — typically an emergency, an eligibility question nobody could confirm in time, or a documented notification error. An elective service where the authorization step was simply missed rarely qualifies, and the default outcome without one of those circumstances is that the denial stands.

CO-197 means no authorization was on file before the service happened at all. A claim that's authorized but denied means the authorization existed and was confirmed, but the claim was still denied for a separate reason — usually a mismatch between what was authorized and what was billed, or a distinct medical-necessity finding made afterward.

Circumstances outside routine scheduling: a genuine emergency, an eligibility status that couldn't be confirmed until after the visit, or a documented error in how the authorization request was submitted. Reading the specific payer's own retro-authorization policy tells you whether this claim's circumstances actually fit, since the criteria are set by that payer's contract, not a general industry rule.

No. A retro-authorization request asks the payer to accept an authorization after the fact; a peer-to-peer review is a direct conversation between the treating clinician and the payer's medical reviewer arguing medical necessity. When the real dispute behind a CO-197 is whether the service was necessary at all, the peer-to-peer is the more direct tool of the two.

The framework behind it can. A self-funded employer plan is governed by federal ERISA law rather than state insurance law, with its own claims-and-appeals process and deadlines. Confirming whether a plan is self-funded before building the appeal tells you which rulebook and timeline actually apply, since retro-authorization policies are set at the plan level.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

1.X12 (2026). Claim Adjustment Reason Codes. X12. link ✓That CARCs, including CO-197, are the standard X12 code list explaining why a claim paid differently than billed — used here as the definition of what a CO-197 actually signals: authorization not obtained before the service.
2.X12 (2026). Remittance Advice Remark Codes. X12. link ✓That RARCs supply the supplemental detail beyond the CARC on a remittance, maintained by X12 as a public list, used here to distinguish a true no-authorization denial from an authorized claim denied for a separate reason.
3.Aetna (2026). Aetna Clinical Policy Bulletins. Aetna provider portal. link ✓That Aetna publishes its own medical and reimbursement policies on its provider portal, cited only as a named example of where a specific payer's retro-authorization criteria live — never as what all payers require.
4.Kaiser Family Foundation (2025). Claims Denials and Appeals in ACA Marketplace Plans. KFF. link ✓That in-network claim denial rates in ACA marketplace plans average in the high teens with wide insurer variation, and that appeals are filed on well under one percent of denied claims, per KFF's analysis of federal transparency data.
5.U.S. Department of Labor (2026). ERISA. U.S. Department of Labor. linkThat self-funded employer plans are governed by ERISA rather than state insurance law, with their own claims-and-appeals framework and deadlines, so a CO-197 appeal can follow a different process depending on the plan type.

https://www.gale.care/for-providers/dn-co197-no-auth · 5 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

← Back to for providers