IOP billing codes: complete guide for treatment centers

In this article▾

1. What this post covers
2. Core IOP billing rules at a glance
3. What counts as IOP and why does ASAM 2.1 matter for billing?
4. Core IOP billing codes and revenue codes
5. How to pick the right IOP code for each payer and program
6. How to bill IOP on UB-04 vs CMS-1500
7. Documentation requirements for IOP claims
8. Where is the line between IOP, PHP, and standard outpatient?
9. Biggest IOP denial drivers and how to fix them
10. What this post does NOT cover
11. How AI can help work IOP claims
12. Common pitfalls to avoid with IOP billing
13. FAQ: IOP billing codes

You finally got census up in IOP, then the first remit drops and half the days are denied for "wrong code for plan" or "no authorization on file."
Intensive outpatient programs usually map to ASAM Level 2.1, with per-diem billing and strict level-of-care rules that payers love to audit.

IOP is commonly authorized and paid as 1 unit per qualifying treatment day, so the code choice, form type, and documentation either protect your revenue or set up recoupments.

---

What this post covers

• Core IOP codes and revenue codes: When to use H0015 vs S9480, and common patterns by payer type.
• Claim structure and level of care: How to bill IOP on UB-04 vs CMS-1500 and where IOP differs from PHP and standard OP.
• Documentation and authorization: What payers expect to see for IOP in the chart and on the auth.
• Denials and prevention: The main IOP denial patterns and how to fix them upstream, not just on appeal.

---

Core IOP billing rules at a glance

Before deep diving codes, lock in the basic IOP billing logic.

IOP level of care

• ASAM Level 2.1 anchor: Typically at least 3 hours of treatment per day and at least 3 days per week.
• Structured program: Scheduled, multi-disciplinary services focused on active treatment, not just support groups.
• Payer variation: Details vary by payer and state, so always confirm, but falling far below 3 hours per day or 3 days per week invites review and recoupment.

Per-diem billing pattern

• One unit per treatment day: Most payers expect IOP as a per-diem, 1 unit per calendar day that meets IOP criteria.
• Sub-threshold days: When the patient attends but does not meet the IOP minimum, many payers expect standard outpatient unbundled codes instead, for example 90853.

Facility vs professional claims

• Facility claims (UB-04): IOP is usually billed with revenue code 0906 (SUD) or 0905 (psych), 1 unit per qualifying day.
• Professional claims (CMS-1500): Some payers want H0015 or S9480 on a 1500, with or without a matching facility claim.

Top denial to watch

• Biggest driver: Prior auth not on file or not matching level of care (IOP vs PHP vs OP), followed closely by using the wrong IOP billing code for that payer.
  If you miss auth or mismatch level of care, every other billing detail is just decoration.

---

What counts as IOP and why does ASAM 2.1 matter for billing?

You cannot bill IOP confidently until you know your program truly meets IOP level-of-care standards.

Practical definition of IOP for billing

Most payers anchor to ASAM Level 2.1 for SUD and a parallel standard for psychiatric IOP.

• Intensity: Typically at least 3 hours of treatment services in a calendar day.
• Frequency: Typically at least 3 treatment days per week.
• Structure: Scheduled, multi-disciplinary, with clear programming and clinical goals.
• Focus: Active treatment, not just "support group" or quick check-ins.

If your schedule and attendance routinely fall below that intensity, assume higher audit risk.

Why this matters for claims

IOP is almost always paid as a per-diem, so your daily "IOP met" decision needs to be accurate.

• Unit logic: Bill 1 unit for each day that meets the IOP threshold for that payer.
• Alternative on light days: If the patient does not hit the IOP minimum, many payers want those services billed as standard outpatient codes instead, often unbundled.

If your front desk clocks someone at 2 hours 20 minutes and you still send H0015 or S9480 per diem, you are building future takebacks.

---

Core IOP billing codes and revenue codes

There are only a few core IOP billing codes. The complexity comes from program type and payer preference.

Core IOP billing codes at a glance

*Revenue codes apply on institutional (UB-04) claims.

• Facility claims: IOP is usually billed on a UB-04 using revenue code 0906 (SUD) or 0905 (psych) with 1 unit per qualifying day.
• Professional claims: Some payers want S9480 or H0015 on a CMS-1500, with or without a facility claim alongside it.

If you only skim this section, remember that the revenue code and HCPCS need to line up with how the payer views your program.

H0015 - SUD IOP per diem

For most SUD-focused IOP programs, H0015 is the default starting point.

• Primary use: SUD or chemical dependency IOP days that meet IOP criteria.
• Typical revenue code: 0906 on UB-04 when billed as facility IOP.

