DENIAL PLAYBOOK · AUTH ON FILE BUT STILL DENIED

How to appeal an Auth on File but Still Denied denial

Common code: CARC 197 (precert/auth absent) — issued even though a valid authorization exists

Why payers issue it

The auth number wasn't attached to the claim or landed in the wrong field
The authorized CPT, units, or dates didn't exactly match what was billed
The payer authorized under a different provider, NPI, or facility than billed
The payer's system simply has no record of an auth it actually issued

What overturns it

Attach the authorization number and tie it to the exact claim lines
Show the auth's approved codes, units, and dates match the billed service
Provide the payer's own auth approval (reference number, letter, or portal screenshot)
Escalate to have the payer locate the auth in its system and reprocess

Worth appealing? An auth-on-file denial is one of the most winnable there is, because you did everything right and the proof is in your hands. Producing the approval and matching it to the claim overturns these cleanly, they're just infuriating to chase one at a time.

Common questions

How do I appeal an Auth on File but Still Denied denial?

This is the auth denial that shouldn't exist: you obtained the prior authorization, the number is on file, and the payer denied the claim anyway because the auth wasn't linked, the codes didn't match, or the payer's own system lost it. To overturn it: attach the authorization number and tie it to the exact claim lines; show the auth's approved codes, units, and dates match the billed service; provide the payer's own auth approval (reference number, letter, or portal screenshot); escalate to have the payer locate the auth in its system and reprocess. The key is matching the documentation to the payer's own rule for auth on file but still denied denials.

Is an Auth on File but Still Denied denial worth appealing?

An auth-on-file denial is one of the most winnable there is, because you did everything right and the proof is in your hands. Producing the approval and matching it to the claim overturns these cleanly, they're just infuriating to chase one at a time. A no-risk recovery service makes it easy to find out, you only pay on what's actually recovered, so there's no cost to working the ones that are winnable.

How does Volari handle Auth on File but Still Denied denials?

Volari's AI agents identify auth on file but still denied denials in your written-off pile, build each appeal with the right documentation and payer-specific argument, file it, and follow it to payment. You pay 25% only on what's recovered, and nothing if nothing comes back.

Other denial types

Modifier 25 →Medical Necessity →Timely Filing →Prior Authorization →Bundling / NCCI Edits →Missing or Invalid Information →Coordination of Benefits →Non-Covered Service →Duplicate Claim →Experimental / Investigational →Downcoding →Eligibility / Coverage Not in Effect →Referral Required / Absent →Diagnosis Inconsistent with Procedure →Provider Not Eligible / Credentialing →Global Surgery Period (E/M During Global) →Frequency / Units Exceeded (MUE) →Step Therapy / Fail-First →Site of Service →Telehealth POS / Modifier →Out-of-Network / Network Status →Assistant Surgeon →New vs Established Patient →Drug / J-Code Units →Screening vs Diagnostic →LCD / NCD (Medicare Coverage Policy) →Documentation Insufficient →Corrected Claim Denied as Duplicate →

Volari's AI agentic crew that works your pile

The same AI agents that build and file your auth on file but still denied appeals inside the app, each a specialist at one part of the fight, paid only on what they bring back.

Reva

Lead

Cody

Coding

Denny

Appeals

Faye

Follow-up

Iris

Intel

See how many Auth on File but Still Denied denials you wrote off.

A free assessment shows your real recoverable number. No risk, paid only on what we recover.

Get your free assessment →Watch the agents work a denial →

Volari AI · no-risk denial recovery for independent practices · all denial types →