- CO-197 indicates an authorization requirement issue: The payer is indicating that required precertification, authorization, notification, or pre-treatment is absent.
- Do not automatically appeal: First confirm whether authorization was actually required, whether it existed, and whether the payer received or matched it correctly.
- Choose the resolution based on what happened: If authorization exists, a corrected claim or payer reprocessing request may be appropriate. If it never existed, check the payer’s retroactive authorization and exception rules before choosing the next step.
- CO-197 is not the same as other authorization-related CARCs: Do not confuse it with codes 198, 210, 284, 296, or 302. Each points to a different problem and a different resolution path.
A CO-197 denial can look straightforward: the payer says authorization was missing, the claim did not pay, and the billing team now has to fix it.
In practice, the right next action depends on a much more specific question: was the required authorization truly absent, or did the payer fail to find, match, or apply it correctly?
That distinction determines whether your team should correct and resubmit the claim, request reprocessing, pursue retroactive authorization, or prepare an appeal.
This guide explains CO-197 from the point of view of a medical billing and revenue cycle team, with current definitions from X12, current prior authorization requirements from CMS, and program-specific examples from Medicare Administrative Contractor guidance.
What Does CO-197 Denial Code Mean?
X12 defines Claim Adjustment Reason Code 197 as “Precertification /authorization/notification/pre-treatment absent.” The code is part of the standardized CARC set used to explain why a claim or service line was paid differently from the amount billed.
The authoritative definition is maintained in the X12 Claim Adjustment Reason Code list.
When a remittance shows CO-197, read the two parts separately:
- CO is the Claim Adjustment Group Code for Contractual Obligation. X12 uses group codes to categorize the adjustment and generally assign responsibility for the adjusted amount.
- 197 is the Claim Adjustment Reason Code explaining the authorization-related reason for the adjustment.
For a broader explanation of CO, PR, OA, and PI group codes, see Droidal’s Medical Billing Denial Codes guide and the official X12 Claim Adjustment Group Codes reference.
Important distinction
CO-197 does not automatically tell you whether the payer is correct, whether the claim is unrecoverable, or whether an appeal is the best first step. It tells you the adjustment reason the payer reported. Your team still has to validate the underlying authorization facts.
Why Does a Claim Receive CO-197?
1. Required Authorization Was Never Obtained
The service required prior authorization under the patient’s plan, but no request was completed before the service. This is the clearest CO-197 scenario. Recovery may depend on the payer’s retroactive authorization rules, documented exceptions, or appeal criteria.
2. Authorization Exists, but the Claim Does Not Carry the Required Reference
The authorization was obtained, but the authorization or tracking number was missing from the claim, entered in the wrong field, or not transmitted from the practice management system to the clearinghouse or payer. In this case, the problem may be claim linkage rather than authorization itself.
3. Required Notification or Precertification Was Missed
Some payer workflows require notification or precertification even when the clinical service is ultimately covered. Missing the required step can result in CO-197 even when the underlying service is medically appropriate.
4. The Payer’s Authorization Rule Changed
Requirements can vary by plan, service, location, network status, and effective date. A service that did not require authorization for one plan year or product may require it later. Revenue cycle teams should verify the rule that applied on the actual date of service.
5. An Urgent or Emergency Exception Was Not Documented Correctly
Emergency and urgent scenarios may follow different authorization or notification rules. If the provider relied on an exception, the payer may still deny when required post-service notification, documentation, or timing requirements were not met.
6. The Payer Failed to Identify an Authorization That Was Already in Place
An authorization can exist yet fail to match because of incorrect member information, service details, provider identifiers, facility data, dates, or payer processing. Before treating CO-197 as a true missing-authorization denial, compare the approval record to the claim and remittance line by line.
CO-197 vs. Other Prior Authorization Denial Codes
| CARC | What It Indicates | How It Differs From 197 |
|---|---|---|
| 197 | Precertification/authorization/notification/pre-treatment absent | The required authorization or notification is absent. |
| 198 | Precertification/notification/authorization/pre-treatment exceeded | Authorization exists, but the approved limit was exceeded. |
| 210 | Authorization was not received in a timely fashion | The issue is timing, not simply absence. |
| 284 | Authorization number may be valid but does not apply to billed services | The authorization does not match the service billed. |
| 296 | Authorization number may be valid but does not apply to the provider | The authorization does not match the provider. |
| 302 | Authorization/pre-treatment time limit has expired | The authorization period has expired. |
How to Fix CO-197 Denial Code: A Step-by-Step Workflow
Step 1: Read the Full Remittance, Not Only “197”
Review the ERA or EOB at the claim and service-line level. Capture the group code, CARC, any Remittance Advice Remark Code (RARC), payer message, adjustment amount, claim control number, and date of service. The companion remark code may clarify whether the payer expects correction, documentation, or appeal.
Step 2: Verify Whether Authorization Was Required
Check the payer’s rule for the patient’s exact plan and date of service. Confirm the billed CPT/HCPCS or service category, place of service, rendering provider, facility, network status, and whether the rule applied to the specific clinical scenario. Do not rely only on a generalized payer list if a current plan-specific provider manual or portal is available.
Step 3: Search for the Authorization Record
If authorization was required, locate the approval or request history. Verify the authorization number, patient/member identifiers, approved service, dates, units or visits, provider, facility, and status. Compare each item to the claim. A mismatch can change the correct CARC and the resolution path.
Step 4: Choose the Right Correction Path
If a valid authorization exists but was missing from the claim, correct the claim or request reprocessing based on the payer’s instructions. If authorization never existed, check whether the payer allows retroactive authorization, emergency exceptions, or other documented post-service review. If the payer incorrectly applied the requirement, prepare evidence and request reconsideration or appeal.
Step 5: Protect the Filing and Appeal Timeline
Document the denial date, every payer contact, portal reference, retroactive authorization request, corrected claim date, and appeal deadline. A recoverable CO-197 can become unrecoverable if the team waits until a filing or appeal window closes.
Corrected Claim vs. Retroactive Authorization vs. Appeal
| Situation | Recommended First Path |
|---|---|
| Valid authorization exists, but the claim omitted the required reference | Follow payer instructions for corrected claim submission or reprocessing with the authorization information. |
| Authorization exists and matches, but payer says it is absent | Send the authorization evidence and request payer reprocessing or reconsideration. |
| Authorization was required and never obtained | Check payer rules for retroactive authorization, post-service review, or an applicable exception. |
| Payer rule did not require authorization on the date of service | Document the applicable payer rule and request correction/reprocessing. |
| Emergency or urgent circumstances affected the normal process | Confirm the plan’s emergency or notification rules and submit the required supporting documentation. |
| Retroactive authorization is unavailable or denied | Evaluate whether a formal appeal is supported by the clinical facts, payer policy, and documentation. |
Do Not Skip This Check
If the authorization exists but applies to a different service, provider, or time period, the denial may align more closely with CARC 284, 296, or 302 than CARC 197. Correct classification helps your team choose the right payer conversation and avoid unnecessary appeals.
What Documents Should You Gather for a CO-197 Review?
A complete denial packet reduces back-and-forth and makes the next action easier to defend. Depending on the payer and case, gather:
- The ERA or EOB showing CO-197 and any RARC or payer message.
- The original claim and service-line details.
- Authorization approval, reference number, portal confirmation, or payer letter if one exists.
- The payer authorization requirement that applied on the date of service.
- Clinical order, referral, and supporting medical documentation when relevant to the payer’s review.
- Proof of any pre-service request, phone call, portal submission, fax, or payer interaction.
- Emergency or urgent-care documentation if an exception is being claimed.
- Payer call reference numbers and names/IDs of representatives when available.
- Corrected claim or reprocessing confirmation if a prior correction was already submitted.
- A clear timeline from scheduling through denial so the root cause is visible.
What Does CO-197 Look Like on an ERA or EOB?
Payer displays vary, but an ERA or EOB will typically show the adjustment group, CARC, adjustment amount, and sometimes a RARC or payer-specific message. A simplified CO-197 example may look like this:
| Field | Illustrative Example | Why It Matters |
|---|---|---|
| Group Code | CO | Shows the adjustment category as Contractual Obligation. |
| CARC | 197 | Indicates that required precertification, authorization, notification, or pre-treatment is absent. |
| RARC | Example: N210 in certain Medicare DME cases | Adds payer- or program-specific context. The same RARC should not be assumed across all payers. |
| Adjustment Amount | $1,250.00 | Shows the amount adjusted on the claim or service line. |
| Claim Control / Reference | Payer-specific | Helps the billing team track reprocessing, corrected claims, or appeal follow-up. |
Medicare DME Example
In certain Medicare DME cases, Noridian associates CARC 197 with RARC N210 and provides specific instructions for submitting an approved Unique Tracking Number. For those claims, the 14-byte Unique Tracking Number may need to be reported in CMS-1500 Item 23 or the applicable 837 electronic claim REF segment.
This guidance is specific to that Medicare DME workflow and should not be applied automatically to other payers or plans. Always review the payer’s authorization and claim-submission requirements before correcting or resubmitting the claim.
Is CO-197 Patient Responsibility?
When the remittance specifically shows CO-197, the CO group code means Contractual Obligation under X12. That is different from PR, which means Patient Responsibility. X12 notes that group codes categorize the adjustment and generally assign responsibility for the adjusted amount. See the X12 Claim Adjustment Group Codes.
Operationally, that means your billing team should not move the denied amount to the patient simply because the claim contains CARC 197.
Review the actual group code, payer contract, member benefit terms, notices, and applicable federal or state requirements before transferring liability.
Also remember that CARC 197 is a reason code and can appear with different group codes in different circumstances. For example, historical Medicare DME guidance has documented CARC 197 with either CO or PR depending on specific Advanced Beneficiary Notice conditions. The exact remittance combination matters.
CO-197 Across Medicare, Medicare Advantage, and Commercial Payers
The CARC definition is standardized, but the operational requirements behind it are not identical across payers. Teams should separate the standardized denial code from the payer-specific rule that triggered it.
| Payer Context | What to Verify |
|---|---|
| Traditional Medicare / MAC Program | Whether the item or service is in a prior authorization program, required tracking/reference information, modifier rules, and the Medicare Administrative Contractor’s denial-resolution guidance. |
| Medicare Advantage | Plan-specific authorization lists, network and delegated authorization rules, approved dates/units, service and provider matching, and plan appeal requirements. |
| Medicaid / CHIP | State and managed-care-plan rules, required authorization workflow, turnaround requirements, and applicable provider manuals. |
| Commercial Plans | Employer/product-specific authorization requirements, payer portal rules, network requirements, and the plan’s correction, retroactive authorization, and appeal processes. |
The practical rule is simple: use the CARC to identify the category of problem, then use the payer’s current policy for the date of service to determine the exact fix.
What Changed for Prior Authorization in 2026?
CO-197 remains an established CARC, but the regulatory environment around prior authorization changed materially in 2026. Under the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), impacted payers must meet specified prior authorization decision timeframes for medical items and services: 72 hours for expedited requests and seven calendar days for standard requests.
CMS also requires impacted payers to provide a specific reason when a prior authorization request is denied. These provisions do not apply to drugs under this rule.
CMS has also stated that electronic Prior Authorization API requirements for impacted payers take effect January 1, 2027. For revenue cycle teams, this makes authorization data quality, status visibility, and standardized handoffs increasingly important. Droidal covers the operational implications in its CMS-0057-F Prior Authorization API Requirements guide.
Where CO-197 Risk Shows Up Across Specialties
The denial code is the same, but the workflow risk differs by specialty. These examples help teams look upstream instead of treating every CO-197 as a billing-office problem.
| Specialty | Common Authorization Risk |
|---|---|
| Radiology | Advanced imaging rules can vary by payer and modality; scheduling and authorization data must stay aligned with the ordered study and date. |
| Orthopedics | Procedures, imaging, injections, DME, and therapy can carry different authorization requirements within the same episode of care. |
| Cardiology | High-cost diagnostic and interventional services may require plan-specific review, and changes to the planned service can break the original authorization path. |
| Oncology | Treatment regimens can change quickly; payer requirements may depend on drug, dose, diagnosis, site of care, or treatment plan. |
| DME | Certain programs require a specific prior authorization decision and tracking information to follow the claim correctly. |
| Behavioral Health | Visit limits, level-of-care changes, and plan-specific authorization rules can create gaps between scheduled care and approved care. |
How to Prevent CO-197 Before the Claim Is Submitted
The most reliable way to reduce CO-197 denials is to move the control point upstream. By the time the denial reaches the remittance, the service has already been delivered and recovery options may be narrower.
| Revenue Cycle Stage | CO-197 Prevention Check |
|---|---|
| Scheduling | Determine whether the service requires prior authorization for the patient’s plan, provider, facility, and date. |
| Pre-Service Review | Confirm the requested service, diagnosis, clinical documentation, location, and rendering provider match payer requirements. |
| Authorization Submission | Record the request date, reference number, submitted documents, status, approved service, dates, units/visits, provider, and facility. |
| Before Service | Reconfirm that the approval is still applicable when the procedure, date, provider, location, or treatment plan changes. |
| Charge Capture | Make sure the performed service maps back to the authorization that was actually approved. |
| Claim Creation | Carry required authorization/reference data into the claim in the payer-specified location. |
| Pre-Submission QA | Flag claims that require authorization but have no matching approval record before they leave the billing system. |
| Denial Analytics | Track CO-197 by payer, specialty, location, service, and root cause so recurring upstream gaps are visible. |
If your organization is evaluating how manual and AI-supported authorization workflows differ, see Manual vs. AI Prior Authorization for a broader workflow comparison.
How AI Agents Can Help Reduce Authorization-Related Denials
CO-197 is often the downstream signal of an upstream workflow gap. The goal is not simply to work the denial faster. It is to keep the authorization decision connected to the service and claim so the denial does not occur in the first place.
Droidal’s Prior Authorization AI Agent can support authorization requirement checks, clinical documentation gathering, request submission, status tracking, denial and appeal support, and approval alerts within configured workflows. For denials that have already occurred, the Denial Management AI Agent can classify remittance responses, route denials to the appropriate next action, prepare corrected resubmissions, support appeal-letter generation, and surface recurring denial patterns.
- Identifying whether authorization is required before the date of service.
- Keeping payer requirements and supporting documentation together in the authorization workflow.
- Tracking pending requests and surfacing cases that need follow-up.
- Recording approval details so they remain available when the claim is built.
- Flagging claims that appear to require authorization but have no matching approval record.
- Separating true missing-authorization denials from service, provider, timing, or matching issues.
- Routing recoverable denials toward correction, retroactive review, or appeal based on the configured payer workflow.
The broader objective is a cleaner handoff from authorization to claim submission, with fewer avoidable denials reaching the back-end revenue cycle. Book a demo to see how Droidal’s AI Agents can support authorization and denial workflows within your existing RCM environment.
