🔗 OasisPro · Peppol Network · eInvoicing Infrastructure Explained
Peppol, explained without the acronyms.
The network behind five mandates.
Peppol network comes up in every eInvoicing conversation and is almost never explained properly. It is not software you buy, it is not a government system, and it is not a format. It is a set of agreed rules that let organisations exchange structured documents without every pair of trading partners building a bespoke connection first. Once you see the shape of it, most of the confusion around European eInvoicing disappears.
This matters more than it used to. Belgium runs its B2B mandate on the Peppol network, and the UK has confirmed it as the framework for the April 2029 regime.
Here is how it actually works, in plain English.
Think of it as the mobile phone network for invoices. You do not need an agreement with your customer's phone company to call them. You need a provider, they need a provider, and the two providers know how to talk.
That analogy holds surprisingly well. Your access point is your network operator. The recipient has their own. The rules that let the two interoperate are what Peppol actually is. And just as you keep your number when you switch operator, your participant identifier stays yours if you change provider.
How the Peppol network moves an invoice
Here is how the Peppol network handles a single document. You raise an invoice in your ERP. Your system produces it in a structured format, typically Peppol BIS, which aligns with the European standard EN 16931.
That document goes to your access point, the accredited provider you have contracted with. It validates the invoice against the specification and rejects anything malformed before it travels.
Your access point looks up the recipient in a directory using their participant identifier, then routes the document to whichever access point serves them.
Their provider delivers it into their finance system. No manual keying, no PDF, no email attachment, and no bespoke integration between your business and theirs.
The OpenPeppol organisation maintains the specifications and accredits providers.
Participant identifiers
Every participant has an identifier, usually derived from a VAT or company registration number. It is how the directory finds the right access point for a recipient, and it stays with you if you change provider.
Peppol BIS and EN 16931
BIS specifications define exactly what a compliant document must contain. They align with EN 16931, the European standard, which is why Peppol capability transfers so readily between countries.
The fifth corner
Some countries add the tax authority as a fifth participant, receiving invoice data alongside the exchange. That is how clearance and digital reporting models get layered onto the same infrastructure.
Why Belgium and the UK both landed on it
A clearance model like Italy's or Poland's puts the tax authority in the middle of every transaction, which is powerful and expensive to build. A Peppol exchange model reuses infrastructure that already exists across Europe, gets businesses onto structured invoicing faster, and leaves the option of adding reporting later. Both countries chose the pragmatic route.
What connecting to the Peppol network actually involves
Joining the Peppol network involves less than most people expect on the technical side, and more than most expect on the data side.
Technically you need a route from your ERP to an access point, and the ability to produce and consume structured documents. Middleware handles both if your ERP cannot.
The harder part is data quality. Missing VAT numbers, inconsistent legal entity names, and duplicate customer records all cause rejections, and validation happens before the document travels.
Receiving matters as much as sending. Once you are registered on the Peppol network, suppliers can send to you, and those documents need somewhere to land.
Our guide to Belgium's Peppol mandate shows what the model looks like in a country where it is already compulsory.
The technical connection is a few weeks. Cleaning the master data behind it is what actually determines whether your project runs to plan.
Common misconceptions about the Peppol network
That the Peppol network is a government system. It is not. Peppol is governed by OpenPeppol, a member organisation, and the access points are commercial providers competing for your business.
That joining means your tax authority sees your invoices. In the standard four corner model it does not. Only where a country adds a fifth corner does the authority receive data.
That it is a format. Peppol BIS specifications define document content, but the network is the routing and interoperability agreement, not the file itself.
That you need one connection per country. You do not. That is precisely the problem the Peppol network was built to remove, and it is why capability built for one mandate carries to the next.
That it only handles invoices. Orders, despatch advices, catalogues and credit notes all travel the same rails, which is where the operational benefits beyond compliance usually appear.
And finally, that adopting it is a finance project. It touches sales order processing, procurement, master data and IT, and it needs an owner across all four.
Where the Peppol network is heading
Belgium made the Peppol network compulsory for domestic B2B from January 2026. The UK has confirmed it as the framework for April 2029, with a dedicated working group developing national specifications.
The European ViDA package pushes cross-border digital reporting from July 2030, aligned to EN 16931, which is the same standard Peppol BIS follows.
You can read the UK government's own position in the consultation outcome on GOV.UK.
One gateway, every network, any ERP.
The OasisPro EU eInvoicing Gateway connects SAP, Oracle, Odoo, IFS Cloud, Dynamics, NetSuite or any other system to Peppol and to the clearance platforms used elsewhere in Europe. You integrate once. We keep pace with specification changes, new countries, and the UK regime arriving in 2029.
Read about the EU eInvoicing GatewayFind out what Peppol readiness looks like for your ERP.
Tell us which system you run and which countries you trade with. We will tell you what your ERP can do natively, what needs middleware, and what state your master data has to reach before anything will validate. No obligation and no jargon.
What is the Peppol network?
Peppol is an international framework that lets organisations exchange structured business documents such as invoices without each pair of trading partners building a bespoke connection. You connect once to an accredited access point, and through it you can reach every other participant on the network, in any country that uses it.
What is a Peppol access point?
An access point is an accredited service provider that connects you to the network. You send your invoice to your access point, it validates and routes the document to the recipient's access point, and that provider delivers it into the recipient's system. Neither party needs a direct relationship with the other's software.
What is the four corner model?
The four corners are the sender, the sender's access point, the receiver's access point, and the receiver. Documents flow from corner one to corner four through the two providers in the middle. Some countries add a fifth corner for the tax authority, which is how clearance and reporting models are layered on top.
Is Peppol used in the UK?
Yes. Peppol has been used for NHS England supplier invoicing for years, and it has been confirmed as the interoperability framework for the UK eInvoicing mandate arriving in April 2029. OpenPeppol also established a dedicated UK working group to develop invoice specifications reflecting national requirements.
Understanding the Peppol network makes every mandate easier to read
Once the four corner model behind the Peppol network is clear, the differences between countries stop looking like separate problems and start looking like variations on one.
Belgium and the UK exchange. Italy and Poland clear through a tax platform. France uses accredited platforms with a central directory. Same shape, different middle.
Build for the shape and the variations become configuration.
None of this requires deep technical knowledge to decide on. It requires knowing which countries you sell into, what your ERP already supports, and how clean your customer and supplier records are.
Those three answers tell you almost everything about how difficult joining the Peppol network will be for your business, and they are answers you can gather this week without engaging anybody.