In substance abuse billing, one clinical decision shapes almost everything that follows on the claim: the level of care. The American Society of Addiction Medicine (ASAM) Criteria sort treatment into levels, from early intervention through medically managed inpatient care. The level a patient is placed in decides what authorization is needed, whether the program is paid per day or per session, which codes fit, and what documentation a payer will ask for before it pays.
This guide explains how each ASAM level changes the billing. It is billing information, not clinical or legal advice, and payer rules vary by payer.
How the level is actually decided
ASAM placement is not based on a single symptom or on how severe the substance use looks. Clinicians assess six dimensions together: intoxication and withdrawal risk; biomedical conditions; emotional, behavioral, and cognitive conditions; readiness to change; relapse potential; and the recovery environment, including housing and support at home. The combination points to the least intensive level that can safely meet the need.
That matters for billing because the authorization a payer issues is tied to the level, not to the program in general. A payer that authorizes intensive outpatient care has not authorized residential care. The assessment record is therefore a billing document as well as a clinical one: it must show why this level, and not a lower one, was needed.
The levels, and what each one means for billing
Level 0.5 — Early intervention. Assessment, education, and brief intervention for people at risk who do not meet diagnostic criteria for a substance use disorder. Billing here is session-based, and the key point is that the service was preventive and screening in nature — not treatment of a diagnosed disorder, and it should not be coded as if it were.
Level 1 — Outpatient. Fewer than 9 hours of treatment per week for adults (fewer than 6 for adolescents), usually counseling at home. Payment is per session, and the claim stands on session documentation: date, duration, modality, and who delivered it.
Level 2.1 — Intensive outpatient (IOP). Nine or more hours per week for adults, typically spread across several days. IOP is still billed per session in most payer arrangements, but the weekly hour count becomes a billing fact: billing IOP for a week below the required hours creates a medical-necessity and compliance risk.
Level 2.5 — Partial hospitalization (PHP). Twenty or more hours per week of programming, without 24-hour care. PHP often shifts to a per-diem payment model, because the program day — not the individual session — is the unit of service. Billing its component sessions separately on top of the per diem is double billing.
Level 3 — Residential. Twenty-four-hour structured care at varying intensity: 3.1 low-intensity, 3.3 population-specific high-intensity, and 3.5 high-intensity residential. Residential care is billed per diem, and the authorization typically covers a date range or a number of days, with continued-stay review deciding whether later days are paid at all.
Levels 3.7 and 4 — Medically monitored and medically managed inpatient. Twenty-four-hour nursing care, with level 4 adding daily physician care for severe, unstable problems. These inpatient levels are billed per diem, and the documentation must support the intensity claimed for each day.
Withdrawal management is its own track
Detox is not a residential level, and billing it as one is a common error. Withdrawal management has its own ASAM levels: 3.2-WM (clinically managed), 3.7-WM (medically monitored), and 4-WM (medically managed). A patient who completes withdrawal management and then enters residential treatment has moved between two different authorizations, not continued one stay. The withdrawal-management claim covers the detox days; the residential claim starts fresh with its own authorization and continued-stay review.
Opioid treatment programs sit alongside the ladder
Opioid treatment programs (OTPs) — including methadone programs and office-based medication treatment — do not fit neatly into the 0.5-to-4 ladder, and payers usually do not bill them through it. OTP payment is commonly a weekly bundle covering medication, counseling, and related services together, rather than a per-session or per-diem charge for each component. Office-based buprenorphine treatment, by contrast, is billed as office visits with medication management. Bill the program the payer’s OTP benefit describes, and keep bundled components out of separate claims.
Per-diem vs per-session: the payment split to get right
The single most useful billing distinction in substance abuse care is between levels paid per day and levels paid per service. Residential and inpatient levels, PHP, and withdrawal management are usually per-diem: one rate covers the day’s program. Outpatient and IOP are usually per-session: each session is its own claim line. Mixing the two is where revenue leaks: components already included in a per diem billed again as separate sessions, or a per-session program billed as a flat day rate a payer never agreed to.
Code sets follow the same split, and they vary by payer and level. Substance abuse services are commonly billed with H-codes for program services and CPT codes for professional services, but no single code list applies to every payer or level. Confirm the code set and the per-diem definition against each payer’s policy, and build the check into intake rather than discovering it at denial.
Authorization follows the level — at admission and at every change
For most payers, the workflow runs: assess and document the ASAM level, verify benefits for that level, obtain authorization for that level, deliver care, and file concurrent review before the authorized days run out. Our prior authorization services follow this same sequence, and the step programs most often miss is the middle one: authorization is level-specific, so it must be re-obtained whenever the level changes.
Step-up and step-down moves are normal — a patient steps down from residential (3.5) to PHP (2.5), then to IOP (2.1), then to outpatient (1) — but each move is a new billing event. A step-down without a new authorization leaves the new level’s days uncovered; a step-up without updated documentation leaves the higher level unjustified. Use a level-change checklist: new assessment note, new authorization request, confirmation in writing, then the first claim at the new level.
Five level-of-care billing mistakes that become denials
First, billing a level the payer never authorized — often residential days billed against an IOP authorization. Second, delivering a level without the hours or structure to support it, such as billing IOP for a week below the required hours. Third, double billing a per diem: sessions billed separately that the per diem already covers. Fourth, rolling withdrawal-management days into a residential claim instead of billing the WM track on its own. Fifth, coordinating records or benefits without the consent substance use records require: federal 42 CFR Part 2 rules limit disclosure of substance use disorder records beyond HIPAA, and a step taken without proper consent can stall a claim.
Labeled illustrative example: one patient, four levels, four billing events
The following table is an illustrative example only. It uses no real patient data and no payment figures.
| Stage | ASAM level | Billing basis | Authorization step |
|---|---|---|---|
| Withdrawal management | 3.7-WM | Per diem, WM track | WM authorization for the detox stay |
| Residential treatment | 3.5 | Per diem | New authorization; continued-stay review before days run out |
| Partial hospitalization | 2.5 | Per diem | New authorization at step-down |
| Intensive outpatient | 2.1 | Per session | New authorization at step-down; weekly hours tracked |
Frequently asked questions
Does the ASAM level decide which payer pays the claim?
Not directly. The level decides what authorization is needed and how the service is billed — per diem or per session. Which payer pays depends on coverage, network status, and benefit design for that level, which is why benefits must be verified for the specific level at intake.
Can a program bill residential rates for detox days?
No. Withdrawal management is its own ASAM track (3.2-WM, 3.7-WM, 4-WM) with its own authorization. Detox days billed as residential days, or rolled into a residential per diem, are a mismatch between the level delivered and the level billed, and payers deny on that mismatch.
What happens if a patient steps down a level mid-authorization?
The new level needs its own authorization. An authorization issued for residential care does not cover PHP or IOP days. Get the new authorization confirmed before billing the first claim at the new level, and keep the step-down assessment note on file.
Why do payers ask for continued-stay reviews so often in residential care?
Because residential and inpatient levels are authorized in windows — a set number of days or a date range — and the payer requires updated clinical justification before extending the window. A day delivered after the window without a review on file is the most preventable residential denial.
How is OTP billing different from IOP or residential billing?
OTP payment is commonly a weekly bundle covering medication and related services together, rather than per-session or per-diem billing for each component. Office-based medication treatment is billed as office visits. Neither should be billed through an IOP or residential template.
Conclusion
Substance abuse billing rewards one discipline above all: treat the ASAM level as a billing fact, not just a clinical one. Document the assessment, authorize the exact level, bill the basis that level uses, and re-authorize at every step up or down. Programs that build that check into intake and level changes spend far less time appealing preventable denials.
For the broader picture, see our substance abuse billing services and our comparison of addiction treatment billing companies. If your program’s level changes, authorizations, or per-diem claims are producing denials, a free billing assessment will show where the workflow breaks down.
