RemitBench

RemitBench/Denial codes/CO-231

CO-231 denial code

Code 231 says two lines on your claim contradict each other. The payer's edits hold them as procedures that cannot both be performed in the same session, so it paid one and refused the other.

The code list's own wording: Mutually exclusive procedures cannot be done in the same day/setting.

What it means
The payer maintains pairs of procedures it will not pay together, on the basis that performing one rules out the other. Your claim contained such a pair.
Who owes the money
The practice CO normally, which makes it a write-off. Do not bill the patient for a line the payer refused as a coding conflict.
Is appealing worth it
Worth it when the procedures really were separate: different sites, different teeth, different sessions on the same day. That has to be shown rather than asserted, and the documentation has to have said so at the time.

A modifier is not a workaround. Modifiers that indicate a distinct service exist for genuinely separate work, and using one to get around an edit for work that was not separate is the kind of thing audits look for specifically. Use it when the chart already shows the separation, and not otherwise.

Why the payer sent it

Remark codes you will see with it

Remark codeWhat it adds
M15Separately billed services or tests have been bundled as components of the same procedure.
N657This should have been billed with the appropriate code for the service.
N130Read the plan document. Its own page.

Read the letters in front of the 231

CO-231
Contractual obligation. Your write-off unless you can show the work was separate.
PI-231
Payer initiated. Not the patient's money.

What to do next

  1. Look at what was actually done

    Two teeth, two quadrants, two sites, or genuinely two separate sessions are all real distinctions. One procedure that includes another is not.

    If the work was separate: resubmit with the documentation and the modifier that describes the separation. If one includes the other: the edit is right. Write it off and correct the template that produced the pair.
  2. Check which of the two the payer paid

    Payers usually pay the higher valued one. If they paid the lower, that is worth a call before you accept the total.

  3. Find out if the pair is a habit

    Mutually exclusive pairs often come from a stored treatment template. One fix there stops the recurrence.

Codes that get mixed up with 231

CodeHow it differs from 231
97Benefit included in payment for another service. Bundling rather than exclusivity. See CO-97.
234Not paid separately. Never its own line rather than conflicting with another. See CO-234.
18Exact duplicate. The payer thinks it is the same line twice. See CO-18.
59Multiple procedure rules. A reduction rather than a refusal. See CO-59.

Code 231 in dental

Dentistry has clear examples of genuinely exclusive pairs and clear examples of pairs that only look exclusive. Two different exam types on one visit is usually a real conflict. The same procedure on two different teeth is not, and it depends entirely on the tooth numbers reaching the claim.

Tooth numbers are what separate the lines

Most dental 231 denials that are wrong are wrong because the tooth or quadrant information did not carry through. The work was separate and the claim did not say so. That is a corrected claim, and it usually points at the bridge between clinical software and billing software rather than at the biller.

Questions people ask about CO-231

Can I use a modifier to get around a CO-231?

Only when the work was genuinely separate and the chart already shows it: different teeth, different sites, or genuinely separate sessions. Using a distinct service modifier on work that was not separate is exactly what auditors look for, and it turns a small write-off into a much larger problem.

Related codes

Back to all denial codes

RemitBench reads dental EOB PDFs and turns them into posting-ready lines, in your browser, with no upload. It does not read medical remittances today.

Open the app

Opens your mail app with the message written. Nothing is sent from this page.