CO-222 denial code: contracted unit limits and claim resolution

The CO-222 denial code indicates that the payer believes the provider exceeded a contracted maximum number of hours, days, or units during a defined period. The adjustment can affect one service line or a larger group of claims, depending on how the payer applies the contract and tracks utilization.

Because CARC 222 is not patient-specific, billing teams must look beyond one patient’s benefit. Identify the provider entity, contract term, measurement period, affected services, and payer accumulator before deciding whether to correct, request reprocessing, or dispute the adjustment.

What does the CO-222 denial code mean?

CMS’s standardized Claim Adjustment Reason Code reference defines CARC 222 as exceeding the contracted maximum number of hours, days, or units by the provider for the period. It also states that the adjustment is not patient-specific and directs users to any policy-identification information supplied on the 835 remittance.

The phrase “by this provider for this period” is important. The payer may measure utilization across a contracted organization, provider, location, specialty, or another contract-defined identifier. The period may be a day, week, month, quarter, contract year, or another interval. Do not infer either element from the code alone.

If the remittance reports CO-222, the CO group code identifies the adjustment as a contractual obligation. That does not automatically prove the payer calculated the limit correctly, and it does not authorize transferring the balance to the patient. The contract, remittance details, benefit rules, notices, and applicable law still control the next action.

Why CO-222 denials occur

A CO-222 adjustment may be accurate, result from incorrect claim data, or reflect a payer configuration problem. Common causes include:

• The submitted hours, days, or units exceed a ceiling stated in the payer contract or provider manual.
• Units were entered incorrectly, duplicated across lines, or reported with the wrong date span or service-unit qualifier.
• Several claims, locations, or rendering providers were accumulated under one billing provider, tax ID, or contract record.
• A corrected or voided claim was not removed from the payer’s accumulator before the replacement claim was processed.
• The payer applied an outdated contract amendment, fee schedule, provider mapping, or utilization limit.
• The service reached a legitimate contractual maximum, but the practice did not identify the remaining capacity before billing.

Read the entire remittance rather than treating the CARC as a complete explanation. The claim level, service line, group code, RARC, adjustment amount, policy reference, and payer message can show whether the issue concerns billed units, accumulated utilization, contract status, or missing support.

Do not confuse CO-222 with a Medicare MUE

A unit-related denial is not automatically a Medically Unlikely Edit. CMS explains that a Medicare NCCI MUE is the maximum units of service generally reported for a HCPCS or CPT code by the same provider or supplier for the same beneficiary on the same date of service. CARC 222, by contrast, describes a contracted provider-level maximum for a period and expressly says it is not patient-specific.

The distinction changes the investigation. An MUE review focuses on the code, beneficiary, date, units, and adjudication indicator. A CO-222 review begins with the payer contract and provider-level utilization history. The complete remittance remains essential.

A practical CO-222 denial resolution workflow

1. Read the complete remittance message

Capture the denied line, adjustment group, CARC, RARC, amount, policy reference, and any 835 identifiers. Confirm whether the adjustment applies to one line or the whole claim and whether the payer names the limit or period.

2. Identify the provider and measurement period

Determine which billing provider, rendering provider, location, tax ID, or contract record the payer used. Ask what period the accumulator covers and when it resets. Record the answer rather than assuming that the limit is daily or patient-based.

3. Reconcile units across the full period

Compare the payer’s utilization total with the organization’s claim ledger. Include paid, denied, corrected, voided, and replacement claims. Look for duplicate lines, reversed claims still counted, overlapping date spans, or services attributed to the wrong provider.

4. Review the controlling contract

Locate the executed agreement, amendments, exhibits, fee schedules, provider manuals, and effective dates. Confirm what is limited, how units are defined, which providers are grouped together, whether exceptions exist, and what dispute route and deadline apply.

5. Validate the submitted claim

Match the billed quantity with the signed record and coding rules. Verify units, dates, modifiers, frequency, place of service, and any code-specific reporting requirements. Never reduce units solely to obtain payment when the record supports the original submission.

6. Choose and document the response

Submit a corrected claim when the original data was wrong. Request reprocessing when the payer’s accumulator, provider mapping, or contract version was wrong. Use the payer’s dispute or appeal route when the claim is accurate and the contract supports payment. Record the outcome and root cause.

Corrected claim, reprocessing request or appeal?

A corrected claim is appropriate for a genuine billing error, such as duplicated units, an incorrect date span, or the wrong provider identifier. The corrected data must match the contemporaneous documentation and should follow the payer’s replacement-claim instructions.

A reprocessing request is often the better route when the submitted claim was accurate but the payer counted a voided claim, mapped the service to the wrong contract, or used an outdated limit. Provide the affected claim numbers, accumulator comparison, and the contract language supporting the request.

An appeal or contractual dispute is appropriate when the payer maintains the adjustment even though the claim and contract support payment. For Original Medicare determinations, the CMS first-level appeal guidance explains redetermination requirements; commercial and managed-care plans may use different forms, portals, deadlines, and escalation paths.

What to include in a CO-222 dispute package

Include the remittance, affected claim lines, signed records, a claim-history ledger for the period, applicable contract pages and amendments, the payer’s utilization detail, and a short reconciliation showing why the limit was not exceeded or was calculated incorrectly.

Organize the case around the payer’s actual rules. A consistent payer-specific denial workflow helps teams use the correct channel, deadline, evidence set, and follow-up schedule instead of sending the same generic appeal to every plan.

Preventing contracted unit-limit denials

Load contract ceilings and reset periods into accessible payer matrices. Assign responsibility for contract amendments, provider rosters, location changes, and payer portal notices. Billing and contract teams should be able to identify which limits apply before a claim reaches final submission.

Use front-end edits to flag unusual units, overlapping dates, duplicate services, and provider-limit risks. A structured claim-scrubbing process can stop clear submission errors while routing contract questions for human review. Automation should support documented judgment, not replace it.

Track CO-222 adjustments by payer, contract, provider identifier, service, period, dollars, action, and disposition. Repeated denials may reveal a training issue, incorrect system mapping, an unfavorable contract term, or a payer accumulator defect that requires escalation beyond individual claims.

How RCMGen approaches CO-222 denial resolution

RCMGen treats CO-222 as a contract-and-utilization issue, not simply a unit correction. Its denial management approach connects the remittance, claim history, documentation, provider mapping, and payer agreement before selecting a response, then feeds recurring findings into prevention and reporting.

Frequently asked questions about the CO-222 denial code

Verify the contract before changing the claim

CO-222 resolution depends on identifying the exact provider, period, unit definition, and contract term used by the payer. Reconcile the complete claim history, correct only verified billing errors, and use reprocessing or appeal when payer data or contract application is wrong. That protects coding integrity and turns recurring unit-limit denials into actionable contract intelligence.