CO-150: Service level not backed by records
Payer says the billed level of service is not supported by the documentation or data on the claim. Balance is treated as a contractual write-off unless you win an appeal or corrected claim.
What it means
The payer is saying the intensity or level you billed does not match what they see in the chart or claim. In their view, the clinical picture or time spent only supports a lower level, a different code, or no payment at all. Mechanically, the claim hits a medical review or automated level-of-service edit that compares your code, modifiers, and units to documentation and policy. The payer reduces or denies payment for the billed line, assigns CO-150, and expects your facility to write off the amount unless you dispute it.
Why it happens in behavioral health
Behavioral payers often use CO-150 when your billed level of care looks higher than what notes or authorizations support. For example, billing PHP per diem for a day when the note only shows 2 therapy groups and no psychiatry contact, so the payer says it looks like IOP, not PHP. You also see CO-150 on outpatient therapy when a clinician bills 90837 every visit but notes read like 45 minutes, or group codes get billed as individual sessions. Some payers auto-flag every 90837, 90792, or 90839 for level-of-service review and downcode them if time, complexity, or interventions are not clear. In SUD and MAT, residential or detox per-diem claims get hit when documentation does not show 24-hour nursing, withdrawal scale use, or required counseling contacts. OTPs can see it when billing a higher-intensity HCPCS or weekly bundle, but the note only documents a medication visit without required counseling or labs.
How to fix it
- Pull the full record for the denied dates of service, including treatment notes, flowsheets, and time logs.
- Compare the billed code, level of care, units, and modifiers to the documentation and the payer's medical policy or provider manual.
- If the original code was clearly too high (for example PHP that reads like IOP), correct the coding and submit a corrected claim at the supported level.
- If the documentation supports the billed level, build an appeal with clear clinical summary, time statements, and policy citations, and attach records.
- Check whether an authorization on file matches the billed level of care; if it shows a lower level, include any upgrade request or clinical rationale in the appeal.
- Track patterns by clinician, program, or code (for example 90837, PHP per diems) and feed back results so coding and documentation can be corrected long term.
How to prevent it
- Train clinicians on time-based and complexity-based coding rules for 90832-90838, 90791-90792, and crisis codes, and tie this training to real payer examples.
- Build templates that prompt for time in and out, modality (group, individual, family), interventions, and level-of-care criteria for PHP, IOP, residential, and detox.
- Use scrubbing rules that flag risk patterns, such as all 90837 by one clinician, PHP days with low service counts, or residential days without required contacts.
- During utilization review, confirm that the requested and approved level of care matches how the program is documenting and how billing plans to code.
