Peppol solves a problem that sounds trivial and is not: how do you send a structured invoice to a company you have never traded with, whose software you know nothing about, without either of you building a custom connection first? Traditional electronic data interchange answered this with bilateral links — every trading pair wired up individually, which works until you have a hundred partners and ninety-nine integrations.
Peppol answers it the way email does. You connect once, to one provider, and through that single connection you can reach every other participant on the network. Understanding that idea is most of understanding Peppol, and it explains why several governments chose it as the backbone for their e-invoicing mandates.
The four-corner model
Peppol is described as a four-corner model, and the four corners are worth naming precisely because the middle two do all the work.
Corner one is the supplier, sending an invoice. Corner two is the supplier’s access point — a certified service provider that takes the invoice out of the supplier’s system. Corner three is the buyer’s access point. Corner four is the buyer, receiving the invoice into their accounting or ERP system.
The essential property is that corners one and four never talk to each other directly, and never need to know anything about each other’s software. Each business has a relationship with its own access point only. The two access points, both bound by the same technical rules, handle discovery, transport and delivery between them. Add a new trading partner and there is nothing to configure — if they are on the network, they are reachable.
- Corner 1 — the sender, in their own accounting system and native format
- Corner 2 — the sender’s access point: converts to the Peppol format, validates, addresses and transmits
- Corner 3 — the receiver’s access point: verifies, acknowledges receipt and converts to what the receiver can consume
- Corner 4 — the receiver, booking a structured invoice into their system without re-keying
What an access point actually does
An access point is a provider certified by Peppol to send and receive on the network — you do not connect to Peppol directly, you connect through one. Most e-invoicing vendors, many accounting platforms and some banks either operate one or resell access to one.
On the way out, the access point converts your invoice into the network’s format, validates it against the rules that apply, looks up the recipient’s address in the network directory, and transmits it over the network’s secure transport profile with encryption and a signature. On the way in, it verifies the sender, decrypts, validates, returns an acknowledgement and hands the invoice to you in whatever shape your system expects.
Two features distinguish this from emailing a file. The lookup means addressing is by registered business identifier — a VAT or company number — rather than by an email address someone typed. And the acknowledgement gives you a technical record that the document was delivered and accepted, which is a materially stronger position than hoping a message did not land in a spam folder.
Peppol BIS and the standard underneath
The document format on the network is Peppol BIS Billing, which is a specification built on top of the European standard EN 16931 and expressed in UBL. In plain terms: EN 16931 defines what an invoice means, UBL defines how to write it in XML, and Peppol BIS narrows the options so that everyone on the network makes the same choices.
That narrowing is the point. A standard with many optional fields and permitted variations is a standard that still requires negotiation between trading partners. By fixing a specific profile and enforcing it with validation rules, Peppol makes documents genuinely interchangeable — an invoice that passes validation will be readable by any participant.
Because it is built on EN 16931, a Peppol invoice satisfies the semantic standard that European mandates reference. This is precisely why a country such as Belgium can mandate structured invoicing and point at Peppol as the mechanism, and why other national formats can map to and from it without loss.
Who needs to be on it
Peppol began in European public procurement, and selling to government bodies is still the most common route onto it — many public authorities across the EU accept invoices only in structured form, frequently over Peppol. If you invoice the public sector, you may already be using it through your software without having thought about the name.
Business-to-business mandates are the newer driver. Belgium’s domestic B2B mandate runs on Peppol, and other jurisdictions reference it as an accepted channel. Adoption also extends well beyond Europe — Australia, New Zealand, Singapore, Japan and others have adopted it — which makes it a de facto international network rather than a European one.
For a small business the practical question is rarely "should I join Peppol" in the abstract. It is whether your customers or your national rules require structured invoicing, and if so, whether your existing accounting software already includes access-point connectivity. Increasingly it does, and joining is a matter of registering your business identifier rather than building anything.
Common Mistakes
Thinking Peppol is a government clearance system
It is a transport network, not a tax platform. Peppol delivers documents between businesses; it does not submit them to a tax authority for approval. Poland’s KSeF is a clearance system, and the two work very differently — some countries combine a network with reporting, but Peppol on its own is delivery.
Expecting to connect to the network directly
Participation is through a certified access point. Businesses do not join Peppol as such; they use a provider that has. Budget for a service relationship rather than an integration project.
Assuming any XML invoice will be accepted
Documents are validated against the Peppol BIS profile and rejected if they fail. Exporting some other XML and hoping it passes will not work — the profile is deliberately strict, which is what makes the network interoperable.
Registering an identifier you do not actually use
Recipients are found through the network directory by registered identifier. If the identifier your customers know you by is not the one registered, their invoices will not reach you — and the failure looks like silence rather than an error.
Frequently Asked Questions
Does Peppol cost money?
The network itself charges businesses nothing, but you reach it through an access point provider and that is a commercial service. Pricing ranges from included-in-your-plan for some accounting software to per-document or subscription fees from specialist providers.
Can I use Peppol if my customer is not on it?
Not for that customer — both parties need to be reachable on the network. Many access point providers handle this by falling back to email or a portal for non-participants, so a single workflow covers both, but the Peppol path itself requires the recipient to be registered.
Is Peppol only for invoices?
No. The network carries a range of business documents including orders, order responses, despatch advices and catalogues. Invoicing is simply the most widely adopted use because that is where the mandates apply.
What is the difference between Peppol BIS and EN 16931?
EN 16931 is the European semantic standard defining what an invoice contains and what each field means. Peppol BIS Billing is a specification built on top of it that fixes the syntax and narrows optional choices, so that every document on the network is validated the same way.
Sources & Further Reading
- About OpenPeppol — network, specifications and participants — OpenPeppol
- eInvoicing and the European standard EN 16931 — European Commission
Ready to put this into practice?
Create a professional invoice in your browser — free, no sign-up, no watermark.
Open the Invoice Generator