S9480 - psychiatric IOP per diem

For psychiatric or general behavioral health IOP, S9480 is the usual choice.

• Primary use: Mood, anxiety, and other non-SUD psychiatric IOP.
• Typical revenue code: 0905 on UB-04 for facility-based psych IOP.

Rule of thumb:

• SUD IOP: Start with H0015.
• Psych or general BH IOP: Start with S9480.

Then adjust based on the payer's published rules and how your program is contracted.

Full deep dives on each code:

• H0015 billing guide
• S9480 billing guide

Real rate example (verify before you rely on it): IOP per-diem rates are heavily state- and payer-specific, and S9480 in particular is thinly published in state Medicaid fee-for-service (it is an S code many FFS programs do not list). One verified data point: UnitedHealthcare Community Plan of Colorado (a Medicaid MCO) pays $219.43 per diem for S9480, the same rate it loads for the SUD-IOP code H0015 (2024 to 2025). Commercial IOP rates are set by contract and are not public. These are real published examples that vary by payer and year, so confirm against your own contracts and remits. Source: https://www.uhcprovider.com/content/dam/provider/docs/public/commplan/co/behavior-health/CO-Value-based-fee-schedule.pdf

When in doubt, your contract and remits outrank any single published rate example.

Facility revenue codes for IOP

On a UB-04, the HCPCS code usually pairs with a revenue code that describes the program type.

Common UB-04 patterns:

• SUD IOP: Rev code 0906 + HCPCS H0015 + 1 unit + per-diem charge.
• Psych IOP: Rev code 0905 + HCPCS S9480 + 1 unit + per-diem charge.

Some Medicaid programs want the HCPCS only, some want revenue only, some want both. Always check your state manuals and fee schedules.

Sample claim line you can copy

Here is a simple SUD IOP institutional example that will pass edits with many payers:

Box 42 (Rev Code): 0906
Box 44 (HCPCS/Rates): H0015
Box 46 (Units): 1
Box 47 (Total Charges): [your IOP per-diem charge]
Service dates: from/to both equal the treatment date that met IOP criteria

For psych IOP, swap in 0905 / S9480.

Start with this template, then overlay payer-specific quirks like modifiers or span billing.

---

How to pick the right IOP code for each payer and program

Most avoidable IOP denials trace back to the wrong IOP code for that line of business.

One-look "which IOP code when" table

Use this table as a fast decision aid, then confirm with contracts and manuals.

If the authorization letter lists a specific HCPCS, that is usually the code you should be billing.

Program type vs payer rules

Start with how your program is defined, then map to each payer.

• Clarify your program design: Is it SUD-focused, psych-focused, or truly co-occurring, and how is it described in contracts and marketing.
• Read the auth details: Check whether the auth specifies service type (SUD vs psych), ASAM level, or a particular code such as H0015 or S9480.
• Build a payer mapping grid: For each payer and plan type, list program, code, revenue code, modifiers, and claim form type.

The practical rule: tie your code choice to how the payer authorized and contracted the service, not to what "usually pays."

---

How to bill IOP on UB-04 vs CMS-1500

Most larger behavioral health and SUD organizations bill IOP as a facility service first, then layer professional claims where allowed.

Facility / institutional IOP billing: UB-04

Use UB-04 when you are billing the IOP program itself under a facility contract.

• When to use UB-04: Facility or program billing, contracts that reference per-diem IOP rates, or manuals that reference revenue codes 0905 or 0906.
• Typical type of bill: Often 13X or 85X, depending on facility type and payer instructions.
• Standard line items: Revenue code 0905 or 0906, HCPCS H0015 or S9480, 1 unit per qualifying day, per-diem charge amount.

Service date structure depends on payer.

• Single-day lines: Each IOP day on its own line with from/to equal to that date, units = 1.
• Span billing: Some payers allow a date span with units equal to covered days; others do not.

Avoid trying to bill multiple IOP units on the same calendar day for longer schedules. Most contracts assume a single per diem per day regardless of whether you ran 3.0 or 4.5 hours.

Professional IOP billing: CMS-1500

Professional billing shows up in a few common scenarios.

• Separate medical services: Physicians or psych NPs bill their own E/M or med management codes in addition to the facility per diem, if the payer allows carve-outs.
• Carved-out therapy: Some plans require therapist or group sessions to be billed as individual CPT/HCPCS codes instead of, or in addition to, a facility IOP rate.
• No facility contract: When you only have professional agreements, you may be limited to CMS-1500 billing.

Patterns to watch:

