What is Peppol? A plain-English guide for business owners
Understand Peppol as a delivery network plus a document standard, how the four-corner model routes an invoice, and what it means when you bill through Stripe.
A customer emails you: from next quarter, they can only accept invoices "over Peppol". You send them a perfectly good PDF every month and it has always been fine, so the request lands as a small mystery. What are they actually asking for, and why can't they just take the PDF like everyone else.
Peppol is the answer to both questions, and it is really two things at once: a network that moves invoices between businesses, and a standard for what those invoices look like inside. Neither half makes sense without the other, so start with the network.
A network, not an email attachment
The name comes from Pan-European Public Procurement OnLine, which tells you where it started: governments wanting a single, reliable way to receive supplier invoices instead of a hundred different PDFs and portals. It has since grown well beyond procurement into general B2B invoicing, and it is governed by OpenPeppol, a non-profit association based in Brussels that maintains the rules every participant follows.
The thing that makes Peppol different from emailing a file is how a document gets from you to your customer. Peppol uses a four-corner model. You (corner one) hand your invoice to your access point (corner two), a certified provider connected to the network. Your access point finds the recipient's access point (corner three) and delivers the document there, and that access point passes it to your customer (corner four). You never connect to your customer's systems directly. Each side only ever talks to its own provider, and the two providers handle the exchange. It is the same shape as email — you use your provider, they use theirs — but with strict rules about identity and document format that email never had.
Because delivery is addressed and acknowledged, the sender learns whether the document actually arrived. That is the part a PDF by email can never give you.
A standard for the document itself
The second half is the invoice. A Peppol invoice is not a PDF; it is a structured UBL file — machine-readable XML with named fields for the seller, the buyer, each line item, the VAT breakdown, and the totals. Because the fields are named and predictable, the recipient's accounting system can read the invoice automatically instead of a person retyping it.
That structure follows a European standard, EN 16931, which defines what a compliant electronic invoice must contain. Peppol applies a specific profile on top of it — Peppol BIS Billing 3.0 — which pins down the details for its own network. We untangle how those layers fit in BIS Billing 3.0 vs EN 16931; for now, the takeaway is that "send it over Peppol" implies both a delivery method and a precise document format, and your customer needs both to be satisfied.
Why it exists, and why it is spreading
Two forces drive Peppol adoption. One is efficiency: structured invoices post straight into a buyer's system without manual entry, which removes errors and speeds up payment. The other is tax enforcement. Several EU governments are moving to structured B2B e-invoicing partly to close the VAT gap, and Peppol is the transport many of them have chosen. Belgium's mandate is already live, and France, Germany, Poland, and others are on the way. Our Belgium rundown covers one such case in full.
So even if only one customer is asking today, the direction of travel means more will. Being able to send over Peppol is becoming a standard cost of doing B2B in Europe.
What this means if you bill through Stripe
Here is the practical rub. Stripe issues excellent invoices and holds all the data a structured invoice needs — your legal name and VAT number, the customer's country and tax ID, the line items and totals. What Stripe does not do is turn that into UBL and hand it to a Peppol access point. Those two steps are exactly the network and the standard described above, and they sit outside Stripe's job.
You do not have to re-platform your billing to fill the gap. A thin delivery layer can read the invoices you already finalise in Stripe, generate the compliant UBL, and dispatch it through a certified access point — which is what Peppost does, on prepaid credits with no subscription and a few free sends to try it. The getting-started guide walks through the first connection, and the FAQ answers the questions that usually come next. If your immediate worry is whether a particular customer can receive a Peppol invoice at all, what is a Peppol ID explains how addressing works and how to check.