What Is Peppol? History, Architecture, and How the Network Works

Where did Peppol come from?

Peppol started life as PEPPOL - the Pan-European Public Procurement OnLine project - funded by the European Commission and running from 2008 to 2012. The goal was ambitious: create a single set of technical specifications that would let any European business send e-invoices and other procurement documents to any public-sector buyer, regardless of which country either party sat in.

Before PEPPOL, cross-border e-procurement was a patchwork. Each member state had its own portal, its own formats, and its own access rules. A supplier in Portugal wanting to invoice a hospital in Norway had to figure out Norway's system from scratch. The project set out to replace that patchwork with standardised protocols, shared infrastructure, and a common governance framework.

By the time the EU funding ended in 2012, the technical building blocks - Access Points, the Service Metadata Publisher (SMP), and the Service Metadata Locator (SML) - were proven in production pilots across multiple countries. The question was what to do with them next.

How did it grow from an EU project into a global network?

On 1 September 2012, the non-profit association OpenPeppol was formally established to take ownership of the specifications, the infrastructure, and the governance rules. Membership was open to both public and private organisations, and the network grew steadily through the 2010s as more European governments mandated Peppol for public-sector invoicing.

In 2019, OpenPeppol dropped the acronym and rebranded simply as "Peppol" - a signal that the network was no longer just about European public procurement. Expansion into Asia-Pacific accelerated: Singapore became the first non-EU Peppol Authority in May 2018, Australia followed shortly after, and Japan joined in September 2021.

The numbers tell the story of adoption. In 2019, roughly 110,000 organisations were registered on the network. By early 2026, that figure had grown to over 2.5 million participants from 111 countries, served by more than 300 certified Access Points operating in 98 countries. Peppol is no longer a European experiment - it is the closest thing the world has to a universal e-invoicing backbone.

How does "connect once, connect to all" work?

Peppol uses a 4-corner model. Each business connects to a single certified Access Point (AP), and that AP handles delivery to every other participant on the network. There is no need to build point-to-point connections with individual trading partners - you send documents to a Peppol identifier and the network routes them automatically.

This is the core difference from traditional EDI, where every new partner means a new integration project. On Peppol, adding a partner is a directory lookup, not a technical build. For a full comparison of 2-corner, 3-corner, 4-corner, and 5-corner architectures, see how e-invoicing networks work.

What are Access Points, SMP, and SML?

An Access Point (AP) is a certified gateway to the Peppol network. APs are operated by commercial service providers or, in some countries, by government agencies. To become an AP, an organisation must pass OpenPeppol's certification process, which tests technical interoperability, security, and operational reliability.

The Service Metadata Publisher (SMP) is the address book for a given AP. It stores records saying "this participant, identified by this Peppol ID, can receive these document types via this AP." When a sending AP needs to deliver an invoice, it first looks up the recipient in the SMP to find out where to send it.

The Service Metadata Locator (SML) is the global directory that ties all the SMPs together. It works like DNS: given a participant identifier, the SML tells the sending AP which SMP to query. Historically the SML used CNAME records, but as of February 2026 NAPTR records are the primary lookup mechanism, and CNAME-based resolution has been deprecated.

What invoice formats does Peppol use?

The core invoice specification is Peppol BIS Billing 3.0, which is built on the UBL 2.1 syntax and fully compliant with the European standard EN 16931. BIS Billing 3.0 defines exactly which UBL fields are required, optional, or forbidden for a Peppol invoice - so there is no ambiguity about what a valid document looks like.

For markets outside Europe, OpenPeppol has developed PINT - the Peppol International invoice specification. PINT uses the same UBL foundation but allows country-specific extensions (called "country specifications") so that non-EU tax rules and business practices can be accommodated without breaking the core standard.

In practice, if you can produce a valid Peppol BIS Billing 3.0 invoice, you can send it to any Peppol participant in Europe. If you trade with partners in Singapore, Australia, or Japan, you may also need to support the relevant PINT country specification - but the underlying structure remains UBL, so the jump is small.

How does Peppol align with EN 16931?

The European standard EN 16931 defines the semantic data model for an electronic invoice - which fields exist, what they mean, and how they relate to each other. It does not prescribe a single syntax; instead, it recognises two: UBL and CII. Any invoice that conforms to one of those syntaxes and satisfies the EN 16931 business rules is considered compliant.

Peppol BIS Billing 3.0 is an implementation of EN 16931 using the UBL syntax. It adds Peppol-specific validation rules (called "Peppol business rules") on top of the EN 16931 requirements, so a valid Peppol invoice is always EN 16931-compliant, but an EN 16931 invoice is not necessarily Peppol-valid.

This alignment matters because EU Directive 2014/55 requires all public-sector buyers in the EU to accept e-invoices that conform to EN 16931. Since Peppol BIS Billing 3.0 satisfies that requirement, sending via Peppol is one of the simplest ways to meet the directive. For more on the standard itself, see EN 16931 explained.

What is the 5-corner CTC model?

The standard 4-corner model was designed for document exchange between trading partners. It does not, by itself, give tax authorities visibility into those transactions. The 5-corner model - formally called DCTCE (Decentralised Continuous Transaction Controls Exchange) - adds the tax authority as a fifth corner.

In a 5-corner setup, the Access Points do double duty: they deliver the invoice to the buyer and report transaction data to the relevant tax authority in real time. This gives governments the Continuous Transaction Controls (CTC) they increasingly demand, without forcing businesses onto a centralised government platform.

France's upcoming e-invoicing system is the highest-profile example. From September 2026, all B2B invoices in France must be exchanged via authorised Partner Dematerialisation Platforms (PDPs) that report to the DGFiP (Direction Générale des Finances Publiques). The architecture is essentially a Peppol-compatible 5-corner model - and several other countries are watching closely to see how it performs at scale.

What does the future hold for Peppol?

On the infrastructure side, the most immediate change is the G3 PKI migration. Peppol's trust model relies on digital certificates issued under its own Public Key Infrastructure. The older G2 certificates were revoked on 1 April 2026, and all Access Points must now operate on the G3 trust chain. This is a behind-the-scenes change for most businesses, but it strengthens the cryptographic foundation of the entire network.

Geographically, Peppol is pushing into regions it barely touched five years ago. Pilots and early adoptions are under way in parts of Africa and Latin America, and the number of certified Access Points continues to climb - from roughly 100 in 2019 to over 300 in 98 countries by 2026.

The bigger strategic question is whether Peppol's 5-corner CTC model becomes the default architecture for government e-invoicing mandates worldwide. If it does, Peppol will evolve from a document-exchange network into a global tax-reporting infrastructure - a much larger role than the EU procurement pilot its founders envisioned in 2008. You can track which countries are adopting Peppol-based mandates on the global overview.