The best accounts payable teams process an invoice for less than three dollars. Everyone else pays more than twelve. The gap lies in how the cycle is designed, not in the license.
Few finance leaders know what it costs them to process a supplier invoice. The number sits on no line of the budget. It is spread across hours of the accounts payable team, approvals waiting in an inbox, queries to procurement and calls from suppliers asking when they will be paid.
Ardent Partners has measured it for years in its AP Metrics that Matter research. Best-in-class teams process an invoice in 3.1 days at 2.78 dollars. All other organizations take 17.4 days and pay 12.88 dollars. The market average is around 9.40 dollars per invoice.
For a mid-sized company receiving 60,000 invoices a year, the difference between the two groups comes to roughly 600,000 dollars annually. That is before adding lost early-payment discounts, late-payment interest and strained relationships with critical suppliers.
Where the money goes
Software does not explain the gap. What explains it is how many times a person has to touch each invoice. In the same research, top teams process almost half of their invoices with no manual intervention at all, close to twice the average.
In the companies we review, the cost concentrates in three points of the procure-to-pay cycle:
- Intake. The invoice arrives as a PDF by email and someone keys it into the ERP. Every keystroke is a chance for error and one more day of cycle time.
- Three-way match. Purchase order, goods receipt and invoice have to agree. When the ERP does not link the three documents on its own, someone does it by hand, and any price or quantity difference leaves the invoice on hold.
- Approval. Workflows that depend on one specific signature, with no backup and no deadline. The invoice stalls because the approver is traveling.
None of the three is a technology problem. SAP S/4HANA, Oracle Fusion and JD Edwards already handle automatic matching and workflows with delegation. What usually fails is the design: poorly set tolerances, purchases made without a purchase order and master data nobody maintains.
The risk that never shows up in the report: paying twice
Cost per invoice is visible if someone measures it. Duplicate payments, on the other hand, go unnoticed until an honest supplier returns the money or an audit finds it.
According to APQC, even top performers record around 0.8% of disbursements as duplicate or erroneous each year. Among laggards the share exceeds 2%. It is a share of payments, not of value, but a single large repeated payment is enough to wipe out a full year of efficiency savings.
The most frequent cause is not the matching but the vendor master. The same supplier set up twice under similar names, or the same invoice arriving by email and later through a portal with a different reference. The ERP duplicate check compares exact fields, so these cases pass without an alert.
In Spain, B2B e-invoicing changes the starting point
For Spanish companies, the conversation now has a date. Order HAC/1028/2026, published on 5 October, triggered the timeline for mandatory business-to-business e-invoicing set out in the Crea y Crece Law and Royal Decree 238/2026. Companies with turnover above 8 million euros must issue and receive structured invoices from 6 October 2027. Everyone else, one year later.
This removes the first friction point at the root: the invoice is no longer keyed in, it arrives as data. But it only saves money if the ERP is ready to receive and match it without intervention. If the process stays the same, the structured invoice ends up reviewed by hand just like the PDF.
There is a second, less discussed effect. The new system includes reporting the status of each invoice, payment included. How long a company actually takes to pay its suppliers stops being internal information. A slow payables function also becomes a reputational risk.
When automation is not the right place to start
Automating the match on top of a dirty vendor master, or in an organization where a large share of purchases is made without a purchase order, only multiplies exceptions. The team goes from keying invoices to clearing holds, and the feeling inside is that the new system works worse than the old one.
That is why sequence matters. First measure: cost per invoice, share processed with no intervention, exception rate and share of purchases without a PO. Then clean the vendor master and set the purchasing policy. Only then configure tolerances, matching rules and approval workflows with delegation and deadlines.
How we approach it at Aunergia
We treat accounts payable as part of the full procure-to-pay cycle, inside the SAP, Oracle or JD Edwards system the client already runs. We start with those four metrics, because without them there is no way to tell whether an improvement was real. For e-invoice intake we add our joint experience with Edicom, which today covers tax compliance in more than 85 countries, so that the structured document enters the ERP and is matched without intervention.
The goal is not to process invoices faster for the sake of tidiness. It is to stop overpaying, stop paying late and reach October 2027 with the process ready, not just the connector.
Does your team know today what it costs to process one supplier invoice, and what share comes in without anyone touching it?
Sources: Ardent Partners, AP Metrics that Matter; APQC, Open Standards Benchmarking for Accounts Payable; Order HAC/1028/2026 and Royal Decree 238/2026; Edicom.
Comentarios recientes