Your biller’s real number is not the collection rate
The note is signed. The code is right. The authorization is valid. The entry is sitting in the system, finished, and it has been sitting there for nine days.
Nothing is broken. That is what makes this stage different from the one before it. Stage 03 is work that got stuck. Stage 04 is work that is done and has not moved.
The number a collection rate cannot see
A collection rate is a ratio of money collected to money billed. Both halves of it require a claim to exist.
Every claim still sitting in the unbilled queue is excluded from the numerator and the denominator. It cannot help the rate and it cannot hurt it. A biller can be nine days behind, indefinitely, and post a 96 percent collection rate every month.
This is the number that tells you whether the person doing your billing is keeping up, and almost nobody reports it, because the report that would show it is a report on work not yet done.
It is also the last stage you can fix on your own. Everything downstream — clean claims, rate integrity, recoupments — needs a payer on the phone. This one needs a queue worked.
Why the queue exists
Rarely incompetence. Usually cadence.
Claims go out in a weekly batch. A batch cadence builds in 3.5 days of average lag before anyone is late — some claims wait a day, some wait six. Twice-monthly submission builds in 7.5. Nobody decided on that lag. It arrived with the calendar.
Then add the hold pile. Claims parked pending an authorization question, claims flagged for review, claims waiting on a correction that was never assigned. A hold with no owner and no date is not a hold. It is a parking space.
And add capacity. A biller covering several practices allocates hours, and the practice that does not ask for a lag number is the practice whose queue absorbs the shortfall.
What the arithmetic looks like
Same illustrative practice. Forty clients, 600 delivered hours a week, $75 blended. Nine of those hours never converted, from the prior chapter, which leaves 591 hours ready to bill.
Illustrative arithmetic, not a client engagement.
Four hours a week forfeited at the window is $300, and across 48 weeks, $14,400 a year. There is no appeal for those. A claim submitted late is not denied, it is declined, and the distinction matters because a denial can be worked.
What the lag itself costs
The 185 late-submitted hours do get paid. They get paid later, and later has a price.
At $44,325 of billable value a week, a working day is roughly $8,900. A nine-day lag means about $80,000 of finished, billable work is sitting in the queue at any given moment. At a two-day target it would be $18,000.
The difference — about $62,000 — is cash permanently parked in the gap between doing the work and asking to be paid for it. Permanently, because the queue never empties. It just rolls.
That is not a loss. It is your money financing your own billing cadence, and it is the cheapest working capital any practice can free up, because it requires no payer, no appeal and no new client.
The clock you are sharing with stage 03
Filing windows run from date of service. Conversion lag and biller lag stack on the same clock.
Twelve days to convert and nine days to submit is 21 days gone before a claim leaves the building. Against a 90-day payer that leaves 69 days to absorb a denial and a rework. Against a 60-day payer you have spent more than a third of the window on two internal handoffs, and a single denial on day 45 leaves you 15 days to correct and resubmit.
You are likely to look at these two stages separately, because different people own them. The payer adds them together.
Why a percentage of collections does not fix this
A biller paid a percentage of collections is paid the same on a claim submitted Tuesday and the same claim submitted three weeks from Tuesday. The fee follows the dollar, not the date.
The incentive is real and it is aligned on collection. It is silent on speed, and a contract that is silent on speed will produce whatever speed is convenient.
If billing is outsourced, the fix is a term, not a conversation: a stated lag target, reported weekly in dollars and days, on claims ready to bill rather than claims billed. A biller who is keeping up will hand you that number without argument. The reaction to the request is itself informative.
Five checks you can run this week
You do not need anybody's help for these. One export and three months of history.
1. Pull converted and unbilled, aged by date of service, in dollars. Weekly at minimum. This is the report that does not exist in most practices.
2. Bucket it. 0 to 2 days, 3 to 7, 8 to 30, 31 and over. Sort the 31-plus bucket by payer filing window, shortest first, and work it today.
3. Find your submission cadence and write down the average lag it builds in. If the answer is weekly, you own 3.5 of your nine days before anyone did anything wrong. Move to daily.
4. Empty the hold pile. Every held claim gets a named reason, a named owner and a date. Anything that cannot get all three gets submitted or written off on purpose.
5. Compare converted dollars to submitted dollars for three consecutive months. The queue should be roughly flat. If it grows month over month, the biller is not behind, the biller is falling behind, and those are different problems with different fixes.
Check five is the one that tells you whether to work the queue or change the arrangement.
The number to actually track
Biller lag — converted and unbilled, aged by day, target 1 to 2 days, reported in dollars.
Pair it with claims submitted past the filing window, target zero. Not a percentage. A count, with a name on each one, reviewed monthly. These are the only losses in the entire revenue cycle that are fully self-inflicted and fully preventable, and counting them in dollars lets them hide.
Where this sits
This is the fourth of seven stages, and the hinge. Stages 01 through 04 happen inside your building, on your clock, with no payer involved. Stages 05 through 07 happen after the claim is out, where the payer is a participant.
It is also where a claims audit begins. A claims audit starts once a session has been converted and billed, and reconciles the back half of the cycle to cash. That is real work and the right instrument when you already know which payer book is the problem.
The Leak Map runs the whole chain. In most practices the larger number is upstream of this line, not below it.
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.
