CO 234 denial code

Claim adjustment reason code 234. Often reported as CO 234.

Procedure not paid separately

Unofficial reference. This is our own plain-English explanation, not the official code text. Payer rules differ. Verify with the payer and the official X12 code list. AlphaPrefix is not affiliated with X12, CMS or any payer. Data last updated Nov 11, 2026.

What 234 means

This procedure is not paid on its own because the payer considers it part of another service on the claim.

The payer bundled the line into another payment. It is usually a procedure that is incidental to, or part of, another service billed on the same day, or something covered by a facility or global payment.

At least one remark code comes with this code and explains the bundling. With group code CO the provider normally cannot bill the patient. Many denials here are correct, but some are fixable with modifiers when the service was truly distinct.

Group codes seen with 234

On a remittance, 234 comes after a group code. These are the ones it is most often reported with:

• CO 234 (Contractual Obligation): The provider's side of the ledger. The reduction comes from the payer contract or a rule the provider has to follow, and the patient normally cannot be billed for it.

The payer chooses the group code for each adjustment, so the same reason code can appear with another group code on your remittance. Read the two together. More about group codes.

Common causes

• The procedure is included in another billed service under correct coding edits.
• The service falls within a global surgical package.
• A supply or minor service is considered part of the main procedure or visit.
• The service was billed by a facility under a payment method that includes it.
• A needed modifier showing a separate site or session was missing.

What to do next

1. Read the remark codes to see which service the line was bundled into.
2. Check correct coding edits for the code pair on the date of service.
3. If the service was truly separate, add the right modifier with documentation and send a corrected claim.
4. Accept the adjustment as a contractual write-off when the bundling is correct.
5. Share repeat bundling patterns with coders so claims stop going out with included services.

Related codes

• 97 (reason code) Service included in another payment
• 236 (reason code) Procedure combo conflicts same day
• 231 (reason code) Mutually exclusive procedures
• 4 (reason code) Procedure code and modifier do not match