Peppol is an international network for sending business documents, mostly invoices, directly from one company's software into another company's software. Think of it as a postal system for structured data. You connect to it once through a certified provider called an Access Point, and from then on you can exchange documents with any other organisation on the network, anywhere in the world, without setting anything up with them individually.
It matters in the UK now because the government has confirmed Peppol as the basis for its e-invoicing framework, with a VAT mandate expected from April 2029.
The problem it was built to solve
Every business sends invoices. The awkward part has never been sending them, it has been getting them into the customer's accounting system at the other end in a form their software can actually process.
A PDF attached to an email looks fine to a person and means nothing to a computer. Someone at the other end retypes it, or runs it through scanning software that gets it mostly right. Either way there is a human in the loop, and that human is where the delays and the disputes come from.
The traditional fix was to agree a direct electronic connection with each customer. That works, and plenty of large suppliers still do it, but it scales badly. Ten customers can mean ten arrangements, each with its own file format, its own connection method and its own quirks to maintain. Cross border trade made it worse again, because tax rules and document requirements differ by country.
Peppol's answer was to stop treating this as something each pair of businesses negotiates privately, and to make it a shared public network instead. One connection, one document standard, everybody reachable.
Connect once, reach everyone. That is the whole idea, and everything else is detail.
How a document actually gets there
The route has four points, which is why you will see it described as the four-corner model. In practice it looks like this.
You only ever deal with corner two. Your Access Point provider handles the network side, including working out which provider your customer uses and delivering it there. You do not need to know who their provider is, and you do not need any relationship with them.
The lookup that makes this work is worth understanding, because it is the part people find genuinely surprising. There is a public directory of the network. When you send to a customer, your Access Point queries that directory using the customer's Peppol ID, finds out which Access Point serves them and what document types they accept, then delivers accordingly. Nobody had to tell your system any of that in advance.
What you can send over it
Invoices and credit notes are the overwhelming majority of traffic and are what most businesses start with. The network carries more than that, though the further you go down this list the more it depends on whether your trading partners have chosen to support those document types.
| Document | Direction | How commonly used |
|---|---|---|
| Invoice | Supplier to buyer | Universal. This is the core of the network |
| Credit note | Supplier to buyer | Universal, supported alongside invoices |
| Order | Buyer to supplier | Common in public sector, growing in retail |
| Order response | Supplier to buyer | Used where buyers want confirmation before despatch |
| Despatch advice | Supplier to buyer | Less common, mainly larger trading relationships |
| Catalogue | Supplier to buyer | Public sector procurement mostly |
The documents are structured XML built to a shared specification, which is what makes them machine readable at the far end. You will not see the XML. Your finance system shows you an invoice and the conversion happens in between.
Who is actually on it
Peppol started as a European public procurement initiative and that heritage still shows: public sector buyers across Europe were the first to mandate it and remain the most consistent users. Several European countries now require it for business to business invoicing as well, not just public sector.
It has also spread well outside Europe despite the name, with national adoption programmes in Singapore, Australia, New Zealand and Japan among others.
For a UK business the practical trigger is usually one of three things. You win a public sector contract in a country that mandates it. A large customer tells you their onboarding requires it. Or you start preparing for the UK mandate ahead of the deadline.
Peppol and the UK mandate
This is the part that has changed the conversation for UK businesses. The UK government has confirmed Peppol as the interoperability basis for its e-invoicing framework, with a VAT e-invoicing mandate expected from April 2029 and detailed specifications due before then.
That is a long runway, and it would be easy to conclude there is nothing to do yet. Two reasons not to file it away entirely. The first is that your customers may reach the requirement before you do, particularly if they are large or trade in Europe, and their timetable becomes yours. The second is that the work involved is mostly data quality rather than technology, and data quality problems take longer to fix than connections do.
Do you need it yet?
An honest assessment rather than a sales one. Most UK businesses trading domestically with private sector customers do not need Peppol today. Some do, and for a few it is already blocking revenue.
- You sell to public sector buyers in Europe or are bidding to
- A customer has asked for e-invoicing and named Peppol
- You trade with businesses in countries where it is already mandatory
- You are replacing your finance system anyway, so the mapping work is already on the table
- Your invoice volume is high enough that manual chasing is a real cost
- You trade UK domestic only with private sector customers
- Nobody has asked you for it
- Your invoice volume is modest and manageable by hand
- Your customer base is stable and unlikely to change requirements soon
If you are in the right hand column, the useful thing to do now is not to connect. It is to check that your customer records hold the data a compliant invoice will eventually need, because that is the work that takes months rather than days.
What getting connected involves
Shorter than most people expect on the technical side, longer than most expect on the data side.
You choose a certified Access Point provider and they register your organisation in the network directory. That part is usually a day or two. What takes the time is mapping your invoice data to the required structure, because the specification is strict about things your current invoice template may be relaxed about: tax categories, units of measure, buyer references and the codes that identify what you are actually selling.
That mapping is where most projects either go smoothly or do not. A supplier whose product data is clean gets connected in a couple of weeks. A supplier with inconsistent tax codes and free text descriptions spends longer, and the delay has nothing to do with Peppol.
Not sure where your data stands?
We are a certified Peppol Access Point and we connect invoicing to Xero, QuickBooks and ERP systems. A short call is usually enough to tell you whether this is a two week job or a longer one.
Talk to the teamCommon questions
The one paragraph version
Peppol is a shared network that lets businesses send invoices straight into each other's systems using one connection and one document standard, rather than negotiating a separate arrangement with every customer. It is already mandatory in parts of Europe and increasingly used elsewhere. The UK has chosen it as the basis for its own e-invoicing framework, with a mandate expected from April 2029. If nobody has asked you for it yet, the sensible move is not to connect today but to make sure your invoice data would stand up when someone does.