Many organizations have invested in AP automation over the past few years. Invoice recognition, digital workflows, Peppol connectivity. The technology is in place, but accounts payable process improvement hasn't followed.
Peppol is a good example. Invoices come in faster and in a structured format, without PDFs sitting in mailboxes. That matters. But anyone who thinks this means their AP process is under control is mistaken.
Automation solves the intake, not what happens after. That is where things break down.
The invoice sits in the system, but the invoice approval workflow still runs through email. Exceptions land on the desk of the same two people who know how everything works. Suppliers call for a status update. At the end of the month the pressure spikes again.
That is not a technology problem. That is a process problem.
The invoice is in. Now what?
An AP team processing 50,000 invoices a year with three or four people handles more than 16,000 invoices per person. At a processing cost of $8 to $12 per invoice, that adds up to $400,000 to $600,000 per year.
These are costs that rarely make it onto the table.
Who knows what an invoice actually costs to process? Who has visibility into the number of exceptions or the time spent on supplier communication? Those are the questions that drive accounts payable process improvement, not which tool you use.
The real problem: no visibility, no feedback loop
What goes wrong in the organization usually ends up with finance. A purchase order that doesn't match, an approver who doesn't respond, a supplier who sends an incorrect invoice.
As long as that happens occasionally, it stays manageable. But in many organizations it has become the norm.
Without a closed end-to-end process and without accounts payable visibility into where time and errors are lost, AP keeps fixing what went wrong earlier in the chain. Peppol, or any other automation layer, just adds another layer on top of a broken process.
What this means for the CFO
A CFO who cannot substantiate their own AP costs is on shaky ground when internal conversations about budgets and efficiency come up. If you want to challenge the business on costs, you need to be able to demonstrate it in your own backyard first.
.webp)