• Place of service (POS): Usually POS 22 (on-campus outpatient hospital) or 11 (office), depending on your setup and payer rules.
• IOP per diem on 1500: Some payers allow H0015 or S9480 on CMS-1500, others do not.
• Unbundled patterns: Where IOP per diem is not recognized, payers often expect codes like 90853, 90834 / 90837, 90791 / 90792, H2019, or H2036.

The only safe rule is to follow the provider manual and contract. If a plan treats IOP per diem as a facility-only benefit, sending H0015 or S9480 on a 1500 is usually wasted effort.

Modifiers for IOP

Modifier use is highly payer- and state-specific, but some patterns repeat.

• Program type modifiers: HF or HG for SUD vs non-SUD in some Medicaid programs, HE for mental health program distinctions.
• Group indicators: HQ for group services when a payer expects component billing in addition to, or instead of, per diem.
• Payer-specific quirks: Some plans require unique modifier stacks that only show up in their BH manuals.

Build a consistent approach.

• Step 1: Pull the payer's BH / SUD billing manual and search for H0015 or S9480.
• Step 2: Add modifier rules to your billing system tied to payer, program, and rendering provider type.
• Step 3: Document these patterns in an internal IOP playbook and prohibit freehand modifier choices.

Inconsistent modifier usage gets noticed quickly on audit, especially in Medicaid.

---

Documentation requirements for IOP claims

Think about IOP documentation in two layers: program-level proof that you actually run an IOP, and day-level proof that each billed date met criteria.

Program-level documentation

Payers look for this when they audit whether your service really qualifies as IOP.

• Program description: Clearly states level of care (IOP / ASAM 2.1), target hours per day, days per week, and the specific clinical services offered.
• Schedules and protocols: Daily and weekly schedules that match the description, including group types, individual sessions, and med management blocks.
• Staffing and qualifications: List of licensed and unlicensed staff roles, supervision structure, and coverage model.
• Policies and procedures: Admission and discharge criteria, and step-up / step-down rules between OP, IOP, PHP, and residential levels.

If your auth request describes one kind of IOP and your policies or schedules show something different, auditors have an easy target.

Date-of-service level documentation

For each IOP day you bill, you should be able to show that the day met intensity and content expectations.

• Attendance and time: Start and end times for each group and service, with a clear tally that shows the patient met the minimum IOP hours.
• Clinical content: Group notes that describe interventions, participation, and response, plus individual, family, or med management notes when applicable.
• Treatment plan alignment: Active treatment goals in the plan that match IOP interventions, with documented progress updates tied to those goals.
• Authorization alignment: Level of care in the chart matches the auth level, and any step-down from IOP is documented and communicated.

Notes do not need to be novels, but they must clearly support that an IOP day, not a routine OP day, was delivered.

---

Where is the line between IOP, PHP, and standard outpatient?

A lot of level-of-care denials come from blurred operational and documentation boundaries between IOP, PHP, and standard outpatient.

IOP vs PHP: billing comparison

High-level contrast:

Billing patterns differ as well.

• IOP codes: H0015 or S9480, usually with revenue 0906 or 0905.
• PHP codes: Often H0035 or S0201, or revenue codes like 0912 / 0913 with program-specific HCPCS.

For PHP details, see: PHP billing codes hub.

If auth is written for PHP but your documented daily hours and structure look more like IOP, many payers will downcode or deny.

IOP vs standard outpatient

The main distinction is structured intensity and per-diem vs component billing.

• Standard outpatient:
  • 1 to 2 hours per visit, weekly or biweekly.
  • Billed with individual CPT codes such as 90834, 90837, 90853, 90791, etc.
• IOP:
  • Multiple coordinated services in a single treatment day.
  • Typically billed as a per-diem covering the structured day.

Operationally, you should have clear written admission criteria and step-down criteria between OP and IOP, and apply them consistently. Payers will look for clinical rationale explaining why someone is in IOP instead of more frequent OP visits.

---

Biggest IOP denial drivers and how to fix them

Most IOP denials fall into a handful of buckets that you can control with front-end process and claim edits.

Top IOP denial patterns

Fixes: front-end first, then denial cleanup

Start by closing the gaps that create denials, then build a disciplined denial workflow.

• Tighten VoB and auth: Confirm BH vendor and IOP coverage, ask which codes they use for IOP (H0015 vs S9480 vs others), and secure explicit IOP auth with dates and approved days.
• Add system rules: Build payer templates that hard-code code plus revenue code, expected modifiers, and claim form type, and add edits to block disallowed unbundled pairs such as 90853 with H0015 when the contract prohibits it.
• Manage true exceptions: Use internal edits to flag IOP days where attendance is below required hours, so staff can downcode to OP instead of pushing through risky per-diems.

