Denials do not originate in billing
The denial arrives in the billing inbox, so the denial becomes billing’s problem.
That is a reasonable operational arrangement and a terrible analytical one, because it puts the fix in the hands of the one department that could not have prevented it.
Where denials actually come from
Four origins, and billing is the smallest of them.
Intake. Wrong member ID, wrong plan, coverage terminated, secondary not captured, demographic mismatch. Everything here was determined before a single session happened, usually in a fifteen-minute phone call months earlier.
Authorization. No auth on the date of service, wrong code authorized, weekly cap exceeded, span shifted. Chapter 02 covers all of these. They surface as denials because that is the first moment the payer speaks.
Documentation. Missing note, unsigned note, note that does not support the code, no supervisory signature where one is required. This is a clinical workflow output arriving three months later wearing a denial code.
Coding and submission. Wrong modifier, wrong place of service, wrong units, duplicate submission. This is the only bucket that genuinely belongs to billing, and in most practices it is under a fifth of the total.
The attribution table
Illustrative arithmetic, not a client engagement.
Eighty-three percent of denials were caused before the claim reached the biller. The biller can rework every one of them and prevent none of them.
This is not an argument about blame. It is an argument about where to spend an improvement effort. Six months of pressure on the billing function will move 17 percent of the problem.
Building the attribution
The denial code tells you the symptom. It does not tell you the origin, and the mapping is not one-to-one.
A “no authorization on date of service” denial could be an authorization that expired — auth origin — or a session delivered on a date outside the span because the schedule was built wrong — scheduling origin — or an authorization that exists and was never entered into the system — intake origin. Same code, three causes, three different fixes.
So the attribution needs a human, once per denial, choosing from four buttons. It is fifteen seconds of work and it is the difference between a denial report and a denial analysis.
Practically: add an origin field to whatever the biller already uses to track denials. Four options, required, filled at the point of first touch. After sixty days you will have a table like the one above, built from your own book rather than from an article.
What to do with it
Take the largest origin and find its two biggest denial codes. That is almost always five or six root causes covering half your denials.
In most practices the intake bucket is dominated by two things: eligibility not re-verified at the start of a new plan year, and secondary coverage never captured. Both are checklist items. Both are free to fix. Both are worth more than any amount of billing process improvement.
Then set a standard per origin rather than one for the practice. The front desk owns an eligibility verification rate. The auth owner owns a valid-auth-on-DOS rate. The clinical lead owns a note-complete-at-submission rate. Billing owns first-pass clean rate on the things it controls.
Four owners, four numbers. The practice-level denial rate becomes a scoreboard rather than a task.
The conversation this makes possible
The useful side effect is that it ends a specific unproductive argument.
Every practice with a denial problem has had a version of the conversation where the owner is frustrated with the biller and the biller is frustrated that nobody upstream gives them what they need. Both are correct and neither can prove it.
An attribution table proves it, in both directions, and it does so without anyone having to characterise anybody’s effort.
Five checks you can run this week
1. Add the origin field with four options and make it required at first touch. Nothing else here works without it.
2. Attribute the last sixty denials by hand so you have a table before the field has collected anything. An afternoon.
3. Find the top two codes inside the largest origin. That is your list, and it will be shorter than you expect.
4. Check whether eligibility is re-verified at plan year boundaries. If it is not, that is likely your single largest denial cause and it is a calendar reminder.
5. Give each origin an owner and a number. A denial rate owned by everyone is owned by the biller, which is where this started.
The number to actually track
Denials attributed to origin — intake, authorization, documentation, coding — with an owner and a number against each.
Pair it with the top two denial codes inside the largest origin. That is usually five or six root causes covering half your denials.
A practice-level denial rate is a scoreboard. It tells nobody what to do on Monday.
Where this sits
This is the sixth of eight stages where ABA revenue leaves, and the first one where a payer has to agree with you. Most of what surfaces here was caused in stages 01 through 05.
A denial is where an error surfaces, not where it happened, and in most practices four fifths of them were caused before billing ever saw the claim.
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.
