Take one invoice and follow it. It arrives on the 3rd. It's entered on the 9th. It goes for approval on the 9th. It's approved on the 17th. It's paid on the 30th.
Twenty-seven days. Now add up the time anyone actually spent doing anything to it: perhaps ten minutes, spread across three people.
That gap is the thing worth looking at. In most AP processes the problem isn't that the work is slow. It's that the invoice spends almost all of its life waiting, and waiting is invisible in a way that work isn't.
Work time and queue time are different problems
Work time is how long a task takes when someone is doing it. Entering an invoice, reviewing it, approving it.
Queue time is how long it sits between tasks. In the inbox before anyone opens it. In the ledger before it goes for approval. In an approver's email while they're on site.
Almost every AP improvement effort goes after work time — faster entry, a better keyboard, a template. And almost all the elapsed time is queue time.
If ten minutes of work is spread across twenty-seven days, halving the work time saves you five minutes. Removing one week of queue time saves you a week.
Where the queues form
Four places, in rough order of how much time they absorb.
1. Between arrival and entry
Invoices arrive continuously. Entry happens in blocks — once a week for many small teams, sometimes only at month-end.
So an invoice that arrives the day after an entry session waits until the next one. With weekly entry, average wait is around three days. With monthly, it's around two weeks before anyone has even looked at it.
This queue is usually the largest and it's the one nobody counts, because from the ledger's point of view the invoice doesn't exist yet. It is also the one recording documents on arrival removes outright.
2. Waiting for an approver
The approver is rarely a finance person. They're the manager who ordered the thing, and approving invoices is not their main job.
Email is the usual mechanism, which means the request competes with everything else in their inbox and has no state. Nobody can see whether it's been read. There's no queue to look at, only a sent message and a hope.
The characteristic failure is silence — not rejection. The invoice isn't refused, it's just not got to, and there's nothing to look at that would tell you.
3. Waiting on a query
Something doesn't match. Wrong quantity, price differs from the quote, no purchase reference, unclear what it was for.
The query goes to the supplier or to the person who ordered it. Then it waits for a reply, and if nobody owns chasing it, it can wait indefinitely. Queried invoices are where the genuinely old items in an aged creditors report come from.
4. Waiting for the payment run
Most businesses pay on a cycle — weekly, fortnightly, or once a month. An invoice approved the day after a run waits for the next one.
This queue is deliberate and mostly fine. It's the one people assume is the problem, and it's usually the smallest of the four.
Why it stays hidden
Queue time doesn't appear in anyone's workload. Nobody is busy while an invoice sits in an approver's inbox, so it doesn't feel like a cost.
It also doesn't appear in most reporting. An aged creditors report shows invoice date against today, which mixes together "we haven't processed this" and "we've processed it and we're not due to pay yet". Those are completely different problems and the report shows them as the same number.
And the person best placed to see the delay — whoever is doing entry — usually can't see the approval stage at all, because it's happening in someone else's email.
Finding your own bottleneck
You don't need a system for this. Take twenty invoices you've recently paid and record four dates for each: invoice received, entered, approved, paid.
Then look at the three gaps.
| Gap | What a long one means |
|---|---|
| Received → entered | Entry is too infrequent for the volume |
| Entered → approved | Approvals have no visible queue or owner |
| Approved → paid | Payment runs are too far apart, or approval lands just after one |
One of the three will usually dominate. Fix that one. The other two are noise until it's addressed, and this is worth redoing after any change, because the bottleneck moves rather than disappearing.
What actually shortens the cycle
Process on arrival, not in batches. The biggest queue is the one before entry, and it exists purely because entry is an event rather than something continuous. Anything that gets documents captured as they land removes most of it.
Give approvals a visible state. The single change with the best return is being able to see what's outstanding and with whom. Email has no state; a list does. It doesn't need to be sophisticated — a shared view of pending items removes most silent delays, because the delay becomes visible to the person waiting on it.
Set a threshold so most invoices skip approval entirely. If everything over £50 needs a manager's sign-off, you've created a queue for items where the review costs more than the risk. Route by value, and let the small recurring ones through on a standing approval.
Give queries an owner and a date. Not a process — just a name against each one and a day when someone checks. Most queried invoices go stale from nobody's-job rather than from difficulty.
Pay more often. Weekly runs instead of monthly halves the last queue at essentially no cost, provided your cash position supports it.
The trade-off worth naming
Faster is not automatically better. Paying sooner than you need to costs working capital, and there's a legitimate reason to hold invoices until they're due.
But there's a difference between choosing to pay on day 30 and taking 30 days to get an invoice through the process. The first is a cash decision. The second is a process that has made the decision for you and removed the option of paying early to secure a discount or keep a supplier onside.
The goal isn't to pay everything immediately. It's to have the invoice approved and ready well before the due date, so that when you pay is something you decide rather than something that happens to you.
A reasonable target
For a small business with straightforward purchases, from invoice arriving to approved and ready to pay in under five working days is achievable without special software. Most of getting there is entering more often, making approval visible, and not sending low-value invoices for sign-off.
If you're currently at three or four weeks, almost all of the difference will be sitting in one of those three gaps.
Cribble reads invoices as they arrive rather than in a monthly batch, and routes them through Admin, Finance and Approver tiers so what's outstanding and with whom is a list rather than a guess. The first queue is the one it removes.