The units were gone before anyone looked
A session happens on a Thursday. The RBT is paid for it. The clinic is heated for it. The authorization it was going to bill against ran out on the Tuesday.
Nobody notices until the denial arrives in March.
The worst shape a leak can take
Most revenue problems are a delay or a dispute. This one is neither.
A denied claim can be appealed. A short payment can be challenged. A slow claim is still a claim. In every other stage there is a mechanism, a window, somebody to talk to.
A session delivered outside a valid authorization has no mechanism. The payer never agreed to cover it. There is no adjudication to argue with, because nothing was adjudicated in your favour and then taken away. You delivered care that nobody had agreed to pay for, and the cost is fully incurred: wages, supervision, drive time, the room.
That is the whole shape of stage 02. Full cost, zero revenue, no recourse.
The four ways it happens
Units exhausted. The authorization covered 480 units. You delivered 512. The last 32 were free.
Span expired. The authorization ran to 30 September. The session was on 2 October. The renewal was submitted, is probably going to be approved, and will very likely not be retroactive to cover the gap.
Wrong code. The session was 97155. The authorization covers 97153. Both are approved, both are valid, neither covers the other.
Weekly cap exceeded. The total units were there. The week’s units were not. This one is the sneakiest because the authorization looks fine at every level except the one being enforced.
All four look identical from the schedule. The appointment is booked, the client arrives, the session runs. The system does not stop you, because most scheduling systems are not wired to the authorization in any meaningful way.
What it costs
Illustrative arithmetic, not a client engagement.
Twenty-three hours a week out of 600 is under 4 percent, which is why it never sets off an alarm. Eighty-three thousand a year is not under 4 percent of anything that matters.
And the clinical cost sits underneath it. Those 23 hours were delivered by people you are paying, to clients who needed them, using capacity you could have sold. The care was good. The transaction never existed.
Why the denial is not the discovery
The obvious objection is that you would find out. The claim denies, the biller tells you, you fix it.
You do find out. Ten to fourteen weeks later.
Between the session and the remittance there is conversion, submission, adjudication and posting. Twelve weeks is normal. In twelve weeks a client at 15 hours a week has delivered another 180 hours, and if the cause was structural — a weekly cap nobody loaded, a code that was never covered — every one of those hours has the same problem.
So the denial does not find the leak. It finds a sample of the leak, after the leak has been running for a quarter.
The check that runs before the session
The only place this is cheap is before the appointment happens.
The test is four questions, and a scheduling system can be made to ask all four: is there an authorization covering this client on this date, does it cover this code, are there units remaining, and is this week under the cap.
Some practice management systems will do this natively and most practices have not turned it on, usually because the authorization data in the system is incomplete and the warnings became noise. That is a data problem wearing a configuration costume, and it is worth a week of someone’s time to clean.
Where the system will not do it, the fallback is a weekly report rather than a per-session block: every client whose remaining units will not cover next week’s scheduled hours. That catches exhaustion and caps. Expiry is caught by the renewal trigger from the next post. Code mismatch is caught at intake by reading the approval against the request.
None of it requires software you do not have. It requires the authorization to be in the system accurately, which is the thing that usually is not true.
Five checks you can run this week
1. Count sessions in the last quarter with no valid authorization on the date of service. Multiply by your blended rate. That is the size of the stage, and most practices have never produced this number.
2. Check whether your scheduling system can see authorization units at all. If it cannot, no amount of process will catch this before the session.
3. For every active client, compare remaining units to next week’s scheduled hours. Anything short is an appointment to move, not a denial to appeal.
4. Pull denials coded to no-authorization or unit-limit for the last six months and group them by client. A client appearing more than twice is a structural cause, not an incident.
5. Check that every authorization’s weekly cap is in the scheduling system as a hard constraint, not in a note. A cap in a note is a cap nobody enforces.
The number to actually track
Sessions delivered with no valid authorization on the date of service, counted weekly, in dollars.
Pair it with clients whose remaining units will not cover next week’s scheduled hours. One measures what already went wrong, the other prevents it.
Denial volume is not a substitute. It reports a sample of this problem, a quarter late.
Where this sits
This is the second of eight stages where ABA revenue leaves. Stage 01 is the reservoir — what a client will realistically receive. Authorization burn is what happens when delivery and authorization stop lining up.
It is the only stage where the money was never available, rather than delayed or disputed.
A Leak Map Assessment measures all eight — the reservoir, authorization burn, cancellations, session conversion, conversion to billed, clean claims, rate integrity and recoupments. A claims audit is a different instrument. It starts once a session has been converted and billed, and reconciles the back half of the cycle to cash.
Aimline closes the books, oversees the revenue cycle, and sits in the CFO seat for ABA practices. We run claims audits scoped to a payer book, and Leak Map Assessments that measure the full cycle — three weeks, $7,500 fixed. Either one gives us a verified number to run oversight against, and the report is yours whether or not you engage us to fix what it finds.
