The exception queue is a headcount plan
The size of an exception queue decides the size of an AP team. Every invoice that fails a check consumes minutes of a person's day, so a company generating a thousand exceptions a week has already written a staffing plan whether anyone meant to or not: enough clerks to clear a thousand exceptions a week. Few finance leaders read the queue that way, which is how the cost stays unexamined for years.
Queue size decides team size
The arithmetic is short. Take weekly exception volume, divide by what one clerk can clear in a week, and you have the team. A clerk who resolves a few dozen exceptions a day supports a queue of a certain size and no more. When volume rises, the choices are a bigger team, a slower queue, or looser checks, and the third option quietly pays for the first two in overpayments. What each of those minutes costs is laid out in the cost of invoice exceptions.
Budgets renew the queue every year
Annual planning takes last year's exception volume, adds expected growth, and requests the headcount to match. The queue becomes a budget line, and budget lines survive. Outsourcing changes the invoice rather than the logic: a BPO contract priced per invoice or per full-time equivalent is the same staffing plan signed with a vendor, which is why outsourcing the queue doesn't shrink it.
Volume grows faster than teams do
Spend growth, new suppliers, new sites, and acquisitions all raise exception volume, and hiring lags behind every one of them. The gap shows up as an aging queue, and aging queues get worse on their own: suppliers chase, discounts lapse, and reviewers under pressure approve invoices they should have questioned. The team then spends its best hours on the oldest, ugliest cases while the fresh ones stack up behind.
Breaking the link between spend and staffing
Lowering the exception rate helps, and the benchmarks show how far that goes. The stronger lever is removing person-minutes from routine resolution itself. When the routine majority of exceptions resolve autonomously, the staffing plan stops tracking invoice volume, and the people you have move to judgment calls and root causes. The queue keeps its size; it loses its payroll. Since exceptions never go to zero, that is the version of the plan worth writing.
Fragment resolves routine exceptions autonomously, so your team's size stops being a function of your invoice volume. See how it works or request a demo.