Payer, product, and carve-out
Identify the plan and the organization that actually manages the behavioral health benefit. Record network, referral, and prior authorization conditions separately from general eligibility.
Prevention, tracking, and resolution
Behavioral health billing denials and prior authorization, in one control loop.
Behavioral health billing denials often begin before the claim: a benefit carve-out, missing authorization, expired review period, unmatched level of care, documentation gap, enrollment issue, or payer-processing failure. ASP-RCM connects prior authorization, claim readiness, denial classification, appeal evidence, follow-up, and prevention so each balance has a reason and an owner.
- Reason-coded queues
- Review-date control
- Appeal evidence trail
Prior authorization control record
A reference number is not an authorization workflow.
A behavioral health authorization record should show exactly what was requested, what was approved, the evidence submitted, the dates and units in scope, the next review point, unresolved payer requests, and the claim impact. That record must remain connected to scheduling, utilization review, clinical documentation, and billing.
Service, setting, dates, and units
Specify the requested service or level, start date, duration, units or visits, clinician or program, location, and the payer's submission channel and required information.
Clinical and administrative package
Maintain the source documents, criteria response, submission timestamp, confirmation, reference number, correspondence, and any request for additional information.
Approved scope and specific reason
Capture approved or denied status, service, dates, units, conditions, denial reason, decision timestamp, notice, and any reconsideration or appeal rights.
Concurrent and renewal review
Place review dates, information due dates, expiration points, unit boundaries, peer-to-peer windows, and appeal deadlines in named work queues before they become denials.
Authorization to claim matching
Compare billed services and dates to the approved scope. Surface mismatches before submission and reconcile payer responses back to the authorization record.
Exhibit 1 · The authorization lifecycle
Four events decide whether a behavioral authorization survives the episode.
An authorization is not a document. It is a span of coverage that has to be opened, renewed, re-matched when the level of care moves, and closed before it lapses. Each of the four events below has a leak directly beneath it, and every one of those leaks produces a claim that was clinically justified and administratively unpayable.
↔ Swipe the diagram
The lifecycle above describes ASP-RCM's operating model. It does not assert how often each leak occurs. Authorization continuity is measured per practice during the free 30-day audit against the practice's own last 90 days of authorization and claim data. The full pipeline, state model, and peer-to-peer escalation ladder are set out in the prior authorization command center whitepaper.
Exhibit 2 · The level-of-care ladder
Each rung authorizes on different evidence, and denies on different grounds.
Behavioral health is the specialty where the same member can move through four levels of care inside one episode, and each move resets the authorization, the criteria set, the code family, and the documentation the payer will read. A program that assesses at one level and bills the per diem of another has a mismatch on the face of the claim.
↔ Swipe the diagram
| Rung | What has to be true to authorize it | What denies it in practice | The control that holds the rung |
|---|---|---|---|
| OutpatientASAM 1.0 | Active behavioral benefit with the entity that actually manages it, a covered diagnosis, and a practitioner the payer recognizes at that license level. Many products do not require prior authorization at this rung at all. | The benefit was verified with the medical plan rather than the behavioral carve-out, or the session was delivered by an associate-level therapist the payer does not accept under the supervising practitioner billed. | Verification routed to the behavioral entity by name, and rendering identity taken from the clinician record rather than typed per claim. |
| Intensive outpatientASAM 2.1 | A documented criteria assessment placing the member at this level, an authorized span with a unit or day allocation, and a program schedule that matches the intensity the level implies. | The per diem is billed on a day that also carries a partial hospitalization per diem, or the counseling delivered inside the program is unbundled onto separate lines alongside the per diem. | One level of care per member per day enforced before submission, with bundled services suppressed automatically rather than caught on the remit. |
| Partial hospitalizationASAM 2.5 | Criteria supporting day-program intensity, physician involvement where the plan requires it, and a concurrent review calendar opened at the moment the span is granted. | The concurrent review date passes unowned, so the payer closes the span and the days already delivered lose authorization retroactively. | A named owner on every review date, with the review packet built before the date rather than requested on it. |
| ResidentialASAM 3.1 to 3.5 | A criteria assessment supporting 24-hour care, the certification of need or equivalent the program's state and payer require, and prior authorization for the initial span with a defined continued-stay review cycle. | Continued stay is not approved and the program keeps the member, so the days convert from a denied claim into unbilled work that never appears in a denial report. | A continued-stay clock that fires before the authorized days run out, and an explicit decision when the payer declines rather than a default to keep serving. |
Level definitions follow The ASAM Criteria, the criteria set most behavioral and substance use payers reference. Code families shown are the ones commonly used for these levels; the exact code, revenue code, modifier, and authorization rule are set per payer and per state program. For a fully worked state-level crosswalk see the ASAM level to Arizona Medicaid code crosswalk. ABA programs run their own authorization structure, with assessment and treatment units authorized separately for BCBAs and RBTs; that model is covered on the behavioral and mental health billing services hub.
From payer response to prevention
Every denial takes one path and leaves behind a better control.
The denial inventory should not be a single aging report. Classification determines the evidence, owner, deadline, remedy, and prevention path. The final outcome is not complete until the balance is reconciled and the source process is updated.
Classify
Assign the denial family, payer reason, financial balance, deadline, and likely source.
Validate
Check the claim, authorization, documentation, enrollment, payer policy, contract, and remit.
Choose remedy
Correct, resubmit, appeal, request reconsideration, pursue payer research, or adjust with approval.
Prove and follow
Send the evidence package, preserve filing proof, record payer responses, and protect deadlines.
Close the loop
Reconcile payment or final disposition and change the upstream prevention control.
CMS-0057-F, scoped correctly
New federal timeframes help, but they do not cover every payer or request.
CMS states that, for prior authorization provisions beginning in 2026, impacted payers must send decisions within 72 hours for expedited requests and seven calendar days for standard requests, with limited exceptions. Impacted payers must also provide a specific reason for denied prior authorization decisions.
The impacted payer categories include Medicare Advantage organizations, state Medicaid and Children's Health Insurance Program agencies, Medicaid and CHIP managed care plans, and qualified health plan issuers on federally facilitated exchanges. CMS notes that the prior authorization policies for QHP issuers on the federally facilitated exchanges are delayed and do not begin January 1, 2026.
The rule does not apply to prior authorization for drugs. It also does not turn the stated federal timeframes into a universal standard for every commercial plan. The workflow should identify the payer category, product, request type, governing requirement, clock start, exception, and escalation path before applying a deadline.
Time the request from a defined event.
A useful queue records when the complete request was submitted, what evidence supports that timestamp, whether the request is standard or expedited, and which rule governs the decision clock.
ProvisionOperational treatment
Expedited
For impacted payers and covered requests, track the 72-hour decision standard and any documented exception.
Standard
For impacted payers and covered requests, track the seven-calendar-day decision standard.
Denial reason
Capture the specific reason supplied by the payer and route the matching response or appeal path.
Drug PA
Do not apply CMS-0057-F prior authorization provisions to drug prior authorization.
APIs
Separate operational deadlines from the generally January 1, 2027 API requirements in the final rule.
Exhibit 3 · The review clock calendar
Two clocks run at once, and only one of them belongs to the payer.
The payer owns the decision clock at the front of the episode. The practice owns every clock after it. Practices staff the first one and forget the second, which is why so many authorization losses happen after the approval, not before it.
↔ Swipe the diagram
The 72-hour expedited and seven-calendar-day standard decision timeframes are the CMS-0057-F provisions beginning in 2026 for impacted payers, with limited exceptions, as described in the CMS fact sheet. They do not apply to drug prior authorization and they are not a universal commercial standard. Day 14, day 28, day 35, and day 42 are illustrative positions in a span, not fixed rules; approved spans, unit pools, review dates, and expiry dates are set per payer, per product, and per authorization.
Denial taxonomy
Reason families that route to a real owner.
The payer code is an input, not the full root cause. Translate it into an actionable internal category, validate the source, and assign the team that can resolve the balance and change the process.
Eligibility, benefit, and carve-out
Coverage inactive, service excluded, behavioral benefit managed elsewhere, visit limitation, referral issue, or patient responsibility misunderstood.
Enrollment and network
Rendering or billing entity not recognized, effective-date mismatch, location missing, network status disputed, or provider relationship not loaded correctly.
Approval and review boundaries
Authorization missing, late, expired, depleted, unmatched to service or setting, or interrupted by a missed concurrent or renewal review.
Medical necessity and level of care
Criteria not met, documentation does not support the requested or billed service, level disputed, information missing, or continued stay not approved.
Data, coding, and filing
Claim element invalid, service and authorization mismatch, duplicate, modifier or place-of-service issue, coordination-of-benefits issue, or filing deadline dispute.
Processing and payment
Payer system error, misrouted claim, missing response, inconsistent adjustment, incorrect contract application, underpayment, or recoupment requiring research.
Exhibit 4 · The taxonomy, drawn as control windows
Every denial family has a last point of control. Past it, you are appealing.
The useful question about a denial family is not how often it happens. It is how early you could still have stopped it. Read the chart left to right: the bar is the window in which the family is preventable, and the moment the bar ends, the only remaining moves are correction, appeal, and research.
↔ Swipe the chart
The chart encodes ASP-RCM's operating taxonomy and the point at which each family stops being preventable. It asserts no denial frequencies. Denial mix is measured per practice during the free 30-day audit against the practice's own last 90 days of remit data, because a hospital-based partial hospitalization program and a solo therapy practice do not share a denial profile.
Appeal and parity evidence
Build the record before making the argument.
An appeal packet should match the actual denial. Preserve the original claim, remit or notice, authorization history, payer criteria and effective version when available, relevant plan language, supporting clinical documentation, corrected data if applicable, correspondence, timely-filing proof, and the requested remedy.
A behavioral health denial may raise a parity question, but a flag is not a legal conclusion. Preserve the plan terms, classification, financial or treatment limitation, medical necessity or authorization criteria, decision facts, and comparable benefit information for qualified review.
On May 15, 2025, the Departments stated that they would not enforce the new portions of the 2024 MHPAEA final rule until a final litigation decision plus 18 months. Statutory MHPAEA obligations, the 2013 final rule, and applicable comparative-analysis obligations continue. Any parity statement in an appeal should use the current plan and legal framework.
EvidenceWhat it establishes
Decision
The exact denied service, reason, date, reviewer, and stated appeal or review path.
Authorization
The requested and approved scope, review history, reference numbers, and correspondence.
Clinical support
The documentation responsive to the stated criteria and service period.
Payer rule
The plan term, policy, criteria, or processing instruction applicable to the decision.
Deadline proof
The submission, receipt, follow-up, and filing evidence protecting review rights.
Exhibit 5 · Parity, as it appears in a work queue
A non-quantitative treatment limitation does not arrive labelled as one.
MHPAEA constrains non-quantitative treatment limitations, the rules a plan applies to the scope or duration of behavioral benefits. Those rules do not show up in a remit as a parity issue. They show up as an ordinary authorization or medical necessity denial. The operational job is to recognize the shape, preserve the comparison evidence, and let qualified review decide whether it is actually a parity problem.
Statute
MHPAEA obligations continue
The statutory Mental Health Parity and Addiction Equity Act obligations remain in force, as do the 2013 final rule and applicable comparative-analysis obligations. Nothing about the enforcement statement below removes them.
U.S. Department of Labor, MHPAEA enforcement statement, May 15, 2025May 15, 2025
Non-enforcement statement issued
The Departments stated they would not enforce the new portions of the 2024 MHPAEA final rule until a final litigation decision plus 18 months. That is a statement about the new 2024 portions specifically, not about parity law generally.
U.S. Department of Labor, MHPAEA enforcement statement, May 15, 2025Evidence
A flag is not a conclusion
Flagging a denial preserves the plan terms, benefit classification, criteria, decision facts, and comparable medical or surgical benefit information. Whether the plan violated parity is a legal determination that depends on the plan, the classification, and current law.
ASP-RCM operating standard; see the primary sources below↔ Swipe the table
| The limitation the plan applies | How it reaches you | The comparison that matters | What to preserve at the moment of denial |
|---|---|---|---|
| Prior authorization requirementApplied to a behavioral service | An authorization-family denial: not obtained, late, or not on file for the level of care delivered. | Whether comparable medical or surgical services in the same benefit classification carry a prior authorization requirement written and applied the same way. | The plan document language, the authorization requirement as published, the request and decision record, and the comparable medical or surgical requirement in the same classification. |
| Concurrent review frequencyHow often the plan re-decides | A medical necessity or continued-stay denial after a review cycle the practice could not realistically meet. | The review cadence the plan applies to a comparable medical or surgical inpatient or intermediate service, and whether the behavioral cadence is stricter in writing or in operation. | The review schedule as communicated, every review submission and payer response, and the plan's stated criteria version in effect on the service date. |
| Medical necessity criteriaWhich criteria set, and which version | A criteria-not-met denial citing a proprietary or licensed criteria set the practice may never have been given. | Whether the plan uses comparable evidentiary standards and processes to develop and apply criteria on the medical or surgical side. | The criteria set named in the denial, the version and effective date if disclosed, the request for the criteria, and the clinical documentation responsive to each cited element. |
| Network composition and accessWho is available and enrolled | An out-of-network or provider-not-recognized denial, often after the member was told the practice was in network. | Network admission standards, reimbursement methodology, and directory accuracy applied to behavioral practitioners versus comparable medical or surgical practitioners. | The directory listing on the date of service, the enrollment and effective-date record, the member's coverage response, and the payer's stated network position. |
| Step therapy or fail-firstLower level required before the next | A level-of-care denial holding that the member must fail outpatient or intensive outpatient before a higher level is approved. | Whether comparable medical or surgical benefits in the same classification carry an equivalent fail-first sequence, written and applied the same way. | The clinical rationale for the level requested, the documented history at any lower level, the plan's stated sequence requirement, and the peer-to-peer record. |
This exhibit describes how limitations surface operationally and what evidence to capture. It is not legal advice and it does not assert that any of these denials violates MHPAEA. Whether a given plan design or application is compliant depends on the plan, the benefit classification, the governing law, the facts, and the current regulatory and enforcement framework. See the Department of Labor parity page and the enforcement statement linked in the primary sources below.
Exhibit 6 · What actually goes wrong
Six failure modes we find in almost every behavioral denial review.
None of these are exotic. Each one is a place where a process assumed something instead of recording it, and each one has a control that costs less than the appeals work it replaces.
Benefits are verified with the medical plan, the answer comes back clean, and the claim goes to a behavioral carve-out the practice never contracted with. Nothing about the verification was wrong. It was the wrong entity.
ControlVerification routed to the behavioral entity by name, with the carve-out recorded on the coverage record and network status confirmed against the vendor rather than the parent plan.The concurrent review date lives in a shared calendar with no name against it. It passes by one business day, and the payer closes the span retroactively across days that were already delivered.
ControlOne named owner per review date, the packet assembled before the date rather than requested on it, and an escalation that fires if the payer has not responded by a defined point.The authorized unit pool is tracked nowhere the schedulers can see. Sessions keep booking after the pool is exhausted, and the reauthorization request is filed only once a denial arrives.
ControlA running unit balance visible at scheduling, with a reauthorization trigger fired at a set share of the pool rather than at zero.The authorization approved one service, one date range and one unit count. The claim carries something else: a different level, a date outside the span, or more units than were granted. Nothing compared the two before submission.
ControlAn authorization-to-claim tie-out that runs pre-bill, comparing billed service, dates, level and units to the approved scope, and holds the claim rather than releasing it into a denial.The payment arrives below the contracted rate and posts as a contractual adjustment. It never enters the denial inventory, never gets appealed, and never appears in any report, because from the system's point of view the claim paid.
ControlRate validation at posting against the loaded fee schedule, so a payment below contract is flagged as a variance with an owner instead of absorbed as a write-off.Denials are worked, balances are recovered, and the same reason code leads the list again next quarter. The resolution work happened. The upstream control never changed.
ControlEvery denial family carries a named prevention owner, and a reason that repeats across two review cycles becomes a workflow change upstream rather than a line item in a deck.These are the failure modes ASP-RCM's denial reviews surface most often. The list is an operating observation, not a measured frequency ranking. Your own distribution is established during the free 30-day audit. Ready to compare? Send a de-identified denial and authorization sample.
Denials and prior authorization FAQ
Questions that determine the queue design.
These answers define the operational control. The governing payer, plan, state, federal program, request type, and date still need to be verified.
What information should a behavioral health prior authorization record contain?
The record should identify the payer and product, member, program or setting, requested service, dates, units or visits, clinical and administrative requirements, submission evidence, reference number, status, decision, approved scope, review date, owner, and next action.
What prior authorization timeframes apply under CMS-0057-F?
For prior authorization provisions beginning in 2026, CMS states that impacted payers must send decisions within 72 hours for expedited requests and seven calendar days for standard requests, with limited exceptions. Impacted payers must also provide a specific reason for denied prior authorization decisions. The rule does not apply to drug prior authorization, and the policy does not cover every commercial plan.
How should behavioral health billing denials be categorized?
Use actionable root-cause families such as eligibility or benefit, enrollment, authorization, medical necessity or level of care, documentation, coding or claim data, timely filing, coordination of benefits, payer processing, contract or payment, and patient responsibility. Each category should route to a named owner and prevention control.
Does a parity flag prove that a behavioral health denial violates MHPAEA?
No. A flag can preserve the denial, plan terms, criteria, dates, and comparable benefit information for qualified review. A legal parity conclusion depends on the plan, benefit classification, governing law, facts, and current regulatory and enforcement framework.
Continue the research
Connect denial operations to the whole specialty.
This page owns the behavioral health denials and prior authorization intent. The connected pages cover multi-program billing, outpatient mental health services, therapist workflows, buyer evaluation, and focused medical-necessity documentation.
Primary sources
Current authorization and parity statements from official pages.
These sources support the 2026 operational timeframes, API distinction, and parity enforcement status described on this page.
Start with the denial reason and follow it upstream.
Share a de-identified denial taxonomy, authorization tracker, or work-queue design. A senior partner can map the evidence, owner, deadline, remedy, and prevention path.
Do not send protected health information through the public contact form.