Peppol e-invoicing: everything you actually need to know

What Peppol is — and why it exists

Peppol stands for Pan-European Public Procurement On-Line. The name is a relic of its origins as a European Union initiative to simplify government procurement, but today it functions as a much broader standard: an international framework for structured electronic document exchange between any businesses that want to participate.

The problem it solves is a real one. Before Peppol, a business that wanted to exchange invoices electronically with ten different trading partners often needed ten different EDI connections, each with its own format requirements, its own protocols, and its own maintenance burden. Cross-border trade made this worse — different countries had different standards, different VAT rules, different compliance requirements. The overhead of managing all of it was significant enough that many businesses simply didn't bother, and continued sending PDF invoices by email instead.

Peppol replaced that with a single network. Connect once, via a certified Access Point, and you can exchange compliant documents with any other organisation that's also connected — regardless of their location, their systems, or their country of operation.

How the network works: the four-corner model

The architecture that makes Peppol work is called the four-corner model. It sounds more complicated than it is.

In plain terms: the sender creates their invoice in whatever format their system uses. Their Access Point converts it into Peppol's standardised format and transmits it across the network. The receiver's Access Point picks it up and converts it back into the format the receiver's system expects. Neither party needs to know or care about what happened in the middle.

The key implication of this model is that the sender doesn't need a direct connection to every receiver. They connect once, to their own Access Point, and that single connection gives them the ability to reach any other Peppol participant anywhere in the network. New trading partner? No new EDI connection required. The network handles the routing.

Peppol IDs: how the network knows where to send things

For the routing to work, every organisation on the Peppol network has a unique identifier — a Peppol ID. This is essentially the network address that documents are sent to, and it's based on the international standard ISO/IEC 6523.

A Peppol ID has two components: an International Code Designator (ICD), which identifies the registration scheme used, and an Organisation Identifier, which is the specific code for that organisation under that scheme. In the UK, most Peppol IDs are based on company registration numbers.

When a document is sent over the Peppol network, the sender's Access Point uses the receiver's Peppol ID to look up their Access Point in the Service Metadata Locator (SML) — a central directory — and route the document accordingly. You don't need to know which Access Point your trading partner uses. The network figures that out automatically.

What documents Peppol supports

Peppol started with invoicing and has expanded significantly. The document types are defined by Peppol BIS (Business Interoperability Specifications) and use the UBL (Universal Business Language) XML format as their standard structure.

For most businesses getting started with Peppol, the invoice is the immediate priority — either because a public sector customer requires it or because a mandate in their trading territory demands it. The order and despatch advice flows tend to follow once the invoicing layer is working.

The benefits — and what they actually mean in practice

The headline benefits of Peppol are well-documented. Here's what they translate to in operational terms:

What a Peppol Access Point actually does

You can't connect to the Peppol network directly. You connect through a certified Access Point (AP) — a service provider that has been authorised by a Peppol Authority to operate on the network. Your Access Point acts as your gateway: sending documents on your behalf, receiving documents addressed to you, and handling all the format conversion and validation in between.

What to expect from a good Access Point:

• Document translation — converting your invoice data from your ERP or finance system into valid UBL format before sending, and converting incoming documents back into something your system can ingest
• BIS validation — checking that every document complies with the relevant Peppol BIS specification before it leaves your side of the network
• Secure transmission — all Peppol traffic is encrypted in transit; your Access Point handles the TLS and digital signature requirements
• Peppol ID registration — getting your organisation registered in the Service Metadata Publisher (SMP) so other participants can find and route documents to you
• Status and acknowledgement — Message Level Responses confirm whether your documents were received and validated, or flag what went wrong if they weren't

Getting connected: what the process actually looks like

For most businesses, getting Peppol-enabled involves four steps:

1. Choose a certified Access Point provider. The official Peppol directory lists all certified APs. Choose one that connects to your existing finance or ERP system — the integration between AP and system matters as much as the AP itself.
2. Get your Peppol ID registered. Your Access Point will register you in the SMP with your organisation identifier. In the UK this is typically based on your company registration number or VAT number.
3. Connect your finance or ERP system. Configure the integration so invoices are pulled from your system and submitted automatically, and incoming documents are pushed back in. This is where Supply Lens sits — handling the connection between your operational systems and the Peppol network.
4. Test and validate. Send test documents through the network and confirm they arrive correctly and generate the right acknowledgements. Most mandates require a formal testing phase before going live with production traffic.

The timeline for this process varies from a few days for a business with a straightforward ERP integration to several weeks for complex multi-entity setups. The biggest delays usually come from data preparation — ensuring your invoice data contains all the mandatory fields the BIS specification requires — rather than from the technical connection itself.

Quick summary: the ten things worth knowing about Peppol

• Peppol is a network, not a software product. You access it through a certified Access Point provider.
• The four-corner model means one connection reaches all Peppol participants, globally.
• Peppol IDs are unique network addresses, based on ISO/IEC 6523, used to route documents to the right recipient.
• BIS Billing 3.0 (invoice and credit note) is the core document type. Orders, despatch advice, and catalogues are also supported.
• UBL is the XML format standard. Your Access Point should handle format conversion — you shouldn't need to build UBL files yourself.
• Documents are validated before transmission. This protects against compliance failures at the point of submission, not after the fact.
• E-invoicing mandates across the EU are expanding. Businesses trading internationally should treat Peppol readiness as a near-term requirement, not a long-term project.
• UK businesses supplying public sector buyers in Peppol-enabled countries already need this.
• An Access Point alone isn't enough — you need the integration between AP and your ERP or finance system to make it genuinely automated.
• The setup timeline is shorter than most businesses expect. Data preparation, not technical connection, is usually the longest stage.