Australia's Digital Business Plan requires government agencies to pay suppliers within five days of receiving an invoice through the Peppol network. Framed as a compliance deadline, it reads like an IT project: get connected to Peppol, tick the box. Framed as what it actually is — an operational commitment — it's a much harder problem, and one a lot of agencies haven't fully worked through yet.
Connecting to Peppol is the easy part
Getting a Peppol Access Point in place is genuinely the straightforward half of this. The document format is standardised, the network handles routing between trading partners without a bespoke integration for each one, and an accredited Access Point provider does the heavy lifting on compliance with the format itself. That part of the project has a clear scope and a clear end date.
Five days is a promise about everything downstream of receipt
The five-day clock starts when the invoice arrives — not when someone gets around to looking at it. That means the promise being made isn't really about eInvoicing at all; it's about everything that happens after the document lands: matching against the purchase order, routing for approval, resolving discrepancies, and releasing payment. An agency that receives invoices instantly via Peppol but still routes approvals through email and spreadsheets hasn't actually solved the problem the mandate is checking for — it's just moved the delay one step later in the process.
Where this usually breaks
In practice, the gap tends to show up in a small number of predictable places: purchase orders that were never raised for the spend in question, approval chains that assume someone is at their desk, and exception handling that has no defined path — a wrong amount or a missing PO reference stalls the invoice indefinitely rather than routing it somewhere specific. None of these are eInvoicing problems. They're accounts payable process problems that a five-day mandate simply makes visible faster than they used to be.
What actually needs to be true
Meeting the mandate reliably — not just on the invoices that happen to go smoothly — means the receiving process needs to be closer to automatic than manual: invoices matched against POs without a person doing the matching, exceptions routed to a specific queue rather than a specific person's inbox, and approvals that don't depend on someone being physically available. That's the same shift AI-assisted invoice capture and automated AP workflows are built for — Peppol just puts a clock on it.