Approving an invoice takes about a minute. Someone looks at it, recognises the supplier, checks it against what was ordered, and says yes.
Getting to that minute takes days. The invoice arrives as a PDF attached to an email, or a photograph, or a scan of a scan. Someone opens it, works out which purchase order it belongs to, finds the goods receipt, notices the amount is 4% higher than the order, and emails the budget holder to ask whether that is expected. Then the invoice sits, because the budget holder is travelling.
Most work on accounts payable has gone into that one minute. Almost none has gone into the days.
Where the time actually goes
Break a manual approval into the steps that really happen, rather than the ones on the process map, and the shape is consistent across finance teams:
| Step | What happens | Who is waiting |
|---|---|---|
| Intake | The invoice arrives in a shared inbox, in whatever format the supplier chose | Nobody yet |
| Reading | Someone types the number, date, amount, tax and line items into a system or a spreadsheet | The AP clerk |
| Matching | Find the purchase order. Find the goods receipt. Compare three documents that never agree perfectly | The AP clerk |
| Questions | The variance, the missing PO, the supplier nobody recognises, the bank details that changed | A named person who has not replied yet |
| Approval | The budget holder says yes | Nobody, once they look |
| Payment | Scheduled in the run | Nobody |
Only two of those six steps involve judgment. The rest is retrieval, transcription and waiting. Most invoice approval software compresses the transcription and leaves the waiting exactly where it was.
The step nobody has automated
Look at the fourth row again. It is the only one where the thing you are waiting for does not exist yet, in any system, in any format. It exists in somebody's head, and it stays there until somebody else asks them for it.
This is the step that actually sets your cycle time. Reading an invoice badly costs minutes. Waiting four days for a project manager to confirm that the extra 4% was agreed on a phone call costs four days, and it costs them again next month on the next invoice from the same supplier.
This is also why approval workflow tooling helps less than it should. Every tool in this category gathers, checks and routes. None of them go and get the answer. The invoice sits in a queue marked "pending approval", which is technically true and tells you nothing, because the approver is not the blocker. The person who owes an answer to the approver is the blocker, and nowhere in the system is that person named.
Price it on your own numbers
Industry benchmarks for cost-per-invoice are easy to find and almost impossible to apply, because they average across companies whose processes have nothing in common with yours. Your own numbers are better, and you already have them.
Four inputs:
| Input | Where to get it |
|---|---|
| Invoices per month | Your ledger |
| Minutes of human handling per invoice, start to finish | Ask the AP team. They will know, and the number is usually higher than the process map implies, because the process map does not count re-reading a thread to remember where something got stuck |
| Share that raise a question | Ask how many need a chase. In most teams it is between a fifth and a third |
| Days those spend waiting | The gap between the question being asked and answered |
A worked example, with illustrative figures rather than benchmarks. Substitute your own:
2,000 invoices a month at 11 minutes of handling each is roughly 367 hours of work every month before anyone has decided anything. If a quarter of those invoices raise a question, that is 500 chases a month. If each one waits three days, you are carrying 1,500 invoice-days of delay per month, all of it in the part of the process nobody owns.
The hours are the visible cost. The delay is the expensive one, because it is what turns into early-payment discounts you did not capture, suppliers who put you on stop, accruals that are wrong at month end, and a period close that starts with reconciliation instead of reporting.
The costs that do not show up as hours
Three of them are worth pricing separately, because they are the ones a finance team feels and rarely attributes to the approval process.
Checks done by eye are checks done inconsistently. Whether a supplier's bank details changed since the last invoice is a question a person can answer perfectly on a quiet Tuesday and miss entirely on the last day of the month. This is not a competence problem. It is what happens when the same check runs 2,000 times a month with no record of it having run.
Nobody can tell you where the queue actually is. "Pending approval" covers an invoice waiting on a director's signature and an invoice waiting on a warehouse manager to confirm a delivery, and those are different problems with different fixes. Without that split, the only lever anyone has is to chase everybody.
Volume growth costs headcount growth. A manual process scales linearly, so twice the invoices means twice the handling. That is the constraint most finance teams are actually trying to escape, and it is the one that makes the arithmetic above worth doing carefully.
One thing worth saying plainly: doing this by hand is not the cheap option, and it was never really a choice. It is manual because until recently nothing could read what arrived, so no alternative existed.
What changes when approval runs as a decision you set up once
The shift is from a process people push invoices through to a decision that runs on its own. You describe the decision once: what has to be true for an invoice to be approved, what the tolerances are, who to ask when something is missing, and what happens when the answer does not come back.
Then every invoice runs through it the same way.
| Step | By hand today | As a decision |
|---|---|---|
| Gather | Open the email, find the PO, find the receipt, open the supplier record | Pulled from wherever they already sit, plus the invoice read on arrival whatever state it is in |
| Chase | Someone remembers to ask, eventually, and then remembers to follow up | The named person is asked automatically, and asked again. The case is on hold with the reason on the front, so the queue tells you who you are waiting on |
| Assess | Three-way match by eye, tolerances from memory | Your tolerances, your thresholds, your rules, applied identically every time, with the evidence attached to each check |
| Decide | The budget holder looks at everything again | A recommendation with the reasons and the source behind each check. Your team makes the call |
That last row matters more than it looks. We do not automate the decision. Agents do the reading, the gathering and the chasing; the rules your team approved make the recommendation, and a person accepts it. Once enough of them have come back right, teams hand over the straightforward invoices and keep the rest for a human. You decide how much it decides.
The step to watch is the chase. It is the one that removes days rather than minutes, and it is the reason a queue stops being a mystery: instead of 400 invoices marked "pending", you have 60 waiting on four named people, and you can see which four.
You keep the system you already pay for
None of this replaces your ERP, your accounting system or your AP tool. The invoice still lands where it lands and the payment still runs where it runs. What changes is the part between them, which is where the days are.
We connect in both directions across 400+ integrations spanning every industry we serve, so the system of record stays the system of record. If your team never wants to open another tool, they do not have to. The decision runs, the questions arrive wherever your team already talks, and the answer lands back in the system you already use.
Where to start
Take one invoice type. Not all of them. The one with the most volume and the fewest exceptions is usually the one where the arithmetic above is worst, because it is the one being handled 800 times a month by someone reading the same three fields.
Write down what has to be true for it to be approved, who gets asked when something is missing, and what happens if they do not reply. That document is the decision. Everything after it is configuration.
Teams pulling ahead on payables are not the ones approving faster. Approving was never slow. They are the ones who stopped spending four days getting to the point where approving was possible.