OA-222: Exceeds Contracted Maximum Units

What Does OA-222 Mean?

OA-222 is uncommon and typically appears in multi-payer coordination scenarios where the volume cap adjustment is not strictly a contractual matter between the provider and a single payer. This may occur in delegated risk arrangements or when volume limitations are applied across a network rather than per-provider.

CARC 222 is a contractual volume limitation adjustment. The payer is telling you that your practice has billed more hours, days, or units than the maximum allowed under your participation agreement for the relevant measurement period (monthly, quarterly, or annually). This is fundamentally different from a per-patient utilization denial — CARC 222 applies at the provider level regardless of individual patient needs.

This adjustment typically appears in contracts that include volume caps, such as capitated arrangements, global budgets, or agreements with hard limits on specific service categories. The 835 Healthcare Policy Identification Segment (Loop 2110) may contain details about the contracted limit, though not all payers populate this field. The key question is whether you have actually exceeded the contracted maximum or whether there is a tracking discrepancy between your records and the payer's system.

CARC 222 is almost always accompanied by Group Code CO, since the overage is a contractual matter between the provider and payer — the patient bears no responsibility for the provider exceeding volume caps. In rare multi-payer scenarios, OA may appear. Because this is a contract-level adjustment, the resolution typically involves either correcting billing errors that inflated your unit count, negotiating with the payer if their tracking is inaccurate, or accepting the write-off and adjusting future billing practices to stay within contract limits.

How to Resolve

Verify the contracted maximum against your actual billing volume, correct any billing errors, and negotiate with the payer if their unit tracking is inaccurate.

1. Clarify the adjustment basis Contact the payer to understand why OA was used. Determine if the volume cap is applied at the network or program level rather than the individual provider contract level.
2. Determine next steps Based on the adjustment context, either submit to another responsible entity in the arrangement or follow the CO-222 resolution process if OA was used in error.

Common RARC Pairings

The RARC code tells you exactly what triggered the OA-222:

How to Prevent OA-222

• Understand the volume cap structure in delegated risk and network-level agreements
• Track utilization at the appropriate level (provider, group, network) as required by the agreement

Also Filed As

The same CARC 222 may appear with different Group Codes:

Related Denial Codes