Once upstream is stable, work denials with a structured approach.

• Use a denial taxonomy: Reference tools like the denial glossary to categorize IOP denials consistently.
• For "not authorized": Confirm actual auth status, then appeal with the auth letter and supporting clinical documentation if the denial is incorrect.
• For "non-covered code": Research the payer policy, then correct and rebill with the right IOP billing code plus an explanation in your appeal when needed.
• For "exceeds units": Request retro auth extensions when clinically justified, otherwise adjust and tighten discharge planning and step-down workflows.

You will not appeal your way out of a broken IOP program structure, so fix scheduling and auth habits before chasing every denial.

---

What this post does NOT cover

To keep this focused on IOP billing codes, here is what is out of scope here and covered in separate guides.

• Per-code deep dives on documentation, examples, and payer quirks for each code:
  • H0015 billing guide
  • S9480 billing guide
• PHP-specific coding and beyond-the-basics IOP vs PHP comparisons:
  • PHP billing codes hub
• Denial code indexing and appeal letter templates across all service types:
  • Denial code glossary

Use this page as your IOP hub, then click into those posts when you need deeper code-level detail.

---

How AI can help work IOP claims

IOP billing is repeatable, rules-heavy, and full of preventable denials, which makes it a good fit for AI agents working alongside your team.

1. Eliminate repetitive grunt work

AI agents can own the repetitive checks that consume staff time but follow clear rules.

• Benefits verification agents: Hit medical and behavioral eligibility, including carved-out BH vendors, confirm whether IOP is covered and which codes the payer expects (H0015, S9480, or others), capture visit limits, auth requirements, and BH contact info, then write structured data back into your practice management system. Supa runs this through Supabill so VoB data is standardized and reusable.
• Auth requirement checks: Log in to payer and BH vendor portals, check prior auth requirements specifically for IOP level of care, capture PA policies, and attach them to the patient record so staff are not re-checking manually.
• Claim scrubbing for IOP rules: Before claims go out, AI scrubbing can confirm code plus revenue code combinations by payer, block unallowed unbundling with group therapy codes, flag dates where documented time does not meet IOP thresholds, and check units against auth totals.

A platform like Supa's Supabill typically runs 80 to 90 percent of the day-to-day billing work, including VoB, portal checks, scrubbing, and status checks, so your human team can focus on judgement calls.

2. Remove painful tasks like payer phone calls

Phone work on IOP benefits and auth is predictable, but slow. AI voice agents can take the first pass.

• Voice agents for payers: Call payers or BH vendors, navigate IVRs, ask targeted questions about IOP-specific benefits and auth, and log call reference numbers and outcomes.
• Structured outputs: Feed those results straight into your billing or practice management system so future claims and auth requests use the same rules.

With tools like Supa's voice agents, you keep oversight but do not have staff stuck on hold to learn, for example, that a plan only accepts S9480 on UB-04.

3. Prevent manual errors and catch denial patterns

AI is also useful once claims and remits start flowing.

• Denial-pattern analytics: Cluster IOP denials by payer, code, and reason to show where your "wrong code" or "no auth" denials are coming from, then propose rule changes such as "for Payer X, S9480 is non-covered on 1500, use UB-04 only." Supabill uses this sort of analytics to drive rule changes automatically.
• Guardrails for complex cases: Keep humans focused on borderline level-of-care decisions between IOP and PHP, unusual program setups, and cases where policies conflict, while AI handles pattern recognition and basic enforcement.

AI is best used as guardrails and accelerators so your billers handle the edge cases, not as an autopilot for clinical or coding judgement.

---

Common pitfalls to avoid with IOP billing

A short do-not list that will save you on audits and remits.

• Do not bill IOP per diem on days that clearly miss the 3-hour intensity threshold.
• Do not swap H0015 and S9480 casually across payers "because they usually pay." Always check each plan.
• Do not unbundle every group and individual code on the same day as IOP when the contract clearly expects per-diem only.
• Do not ignore BH carve-outs: Always check who actually pays IOP and route claims correctly.
• Do not let clinicians or front desk set level of care on the fly without written criteria and training.
• Do not run IOP past the auth end date with no concurrent review and then act surprised at denials.
• Do not mix PHP and IOP documentation or schedules so much that you cannot prove which level was delivered.

If your workflows break these rules regularly, fix them before you scale census.

---

FAQ: IOP billing codes

1. Can I bill more than one IOP unit per day if the patient stayed longer?

