PEPPOL Explained for Procurement Teams
PEPPOL is the four-corner network behind most of Europe's e-invoicing mandates. Here is how it actually works, why procurement teams should care, and what to look for in an Access Point.
If you procure goods or services in Europe, PEPPOL is no longer an acronym you can ignore. From January 2026 Belgium has required B2B e-invoices over the network, France's phased mandate kicks in through September 2026, and Germany's send obligation begins in 2027. Behind every one of those rollouts sits the same plumbing: PEPPOL.
What PEPPOL actually is
PEPPOL stands for Pan-European Public Procurement On-Line. It started as an EU project in 2008 to make cross-border public procurement work without bilateral integrations, and is now governed by OpenPeppol, a non-profit headquartered in Brussels. It is best understood as three things stacked on top of each other:
- A network — a federated, four-corner exchange where buyers and suppliers connect through certified Access Points rather than point-to-point.
- A set of specifications — most notably PEPPOL BIS Billing 3.0, a UBL 2.1 profile built on the European semantic standard EN 16931.
- A legal and governance framework — Access Points sign the PEPPOL Transport Infrastructure Agreement, which is what makes documents legally interoperable across borders.
The four-corner model in plain language
Most legacy EDI is "two corner": your system talks directly to your supplier's system. PEPPOL adds two intermediaries:
- Corner 1 — the sender (e.g., your supplier's ERP).
- Corner 2 — the sender's Access Point.
- Corner 3 — the receiver's Access Point.
- Corner 4 — the receiver (your procurement or AP system).
Routing happens through the Service Metadata Locator (SML) and Service Metadata Publishers (SMPs), which together act like DNS for business documents: given a participant identifier (typically a VAT number prefixed with a scheme), any Access Point can look up where to deliver a document and which formats the recipient supports.
Why procurement teams should care
For a procurement organisation PEPPOL changes three things that have historically been painful:
- Supplier onboarding — once you can receive on PEPPOL, any supplier on the network can invoice you without a new integration. The "long tail" of small vendors stops being a CSV problem.
- Document scope — PEPPOL is not just invoices. Orders, order responses, despatch advices, catalogues and credit notes are all in scope, which means the procure-to-pay loop can be closed on a single rail.
- Compliance posture — using a PEPPOL BIS-compliant flow is one of the documented ways to meet ViDA's 2030 intra-EU e-invoicing requirement, and the default route for the Belgian, Dutch and Nordic mandates.
Choosing an Access Point
You can technically become an Access Point yourself, but it is rarely worth it. For most procurement platforms the right pattern is to integrate with a certified Access Point provider. Things to check:
- Coverage of the documents you actually exchange (BIS Billing 3.0 is table stakes; Order, Order Response and Despatch Advice are not).
- Support for country-specific extensions — France's PPF/PDP model, Italy's SdI bridge, and Belgium's Hermes fallback all have nuances on top of base PEPPOL.
- How participant identifiers are managed and whether the provider keeps your SMP entries up to date.
- Validation tooling — a good Access Point fails invalid documents before they hit the network, not after.
Rule of thumb: if your supplier base spans more than three EU countries, integrating with PEPPOL once is cheaper than maintaining bilateral EDI feeds, even before the mandates make it compulsory.
What to do this quarter
Even if your country has no domestic B2B mandate yet, you can prepare:
- Register a PEPPOL participant ID through an Access Point.
- Make sure your AP system can ingest UBL 2.1 / PEPPOL BIS Billing 3.0 invoices and credit notes.
- Audit your supplier master data — VAT numbers must be clean, because they are the routing key.
- Pilot with one or two large suppliers before you flip the switch for everyone.
Sources and further reading: peppol.org, PEPPOL BIS Billing 3.0 specification, European Commission — eInvoicing in Belgium.