Authorization utilization is the master metric of ABA revenue.
Nearly every billable ABA hour must be pre approved, unit by unit, credential by credential. The gap between what payers authorized and what practices actually delivered and billed is routinely the largest source of foregone revenue, and it never appears on an aging report.
Entry 01 · the invisible leakApproved revenue quietly expires.
Authorization failure rarely looks like a rejection. Units that were approved but never scheduled, delivered, and billed simply vanish at period end. No denial fires, no report flags them, and no appeals team can recover them.
Entry 02 · the exposureFour ways authorizations fail without denying.
Authorization failure rarely looks like a rejection. It looks like a schedule that never hits authorized frequency, an approval that expired Friday while sessions ran through Wednesday, and units drawn against the wrong credential tier. Payer rules on units, tiers, and renewal vary by state and plan; the ABA Payer Policy Matrix tracks them jurisdiction by jurisdiction.
Silent underutilization
Scheduled frequency never matches authorized frequency, so units expire unused. Nothing denies. Nothing alerts. Revenue simply never exists.
Sessions past expiry
Care continues across an authorization boundary. Lapsed days can rarely be billed retroactively; those sessions are delivered free.
Credential tier mismatch
97155 protocol modification and 97153 technician units draw from separate pools. Billing the wrong pool burns one and strands the other.
Late re-authorization
Renewal needs updated assessments and plans. A late assessment does not delay revenue; it deletes the gap days entirely.
Entry 03 · the defenseThe ledger treats every approval as perishable inventory.
Every authorization is a grant of revenue with an expiration date. The ledger method posts it like an accountant would: credit the approval in, debit the consumption out, reconcile the balance to remittance, and flag the drift before it becomes forfeiture.
Every approval logged day of arrival: payer, codes, units by credential, dates, frequency limits.
Scheduled sessions convert to projected unit consumption per week, per code.
Below 85% projected utilization at midpoint triggers a scheduling alert to the BCBA team.
Re-auth packets enter preparation 30 days out; assessment dependencies tracked.
Approved, billed, and paid units tie out. Variances become root cause work.
| Ledger metric | Target | Warning | Cadence |
|---|---|---|---|
| Authorization utilization | 85 to 95% | Below 75% | Weekly per client |
| Authorization accuracy | 98%+ | Below 95% | Every submission |
| Re-auth lead time | 21 to 30 days | Under 14 days | Weekly pipeline |
| Sessions without active auth | 0 | Any | Daily exception report |
| Lapsed days per client per year | 0 to 3 | Over 7 | Monthly |
Step five is where the ledger meets the claim. Reconciling approved units to billed and paid units is the same discipline as matching the schedule, the session note, and the claim line, which is the subject of the companion paper in this series, The Three-Way Match Handbook.
Denials are visible and get worked. Unused authorized units are invisible: they never become claims, so no report flags them. In most ABA practices the utilization gap exceeds total denials.
The Authorization Ledger · ABA Revenue Engine series · Paper 01
Entry 04 · lifecycle checkpointsA 90-day authorization, run on rails.
Plot authorized units against consumed units and the whole story is visible in one picture: the pace the approval demands, the pace the schedule is actually delivering, and the exact day the gap becomes an intervention.
Units, tiers, dates, and limits logged into the ledger same day.
Projected utilization below 85% triggers scheduling intervention.
Re-auth packet in preparation; assessment dependencies chased.
New approval active before old expiry. No unbillable days.
Entry 05 · proofWhen the ledger meets a payer that will not pay.
Valid authorizations, denied at scale, overturned in full.
An established provider began receiving mass denials on claims backed by valid, documented approvals. ASP-RCM matched every denied claim to its authorization letter, unit grant, and rendering credential, escalated to payer leadership with a consolidated evidence file, and when correction did not follow, filed a formal intervention through the State Insurance Commissioner.
Under regulatory scrutiny, every denied claim in the disputed population was overturned.
Entry 06 · FAQFour questions ABA operators ask us.
What is authorization utilization rate?
Units delivered and billed divided by units authorized, measured per client, per code, per authorization period. Best practice reviews it weekly at client level and monthly at practice level.
Why does utilization matter more than denial rate?
Denials are visible and get worked. Unused authorized units are invisible: they never become claims, so no report flags them. In most ABA practices the utilization gap exceeds total denials.
How much lead time does re-authorization need?
Packets should enter preparation 21 to 30 days before expiry, because updated assessments and treatment plans are the usual bottleneck, not the payer form.
Can lapsed days be billed retroactively?
Rarely. Most payers will not pay sessions rendered without an active authorization, which is why the ledger standard for lapsed days is zero.
Is approved revenue expiring on your schedule?
Our team will map your authorization pipeline, quantify unbilled approved units, and hand you a corrective plan at no cost.