CO-222 denial code: what it means and how to fix it.
CO-222 shows up on your ERA when a rendering provider has gone past the volume their payer contract allows for a period. The cap belongs to the provider, not the patient, so a patient with unused benefits can still trigger it.
See how Needletail's verification keeps provider and plan data consistent across every location.
RARC codes decoded
ranked dental triggers
% cap threshold to act on
TL;DR
CO-222 means the provider exceeded the contracted maximum hours, days, or units for the period. The practice absorbs the adjustment.
This is a provider-level cap tied to the rendering NPI. It has nothing to do with the patient's benefit maximum.
Dental triggers: annual unit caps on high-volume procedures, claims aggregated across locations under one NPI, a group NPI used in place of the individual NPI.
Check the RARC first. N640 usually means a real cap or an aggregation problem. Audit the NPI before you assume the cap is legitimate.
Many CO-222 denials trace back to inconsistent provider data across locations. A legitimate cap hit is a contract signal: your volume outgrew the agreement.
What is the CO-222 denial code?
The official definition: "Exceeds the contracted maximum number of hours/days/units by this provider for this period." The payer counted the services billed under one provider and found the total was higher than the contract allows.
The key word is provider. Most dental denial codes that mention a maximum are about the patient: annual maximums, lifetime maximums, frequency limits. CO-222 is about the dentist or hygienist whose NPI is on the claim. A patient with $1,500 of unused benefits can still generate a CO-222 if the rendering provider has already hit the contracted ceiling.
Why does the "CO" matter? It tells you who's on the hook. Contractual Obligation means the provider's payer contract makes the practice responsible for the adjusted amount. The patient doesn't owe it. You can't bill the patient for a cap the contract placed on your own volume.
For DSOs this code carries extra weight. Contracts are often negotiated at the group level but enforced per NPI. One hygienist who rotates across five offices can hit a cap that no single office would ever see on its own report, and when the cap is real, the denial is the payer telling you the contract no longer fits your volume.
Don't confuse CO-222 with CO-119
CO-119 means the patient's benefit maximum for the period was reached. CO-222 means the provider's contracted maximum was reached. Different limit, different owner, different fix. Treating a CO-222 like a benefits problem sends your team to the wrong place.
How to fix a CO-222 denial,
and the provider caps behind it.
This is a contract and data problem, not a coverage dispute. Work out whether the cap is real, then either correct the NPI or deal with the contract.
Provider
Provider Cap Exceeded
N640, M86
Patient
NPI Aggregation Error
N640, MA130
Coding
Contract Limit Reached
N640, N386, N20
- 1
Pull the ERA and note the rendering NPI.
Open the 835 or paper EOB. Record the RARC, the date of service, the procedure code, and the NPI on the denied line. CO-222 is tied to a provider, so the NPI is the first fact you need.
- 2
Confirm the NPI on the claim is the right one.
Was the rendering provider's individual NPI used, or did the claim go out under the group NPI? A group NPI on a rendering field can make the payer count every provider's volume against one cap.
- 3
Audit the provider's total units across all locations.
Pull year-to-date counts for the procedure by rendering NPI, across every office, and compare the total against the cap in the contract.
- 4
If the NPI was wrong, correct and resubmit.
Fix the rendering NPI and resubmit with frequency code 7 (replacement of prior claim). Don't file a brand-new claim for the same date of service; that risks a duplicate denial on top of the original.
- 5
If the cap is real, choose a contract path.
Move future volume to another credentialed provider in the group, or open an amendment request with the payer to raise the cap, bringing your utilization data.
- 6
Watch the timely filing window.
Corrected-claim deadlines vary by payer. Some count from the date of service, others from the denial date. Check the specific contract before you assume there's time.
| Cap Type | Typical Rule | Dental Example |
|---|---|---|
| Provider annual unit cap | Set units per year on high-volume procedures | Prophylaxis or exam counts pass the per-NPI yearly ceiling |
| Multi-location aggregation | All offices' claims sum under one NPI | A provider who rotates across locations is invisible to any single office's report |
| Group NPI as rendering | Individual NPI missing from the claim | Every provider's volume lands on a single identifier and blows through the cap |
| Specialty procedure cap | Per-provider limits on SRP, ortho adjustments | A caseload growing faster than the contract anticipated hits the wall late in the year |
CO-222 starts upstream.
When eligibility verification reveals plan details before the appointment, practices can track which procedures are approaching provider caps. Needletail's verification feeds cleaner data into your utilization tracking.
CO-222 RARC decoder:
what each remark code means.
CO-222 states that a provider limit was exceeded. The RARC tells you what kind of limit and how the payer handled the line.
Provider Cap
NPI and Claim Handling
Contract and Plan Limits
| RARC | What the Payer Is Saying | Dental Context | The Fix |
|---|---|---|---|
| N640 | Exceeds number/frequency approved/allowed within time period | The rendering NPI passed its contracted units for the period, for example annual prophylaxis or SRP counts. | Pull year-to-date units by NPI across all locations. Confirm the NPI is correct, then decide between redistribution and a cap amendment. |
| M86 | Service denied because payment already made for same/similar procedure within set time frame | Often appears when a provider was added mid-year and the payer applied the group's cap to the new NPI. | Confirm the effective date and cap terms for the added provider. Request the contract schedule in writing. |
| N386 | This decision was based on a National Coverage Determination (NCD) | Payer processed the line against a contract schedule where the provider's allowance was already used. | Compare the denied procedure against your fee schedule and limits exhibit. Escalate to provider relations if the limit isn't in your copy. |
| MA130 | Claim contains incomplete/invalid information, no appeal rights afforded | Informational code. Often appears when the claim carries a group NPI where an individual rendering NPI belongs. | Don't appeal. Correct the NPI fields and resubmit as a corrected claim. |
| N20 | Service not payable with other service rendered on the same date | When a provider is near the cap and multiple procedures are billed on the same date, the payer may deny one as not payable alongside the other. | Call provider relations to confirm the true reason. If it's a same-day conflict, separate the billing dates or attach a narrative. |
If a CO-222 arrives with no N640 or M86, pull the full remark set from the 835 and check every line. Payers vary in how they pair remark codes with contract-based denials, so the NPI audit stays the first step whatever the RARC says.
Provider-level caps are a contract problem, but they surface as claim denials.
When every verification is clean and documented, your data tells you exactly where utilization stands before the payer does.
Common causes of CO-222
in dental practices.
CO-222 comes down to one question: whose volume did the payer count, and did it exceed what the contract allows? Here's what dental groups and DSOs actually run into, mapped to the remark codes that come with each cause.
Provider annual unit cap on high-volume procedures
N640Prophylaxis or exam counts pass the per-NPI yearly ceiling
NPI aggregation across multiple locations
N640A provider rotates between offices and the payer sums every claim under one NPI
Group NPI used instead of individual rendering NPI
N640All providers' volume lands on a single identifier
Contract cap on specialty procedures
N640SRP and ortho adjustments carry their own per-provider limits
Mid-year provider addition to an existing group contract
M86A new NPI inherits a cap or enrollment terms that don't match the group's volume
Locum tenens billing under the primary provider's NPI
N640A covering dentist's volume stacks onto the primary provider's count
Historical utilization spikes triggering an automated cap review
N640The payer's system flags a provider whose volume jumped against prior years
- The cleanest case: the contract says a provider can bill up to a set number of units per year on certain procedures, and the provider billed more. A busy hygienist or a high-volume general dentist reaches the ceiling before year end, and every later line comes back CO-222 + N640.
- Specialty work follows the same pattern with lower numbers. Periodontists and orthodontists often carry procedure-level limits tied to their credentialing category, and a caseload that grows faster than the contract anticipated hits the wall in the fourth quarter.
- Mid-year additions are a quieter version of this problem. A new associate joins the group and is added to the contract, but the cap terms for the new NPI don't match what the practice expected, often showing up as M86 on those lines.
- These are the most frustrating CO-222 triggers because the cap wasn't actually hit. Claims were counted under the wrong identifier.
- The group NPI goes into the rendering field, and the payer treats every provider's units as one provider's volume, so the group "provider" blows through the cap in a few months.
- A locum tenens or covering dentist bills under the primary provider's NPI, so the primary provider's count now includes someone else's work. Neither shows up as a problem in the PMS because each claim looks normal on its own.
NPI aggregation errors start with inconsistent provider data across locations.
Needletail's verification standardizes the eligibility data flowing into your PMS, so a provider's volume gets counted under the right NPI every time.
- Sometimes the denial is simply correct. The provider is productive, the contract was written for lower volume, and the payer is enforcing the agreement. A historical utilization spike can also trigger an automated review that lands on N640 even when the provider stayed under the written cap.
- This is the category that should change how you run contracts. A CO-222 that keeps coming back for the same provider and procedure is your data telling you the agreement needs to be renegotiated, or that volume needs to move to another credentialed provider.
| Trigger | What's Wrong | RARC You'll See |
|---|---|---|
| Provider annual unit cap on high-volume procedures | Prophylaxis or exam counts pass the per-NPI yearly ceiling | N640 |
| NPI aggregation across multiple locations | A provider rotates between offices and the payer sums every claim under one NPI | N640 |
| Group NPI used instead of individual rendering NPI | All providers' volume lands on a single identifier | N640 |
| Contract cap on specialty procedures | SRP and ortho adjustments carry their own per-provider limits | N640 |
| Mid-year provider addition to an existing group contract | A new NPI inherits a cap or enrollment terms that don't match the group's volume | M86 |
| Locum tenens billing under the primary provider's NPI | A covering dentist's volume stacks onto the primary provider's count | N640 |
| Historical utilization spikes triggering an automated cap review | The payer's system flags a provider whose volume jumped against prior years | N640 |
CO-222 vs.
CO-119, CO-35, and CO-45.
Dental billing teams mix these codes up because all of them mention a maximum. The difference is whose limit it is.
| Code | Trigger | Who Owes | Type |
|---|---|---|---|
| CO-222 | Provider's contracted maximum exceeded | Practice absorbs | Provider |
| CO-119 | Patient's benefit maximum for the period | Practice absorbs | Benefits |
| CO-35 | Patient's lifetime benefit maximum | Practice absorbs | Benefits |
| CO-45 | Charges exceed fee schedule | Practice absorbs | Fee |
| CO-151 | Prior authorization frequency exceeded | Practice absorbs | Auth |
CO-222 is the provider's limit. CO-119 is the patient's limit. A CO-119 means this patient used up their benefits for the period, and the fix involves the patient's plan. A CO-222 means this provider used up the contract's volume allowance, and the fix involves the provider's NPI and the payer contract.
The same ERA can contain both. Ask whose count the payer is enforcing: benefits remaining on the patient's plan point to CO-119 or CO-35, while units billed by one NPI point to CO-222.
CO-45 can also look similar on a bad day. Charges exceeding the fee schedule produce a contractual write-off on the amount, while CO-222 stops payment on the line entirely because the provider's volume cap was reached. CO-151 is about the frequency of an authorized service, tied to an approval, not to the provider's contract total.
CO-222 is about provider contracts, not patient benefits. But both trace to data accuracy.
Clean verification data powers clean utilization tracking, whether the question is a patient's remaining benefits or a provider's contracted cap.
How to prevent CO-222 denials
before they happen.
CO-222 prevention runs on a calendar, not a 48-hour clock. The cap builds up over months, so the controls are recurring audits that catch the trend before the payer does.
Review NPI assignments at each location.
Confirm individual vs. group NPI on rendering fields across locations.
Track high-volume procedure counts per rendering NPI.
Sum high-volume procedure counts by NPI across every location.
Redistribute scheduling or start an amendment.
Act once a provider nears 80% of a contracted cap, not at 100%.
Audit provider utilization against contract caps.
Compare year-to-date totals against every payer's cap, per provider.
Analyze utilization trends, negotiate cap increases.
Bring a multi-year volume trend to the payer renewal conversation.
The cost of location-level reporting
Location-level reports hide the problem: a provider who works five offices looks like five small numbers instead of one big one. Utilization tracking is only as good as the data behind it, and inconsistent plan details and provider assignments across locations make cap reports unreliable. Pre-appointment verification that records plan details in the same format at every office gives tracking a stable base for the contract conversation.
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.
Three CO-222 patterns straight from dental group and DSO billing teams. Each one produces a denial that a recurring audit would have caught earlier.
DSO hitting an aggregate provider cap
A 15-location DSO has a hygienist who rotates across five offices. Each office sees a normal weekly schedule. The payer contract caps prophylaxis at 800 per provider per year, and the hygienist passes it in the fall.
What comes back
CO-222 + N640 on every prophylaxis line billed under her NPI after the cap is reached.
The fix
Audit her total across all five locations. Move upcoming hygiene appointments to other credentialed hygienists, or open a contract amendment to raise the cap.
How to prevent it
Track provider utilization monthly, summed by NPI across every location. Set an alert at 80% of the cap so scheduling can shift before the denials start.
Provider unit limit on a specific procedure
A periodontist's contract with one payer caps scaling and root planing (D4341, D4342) at 200 units per year. Referrals are strong, and he reaches the cap by October.
What comes back
CO-222 + N640 on SRP lines for the rest of the year.
The fix
Request a contract amendment with a higher SRP cap, or route remaining cases to another credentialed periodontist in the group while the amendment is pending.
How to prevent it
Monitor procedure-specific caps quarterly. A specialist whose referral volume is climbing needs the cap conversation in the spring, not after the denials arrive.
NPI aggregation error across locations
At one location, the billing template defaults to the group NPI in the rendering field instead of each provider's individual NPI. The payer aggregates every provider's claims from that office under one identifier.
What comes back
CO-222 + N640 within a few months, even though no individual provider is near a cap.
The fix
Correct the NPI assignments in the PMS and resubmit the affected claims with frequency code 7 and the right individual rendering NPI.
How to prevent it
Run a quarterly NPI audit across locations. Compare templates and provider setup at each office, and confirm that a new location inherits the individual NPI configuration.
What these three scenarios have in common
Every one of them was visible in the data before the denial. A regular audit is the cheapest fix, and it only works when provider and plan data are consistent across offices.
- The hygienist's count climbed all year before the fall cap hit. The periodontist's SRP volume was on a clear path to the ceiling.
- CO-222 punishes groups that watch volume location by location instead of provider by provider.
- An NPI aggregation error can hit even when no individual provider is anywhere near a real cap.
- Needletail's dental verification confirms eligibility and provider assignments before the visit, so utilization tracking across locations has a consistent baseline to audit against.
Provider cap denials are a data and contract problem, not a coverage dispute.
Needletail's dental verification confirms eligibility and provider assignments before the visit, giving DSOs a consistent baseline to audit NPI-level utilization against contracted caps.
Your call is with Jofin Joseph,
Co-Founder and CEO.
Questions about this code