Level-of-Care Codes That Don't Match the Authorization
Why IOP, PHP, residential, and detox claims deny when the code is right — the referral names a different episode — and how to confirm the pairing before you bill.
On this page: Direct answer
Direct answer
Procedure code not listed under the referral: what operators need to know
Why IOP, PHP, residential, and detox claims deny when the code is right — the referral names a different episode — and how to confirm the pairing before you bill. Behavioral-health levels of care are described by several overlapping HCPCS and revenue-code conventions, and payers do not agree on which to use.
There is a denial that reads like a coverage dispute and is not one. The benefit covers partial hospitalization. The patient attended partial hospitalization. The code you billed is a partial hospitalization code. And the claim denies because the procedure code is not listed under the referral — the authorization on file names a different episode, a different code set, or a modifier the payer's system expects and your claim does not carry.
This is the hardest denial class to reason about from the remittance alone, because nothing in the message tells you the authorization is the problem. It is also one of the most preventable, because both documents are in your possession before you bill. This guide is about confirming the pairing up front, and about what to do when a payer's accepted code changes underneath a working workflow.
Key takeaways
The short version
- Behavioral-health levels of care are described by several overlapping HCPCS and revenue-code conventions, and payers do not agree on which to use.
- The authorization or referral names an episode. If the code you bill is not within what that episode names, the claim denies regardless of coverage.
- Confirm three things per payer per level of care: the accepted code, the required modifiers, and whether the referral is written to the code or to the episode.
- Medicaid managed care and Medicaid fee-for-service in the same state often differ, and so do a payer's commercial and government lines.
- When a code that paid for years suddenly denies, look for a policy or system change at the payer before changing your coding.
- Record the answer with its source and date. A verbal answer from a representative is a lead, not a rule.
Take the template with you
Free to copy · no email required
Payer level-of-care code matrix
One row per payer, line of business, and level of care — accepted code, required modifiers, per diem or per unit, whether the authorization is code-based or episode-based, and the source and date of each answer.
payer,line_of_business,level_of_care,claim_type,accepted_code,required_modifiers,optional_modifiers,per_diem_or_per_unit,revenue_code_if_facility,auth_basis,episode_name_if_episode_based,codes_mapped_into_episode,step_down_needs_new_auth,units_or_days_typical_approval,source_document,source_section,confirmed_by,confirmed_date,recheck_due,notes [payer],Medicaid managed care,IOP (SUD),professional,[code],[modifier],,per diem,n/a,episode-based,[episode name as written on the referral],[codes the payer maps into it],yes,[n],provider manual,[section / page],[rep name or doc],2026-10-19,2027-01-01,verify at plan-year boundary [payer],Commercial,PHP,facility,[code],,,per diem,[rev code],code-based,,,yes,[n],billing guide,[section],[source],2026-10-19,2027-01-01,
Saves as payer-level-of-care-code-matrix.csv
Payer call script: settling the pairing
The questions to ask, in an order that gets usable answers, plus what to record so the answer survives the call.
1. Why correct codes get denied
Behavioral-health levels of care never settled on a single coding convention. Depending on the payer and the setting, the same programme can be described by an H-code, an S-code, a revenue code paired with a procedure code, or a facility per diem, sometimes with a modifier carrying the waiver, programme, or supervision context. A professional claim and a facility claim for the same service can use different conventions entirely.
Authorizations are written on top of that. Some name specific procedure codes. Some name an episode of care — a span, a level, a unit count — and leave the coding to adjudication. When the authorization names an episode and your claim carries a code the payer does not map into that episode, the adjudication system sees a mismatch and denies. Nobody made a clinical judgement; two documents simply failed to line up.
| Denial you see | What it usually means | Where to look |
|---|---|---|
| Procedure code not listed under the referral | The referral names an episode or code set your billed code is not inside | The referral document — read what it actually authorises |
| Incorrect modifier, where no modifier seems to apply | The payer expects a programme, waiver, or supervision modifier you are not sending | The payer's own billing guide for that programme |
| Prior authorization denied though benefits show the service covered | Authorization is keyed to a code or setting different from the one requested | The authorization request itself, not the benefit summary |
| Modifier not typical for the procedure code | The payer's system does not recognise a modifier that another payer requires | Whether this payer accepts the convention at all |
| Records do not support the billed procedure code | The note reads like a different level of care than the code claims | The documentation template for that level |
| Code submitted more than once per date of service | A per diem billed as units, or a unit-based code billed as a per diem | Whether the payer treats this level as per diem or per unit |
2. Three questions to settle per payer, per level of care
- 01
Which code does this payer accept for this level of care, on this claim type?
Ask separately for professional and facility claims. The answer differs, and a correct professional code on a facility claim denies like an incorrect code.
- 02
Which modifiers are required, and what do they signify?
Programme, waiver, telehealth, and supervision modifiers all appear in behavioral health. Ask which are required, which are optional, and which the payer's system will reject.
- 03
Is the authorization written to the code or to the episode?
This is the question nobody asks and the one that explains most of these denials. If it is written to the episode, ask which codes the payer maps into that episode.
- 04
Per diem or per unit?
Determines whether multiple lines on one date are correct or a duplicate. Get it in writing, because the duplicate denial that follows is slow to unwind.
- 05
What happens when the level changes mid-episode?
Ask whether a step-down needs a new authorization, and whether a single authorization can span two levels. Most cannot.
- 06
Where is this published?
Ask for the provider manual section or billing guide, by name and page. A representative's verbal answer is a lead to verify, not a rule to bill against.
3. The conventions you will meet
The table below is a map of the terrain, not a billing instruction. Which of these applies to you is determined by your payer, your state, your claim type, and your contract — never by a general reference, including this one. Use it to know what to ask about, then confirm each cell against the payer's own published guidance.
| Level of care | Conventions you may encounter | What usually varies |
|---|---|---|
| Intensive outpatient (IOP) | H-code or S-code per diem; sometimes revenue code plus procedure code on a facility claim | Per diem versus per unit; whether substance use and mental health use different codes |
| Partial hospitalization (PHP) | Distinct PHP per diem codes, which differ between payers and between government and commercial lines | Which per diem the payer recognises; hospital-based versus freestanding |
| Residential treatment | Per diem codes by programme type; facility claims with revenue codes | Programme type distinctions; whether outpatient E/M codes are ever appropriate (usually not) |
| Withdrawal management / detox | Per diem codes distinct from residential, sometimes by intensity | Whether the payer distinguishes ambulatory from residential withdrawal management |
| Medicaid waiver services | Programme-specific codes with waiver modifiers | Whether a commercial plan administering waiver business recognises the waiver convention at all |
| Crisis and stabilisation | Separate code families, often state-defined | State-by-state definitions; whether it is carved out to another vendor |
4. When a code that always paid suddenly stops
A workflow that paid reliably for years and starts denying at the beginning of a plan year or a contract period is usually not a coding error that went unnoticed. It is a change on the payer's side — a policy update, a system migration, a new referral structure, or a different administrator. The instinct to change your coding first is the expensive one, because if the payer's change is defective you will have altered a correct workflow to accommodate a bug, and you will own that for every claim afterwards.
- Establish the exact date the behaviour changed, and whether every claim since has denied or only some.
- Check whether the denial reason changed too, or only the outcome — a new reason code points at a policy change.
- Look for a published policy update, provider bulletin, or operating-guide revision effective near that date.
- Ask whether the referral structure changed: a new episode-of-care format is a common cause.
- Ask whether other providers in your region are affected. A regional pattern points at a payer defect, not at you.
- Hold the claims rather than rebilling repeatedly. Repeated rebilling creates duplicate denials that complicate the eventual correction.
- If it is a payer defect, route it to the write-off-with-cause or payer-escalation path rather than looping it through appeals.
5. Catching it before submission
Everything above becomes a pre-submission check once the authorization is stored as data rather than as a number. The reconciliation step compares the approved code set, modifiers, unit or day count, date span, place of service, rendering provider, and facility against what the claim carries, and holds anything that disagrees.
The addition this guide makes to that check is the episode question. Where an authorization names an episode rather than codes, the comparison has to be against the payer's mapping for that episode — which means the mapping has to be recorded in your payer matrix, not inferred claim by claim.
- Store the authorization as fields, including whether it is code-based or episode-based.
- Keep a payer matrix with accepted codes, required modifiers, per diem or per unit, and the source and date of each answer.
- Hold, do not rebill, when the check fails, and record which field disagreed.
- Re-verify the matrix at plan-year and contract boundaries, which is when these change.
- Give step-downs their own authorization check, since one authorization rarely spans two levels.
- Track denials in this class separately from medical-necessity denials. They have different owners and completely different fixes.
Common questions
Answers before you build.
The benefit summary says PHP is covered, so why was prior authorization denied?+
Coverage and authorization are different questions. A benefit summary describes what the plan pays for in principle; the authorization decides what was approved for this member, for these dates, at this level, sometimes keyed to specific codes. A denial here usually means the request was keyed to a code or setting different from the one you intend to bill, so check the request against the referral before treating it as a coverage dispute.
The denial says the modifier is wrong, but no modifier applies to this code.+
That phrasing usually means the payer's system expects a modifier you are not sending, rather than objecting to one you are. Ask which modifier the payer requires for this programme and level of care, and ask where it is published. Programme and waiver modifiers are the common answer in behavioral health, and they differ by payer and state.
Can we bill residential treatment with outpatient evaluation and management codes?+
Almost certainly not, and a note that reads like an outpatient encounter is a documentation problem as much as a coding one. Residential is generally billed with per diem conventions appropriate to the programme and claim type. If someone is advocating codes on the basis that they get paid, that is a compliance conversation, not a coding one — treat it as such and get it reviewed.
A representative told us to use a different code. Is that enough?+
It is a lead, not a rule. Ask for the provider manual section or billing guide that says so, record the representative's name and the date, and keep both. If the published guidance cannot be produced, note that too — it matters if the instruction is later disputed.
Should these denials go to the appeals desk?+
No. These are matching failures, not determinations: the payer never reached a judgement about necessity. Route them to whoever owns the field that disagreed — authorization, coding, or credentialing — correct, and resubmit. Appealing them spends weeks to achieve what a corrected claim achieves in days.
Practical closeout
Use this operator checklist.
- Behavioral-health levels of care are described by several overlapping HCPCS and revenue-code conventions, and payers do not agree on which to use.
- The authorization or referral names an episode. If the code you bill is not within what that episode names, the claim denies regardless of coverage.
- Confirm three things per payer per level of care: the accepted code, the required modifiers, and whether the referral is written to the code or to the episode.
- Medicaid managed care and Medicaid fee-for-service in the same state often differ, and so do a payer's commercial and government lines.
- When a code that paid for years suddenly denies, look for a policy or system change at the payer before changing your coding.
- Record the answer with its source and date. A verbal answer from a representative is a lead, not a rule.
Continue through the cluster
Verified customer case studies are added only with customer permission and supporting evidence; none is implied by these operational examples.
Codes on this topic
Look up the code on the remittance
- CO-197The payer found no authorization on file for this service, or none it could match to the claim.Denial code · Authorization
- CO-16Something is missing or wrong on the claim itself, and the remark code on the line says what.Denial code · Coding & billing
- CO-199On a facility claim, the revenue code and the procedure code on the same line don't match under the payer's rules.Denial code · Coding & billing
Sources & methodology
Trace the operational claims.
Marsa Health Editorial reviewed the primary and research sources below on October 19, 2026. We translate them into workflow controls, distinguish proposals from final rules, and flag where plan, program, state, contract, or clinical requirements vary.
- 01Health care payment and remittance advice Centers for Medicare & Medicaid ServicesHow the 835 carries claim adjustment reason codes and remittance advice remark codes, which is what a reconciliation step actually reads.Accessed or rechecked October 19, 2026
- 02Medicare Coverage Database Centers for Medicare & Medicaid ServicesSearchable national and local coverage determinations and billing articles, which is where a contractor's own expectations for a level of care are published.Accessed or rechecked October 19, 2026
- 03Medicare and Mental Health Coverage Centers for Medicare & Medicaid ServicesThe MLN booklet covering which behavioral-health services Medicare pays for, the settings they are furnished in, and the supervision and provider-type rules attached to them.Accessed or rechecked October 19, 2026
- 0442 CFR 438.210: Coverage and authorization of services Electronic Code of Federal RegulationsParagraph (d) sets 7-calendar-day standard and 72-hour expedited decision limits for rating periods beginning on or after January 1, 2026; (c) governs notice of adverse benefit determination.Accessed or rechecked October 19, 2026
- 05CMS Interoperability and Prior Authorization Final Rule CMS-0057-F Centers for Medicare & Medicaid ServicesThe fact sheet listing which payers are impacted, the four required APIs, the denial-reason duty, and the compliance dates.Accessed or rechecked October 19, 2026
- 06Appealing health plan decisions Centers for Medicare & Medicaid ServicesCMS guidance on internal claims and appeals rights, notice contents, and the relationship between internal appeals and external review.Accessed or rechecked October 19, 2026
- 07External Appeals Centers for Medicare & Medicaid ServicesFederal external-review process and consumer protections.Accessed or rechecked October 19, 2026
Organizational author. Editorial review covers source accuracy, search intent, workflow boundaries, and human-oversight requirements. This material is educational and does not provide clinical, legal, coding, or coverage advice.
No named clinical or legal expert reviewer is attributed to this version. Marsa Health does not invent reviewer credentials.
Read our editorial methodRevision history
What changed and when
October 19, 2026
Initial publication, source review, and operational editing.