CO-256 means “Service not payable per managed care contract.” To resolve it, identify the agreement the payer applied and the specific mismatch: the service may fall outside that agreement, the payer may have matched the claim to an incorrect contract record, or another administrator may be responsible for the benefit.
Start with the affected claim or service line and its accompanying remarks. If the explanation still says only “not allowed per contract,” ask the payer which contract provision, provider record or benefit-routing rule caused the denial. That answer determines whether to correct the claim, challenge the payer's processing, submit elsewhere or accept a valid contractual adjustment.
What CO-256 means on a remittance
X12 defines reason code 256 as a managed-care contract payment restriction. The CO group means contractual obligation. CMS explains that CO assigns the adjustment to the provider, while PR identifies patient responsibility. Don't move a CO-256 amount to a patient statement just because the payer didn't pay it.
Read the adjustment at the level where it appears. A denial attached to one service line doesn't establish that every service on the claim is unpaid. The payer's remarks, payment detail and provider-portal explanation may already identify the issue. Use those details before requesting a general contract review.
CO-256 differs from CO-204, which concerns a service excluded from the patient's current benefit plan, and B7, which concerns provider eligibility on the service date. Their investigations can overlap, but the payer's stated reason determines what you need to verify.
If CO-256 appears with remark N448, the payer is saying the drug, service or supply is absent from the applicable fee schedule or contracted or legislated fee arrangement. Compare the billed item with that arrangement, including its effective date, before treating the omission as a valid exclusion.
Which agreement did the payer apply?
For a pharmacy billing a clinical service, participation in a prescription network doesn't establish participation in the medical network for that service. UnitedHealthcare's 2026 administrative guide explicitly distinguishes medical and pharmacy benefit networks. Our medical benefit versus pharmacy benefit guide explains the broader difference.
Find the executed agreement and applicable service addendum for the member's plan and the pharmacy location that provided the service. Compare the billed procedure and service date with the relevant payment schedule. Ask the payer to identify the billing or rendering provider record it used when matching the claim to that agreement. A contract held by another location, or an agreement effective after the visit, doesn't resolve that comparison.
In an April 2023 Amerigroup Iowa bulletin, the plan explained that G18/CO-256 could reflect a procedure's effective date, a pending fee-schedule update, or billing/rendering provider eligibility for that code and date. This is a dated example of that payer's code use, not a current rule for every plan. For today's claim, ask whether the payer found the correct agreement and whether its payment records match the terms effective for your service date.
A pharmacy's signed agreement and the payer's record disagree
Suppose a pharmacy's executed clinical-service addendum includes a service from July 1, but an August claim returns CO-256. This is a hypothetical example. The claim carries the correct procedure, location and provider identifiers. The payer then confirms that it processed the claim under the pharmacy's older agreement, which didn't include that service.
Send the relevant addendum and effective-date confirmation through the payer's contract or provider-relations channel. Ask how it will correct the contract association and reprocess the affected claim. Keep the payer's case reference so you can connect the contract correction to the eventual claim result. Changing an accurate procedure code would not repair this mismatch.
Now suppose the submitted claim used the identifier for a different pharmacy location, and the payer correctly matched that identifier to an agreement that excludes the service. The claim information needs correction. Follow the payer's corrected-claim instructions for the location that actually provided the service; don't substitute an eligible location that didn't perform it.
If both the submitted claim and the payer's contract record are accurate, review the exclusion with the person responsible for the pharmacy's payer agreements. A valid contractual adjustment may need to be posted. A request to expand future participation is a separate matter from whether this already-rendered service was payable.
When another administrator is responsible
A managed-care contract may also divide responsibility for benefits. Maryland Physicians Care's February 2026 emergency-department policy uses CO-256 for certain behavioral-health or substance-use ED claims and directs providers to Carelon. That is an ED-specific example, not a pharmacy routing instruction; it shows why “managed care contract” doesn't always mean the provider's participation agreement.
For a pharmacy claim, confirm the responsible benefit and recipient for the actual service. If the payer directs you elsewhere, verify the receiving payer's submission requirements and whether the original claim was already forwarded. X12 uses separate codes for a medical claim that should be submitted to a pharmacy plan (280) and one already forwarded there (292). CO-256 alone doesn't establish either event.
Correct the claim or dispute the decision?
Use a corrected claim when the original submission contains a verified error. Use the payer's reconsideration or appeal process when the submitted information is accurate and you disagree with its payment decision. UnitedHealthcare describes these as different processes; other payers have their own requirements and deadlines. Check those while a contract inquiry is open rather than assuming the inquiry preserves your filing rights.
Make a dispute about the discrepancy: “This addendum includes the billed service for this location from July 1. Please explain why the August claim was processed under the earlier agreement.” Include the relevant provision and affected claim reference. If the payer's response still conflicts with the agreement, have the pharmacy's contracting lead review that conflict before another submission or a final write-off.
