CO-22 DENIAL CODE: AT A GLANCE
| Code | CARC 22 |
| Official CARC Name | Claim Adjustment Reason Code 22 |
| Group Code | CO: Contractual Obligation |
| Official X12 Definition | “This care may be covered by another payer per coordination of benefits” |
| Active Since | January 1, 1995 |
| Last Modified | September 30, 2007 (still active as of 2026) |
| Common Remark Code | MA04 |
| Can Provider Bill Patient | No |
| Primary Resolution | Verify COB order and resubmit to correct payer |
| Payers Affected | Medicare, Medicaid, BCBS, all commercial payers |
The CO-22 denial code means another payer might be responsible. X12 defines CARC 22 as: “This care may be covered by another payer per coordination of benefits.”
That CO group code stands for Contractual Obligation. You can’t bill the patient while the coordination of benefits issue remains unresolved.
CO-22 isn’t a clinical denial. It doesn’t flag documentation errors or wrong codes. This is a data and workflow failure. The issue starts at registration and shows up on your Explanation of Benefits or Electronic Remittance Advice.
Unresolved claims stretch A/R days and drain cash flow. They also put your revenue cycle at risk of timely filing write-offs. This guide covers the causes, resolution steps, and prevention tactics you need.
What Is the CO-22 Denial Code
The CO-22 denial code description for CARC 22 in the X12 standard is: “This care may be covered by another payer per coordination of benefits.” You’ll find this on the X12 CARC 22 official definition page. This code has been active since January 1, 1995, was last modified on September 30, 2007, and remains unchanged as of 2026.
Pay attention to the word “may” in that definition. It signals the payer believes another insurer could be responsible, not that one definitely is. This distinction gives you room to appeal. If your eligibility verification shows no other coverage, you can challenge the payer’s assumption with documentation.
A CO-22 denial code doesn’t mean your claim is invalid. The service wasn’t rejected for medical necessity, and your coding isn’t wrong. The claim just went to the wrong payer first.
The service might be fully covered, but a different insurer holds primary responsibility. The denial code CO-22 means you resubmit to the correct payer instead of appealing medical necessity. You’re fixing a routing error, not defending clinical care.
On paper remittances, you’ll find CO-22 in the adjustment reason section of the Explanation of Benefits. Electronic Remittance Advice records show the CO-22 denial code in the CAS segment of the X12 835 transaction. Scan for the exact notation: CASCO22*[adjustment amount].
That CAS segment notation tells your billing system how to flag the claim. Train your team to recognize the denial code CO 22 pattern so they can route the claim correctly.
The CO group code stands for Contractual Obligation. You can’t bill the patient due to this Contractual Obligation while the coordination of benefits issue stays open. Trying to collect now triggers compliance violations and patient complaints.
Delays push claims toward timely filing deadlines with the correct primary payer. A solvable denial can turn into a permanent write-off if you wait too long. High-volume practices need systematic workflows. One O Seven RCM’s medical billing services include systematic COB verification and denial resolution protocols that prevent CO-22 from reaching the write-off stage.
CO-22, PR-22, OA-22, and PI-22: Understanding the Prefix Difference
Reason code 22, often called denial code 22, doesn’t always mean the same thing. The number 22 points to a coordination of benefits situation, but the group code in front tells you who owes the money. A CO-22 denial code tells you to bill another insurer. A PR-22 tells you to bill the patient.
Mixing these up leads to wrong statements, missed revenue, and compliance trouble. Here’s how each prefix changes your next move.
| Group Code | Full Name | What It Means | Can You Bill the Patient | Resolution Action |
| CO-22 | Contractual Obligation | Another payer is expected to be primary. Provider write-off required while COB is unresolved. | No | Identify correct primary payer and resubmit |
| PR-22 | Patient Responsibility | The patient is responsible for this balance. No other primary payer applies in this context. | Yes | Bill the patient directly after COB verification |
| OA-22 | Other Adjustment | Adjustment that does not fit CO or PR category. Common in Medicare secondary contexts. | Situation-dependent | Contact payer for specific COB guidance |
| PI-22 | Payer Initiated | Payer made this adjustment post-payment during review when COB data was discovered after processing. | No | Contact payer to verify COB data accuracy |
The PR 22 denial code causes the most confusion. When your remittance shows PR-22 instead of the CO-22 denial code, the group code shifts from the CO group code to Patient Responsibility. The payer has decided the patient owes this balance. Some systems display the pr22 denial code without a hyphen.
The PR-22 denial code description explicitly states Patient Responsibility. Check for missed secondary coverage before you send the statement.
You can bill the patient after a PR 22 denial code. You can’t bill the patient after CO-22 without risking a compliance violation. This rule protects your practice from billing errors and keeps patient trust intact.
The OA-22 denial code shows up mostly in Medicare secondary scenarios. You’ll see the OA-22 denial code when Medicare processes a claim as secondary but the adjustment falls outside normal CO or PR categories. Some remittances list the OA 22 denial code with a space instead of a hyphen.
Contact the payer to clarify the adjustment reason. This code often requires manual review because automated rules don’t apply.
The PI-22 denial code means the payer found COB data after processing and made a retroactive change. The PI-22 denial code indicates the payer initiated this adjustment without a new claim submission. You might see the PI 22 denial code formatted differently in some clearinghouse reports.
This often happens when a patient updates their coverage mid-cycle or the payer receives late COB questionnaire data. You’ll need to verify the COB data accuracy before you accept the change or file an appeal. Call the payer to confirm the update matches your records.
How CO-22 Appears on Your ERA and the MA04 Remark Code Connection
Payers send payment data through the X12 835 transaction, known as the Electronic Remittance Advice. Adjustments live in the CAS segment, short for Claim Adjustment Segment. Your billing system reads this segment to post payments and denials automatically.
Here’s the thing: the CAS segment breaks down adjustments line by line. Each segment holds the group code, reason code, and monetary value. Your practice management system parses these elements to update the account balance. If the CAS segment shows CO-22, the system flags the claim for COB review.
Look for the exact string: CASCO22*[denied amount]. The first element is the group code CO. The second is reason code 22. The third shows the dollar amount adjusted. Spotting this notation tells you exactly where the denial sits in the remittance data.
A Remittance Advice Remark Code adds context that the CARC alone doesn’t provide. The MA04 denial code is the most common remark paired with CO-22. Its official text reads: “Secondary payment cannot be considered without the identity of or payment information from the primary payer.”
MA04 functions as a RARC that clarifies the denial reason. Payers use RARCs to provide actionable instructions beyond the standard CARC list. The MA04 denial code description explicitly tells you what documentation is missing. Ignoring this remark code guarantees the secondary claim will reject again.
When the CO-22 denial code appears with MA04, the payer is sending two messages. Another insurer holds primary responsibility, and the secondary claim can’t process until you supply the primary payer’s identity and payment details. Noridian documents this CO-22 and MA04 pairing in its Noridian MA04 guidance for providers.
That combination almost always means you submitted a secondary claim without the primary payer’s Explanation of Benefits. The secondary payer needs proof of what the primary plan paid and what the patient owes.
Grab the primary remittance showing the paid amount, deductible, coinsurance, and copay. Resubmit the secondary claim with those details populated in the correct fields. Sending the claim again without this documentation triggers the same denial code MA04 and CO-22 loop.
Scan for the CO 22 remark code pairing to triage quickly. CO-22 without MA04 points to a different problem. The claim went to the wrong primary payer instead of missing secondary documentation.
You need to identify the correct primary insurer and route the original claim there first. Gathering a primary EOB won’t help because you haven’t billed the right payer yet.
The 5 Real Causes of CO-22 Denials (And 4 Codes Commonly Mislabeled as CO-22)
The CO-22 denial code is strictly a coordination of benefits denial. It doesn’t trigger for wrong codes, medical necessity gaps, duplicate submissions, out-of-network status, or non-covered services. Those scenarios produce different CARCs entirely. Payers issue this covered by another payer denial code only when COB sequencing or data is the issue.
Some billing resources list those issues as CO-22 causes. That mistake sends your team down the wrong path. You’ll contact the wrong department, request useless documents, and waste days on claims that need a simple COB fix. The five causes below are the only real triggers for a coordination of benefits denial code.
If your practice sees CO-22 denials mixed with unrelated codes, One O Seven RCM’s denial management services can audit your patterns and find the true root causes.
Cause 1: The Claim Was Submitted to the Wrong Primary Payer
This is the most common trigger. The provider bills the secondary insurer before the primary plan adjudicates the claim. What usually happens is the secondary system detects other active coverage and kicks the claim back.
Take a patient with an employer group health plan and Medicare Advantage. If the employer has 20 or more employees, the group plan pays first. Billing Medicare first generates a CO-22 denial code on the Medicare remittance because Medicare knows the employer plan is primary.
The secondary payer won’t process the claim until the primary adjudication completes. Resubmitting to the secondary without fixing the order just creates rework. You have to pull the claim back and send it to the primary insurer first.
Cause 2: Outdated or Unverified Coordination of Benefits Information
Payers often require patients to complete a COB questionnaire confirming which plan is primary. When the patient ignores this form, the payer freezes adjudication for that member.
Your claims hit a CO 22 denial code reason tied to pending COB data. The block stays in place until the patient calls the insurer and updates their file. This is a patient-side issue that requires outreach from your front desk.
Cause 3: Medicare Secondary Payer Rules Not Applied
Medicare Secondary Payer rules under 42 U.S.C. 1395y(b) dictate when Medicare pays second. Medicare is secondary for patients with employer coverage through a company with 20 or more employees. It also pays second for Workers’ Compensation, auto accidents, and liability cases.
Liability insurance includes no-fault and homeowner policies when an injury occurs on private property. Medicare requires a conditional payment investigation in these cases. The denial protects Medicare from paying when another source holds liability for the medical costs.
That’s why billing Medicare first in these situations triggers a denial. The system flags the other coverage and denies primary responsibility. You’ll see the CO-22 denial code until you bill the correct primary payer and submit the crossover claim properly.
Cause 4: Birthday Rule Conflict for Dependent Children
The Birthday Rule decides primary coverage for dependents on both parents’ plans. The parent with the earlier birthday in the calendar year holds the primary plan. You compare month and day only, not the birth year.
If the father’s birthday is March 10 and the mother’s is September 22, the father’s plan is primary. Billing the mother’s plan first causes a denial. The mother’s insurer issues a CO 22 denial code descriptions note pointing to the father’s coverage as primary.
Cause 5: Missing Coordination of Benefits Data on the Claim Form
Payers cross-check claims against internal COB databases and clearinghouse data. If their records show other coverage but your claim lacks the required fields, the system flags it automatically.
The X12 837 transaction requires other payer details in Loop 2320 and Loop 2330A. Omitting these loops triggers a denial code CO 22 even when you bill the correct primary payer. The claim must disclose and sequence all active coverage to avoid the rejection.
Loop 2320 carries the other payer name and payment data. Loop 2330A holds the other payer subscriber information. Your clearinghouse may reject the claim before it reaches the payer if these loops are empty. Always populate COB fields when dual coverage exists.
These scenarios are not CO-22. They generate different codes and need different fixes. Applying CO-22 resolution to these codes delays payment and frustrates your staff. Each code has a distinct workflow. CO-97 requires contract review. CO-96 needs benefit verification. CO-18 demands a claim merge or void. Treating them as COB issues sends your team in circles.
| Scenario | Correct CARC | Why It Is Not CO-22 |
| Out-of-network provider | CO-97 | Network restriction, not COB |
| Non-covered service | CO-96 | Benefit exclusion, not COB |
| Duplicate claim submission | CO-18 | Exact duplicate, not COB |
| Lack of prior authorization | CO-15 or CO-167 | Authorization failure, not COB |
Understanding Coordination of Benefits in Medical Billing
Coordination of Benefits determines payment order when a patient carries multiple active policies. The goal is simple. Payers prevent duplicate payments so total reimbursement never exceeds 100% of charges. CMS governs COB for Medicare and Medicaid programs. You can review the rules on the CMS Coordination of Benefits page. Commercial plans follow NAIC model regulations adopted by most states.
The primary payer processes the claim first and pays according to its contract. The secondary payer waits for the primary adjudication before reviewing the remaining balance. Secondary plans only cover amounts that fall within their specific benefits after the primary payment applies.
Here’s a quick example. A service billed at $500 might get $350 from the primary payer. A $150 balance remains. The secondary payer evaluates that $150 against the patient’s secondary benefits. They determine if coinsurance or copay amounts apply before calculating any patient responsibility.
The following table shows how COB rules determine payer order in common scenarios.
| Coverage Scenario | Primary Payer | Secondary Payer |
| Both spouses have separate employer plans | Each person’s own employer plan | Spouse’s plan |
| Dependent child, parents married | Parent whose birthday is earlier in the year | Other parent’s plan |
| Dependent child, parents divorced | Custodial parent’s plan | Non-custodial parent’s plan |
| Patient has Medicare and employer plan (20+ employees) | Employer plan | Medicare |
| Patient has Medicare and employer plan (under 20 employees) | Medicare | Employer plan |
| Patient has COBRA and new employer coverage | New employer plan | COBRA |
| Patient has Medicaid and any other coverage | Any other coverage first | Medicaid (always last) |
Every scenario in that table can trigger a CO-22 denial code if you bill the wrong payer first. Complex coverage situations increase your risk significantly. Systematic verification at registration stops these denials before they start. One O Seven RCM’s denial management services include COB verification protocols for all of these scenarios.
STRUGGLING WITH RECURRING CO-22 DENIALS?
One O Seven RCM’s denial management team identifies the root cause of every CO-22 denial your practice receives. We implement payer-specific resolution workflows that stop recurrence. Our clients see measurable reductions in COB-related denials within the first billing cycle.
Contact our team for a free denial analysis.
View Our Denial Management Services
CO-22 Denial Code by Payer Type: Medicare, Medicaid, BCBS, and Commercial Plans
CO-22 denials require different workflows depending on the payer. Medicare follows MSP rules. Medicaid enforces last-resort requirements. BCBS uses BlueCard processing for multi-state claims. Commercial payers rely on COB portals with specific update procedures. Using a generic approach for every payer slows you down and creates unnecessary rework.
Medicare CO-22 Denial Code: MSP Rules and Resolution
Medicare CO-22 denials follow Medicare Secondary Payer rules. According to CMS, Medicare denies primary payment when their system shows other insurance is responsible. This guidance was last updated February 12, 2026. The most common trigger involves patients with employer group health plans at companies with 20 or more employees. That employer plan pays first.
You need to separate claims issues from database errors. Contact your Medicare Administrative Contractor for processing questions. If Medicare’s records show coverage the patient denies, call the Benefits Coordination and Recovery Center at 1-855-798-2627. The BCRC handles MSP database corrections directly. Review the CMS MLN MSP Fact Sheet MLN7748519 for current billing order guidance.
Verify your payer contracting status to confirm network obligations. In-network rules still apply once you identify the correct primary payer.
Medicaid CO-22 Denial Code: The Last Resort Rule
Medicaid operates as the payer of last resort under federal law. The program won’t process a claim until you bill all other active coverage first. A CO 22 denial code Medicaid scenario means you submitted to Medicaid before exhausting commercial plans, Medicare, or COBRA.
Resolution requires a complete coverage audit. Identify every non-Medicaid policy the patient holds. Bill those plans and obtain their EOBs. Resubmit to Medicaid with all prior payer adjudication details attached. Check your state Medicaid provider manual for specific COB filing requirements. States often have unique sequencing rules.
BCBS CO-22 Denial Code: BlueCard and Multi-Plan Coordination
Blue Cross Blue Shield plans use the BlueCard program to route claims through the local host plan to the patient’s home plan. When a patient holds BCBS coverage in multiple states, the home plan usually serves as primary. A BCBS denial code 22 often means you billed the wrong BCBS plan first.
Standard COB rules apply when BCBS pairs with another carrier. The birthday rule governs dependent coverage. Employment rules determine spousal primary status. Contact BCBS provider relations if you need plan-specific sequencing guidance. Inter-plan coordination can get complex when multiple BCBS entities are involved.
Commercial Payers: UHC, Aetna, Cigna, Humana COB Requirements
Major commercial payers like UnitedHealthcare, Aetna, Cigna, and Humana cross-reference COB databases against employer enrollment data. These systems flag other active coverage and issue CO-22 denials until you verify the correct payer order. Each payer maintains a dedicated provider portal for COB updates. A phone call rarely updates the file permanently.
Prior authorization must come from the primary payer based on COB order. Getting auth from the wrong payer creates a denial you can’t fix easily. Network status doesn’t change COB sequencing. The correct primary payer is determined by COB rules regardless of your participation status. Understanding your credentialing and contracting position helps you manage network obligations across all active payers.
How to Fix a CO-22 Denial: Step-by-Step Resolution Workflow
Fixing a CO-22 denial starts with identifying the specific scenario. Using the wrong approach wastes time and risks your filing deadlines. You might appeal a claim that needs resubmission, or resubmit without the required documents. There are three distinct resolution paths. Identify your situation before you take any action.
TIMELY FILING ALERT
CO-22 resolution delays create a compounding risk. If the primary payer takes 30 to 60 days to adjudicate, and the secondary payer has a 90-day timely filing limit from the date of service, you may lose secondary payer collection rights before the primary claim resolves. Track all CO-22 claims against both primary and secondary payer timely filing deadlines simultaneously. One O Seven RCM’s AR follow-up team monitors timely filing exposure on every outstanding denial.
Resolution Path A: Secondary Claim Submitted Without Primary EOB (MA04 Pattern)
Stop and do not bill the patient. The CO group code prohibits patient billing while the COB issue remains open.
Confirm the MA04 remark code appears on the ERA. MA04 confirms this is a secondary claim missing primary documentation.
Contact the primary payer to obtain the Explanation of Benefits or ERA. You need the paid amount, deductible, coinsurance, and copay details.
Verify the primary payer’s claim control number and trace number from the primary ERA. These identifiers link the claims together.
Resubmit the secondary claim with complete primary adjudication information populated in the required fields. Missing data triggers an automatic denial.
Set a 14-day follow-up alert. Call provider services if the secondary payer doesn’t adjudicate within two weeks. Reference your resubmission date during the call.
Resolution Path B: Claim Submitted to Wrong Primary Payer
Confirm the actual primary payer by running an EDI 270/271 real-time eligibility check. You can also call both payers’ provider services lines to verify coverage order.
Verify the COB rule that applies to this patient. Check the birthday rule, employment rule, or MSP rule based on the coverage details.
Submit the original claim to the correct primary payer with all required COB fields populated. This is the most common resolution path.
Monitor the primary claim for adjudication. Hold the secondary claim until you receive the primary EOB. Submitting too early creates another denial.
Submit the secondary claim with the primary EOB attached once the primary payer adjudicates. Include all payment and adjustment details.
Document every action with timestamps, representative names, and reference numbers. A clean audit trail protects you during payer disputes.
Resolution Path C: Stale or Unverified COB Information
Contact the patient immediately. Explain that their claim is on hold pending updated coordination of benefits information.
Ask the patient to confirm all active insurance policies. You need effective dates, subscriber names, and policy numbers for every plan.
Instruct the patient to contact their insurer and complete the COB questionnaire. Provide the member services number if you have it available.
Update the patient’s insurance information in your practice management system. Reflect the verified coverage details accurately.
Call the payer’s COB department to confirm the update applied to the member record. Don’t assume the patient’s call fixed the file.
Resubmit the corrected claim once the payer confirms the COB update. If the patient claims no other coverage exists, obtain a signed patient attestation and submit it with your appeal.
Managing CO-22 resolution across multiple payers and patients requires a systematic workflow. Most practices lack the bandwidth to maintain this internally. One O Seven RCM’s medical billing services include full CO-22 denial resolution management across all three resolution paths.
How to Prevent CO-22 Denials: The Front-End Control System
CO-22 prevention is a registration design problem. Every CO-22 denial that reaches the billing team represents a data collection failure at patient intake. The claim was denied because the insurance information collected at registration was incomplete, outdated, or improperly sequenced. The AAPC’s coordination of benefits guidelines confirm that front-end eligibility verification is the primary defense against COB-related denials. Implementing systematic front-end controls eliminates the majority of CO-22 denials before a single claim is submitted.
The 12-Point Insurance Verification Checklist
Collect and verify these 12 data points at every patient visit. Coverage changes between visits more frequently than most practices account for. Treatment-course assumptions about insurance status create CO-22 exposure on every claim submitted after a coverage change occurs. Complete this checklist at every visit, not just the first.
- Subscriber full name exactly as it appears on the insurance card
- Subscriber date of birth, verified against the physical card
- Member ID number, which is distinct from the group number
- Group number, required for employer-sponsored plan identification
- Patient relationship to the subscriber: self, spouse, child, or other
- Plan name and payer ID, required for correct electronic claim routing
- Plan effective date, confirming coverage was active on the date of service
- Plan termination date, identifying recently expired or changed coverage
- Secondary insurance, asked explicitly using the intake script below
- Accident or work-related injury indicator, since Workers Compensation or auto coverage may be primary
- Employer name, required for MSP determination on Medicare patients
- Medicare status: for patients 65 or older or disabled, confirm MSP order before submitting any claim
The Four Intake Questions Every Registration Staff Member Must Ask
Train every registration team member to ask these four questions at every patient check-in, regardless of how long the patient has been with the practice. This isn’t optional for established patients. Coverage changes constantly, and the front desk is the only place where that change gets caught before it becomes a denied claim.
Question 1: “Do you have any other medical coverage today, including through a spouse, a parent, Medicare, or Medicaid?”
Question 2: “Has your insurance changed since your last visit with us?”
Question 3: “Is today’s visit related to a work injury, automobile accident, or any other situation involving liability or Workers Compensation coverage?”
Question 4: “If you have Medicare, are you currently employed or covered under an employer health plan through your job or your spouse’s job?”
These four questions surface the most common CO-22 triggers before the claim is ever submitted.
Technology Controls That Prevent CO-22 at the Claim Level
Front-end controls must be supported by technology that catches what human intake processes miss. Three specific tools handle the gaps that verbal scripts and checklists can’t fully close.
Real-Time Eligibility Verification: Run EDI 270/271 eligibility checks on the date of service, not just at initial registration. Payer COB records update daily. A check run at registration may be outdated by the time of service two weeks later.
Claim Scrubbing Rules: Configure your clearinghouse or practice management system to block secondary claim submission if the primary EOB fields are empty. This single rule eliminates the entire MA04 denial scenario before the claim ever leaves your system.
COB Exception Queue: Route all CO-22 denials to a dedicated queue with a same-day review SLA. Denials that sit without action for 30 days create timely filing risk that turns a solvable problem into a permanent write-off.
One O Seven RCM’s revenue cycle management technology includes all three of these controls as standard components of our denial prevention workflow.
The Prevention ROI Statement
For a practice submitting 400 claims per month with a 4% CO-22 denial rate, that’s 16 denied claims per month. At an average claim value of $280 and a rework cost of $30 per claim, the CO-22 denial code is costing this practice approximately $4,960 per month in combined revenue exposure and administrative overhead, before accounting for timely filing write-offs on claims that aren’t resolved in time. Reducing the CO-22 denial rate by 60% through front-end controls saves this practice nearly $36,000 annually.
That’s not a billing department problem. It’s a front-end investment with a calculable return.
CO-22 vs CO-24 Denial Code: Key Differences Every Biller Must Know
CO-22 and CO-24 are two of the most frequently confused Claim Adjustment Reason Codes in medical billing. Both carry the CO (Contractual Obligation) group code, which means the patient cannot be billed in either case. But their causes and resolution workflows are entirely different. Applying CO-22 resolution steps to a CO-24 denial, or vice versa, wastes time and delays payment.
How Each Code Works
The confusion usually starts at the remittance. Both codes appear under the same group classification, and both show up when a payer is declining to pay the full billed amount. That’s where the similarity ends.
CO-22 tells you the claim went to the wrong payer or that COB sequencing is incorrect. The payer believes another plan should be paying first. CO-24 tells you the service is included in a capitation arrangement. The payer isn’t saying someone else should pay; they’re saying the contracted payment structure already covers this service.
| Feature | CO-22 | CO-24 |
| Official CARC Description | “This care may be covered by another payer per coordination of benefits” | “Charges are covered under a capitation agreement or managed care plan” |
| Root Cause | Claim submitted to wrong primary payer or COB information missing | Provider is in a capitated contract and the service is included in the capitation payment |
| Primary Payer Trigger | Any payer when dual coverage exists and COB sequencing is incorrect | HMO or managed care payers when the service falls within a capitation arrangement |
| Resolution Path | Identify correct primary payer, obtain COB documentation, resubmit to correct payer in correct order | Verify capitation contract scope, contact plan administrator, request fee-for-service exception if service is outside capitation scope |
| Appeal Viability | Strong, if COB data is incorrect, appeal with eligibility documentation | Limited, if the service is genuinely capitated, the plan is contractually correct |
| Patient Billing | Cannot bill patient (CO = Contractual Obligation) | Cannot bill patient (CO = Contractual Obligation) |
The Distinguishing Rule
The fastest way to tell them apart: if the denial description references another payer or coordination of benefits, it’s CO-22 and requires COB verification. If the denial description references capitation or managed care, it’s CO-24 and requires contract review. The resolution workflows diverge completely from that point. Applying the wrong workflow to either code delays payment by 30 to 60 days on average.
When the remittance states that charges are covered under a capitation agreement or managed care plan, the denial is CO-24, not CO-22. That distinction matters because capitation denials require contract-level review with the managed care organization, not payer COB database updates. Sending a COB appeal for a CO-24 denial accomplishes nothing.
CO-22 Denial Code Appeal Letter Template
Not every CO-22 denial warrants an appeal. Most CO-22 denials are resolved through corrected resubmission, not formal appeal. Appeal a CO-22 denial only when the payer’s COB determination is factually incorrect and you have documentation to prove it. Use the following decision guide before investing time in an appeal.
| Scenario | Correct Action | Reason |
| Claim sent to wrong payer | Resubmit to correct payer | Process error, not a payer dispute |
| Secondary claim missing primary EOB | Resubmit with primary EOB attached | Data omission, not a payer dispute |
| COB information was outdated | Resubmit after COB update | Data correction, not a payer dispute |
| Payer claims another plan exists but patient has no other coverage | Appeal with patient attestation | Payer’s data is incorrect, dispute required |
| Primary has paid and secondary still denies CO-22 | Appeal with primary EOB as evidence | Secondary payer’s denial is unsupported |
The Appeal Letter Template
Use the template below for situations where the payer’s CO-22 determination is factually wrong. Select the option that matches your specific scenario and delete the others before submitting.
[Practice Letterhead]
[Date]
[Insurance Company Name]
Appeals Department
[Payer Address]
RE: Formal Appeal of CO-22 Denial
Patient Name: [Patient Full Name]
Member ID: [Member ID Number]
Date of Birth: [Patient DOB]
Claim Number: [Claim Number from EOB or ERA]
Date of Service: [DOS]
Billed Amount: [Total Charge Amount]
Provider NPI: [Rendering Provider NPI]
Dear Appeals Review Committee,
We are formally appealing the denial of the above-referenced claim under Claim Adjustment Reason Code CO-22 (This care may be covered by another payer per coordination of benefits).
We dispute this denial for the following reason:
[Select the applicable statement and delete the others]
Option A: Our eligibility verification dated [date] confirms that [Insurance Company Name] is this patient’s sole active primary coverage on the date of service. No secondary or tertiary coverage exists. The enclosed patient attestation signed on [date] confirms this.
Option B: The enclosed Explanation of Benefits from [Primary Payer Name] dated [date] confirms that primary adjudication was completed. We are submitting [Insurance Company Name] as the secondary payer with complete primary payment information as required.
Option C: Coordination of benefits records confirm that [Insurance Company Name] is the correct primary payer for this patient based on [birthday rule / employment rule / MSP determination, select applicable]. Supporting documentation is enclosed.
Enclosed Documentation:
- Copy of original claim
- Real-time eligibility verification dated [date]
- [Primary payer EOB, if applicable]
- [Patient insurance attestation, if applicable]
- [COB determination documentation, if applicable]
We respectfully request reprocessing within your standard appeal timeframe per your provider agreement.
Sincerely,
[Provider or Billing Manager Name]
[Title]
[Phone] | [Email]
If your team is managing CO-22 appeals across multiple payers simultaneously, One O Seven RCM’s denial management specialists handle the full appeal workflow, including documentation, submission, and follow-through. Learn more about our denial management services.
The Financial Impact of CO-22 Denials on Healthcare Practices
The American Hospital Association reports that claim denials cost the healthcare industry approximately $125 billion annually. Industry benchmarking data consistently shows that coordination of benefits issues, including CO-22 denials, account for 15 to 20 percent of all medical claim denials. In a single year, an estimated 48 million healthcare claims are denied, creating significant administrative burden and revenue risk across practices of every size and specialty. The CO-22 denial code is consistently ranked among the top ten most frequent denial codes by payer remittance data.
Those numbers reflect the industry. What they don’t show is what CO-22 denials cost your practice specifically, in dollars and staff hours, every single month.
What CO-22 Denials Actually Cost
The measurable costs of CO-22 denials extend beyond the denied claim amount.
| Impact Category | Conservative Estimate | Higher Estimate |
| Monthly CO-22 denials per practice | 12 | 40 |
| Rework cost per denial (staff time + system) | $28 | $50 |
| Monthly rework cost | $336 | $2,000 |
| Annual rework cost | $4,032 | $24,000 |
| Staff hours spent monthly on CO-22 rework | 10 hours | 35 hours |
| Timely filing write-off risk per month | $500 | $3,500 |
The Costs That Don’t Show Up in the Table
Beyond rework costs, CO-22 denials delay cash flow by 30 to 60 days per affected claim, contribute to billing staff burnout when denial volumes are high, and create patient confusion when coordination of benefits issues generate unexpected statements. Practices that don’t have systematic CO-22 prevention protocols in place absorb these costs as a permanent operational drag on revenue cycle performance. Request a free denial analysis to see where your practice stands.
CO-22 Denial Code: Frequently Asked Questions
What does CO-22 denial code mean?
CO-22 is a Claim Adjustment Reason Code with the official X12 definition: “This care may be covered by another payer per coordination of benefits.” The CO prefix means Contractual Obligation, which means the provider cannot bill the patient for this amount. CO-22 means the claim was submitted to the wrong primary payer, or a secondary claim was submitted without the primary payer’s adjudication information attached.
What does CO-22 mean in medical billing?
In medical billing, CO-22 means the payer received a claim that it believes should have been submitted to another insurer first under coordination of benefits rules. CO-22 doesn’t indicate a clinical error, a coding mistake, or a lack of medical necessity. It’s a payer sequencing problem. The service may be fully covered, but the claim must be submitted to the correct primary payer before secondary payment can be considered.
What is the difference between CO-22 and PR-22?
CO-22 and PR-22 share reason code 22 but carry different group codes. CO-22 (Contractual Obligation) means another payer is responsible, and the provider cannot bill the patient. PR-22 (Patient Responsibility) means the patient owes this balance and the provider can collect it directly. The prefix determines financial responsibility entirely. Applying CO-22 collection logic to a PR-22 denial, or vice versa, creates compliance violations and collection errors.
Can a CO-22 denial be appealed?
Yes, a CO-22 denial can be appealed when the payer’s coordination of benefits determination is factually incorrect. Appeal when the payer claims another plan is primary but the patient has no other active coverage, or when the secondary payer continues to deny after primary adjudication documentation has been provided. Most CO-22 denials resolve through corrected resubmission rather than formal appeal. Appeal only when the payer’s data is wrong, not when the submission process failed.
What is the Birthday Rule and how does it cause CO-22 denials?
The Birthday Rule determines which parent’s insurance is primary for a dependent child covered under both parents’ plans. The plan belonging to the parent whose birthday falls earlier in the calendar year, by month and day only rather than birth year, is primary. When registration staff fail to apply this rule and bill the second parent’s plan first, the billed payer denies the claim with CO-22, indicating the other parent’s plan should be paying first.
What is MA04 and how does it relate to CO-22?
MA04 is a Remittance Advice Remark Code that frequently appears alongside CO-22. Its official description is: “Secondary payment cannot be considered without the identity of or payment information from the primary payer.” When your ERA shows CO-22 paired with MA04, you submitted a secondary claim without the primary payer’s adjudication details. Resolution requires obtaining the primary Explanation of Benefits and resubmitting the secondary claim with complete primary payment information attached.
What if the patient has no other insurance but I still receive a CO-22 denial?
This happens when the payer’s internal COB database shows a coverage record that the patient says no longer exists. Resolution requires three steps: obtain a signed patient attestation confirming no other active coverage exists, contact the payer’s COB department to request a database correction, and submit the attestation with your formal appeal. For Medicare patients specifically, contact the Benefits Coordination and Recovery Center at 1-855-798-2627 to correct the MSP record directly.
What is CARC 22?
CARC 22 stands for Claim Adjustment Reason Code 22. It’s part of the X12 standard used in the 835 Electronic Remittance Advice transaction. CARC 22 has been active since January 1, 1995, and was last modified September 30, 2007. Its official definition is: “This care may be covered by another payer per coordination of benefits.” When paired with Group Code CO, it becomes CO-22. When paired with Group Code PR, it becomes PR-22.
What does claim status code 22 mean?
Claim status code 22 and CARC 22 are related but appear in different transactions. CARC 22 appears on the X12 835 ERA after claims processing and indicates a coordination of benefits denial. Claim status code 22 may appear in the X12 277 claim status response, indicating the claim is pending or suspended. Always identify whether you’re reading an 835 remittance or a 277 status response before interpreting code 22 in your billing system.
What is a COB balancing error with CO-22?
A COB balancing error with CO-22 occurs when billing software detects a mathematical discrepancy between the primary payer’s payment data and the secondary claim’s COB fields. This happens when the primary EOB amounts, including paid amount, patient deductible, coinsurance, and copay, are not entered exactly as shown on the primary remittance. Even a one-cent rounding difference can trigger the error. Enter primary payer data exactly as it appears on the EOB, without any modification.
What is the difference between OA-22 and CO-22?
OA-22 uses the Other Adjustment group code, while CO-22 uses the Contractual Obligation group code. OA-22 most commonly appears in Medicare secondary payment scenarios where the adjustment category falls outside standard contractual or patient responsibility classifications. CO-22 is the more common variant and indicates a COB sequencing problem where another payer is expected to be primary. Contact the payer directly when OA-22 appears, because the resolution path is payer-specific and isn’t always a resubmission.
Does BCBS issue CO-22 denials?
Yes. Blue Cross Blue Shield plans issue CO-22 denials when coordination of benefits information is incorrect or when the claim is submitted to the wrong plan first. For patients with BlueCard program coverage, claims route through the local host plan to the patient’s home plan. Standard COB rules apply to inter-carrier BCBS situations: the birthday rule governs dependent coverage, and employment rules govern spousal coverage. Contact BCBS provider relations for plan-specific COB sequencing requirements before resubmitting.
What is the difference between CO-22 and Modifier 22?
CO-22 and Modifier 22 are completely unrelated. CO-22 is a Claim Adjustment Reason Code appearing on the remittance advice after a claim is denied due to coordination of benefits. Modifier 22 is a CPT procedure modifier appended to a procedure code before claim submission to indicate the service required significantly more complexity than typically required. CO-22 signals a denial. Modifier 22 requests additional reimbursement. They appear at different points in the billing workflow and have no connection to each other.
What are the most common denial codes related to CO-22?
The denial codes most commonly associated with CO-22 situations include CO-24 (charges covered under capitation or managed care), CO-29 (timely filing limit exceeded, a secondary risk when CO-22 resolution is delayed), MA04 (missing primary payer payment information, the most common remark code paired with CO-22), COB-11 and COB-15 (coordination of benefits sequencing codes), and PR-22 (the patient responsibility version of reason code 22 when the patient holds financial responsibility for the balance).
How long do I have to appeal a CO-22 denial?
Appeal timelines vary by payer. Medicare appeals must generally be filed within 120 days of the initial determination date. Commercial payers typically require appeals within 30 to 180 days of the denial date, depending on the provider agreement. File as early as possible rather than waiting for the deadline. Monitor secondary payer timely filing limits independently of the appeal process, because CO-22 resolution delays can cause you to miss the secondary payer’s filing window even while the primary appeal is still pending.
Related Denial Codes Healthcare Providers Need to Know
Understanding CO-22 in context requires familiarity with the denial codes that appear alongside it, replace it in specific scenarios, or are caused by it when resolution is delayed.
| Denial Code | Official Description | Relationship to CO-22 |
| CO-24 | Charges covered under capitation or managed care plan | Most commonly confused with CO-22; different root cause and resolution |
| CO-29 | Time limit for filing has expired | Secondary risk when CO-22 resolution delays exceed payer timely filing windows |
| CO-96 | Non-covered charge | Frequently mislabeled as a CO-22 cause; separate CARC, separate resolution |
| CO-97 | Payment included in allowance for another service | Frequently mislabeled as a CO-22 cause; separate CARC, separate resolution |
| CO-18 | Exact duplicate claim | Frequently mislabeled as a CO-22 cause; separate CARC, separate resolution |
| PR-22 | Patient responsibility version of reason code 22 | Same reason code, different group code; patient owes this balance |
| OA-22 | Other adjustment version of reason code 22 | Medicare-specific COB adjustment context |
| MA04 | Secondary payment cannot be considered without primary payer information | Most common RARC companion to CO-22 on ERAs |
| COB-11 | COB sequencing code | COB family code frequently appearing in dual-coverage denials |
| COB-15 | COB sequencing code | COB family code related to coordination sequencing disputes |
| N-522 | RARC associated with COB situations | Occasionally paired with CO-22 in commercial payer remittances |
Each of these codes has a distinct resolution workflow. Applying the correct workflow from the moment the denial is identified reduces rework time and protects timely filing deadlines across your entire denial management operation. Learn more about our denial management services.
Official Sources and Regulatory Framework for CO-22
The guidance in this article is based on the following official sources, which remain current as of 2026.
| Source | Document | Relevance |
| X12 | CARC 22 Official Definition | Governing body for all Claim Adjustment Reason Codes; definition active since January 1, 1995, last modified September 30, 2007 |
| CMS | Coordination of Benefits Overview | Governs Medicare COB rules; last modified February 12, 2026 |
| CMS | Provider Services MSP Page | BCRC vs. MAC operational distinction; last modified February 11, 2026 |
| CMS MLN | Fact Sheet MLN7748519 | Medicare Secondary Payer billing order guidance; May 2025, no substantive content updates |
| 42 U.S.C. 1395y(b) | Medicare Secondary Payer statutory authority | Federal statute establishing MSP rules |
| 42 C.F.R. Part 411 | MSP regulatory authority | Federal regulations governing Medicare secondary payer determinations |
| Noridian Healthcare Solutions | MA04 Remittance Advice Guidance | Medicare Administrative Contractor documentation of CO-22 and MA04 pairing |
| AAPC | Coordination of Benefits Guidelines | Professional coding organization guidance on COB rule application |
CO-22 Denials Are Preventable. Here Is How One O Seven RCM Helps.
If your practice is experiencing recurring CO-22 denials, the root cause is almost always a front-end verification gap or a COB resolution workflow that doesn’t match payer-specific requirements.
One O Seven RCM’s billing specialists implement systematic COB verification, payer-specific denial resolution, and AR Follow-Up protocols that eliminate CO-22 at the source, before it damages your cash flow.
Request a free denial analysis. We’ll review your last 90 days of denials, identify the CO-22 root causes specific to your payer mix, and show you exactly what it will take to fix them.