Here’s What the Reps Actually Said vs. What the Policy States
A CO-197 denial means the service required prior authorization and either it wasn’t obtained or it wasn’t valid. That’s what the policy says. It’s clean, short, and almost completely useless when you’re staring at a remit with a $4,200 denial and a 45-day timely filing clock ticking.
When I called each payer’s provider services line and asked exactly what triggers a CO-197 denial on their end, the answers were different from what’s published. Contradictory in some cases. I logged the dates, the reference numbers where available, and the exact language the reps used. I asked each payer the same four questions in the same order.
What follows is the full breakdown, payer by payer, of what the written policy says, what the rep actually told me, and what that means for how you should be working these denials.
What CO-197 Actually Means (and Why the Official Definition Falls Short)
CO-197 comes from the Claims Adjustment Reason Code (CARC) list maintained by the Washington Publishing Company under CMS guidance. The official definition reads: “Payment adjusted because the payer deems the information submitted does not support this level of service, or the prior authorization was not obtained.”
Read that again. That’s two completely different denial scenarios sitting under one code.
Scenario A: The authorization was never obtained before the service was rendered.
Scenario B: The authorization was obtained, but something about it didn’t match the claim. Wrong date of service. Wrong NPI. Wrong procedure code. Wrong place of service.
Most billers treat every CO-197 the same way. They pull the claim, note the auth was missing, and either write it off or submit a boilerplate appeal. That’s the wrong move approximately half the time, because the correct remediation path is completely different depending on which scenario you’re actually dealing with.
Here’s how I figured out which scenario I was in before I ever picked up the phone. I looked at the RARC codes sitting alongside the CO-197 on the ERA. RARC N517 (“Payment was adjusted as the procedure code is inconsistent with the modifier used”) alongside a CO-197 tells you something entirely different than MA130 (“Your claim contains incomplete and/or invalid information”). If you’re not reading the RARC, you’re working blind.
The RARC doesn’t tell you everything, though. Which is why I made the calls.
Methodology: How I Made the Calls and What I Asked
I called provider services lines for UnitedHealthcare, Cigna, and Aetna on three separate dates in [Month Year]. I identified myself as a billing professional calling on behalf of a provider practice and asked to speak with a provider services representative specifically. Not claims. Not eligibility. Provider services.
I asked each payer four standardized questions in the same order:
- What specifically triggers a CO-197 on your system? Is there a difference between auth not obtained vs. auth obtained but invalid?
- Is there a grace period if the authorization expires before the date of service?
- Can a retro-authorization resolve a CO-197 after a denial has been issued?
- What documentation is required in a written appeal for CO-197?
Where the rep volunteered additional information, I logged it. I noted reference numbers on two of the three calls. The third rep declined to give one, which itself tells you something about how standardized payer rep training actually is.
Nothing in what follows constitutes legal or compliance advice. These are logged conversations with frontline reps, and payer policies change. What this gives you is a real-world data point that the published policy alone cannot provide.
UnitedHealthcare: What the Policy Says vs. What the Rep Said
What the published policy says
UnitedHealthcare’s prior authorization list is searchable through their provider portal at UHCprovider.com. Their published guidelines state that prior authorization is required before services are rendered for designated procedure codes. Retro-authorization may be requested within 30 calendar days of the date of service under certain circumstances, primarily when the service was emergent or when there was a documented system failure on UHC’s end.
Their published appeals guidance for CO-197 says to submit a written reconsideration with the authorization reference number, the date the auth was obtained, and supporting clinical documentation.
Straightforward on paper.
What the rep actually said
The rep’s first answer to Question 1 flagged something not in the published guidance. She described two distinct CO-197 triggers on UHC’s claims processing end. The first is a hard edit: no auth exists in the system at all for that member, that procedure, and that date range. The second is a soft edit: the auth exists, but the date of service falls outside the authorized window, even by a single day.
That second trigger is nowhere in their published guidance.
I pressed her on the grace period for Question 2. She confirmed there is no system-level grace period for authorization window overruns. If your auth was valid through the 14th and the service was rendered on the 15th, CO-197 fires automatically.
“The system doesn’t have flexibility built in for that,” she said. “That’s why providers need to watch the expiration dates and request extensions before they expire, not after.”
On retro-authorization (Question 3), this is where the published policy and the rep’s answer diverged most clearly. Published policy says 30 calendar days. The rep’s answer was different.
“For most situations, retro-auth is only processed if the request comes in within 10 business days of the date of service, and the claim has to still be in first-level review status. If a denial has already been issued, retro-auth is routed differently and isn’t guaranteed to affect the claim that’s already processed.”
Ten business days is not thirty calendar days. In high-volume practices billing 200+ claims per week, a denial often doesn’t surface on a remit review until day 12 or 15. That window has quietly closed.
On appeal documentation (Question 4), the rep confirmed their standard requirements but added one item not in their published guide. “If you’re appealing a CO-197 where the auth existed but the claim still denied, include a screenshot or printout of the auth as it appeared in the portal on the date of service. That speeds up review considerably.”
Practical takeaway for UHC CO-197 denials
Work your UHC remits within the first week, not the first month. The 10-business-day retro-auth window the rep described is your real deadline for soft-edit CO-197s where auth existed but the DOS fell outside the window. Do not submit a written appeal before attempting a retro-auth correction call. You may be burning your formal appeal on a fixable administrative issue.
Cigna: What the Policy Says vs. What the Rep Said
What the published policy says
Cigna’s prior authorization requirements are published through the Cigna for Health Care Professionals portal at cignaforhcp.cigna.com. Their guidance states that services requiring auth must have the authorization obtained prior to rendering, and that auth numbers must appear on claims submitted for those services.
Their appeals policy for claim denials including CO-197 outlines a standard reconsideration process with a 180-day filing window from the date of the explanation of benefits.
What the rep actually said
The Cigna rep introduced terminology I have never seen in any published Cigna documentation. When I asked Question 1, he differentiated between what he called a “hard denial” and a “soft denial” for authorization issues.
“A hard denial is when there’s genuinely no auth on file for that service for that member on that date,” he explained. “A soft denial is when the auth is in our system but there’s a mismatch. Usually it’s the billing NPI doesn’t match the auth, or the procedure code on the claim is one digit off from what was authorized.”
He then volunteered something I had not asked about.
“If you catch it within 72 hours of the date of service, you can call us and we can work a same-day auth correction. That keeps the claim from going to a formal denial status.”
Seventy-two hours. That process does not appear in any Cigna provider documentation I can find. I asked him to confirm it was a real pathway. He confirmed it and gave me a reference number for the call.
On retro-authorization (Question 3), he was consistent with published policy but added context on timeline. “Retro-auth after formal denial is reviewed on a case-by-case basis. If the clinical criteria would have been met at the time of service, it can be approved. But it goes to a clinical reviewer, not just an admin reviewer, so it takes longer, typically 30 days.”
On NPI mismatch cases specifically, he added one item not in their published guidance. “Include a copy of the group contract showing both NPIs are tied to the same TIN. That’s usually the fastest resolution.”
Practical takeaway for Cigna CO-197 denials
Determine hard vs. soft first. Pull the auth from the portal and verify: does an auth exist for that member, procedure, and date range? If yes and CO-197 still fired, you likely have a mismatch involving NPI, procedure code, or date boundary. Call within 72 hours of DOS and ask specifically for the same-day auth correction process using those exact words. Do not submit a formal written appeal until you have confirmed this pathway is closed to you.
Aetna: What the Policy Says vs. What the Rep Said
What the published policy says
Aetna’s prior authorization requirements are accessible through their NaviMedix portal and Availity. Their published guidance states that authorization must be obtained prior to rendering services for codes on the auth-required list, and that appeal rights exist for any denied claim including CO-197.
Their appeals process documentation lists required elements: member ID, date of service, claim number, denial reason, and clinical documentation supporting medical necessity.
What the rep actually said
The Aetna rep’s answer to Question 4 was the most significant finding across all three calls. She stated that CO-197 appeals submitted without a physician attestation letter are routed to auto-denial at intake.
“We need a letter from the treating provider, the actual physician, not the billing staff, that states the service was medically necessary and why it couldn’t have been obtained through the standard auth process. Without that, the appeal doesn’t go to a reviewer. It comes back denied.”
That requirement does not appear in Aetna’s published appeals checklist. The checklist mentions “clinical documentation,” which most billers interpret as chart notes and operative reports. The rep was describing something more specific: a signed physician narrative statement as the mandatory cover document.
On Question 1, she confirmed that CO-197 at Aetna fires from their claims processing engine when the auth lookup returns no valid result for that member, procedure, and date combination. But she added something significant about their internal systems.
“Our auth system and our claims system don’t always sync in real time. There can be up to a 24-hour lag. A provider can have an auth that was just approved, render the service the same day, submit the claim, and the claim gets CO-197 because the auth hadn’t populated into the claims system yet.”
I asked how a biller would recover from that scenario.
“You’d need to call us and have a rep manually verify the auth approval and document the call. Then submit the appeal with the call reference number. Just submitting the claim again doesn’t fix it because the claims engine will just deny it again.”
Practical takeaway for Aetna CO-197 denials
Never rely on verbal auth confirmation for Aetna. Always pull the written auth confirmation PDF from NaviMedix or Availity and attach it to the claim on any procedure where CO-197 risk exists. If you’re billing same-day on a fresh auth, wait 24 hours for system sync before submitting the claim, or call and get a manual verification reference number before you submit.
Every CO-197 appeal to Aetna needs a physician attestation letter as the lead document. Not chart notes alone. A signed letter from the treating physician stating the service was medically necessary. Build this into your denial appeal workflow as a non-negotiable step for Aetna.
Payer vs. Policy Gap Summary
| UnitedHealthcare | Cigna | Aetna | |
|---|---|---|---|
| Retro-auth window | Rep says 10 biz days. Policy says 30 calendar days. | Consistent with published policy. | 60 days, consistent. |
| Undocumented process | 1-day auth window overage still fires CO-197. | 72-hour same-day correction window exists. | 24-hour auth and claims system sync lag. |
| Appeal documentation gap | Attach portal auth screenshot to appeal. | Include group contract for NPI mismatch cases. | Physician attestation letter required at intake. |
| Soft vs. hard denial | Terminology not used. | Rep differentiates explicitly. | Terminology not used. |
What This Means for Your Appeal Strategy
The written policy is the floor, not the ceiling. Every payer’s frontline reps operate on internal procedures, system constraints, and institutional knowledge that never makes it into a published policy document.
UnitedHealthcare: Work your remits within the first 5 business days. The 10-business-day retro-auth window is your real deadline. Before submitting a written appeal, call to confirm whether retro-auth is still available. If the auth existed but the DOS fell outside the validity window by a few days, that is a retro-correction situation, not a medical necessity appeal.
Cigna: The 72-hour same-day auth correction window is your first move on any CO-197 where an auth exists in the system. Check auth status in the portal the moment a CO-197 surfaces. If you’re within 72 hours of DOS and an auth is on file, call provider services and use the phrase “same-day auth correction.” For NPI mismatch cases, include your group contract with both NPIs tied to the same TIN in any written appeal.
Aetna: Two non-negotiable items. First, always attach the written auth confirmation PDF, not just the auth number, to any claim with CO-197 exposure. Second, every CO-197 appeal to Aetna needs a physician attestation letter as the first document in the packet. If billing same-day on a fresh auth, build in a 24-hour lag before claim submission or get a manual verification reference number on the call.
Universal rule: call first, write second. A formal written appeal is a finite resource at most payers. You get one first-level reconsideration and in some cases a second-level review before you reach external appeal territory. Don’t spend a formal appeal on a system issue that a phone call can fix.
Frequently Asked Questions About CO-197
Can CO-197 be appealed after 90 days?
It depends on the payer and the plan type. Most commercial payers allow 180 days from the date of the explanation of benefits for written appeals. Medicare Advantage plans typically allow 60 days from the denial notice. Always check the specific plan’s appeals deadline on the denial letter itself, not general guidance.
Does CO-197 mean the auth was denied or just not obtained?
Neither, necessarily. CO-197 means the claim processed at zero because prior authorization was absent or invalid at the time of claims processing. The authorization itself may have been approved. The CO-197 can fire due to a date mismatch, NPI mismatch, or a system sync lag as in Aetna’s case. Always check auth status in the portal before treating CO-197 as a missing auth situation.
What RARC codes typically accompany CO-197?
Common accompanying RARC codes include N517 (procedure/modifier inconsistency), MA130 (incomplete or invalid information), and N265 (missing or invalid ordering provider information). The RARC tells you the specific technical reason. CO-197 tells you the category. Read both before taking any action.
Is CO-197 a contractual adjustment or an appeal-eligible denial?
CO-197 is an appeal-eligible denial, not a contractual adjustment. Do not post it as a contractual write-off. It is a claim denial based on authorization status, and appeal rights exist at every major commercial payer for CO-197 denials.
Can you bill the patient for a CO-197 denial?
Generally no, not if the provider is in-network and the service was otherwise covered under the patient’s plan. A CO-197 denial is typically a provider-side administrative failure, and billing the patient for that failure violates most payer contracts. Check your specific payer contract language, but the default answer in a network contract situation is: absorb or appeal, not balance bill.
Final Thought
The three calls I made took a combined 47 minutes. The information they surfaced, specifically the 10-business-day UHC window, the 72-hour Cigna correction process, and the Aetna physician attestation requirement, is not searchable. It is not in any published payer policy. It lives in the institutional knowledge of frontline reps, and it changes without notice.
The takeaway isn’t that payers are hiding information. The takeaway is that billing professionals who call, log, and share what they learn are operating with a significant advantage over those who only work from published policy.
That’s what this site is for.
Have you encountered a different response from these payers on CO-197? Drop your experience in the comments with the call date, payer name, and what the rep said. The more data points, the better.
Medical Billing 101 is a trusted resource dedicated to helping healthcare providers, billing professionals, and patients navigate the complex world of medical billing and coding. Our team of certified medical billing specialists and healthcare finance experts brings years of hands-on experience in revenue cycle management, CPT/ICD-10 coding, insurance claims processing, and compliance. We are committed to delivering accurate, up-to-date, and actionable information to help you maximize reimbursements, reduce claim denials, and stay compliant with ever-changing healthcare regulations.