CO-197 denial code: what missing pre-auth means and how to fix it.
CO-197 means the payer required authorization before the procedure and never got it. It's one of the most preventable denials in dental billing, because the authorization requirement is knowable before the appointment is ever scheduled. Retroactive approval can recover revenue after the fact, but prevention is where the real fix lives.
See how Needletail confirms pre-authorization requirements for every procedure and payer before the appointment is ever scheduled.
RARC codes decoded
CDT codes most often needing pre-auth
equal-weight fix tracks
TL;DR
CO-197 means pre-authorization, precertification, or pre-treatment notification was required but never obtained before the procedure.
Crowns, implants, orthodontics, bone grafts, periodontal surgery, and some endo commonly require pre-auth, and the dollar/procedure thresholds vary by payer.
Two fix tracks matter equally: retroactive authorization after a denial, and prevention through pre-appointment verification. One recovers past revenue, the other stops it from happening again.
Most payers allow a grace period, often 14 to 30 days, to request retrospective authorization with supporting clinical documentation.
Emergency procedures usually have an exception path, but it still requires documentation to invoke.
This is the single most preventable denial in the series: the authorization requirement exists before the patient ever sits in the chair.
What is the CO-197 denial code?
The official definition: "Precertification/authorization/notification/pre-treatment absent." The payer required the practice to get approval, notify them, or submit a pre-treatment estimate before performing the procedure, and that step never happened.
Dental pre-authorization requirements are inconsistent by design across payers. Delta Dental may require pre-auth only above a dollar threshold, while MetLife might require it specifically for implants and orthodontics regardless of cost. There's no universal CDT list; the threshold and scope are set plan by plan.
Procedures that most commonly carry a pre-auth requirement across dental payers: crowns, implant placement, orthodontic treatment (almost universally), bone grafts, periodontal surgery, and some endodontic procedures on molars. A practice performing any of these without first checking the specific payer's requirement is exposed to CO-197.
This is arguably the most preventable denial in dental billing, because unlike a clinical judgment call or a coding ambiguity, the pre-auth requirement is a known, checkable fact before the appointment is scheduled. Every CO-197 traces back to a verification step that either wasn't done or wasn't done early enough.
Don't confuse CO-197 with CO-50
CO-197 means the authorization step itself was never requested. CO-50 means the payer reviewed the clinical case, often as part of that same authorization process, and decided the treatment wasn't medically necessary. A denial for missing paperwork is CO-197. A denial after review is CO-50.
How to fix a CO-197 denial,
two tracks, equal weight.
There are two things to do here, and neither is optional. Recover what you can from the denial in front of you, and make sure the next patient never generates one.
Retroactive
Request Retro Auth
N210, MA130
Prevention
Verify Before Scheduling
N210, N386
Verify Requirement
Confirm Auth Was Actually Required
N210, N386
- 1
Track one: Request retroactive authorization.
Most payers allow a grace period, commonly 14 to 30 days from the date of service, to request retrospective approval. Call the payer or check their portal for the exact window before it closes.
- 2
Submit full clinical documentation with the retro request.
Radiographs, periodontal charting, and clinical notes explaining why the procedure was performed should accompany the retroactive authorization request. The stronger the documentation, the better the odds of approval after the fact.
- 3
For emergencies, invoke the payer's exception path.
Most payers have an emergency exception to the pre-auth requirement, but it still requires documentation of the acute condition, like infection, swelling, or pain, to invoke. Don't assume the exception applies automatically just because the procedure felt urgent.
- 4
Track two: Build pre-auth checks into scheduling, not billing.
The single biggest shift that eliminates CO-197 going forward: move the pre-auth check to the point of scheduling, before the appointment is booked, not after the procedure is performed. Billing catching it after the fact is too late.
- 5
Track down payer-specific thresholds in writing.
Build a reference of which procedures need pre-auth for each major payer your practice sees, including dollar thresholds where they apply. This turns a judgment call into a checklist item the front desk can run every time.
| Track | Codes You'll See | The Fix |
|---|---|---|
| Retroactive authorization | N210, MA130 | Request retrospective approval within the payer's grace period with radiographs, charting, and clinical notes. |
| Prevention at scheduling | N210, N386 | Verify the specific payer's pre-auth threshold for the procedure before the appointment is booked. |
This is the denial pre-appointment verification is built for.
Needletail checks pre-authorization requirements for every procedure and every payer before the appointment is ever scheduled, so the practice never performs a procedure without the approval already secured. No retroactive scramble, no grace-period countdown.
CO-197 RARC decoder:
what each remark code means.
CO-197 carries a small, consistent set of remark codes. Here's what each one confirms about the authorization gap.
Authorization Status
| RARC | What the Payer Is Saying | Dental Context | The Fix |
|---|---|---|---|
| N210 | Authorization/precertification required but not obtained | The standard RARC confirming the procedure needed pre-auth and the claim shows none | Request retroactive authorization within the payer's grace period, with full clinical documentation. |
| MA130 | Claim contains incomplete/invalid authorization number | An authorization may exist but the number on the claim is missing, wrong, or expired | Confirm the correct authorization number with the payer and resubmit as a corrected claim. |
| N386 | This decision was based on a National Coverage Determination (NCD) | Ties the authorization requirement to the plan's own coverage determination rules | Check the specific plan provision that requires authorization for this procedure before resubmitting. |
If your RARC isn't in this table, pull the full code from your ERA/835 file and look it up in the official RARC code list. N210 is by far the most common companion to CO-197 in dental claims.
N210 showing up every week? That's a process gap, not bad luck.
A missing pre-auth is the single most preventable denial in dental billing. Needletail's verification flags the exact payer and procedure combinations that require authorization before anything gets booked, so N210 stops appearing on your ERA.
Common causes of CO-197
in dental practices.
Three scenarios drive most dental CO-197s, ranked by how often they occur across the practices Needletail works with.
Procedure performed without any pre-auth request
N210Implant, crown, or ortho treatment started before anyone checked whether this payer requires authorization
Authorization expired before treatment
N210, MA130Pre-auth was approved but the treatment window (typically 60-90 days) lapsed before the procedure was performed
Emergency procedure without documentation
N210Urgent extraction performed without pre-auth, and the emergency exception wasn't properly documented
- This is the highest-volume cause, and it's almost always a process gap, not a judgment error. Implants, crowns above a certain dollar threshold, and orthodontic treatment are the usual suspects.
- The pattern: a treatment plan gets approved clinically, scheduled, and performed, with the pre-auth question never surfaced to anyone responsible for checking it. By the time billing files the claim, the procedure already happened.
- Multi-location DSOs see this at higher volume simply because more locations means more payers, each with a different threshold, and no single person tracking all of them by memory.
- Most pre-auth approvals have a treatment window, commonly 60 to 90 days, after which the authorization lapses even though it was genuinely approved at one point.
- Scheduling delays, patient reschedules, or a treatment plan that takes longer to finalize than expected can all push the actual procedure date past the authorization's expiration.
- The fix here isn't clinical documentation; it's tracking auth expiration dates in the scheduling system and re-requesting authorization before the window closes, not after the procedure is already done.
| Trigger | What's Wrong | RARC You'll See |
|---|---|---|
| Procedure performed without any pre-auth request | Implant, crown, or ortho treatment started before anyone checked whether this payer requires authorization | N210 |
| Authorization expired before treatment | Pre-auth was approved but the treatment window (typically 60-90 days) lapsed before the procedure was performed | N210, MA130 |
| Emergency procedure without documentation | Urgent extraction performed without pre-auth, and the emergency exception wasn't properly documented | N210 |
CO-197 vs.
CO-15, CO-50, and CO-16.
These three get confused with CO-197 because they all touch authorization or clinical review in some way. Here's the distinction.
| Code | Trigger | Who Owes | Type |
|---|---|---|---|
| CO-197 | Pre-authorization required but never obtained | Practice absorbs | Auth |
| CO-15 | Authorization number is present but invalid for the services billed | Practice absorbs | Auth |
| CO-50 | Payer judges the treatment not medically necessary | Practice absorbs | Clinical |
| CO-16 | Claim missing or has invalid data | Practice absorbs | Data |
CO-197 and CO-15 both involve authorization, but the problem is different. CO-197 means no authorization was ever requested. CO-15 means an authorization exists on the claim but doesn't match what was actually billed, often because the procedure changed between the authorization request and the actual treatment.
CO-197 and CO-50 are related but distinct: pre-authorization review often includes a medical necessity check, so a denied authorization request can resemble a CO-50 decision. If the procedure was never submitted for authorization at all, it's CO-197. If it was submitted and rejected on clinical grounds, it's closer to CO-50.
CO-16 is purely a data error. Some payers code a missing authorization number as CO-16 plus M62 instead of CO-197; the underlying fix is identical either way, get the authorization number and resubmit.
One verification pass. No procedure performed without approval.
Whether the question is pre-authorization, a stale auth number, or a medical necessity review, it all comes down to confirming the payer's requirement before treatment. Needletail's pre-appointment dental verification checks authorization status alongside everything else, in one pass, before the patient is ever scheduled.
How to prevent CO-197 denials
before they happen.
This is the most preventable code in the entire series. Every pre-auth requirement is a known, checkable fact before the appointment exists.
Check the payer's pre-auth requirement at treatment planning.
Confirm pre-auth requirement and threshold for this payer before scheduling.
Submit the pre-auth request with full documentation.
Submit complete clinical documentation with the initial pre-auth request.
Track authorization expiration dates.
Log expiration dates and re-request authorization before any lapse.
Build a payer-specific pre-auth reference.
Keep a current, payer-specific pre-auth requirement reference.
Why this is the highest-value fix in the series
Unlike a coding error or a clinical judgment call, a missing pre-authorization is 100 percent knowable before the appointment. A practice that verifies pre-auth requirements at scheduling, not at billing, eliminates CO-197 almost entirely. Needletail checks pre-auth requirements per procedure and per payer before scheduling, so the practice never performs a procedure without the required approval already in hand.
Make this checklist automatic.
Needletail runs the 48-hour prevention checklist for every scheduled patient: automated eligibility pulls, subscriber matching, and NPI checks, without a biller touching a portal.
Real dental practice
scenarios.
These three come straight from dental billing teams. All three could have been avoided with a pre-auth check at scheduling.
Implant placed without any pre-auth request
A practice performs D6010 (implant body placement) without ever checking whether the payer required pre-authorization for implants.
What comes back
CO-197 + N210 (authorization required but not obtained).
The fix
Request retrospective authorization within the payer's grace period, typically 14 to 30 days, submitting radiographs, perio charting, and clinical notes to support the retroactive request.
How to prevent it
Build implant placement into the pre-auth checklist for every payer that requires it, so the authorization request goes out before the procedure, not after.
Crown authorization expired before treatment
D2750 (crown) had pre-auth approved, but the treatment window of 60 to 90 days lapsed before the procedure was actually performed due to scheduling delays.
What comes back
CO-197 on the claim submission, despite the original approval.
The fix
Request re-authorization before the original approval's expiration date whenever possible, or submit a new retroactive request if the window has already closed.
How to prevent it
Track authorization expiration dates directly in the scheduling system, with an alert when a scheduled date is approaching the auth's expiration window.
Emergency extraction without documented exception
An emergency extraction (D7210) is performed without pre-auth due to the acute nature of the visit, but the documentation supporting the emergency exception wasn't captured at the time.
What comes back
CO-197 denial, despite most payers having an emergency exception available.
The fix
Appeal with documentation of the acute infection, swelling, or pain that made the procedure urgent, requesting retrospective approval under the payer's emergency exception.
How to prevent it
Build emergency documentation capture into the clinical workflow itself, so the exception can be invoked without a scramble after the fact.
What these three have in common
Every one of them had a known, checkable authorization requirement before the procedure was ever performed.
- The payer's pre-auth rule for implants, crowns, and extractions existed before the patient was scheduled, not after the claim was filed.
- None of these required a clinical judgment call once the payer's specific requirement was checked at the right point in the workflow.
- Needletail's dental verification identifies pre-authorization requirements per procedure and per payer before scheduling, so the practice never performs a procedure without the required approval already secured.
- This is the single area where pre-appointment verification has the most direct, measurable impact: moving the check from billing to scheduling eliminates the denial almost entirely.
Secure the authorization before scheduling, not after the denial.
Needletail verifies dental eligibility, benefits, and pre-authorization requirements before every appointment. AI voice agents and portal automation confirm what's required for the specific procedure and payer, and human specialists review every verification before the full breakdown goes into your PMS, so no procedure gets performed without the approval it needs.
Your call is with Jofin Joseph,
Co-Founder and CEO.
Questions about this code