Generally no. IOP is typically contracted as 1 per diem per calendar day, regardless of whether you delivered 3.25 or 4.5 hours.

If your days are consistently well above assumed hours, talk to contracting about PHP or adjusted rates instead of trying to bill multiple units.

2. What if a patient only attends 2 hours of group, but we billed IOP?

You are exposed on audit. A payer can recoup those days as not meeting level of care if the documented time is below IOP thresholds.

Best practice is to downcode those dates to standard outpatient codes, for example group therapy like 90853, and not bill H0015 or S9480 for that day.

3. Can I bill both IOP per diem and separate group therapy codes on the same day?

Sometimes, but many payers prohibit it. You must read the provider manual for each plan.

If the plan pays a flat IOP per diem, it usually expects group services to be included; use claim edits to block disallowed combinations.

4. How do I handle mixed-diagnosis IOP where patients have both SUD and psychiatric needs?

Align with how the program is registered and authorized.

If your contract and auth call it SUD IOP, use H0015 and 0906. If it is psych IOP, use S9480 and 0905, even when patients have co-occurring SUD, and make sure documentation still addresses both conditions.

5. Do Medicare plans pay for IOP the same way as Medicaid and commercial?

Traditional Medicare has its own rules and historically focused more on hospital-oriented partial hospital and IOP-type services.

Many Medicare Advantage plans mirror commercial patterns and may use S9480 or H0015, so always check MA plan manuals and verify IOP coverage during VoB.

6. Which modifiers should I use on IOP claims?

It depends on state and payer. You will see HF or HG, HE, HQ, and others.

Start with the payer's BH or SUD manual and any Medicaid state bulletins, then build payer-specific modifier rules in your system so staff are not guessing.

7. Do I need a separate auth when stepping a patient from PHP down to IOP?

Often yes. Many payers treat PHP and IOP as distinct levels of care with separate auths or auth segments.

Some plans allow a single "day treatment" auth that spans both, so confirm this during auth calls and document the level-of-care language in your system.

8. Our payer denies H0015 as non-covered but pays S9480. Can I just switch codes?

Only if the service truly meets the payer's definition of psychiatric IOP and the program is contracted that way.

Blindly swapping codes to "see what pays" is risky and looks bad in an audit; fix your contracting and auth language first, then bill consistently with that.

9. Should physicians bill their own E/M codes on IOP days?

Some payers allow separate physician billing, others consider it part of the per diem.

Check contract language about "professional services included in per diem" and payer manuals for carve-out rules, and if allowed, build edits so you only bill separate E/M where the payer explicitly pays for it.

10. How many IOP days per week can I bill?

Usually as many days as the patient actually attends that fall within auth limits and your program design, for example 3 to 5 days per week.

There is no universal cap, but many plans watch for outliers like 7-day-per-week IOP sustained for months.

11. Can I bill IOP telehealth days the same way as in-person?

Some payers allowed tele-IOP during and after COVID, others still do not.

Where allowed, you may use the same IOP billing codes with a telehealth modifier or telehealth place of service, but you must still meet the same time and content requirements, so check plan telehealth policies specifically for IOP.

12. What if we change our IOP schedule from 3 hours to 4 hours per day?

You usually do not change the per diem code, but you should update your program description and policies, confirm that payer rules and caps do not conflict with the new schedule, and ensure your EHR and scheduling reflect the new standard so documentation matches.

13. How do I handle holidays or days when we run a shortened schedule?

If the total clinical time is meaningfully below the IOP threshold, bill those days as standard outpatient services instead of IOP.

Some payers will accept a slightly shorter day if clearly documented, others will not, so set a conservative internal rule and enforce it with claim edits.

14. The payer says "service inconsistent with level of care" on an IOP audit. What do they actually mean?

Usually one of three things: documented time is under the IOP minimum, the treatment intensity is low-quality (education only, little clinical work), or progress notes look like routine OP check-ins.

You fix this by tightening clinical protocols and documentation expectations, not just by arguing about the code.

15. How can I quickly see if a new payer prefers H0015 or S9480 for IOP?

Use a mix of front-end research and small, controlled tests.

• Ask targeted VoB questions like "How do you pay for intensive outpatient, and which codes do you use."
• Search the payer's BH manual for "intensive outpatient," "H0015," and "S9480."
• If needed, test a small volume of correctly documented claims with each pattern and track responses, with clear internal notes.

Once you know the payer preference, hard-code it into your payer rules so staff do not have to re-learn it for every patient.

---

If you want to see how an AI-first billing stack like Supabill would handle your IOP programs, you can grab time with our team here: book a live demo.