CO-96 means the payer treated a charge as noncovered and assigned the adjustment to the provider. Read the affected service line and accompanying remark: a plan restriction, an item billed in the wrong category and a service excluded by law each require a different response.
X12 requires reason code 96 to include at least one non-alert remittance advice remark code or an NCPDP reject reason. Find that explanation on the full remittance before changing the claim. If it only directs you to the plan's benefits, the next question is which provision the payer applied to this service.
What the remark adds to “noncovered”
A remittance can assign an adjustment to an entire claim or to an individual service line. Read CO-96 with the affected service, amount and all associated remarks. The claim number and line may already identify exactly what wasn't paid; the unresolved question is why that charge failed the coverage rule.
The X12 remark-code list illustrates several different explanations. These are examples to interpret when present, not a list of pairings every payer uses.
N130 points to plan benefit restrictions. Find the benefit document or coverage guideline for the member's actual plan and service date. Ask the payer to identify the restriction if the document covers several possibilities. “See benefits” is not specific enough to decide whether your submitted claim was wrong.
N180 questions the category used to bill the item or service. Compare the submitted code's description with what was actually supplied or performed, then check the category's coverage criteria. A product-code mismatch and a correctly coded item that doesn't meet those criteria are different findings.
N425 identifies a statutory exclusion. For a Medicare claim, that means the payer is pointing to an exclusion in law. Check that the exclusion fits the actual service and read the responsibility group with it. A statutory exclusion requires a different review from a missing claim field.
Other remarks can identify a procedure relationship or a coverage policy. For example, Noridian's JE Part B guidance for CO-96 with N431 tells providers to compare the submitted procedure code with the medical documentation and describes appeal rights for that message. That appeal guidance applies to this Medicare contractor message.
For pharmacy teams, confirm that you are reading a medical-claim remittance. A prescription rejection at the dispensing counter uses a different transaction and code context. The NCPDP option in the X12 rule describes an accompanying reason on the remittance; it does not make every pharmacy reject code interchangeable with CARC 96.
A pharmacy DME claim with a category mismatch
Suppose a pharmacy's medical claim returns CO-96 with N180 for a supplied item. This is a hypothetical example. The billing team compares the product model and delivery record with the HCPCS description on the submitted claim and finds that a saved product mapping sent a code for a different category of equipment.
The team has identified a claim-data problem. A coding reviewer confirms the code that describes the item actually supplied, and the biller follows the payer's correction process. Correct the saved mapping too, so the next claim carries the verified code. Selecting a different code solely because the payer covers it would misrepresent the item.
If the submitted code accurately describes the item, compare the specific coverage criterion with the pharmacy's supporting record. When that record appears to meet the requirement, use the payer's review process to challenge the coverage decision with the relevant evidence. Replacing an accurate code would not answer the coverage disagreement.
If the item really falls outside the applicable benefit, neither a coding correction nor more copies of the same claim changes that exclusion. Handle the supported adjustment under the payer's rules and review any patient-liability question separately. The DME medical billing guide covers the broader claim documentation.
CO-96, PR-96 and CO-204
CO and PR are responsibility groups, while 96 is the reason. CMS explains that CO assigns an adjustment to the provider and PR assigns it to the patient. CO-96 is therefore not an instruction to move the denied amount to a patient statement. A claim can also contain a separate PR amount; review each adjustment where it appears.
PR-96 uses the same noncoverage reason with a different responsibility assignment. Before collecting a reported patient balance, reconcile other coverage, payments already received and the applicable patient-billing rules. If the payer's assignment conflicts with the evidence, resolve that conflict with the payer instead of changing CO to PR in your ledger.
CO-204 specifically concerns a service, equipment item or drug outside the patient's current benefit plan. Code 96 is broader and requires an accompanying explanation. Use the 204 guide when the payer specifically identifies the current benefit plan as the reason.
For Original Medicare, an Advance Beneficiary Notice of Noncoverage, or ABN, is not a universal fix for code 96. CMS's notice instructions distinguish situations requiring advance notice from statutorily excluded care, for which an ABN isn't required. Have a billing reviewer check the actual denial basis and any notice given before care. Don't add an ABN-related modifier simply to shift an existing CO balance to the patient.
Correct the submitted facts or challenge the coverage decision
Use the payer's correction process when you've verified an error in the claim. Use its reconsideration or appeal process when the claim is accurate and the payer's coverage decision appears wrong. UnitedHealthcare distinguishes corrected claims from reconsiderations; Original Medicare uses reopening for minor claim errors. The process and deadline come from the actual payer and decision, not from code 96 alone.
For a coverage dispute, identify the exact conflict: “The denial cites this category restriction, but the billed item and supporting record meet the listed criterion. Please review the attached evidence.” Include the affected claim or service line and the relevant policy passage. Keep the payer's reference number for that follow-up.
If your billing screen shows only CO-96, open the complete ERA, paper remittance or payer-portal explanation. If the remark exists there, ask the software owner to make it visible in the claim view. If the complete response still lacks the required explanation, request it from the payer and check the applicable review deadline while that request is pending. The ERA guide explains how to connect that response to the claim and payment.
