Products
See how Stratas automates AP for mid-market finance teams.
Stratas connects to 100+ ERPs. Start with the system you run.
Proof
Find out what Stratas could save your team.

How Smeg built an efficient, transparent invoice process with Stratas.
Talk to our team about what Stratas could do for you.
What is Peppol? A plain guide for UK finance teams
In this article
Peppol is a network for sending structured invoices and other business documents between organisations, along with the standards that keep those documents readable at both ends. If your supplier and you both connect to it, an invoice can travel from their finance system to yours without anyone printing, emailing or rekeying it. The name once stood for Pan-European Public Procurement On-Line, though it now runs well beyond Europe and well beyond the public sector.
What Peppol is
Two things share the Peppol name, and it helps to keep them apart. The first is the network: a set of connection points that let any member reach any other member. The second is a set of document standards, the Peppol Business Interoperability Specifications, which define exactly how an invoice, a credit note or a purchase order should be laid out so that software on the receiving end can read every field.
Peppol is run by OpenPeppol, a non-profit association based in Belgium and set up in 2012. Its members include software providers, government bodies and businesses, and it maintains the specifications and the rules that connection providers have to follow. As peppol.org describes it, Peppol is an enabler: you reach it through an accredited provider that puts you on the network.
The standards part is what changes the day-to-day for a finance team. When a supplier emails a PDF, someone on your team opens it and keys the supplier, the invoice number, the net, the VAT and each line into your system, or OCR reads it and someone checks the guesses. A Peppol document arrives already structured, field by field, so your finance system reads every value straight off it. That is what lets the invoice move into your ERP with the rekeying step gone.
How it works
Peppol uses what it calls a four-corner model. Picture four corners. In the first is the supplier sending the invoice. In the second is the supplier's access point, the provider that puts the invoice onto the network. The third is your access point, the provider that receives it on your behalf. The fourth is you, the buyer, reading the invoice in your own finance system.
An access point is an accredited provider that connects to the Peppol network. The value of the model is that the two sides do not have to use the same one. Older document networks were closed: to trade electronically, both parties had to be customers of the same service. Peppol compares that to being able to phone only people on your own mobile network. With four corners, your supplier picks their provider, you pick yours, and the two providers exchange documents over agreed standards.
That is why a single Peppol connection reaches a large and growing group of trading partners at once. You connect once, through one access point, and you can exchange documents with any other organisation on the network.
The network also checks the documents that pass across it. Because every access point works to the same specifications, an invoice that does not match the format is rejected at the door. Both sides can rely on the same fields being present and correctly typed, which is the part that makes automation on the receiving end dependable.
Peppol in the UK today
In the UK, e-invoicing is currently voluntary. There is no rule that says you must send or receive invoices through Peppol, and most UK businesses still handle supplier invoices as PDFs or paper. Where Peppol already appears is in parts of the public sector.
The clearest example is health. As the government's e-invoicing consultation response records, NHS Supply Chain requires its suppliers to issue e-invoices through the Peppol network, which is why many organisations that sell into the NHS already have a Peppol connection in place. Public procurement rules also require contracting authorities to be able to receive e-invoices. Most private-sector finance teams have heard the name without ever needing a Peppol connection of their own.
Peppol and the 2029 mandate
That is changing. The government has confirmed that all VAT invoices will have to be issued as e-invoices from 2029, covering business-to-business and business-to-government transactions where VAT is due. The consultation that led to this ran through 2025 and drew several hundred responses, and an implementation roadmap is due at Budget 2026. For the full picture, see our guide to the UK e-invoicing mandate.
The government has not yet said that Peppol will be the required standard. Its consultation response commits to weighing the benefits of adopting an existing standard against designing a UK-specific one, and many respondents pointed to Peppol as the natural choice given its use across the EU and for cross-border trade. The government has also said it will focus on a decentralised exchange model, the shape Peppol takes, but it has not named a standard. What is settled is the direction: structured e-invoicing is coming. Whether Peppol underpins it is a decision for the roadmap.
It is worth watching which standard the government settles on, since that choice shapes what your team will have to support. A number of European countries have already built mandates around Peppol, which is part of why so many UK respondents expect it here too. The detail that matters for your team will land in the Budget 2026 roadmap: which invoices are in scope, which format is required, and how long you have to be ready.
What to ask your software vendor
Peppol may not be on your desk this quarter. It is still worth knowing whether the software you run, or the software you are considering, can handle it when the time comes. A few questions cut to the heart of it.
Can the platform send and receive documents over the Peppol network, and through which access point?
Does it produce and read the structured Peppol invoice format, as well as PDF attachments?
How would a Peppol invoice post into our ERP, with our nominal codes, tax groups and cost centres intact?
If the mandate settles on a different standard, how would the platform support it?
Who owns the access point relationship and accreditation, our team or the vendor?
The answers tell you whether e-invoicing will slot into your existing process or force you to rebuild it. Capture, matching, approval and posting to the ERP should work the same way whether an invoice arrives as a PDF or as a structured Peppol document.
A live walkthrough with our team, built around the questions you bring.
We use your email to arrange the demo. Privacy policy
Want to see this in action?
Book a demo and we'll show you how Stratas handles your specific document types.