
The UK has settled one of the biggest open questions in business payments. Peppol will be the framework underpinning mandatory e-invoicing from April 2029, confirmed through the government's consultation response and reinforced by the work now under way to define a UK invoice standard. For anyone running an accounts payable network, this is not a distant compliance date. It is a signal about the rails every UK invoice will travel on, and the time to design for them is now, not in 2028.
For years, UK finance teams have watched the rest of Europe move to structured e-invoicing while the UK held back. That hesitation is over. The government has confirmed that VAT-registered businesses will need to issue and receive structured electronic invoices for B2B and B2G transactions from 1 April 2029, and that the regime will be built on Peppol rather than a bespoke national system or a centralised government platform.
This matters because the choice of framework shapes everything that follows. Peppol is not a piece of software. It is an open, four-corner network model: your system connects to an access point, the supplier connects to theirs, and the two access points exchange a standardised document over a governed network. No portal to log into, no PDF to rekey, no bilateral integration to build for every trading partner. If that sounds familiar, it should. It is the same logic that underpins a connected accounts payable network, applied to the invoice document itself.
What the government has actually committed to
It is worth being precise about what has been decided, because the detail is easy to lose in the noise.
The mandate covers VAT invoices in B2B and B2G transactions and applies from April 2029. The government has ruled out a centralised clearance platform of the kind used in Italy, opting instead for a decentralised model that follows the four-corner Peppol approach, which was the clear preference of respondents to the consultation. Crucially, the 2029 mandate does not introduce real-time digital reporting to HMRC alongside it. The government continues to explore real-time reporting, but it will not arrive with the e-invoicing mandate.
The format itself is expected to be a UK-specific version of the Peppol International Invoice, commonly referred to as PINT UK, built on the EN 16931 European standard and Peppol BIS Billing. To get there, OpenPeppol established a UK working group towards the end of 2025 with an 18-month remit, timed to land ahead of the deadline. The full implementation roadmap and technical standards are due to be published at the next Budget, which is where formats, interoperability rules, and access point certification will be confirmed.
In short: the direction is fixed, the framework is chosen, and the fine print is being written now.
Why this is good news, not just another deadline
It would be easy to file this under regulatory burden. That would be a mistake. The Peppol decision quietly removes one of the biggest sources of friction in supplier payments.
Today, every buyer and supplier pair negotiates its own way of exchanging invoices. Some send PDFs by email. Some upload to portals. Some still post paper. Each method has to be received, read, validated, and keyed into the buyer's system, which is where errors, delays, and fraud creep in. A structured invoice on a Peppol network arrives as machine-readable data that matches an agreed schema. It can be validated automatically against a purchase order, checked for duplicate or altered details, and routed for approval without a human retyping a single line.
That has a direct bearing on fraud. Invoice redirection and supplier impersonation thrive on unstructured documents and manual handling, where a changed sort code on a PDF can slip through unnoticed. Structured invoicing on a governed network narrows that gap considerably, and it pairs naturally with network-layer signals that flag altered bank details and impersonation attempts before a payment leaves the building. The framework moves the UK closer to the Fair Payment Code's ambitions on prompt payment too, because faster, cleaner invoice exchange shortens the path from receipt to approval.
What it means for your accounts payable network
Here is the part most coverage misses. Peppol standardises the invoice document. It does not, on its own, tell you whether the supplier sending that invoice is who they claim to be, whether their bank details changed last week, or how reliably they are paid across the wider market. The mandate makes the pipe; it does not fill it with trust.
That is precisely where an accounts payable network earns its place. Structured invoices are far more valuable when they land on top of a verified, continuously maintained supplier identity rather than a static row in a master supplier file. A clean Peppol invoice from an unverified supplier is still a risk. A clean Peppol invoice matched to a verified supplier, with current banking details and a known payment history, is something you can act on with confidence.
The same logic extends to visibility. Once invoices flow as structured data, real-time tracking of every invoice across both sides of the transaction stops being aspirational and becomes the default. Buyer and supplier work from one shared record rather than two reconciling copies. Layer in live payment behaviour data and the structured invoice becomes a signal in its own right: who pays on time, who disputes, where bottlenecks sit. The mandate gives you the data format. A network turns that format into intelligence.
What to do before 2029
The deadline is years away, but the businesses that benefit will be the ones that treat the intervening period as preparation rather than delay.
Start by confirming how your finance system will connect to a Peppol access point, since that connection, not the mandate date, is the practical gating item. Map which of your suppliers can already send structured invoices and which will need help, because the long tail of smaller suppliers is where adoption stalls. Watch for the technical standards at Budget, particularly the confirmed PINT UK specification and certification rules. And use the runway to clean up supplier data now, because structured invoicing rewards accurate, verified records and punishes stale ones.
If you want to see how verified supplier identity, fraud signals, and live invoice tracking fit together on a single network, our platform walkthrough shows how it works.
The UK has made its choice. Peppol is the framework, 2029 is the date, and the rails are being laid now. The invoice is becoming structured data on an open network. The advantage will go to the businesses that build the trust layer to sit on top of it.