Peppol for Beginners:
What It Is and Why It Matters (No Jargon)

Peppol Is Not an Invoice Format

Let's clear the biggest misconception first, because almost every article about Peppol buries this five paragraphs deep. An invoice format is a file structure — a template that dictates where the date goes, where the line items sit, what the VAT field is called. PDF is a format. UBL XML is a format. Factur-X is a format.

Peppol is none of those. Peppol is three things at once, and understanding them separately is what makes the whole picture click:

First, Peppol is an organization. OpenPeppol is a non-profit international association, registered under Belgian law, with members from both the public and private sectors. It was launched in 2012 to take over a European Commission project (the original PEPPOL acronym stood for Pan-European Public Procurement OnLine, though the acronym has since been dropped). OpenPeppol writes the rulebook — it defines the technical specifications, enforces the governance model, and accredits the service providers who connect you to the network. By March 2025, over 1.4 million organizations across 98 countries were registered Peppol participants.

Second, Peppol is a set of document specifications. The most important one is Peppol BIS Billing 3.0, which defines exactly what fields an electronic invoice must contain, in what format, with what validation rules. BIS 3.0 is a CIUS — a Core Invoice Usage Specification — of the European e-invoicing standard EN 16931, published in 2017 by the European Committee for Standardization (CEN/TC 434). Practically speaking, BIS 3.0 says: "Here is the structure. Dates go here as YYYY-MM-DD. Currency codes follow ISO 4217. VAT categories use these predefined codes. Every invoice that enters the Peppol network must pass these validation checks before it's sent anywhere." The actual file is UBL 2.1 XML — Universal Business Language, a globally recognized business document format.

Third — and this is the part that matters most — Peppol is a transport network. It doesn't store your invoices. It doesn't process payments. It moves structured documents from one business system to another through a standardized delivery infrastructure. The technical transport protocol is AS4, secured by digital signatures and encryption under the eIDAS Regulation (EU Regulation No. 910/2014). Think of Peppol as the postal service for electronic invoices — not the letter you wrote, not the post office building, but the routing system that gets your envelope from your hand to the recipient's mailbox, with delivery confirmation built in.

How the Network Delivers: The Four-Corner Model, Explained With a Shipping Analogy

Now that we've established Peppol is a transport network, the next question is: how does it actually route a document from A to B? The architecture is called the four-corner model, and it's simpler than most diagrams make it look.

Imagine you're shipping a package internationally. You don't drive it to the recipient's house yourself. You drop it at your local courier depot. That depot handles customs paperwork, weighs the package, labels it for the destination country, and hands it to the international shipping network. At the other end, a depot in the recipient's country receives it, clears local customs, and delivers it to their door. You never interact with the recipient's courier. The recipient never interacts with yours. The two depots talk to each other through a shared routing system.

Peppol works exactly like this:

The key detail: Corners 1 and 4 never talk directly. The sender doesn't need to know which Access Point the recipient uses. The recipient doesn't need to know the sender's. Each party only deals with their own provider, and the Peppol network handles the routing in between. Switch your ERP, change your Access Point, move to a different country — the rest of the chain keeps working.

How Access Points Find Each Other — SMP and SML

If the sender's Access Point has never heard of the recipient, how does it know where to send the invoice? This is where two layers of internet directory infrastructure come in — and you don't need to understand the technical details to get the intuition.

Every organization on the Peppol network has a unique Peppol ID — think of it as a phone number. When a business registers with Peppol, its details are stored in a Service Metadata Publisher (SMP) — a decentralized registry maintained by its Access Point. The SMP record says: "This Peppol ID can receive invoices in BIS 3.0 format. Route to this Access Point endpoint."

Above the SMPs sits the Service Metadata Locator (SML) — the one truly centralized component in the entire Peppol network, operated by OpenPeppol. The SML is a DNS-based lookup system. When the sender's Access Point (Corner 2) needs to deliver an invoice to a recipient, it queries the SML with the recipient's Peppol ID. The SML points it to the correct SMP. The SMP serves the routing details. Delivery happens. All of this is invisible to the human users at both ends — it's machine-to-machine, happening in milliseconds.

What's Inside a Peppol Invoice — BIS Billing 3.0 and EN 16931

If Peppol is the postal service, what's inside the envelope? An XML file structured according to Peppol BIS Billing 3.0, which is itself a profile of EN 16931 — the European standard for electronic invoicing.

This hierarchy is worth understanding because it explains why a Peppol invoice is fundamentally different from a PDF:

EN 16931 sits at the top. Published in 2017 under Directive 2014/55/EU, it defines a semantic data model for what an electronic invoice must contain — supplier and buyer identification, VAT information, invoice totals, line item breakdowns, payment terms. It's a conceptual model, not a file format. It says "an invoice must have these 160+ data elements" without specifying how they should be arranged in a file.

Peppol BIS Billing 3.0 is a CIUS (Core Invoice Usage Specification) of EN 16931. It takes the full EN 16931 model and applies concrete business rules: which fields are mandatory vs. optional, exactly which code lists to use for VAT categories, how to format dates, what validation checks to run. BIS 3.0 uses UBL 2.1 as its syntax — the actual XML tags and structure. Every valid Peppol BIS 3.0 invoice is also a valid EN 16931 invoice.

Here's what this means in practice, summarized in one table:

The gap between these two columns is not a minor efficiency difference. It's the difference between an invoice that a human must interpret and an invoice that a system can process without looking at it. Belgium's mandate went live on January 1, 2026, requiring all VAT-registered businesses to exchange B2B invoices via Peppol BIS 3.0 — over one million businesses. That's not a pilot. That's an operational network at national scale.

Peppol vs. National Systems — Layers, Not Rivals

Another source of confusion, especially for businesses operating in multiple EU countries, is how Peppol relates to national e-invoicing systems — France's Chorus Pro, Germany's XRechnung, Italy's FatturaPA/SdI. The common misconception is that these are competing standards and you have to pick one. They're not. They operate at different layers.

The pattern is consistent: Peppol provides the transport layer and a common document specification. Individual countries layer their own requirements on top — extra mandatory fields, different code lists, specific validation rules — while staying within the EN 16931 framework. If your business transacts only within Germany B2B, you'll primarily deal with XRechnung. If you invoice a French government agency, you'll touch Chorus Pro. If you invoice across borders — a Dutch company billing a German customer, a Swedish supplier billing a Belgian buyer — Peppol is the common denominator that makes the connection without requiring you to register in every country's portal.

For a detailed country-by-country timeline, see our Europe e-invoicing mandate timeline. For Germany-specific requirements, read the German e-invoicing guide, and for France, the France e-invoicing 2026 guide.

Do You Actually Need Peppol? A Decision Framework

The practical question every business owner arrives at: "Do I need to do anything about this?" The answer depends on who you invoice — not where you're located, not how big you are, not what software you use.

Here is a decision matrix based on your transaction patterns:

One more nuance: even if you are legally required to use Peppol in one direction, that doesn't mean every invoice you receive will arrive via Peppol. Cross-border suppliers from outside the EU, small businesses still transitioning, and B2C invoices will continue arriving as PDFs for years. That's not a failure of the system — it's the reality of a mandate that phases in by country, by business size, and by transaction type.

What It Takes to Connect — Access Points, Peppol IDs, and Costs

If the decision framework points to "yes, you need Peppol," the practical next step is straightforward: you connect through a Peppol-certified Access Point provider.

An Access Point is a certified service provider that acts as your gateway to the Peppol network. It handles format conversion (your system's native format → Peppol BIS 3.0 UBL XML), validation, encryption, routing via the SML/SMP directory, and delivery confirmation. OpenPeppol maintains a public directory of all certified Access Points worldwide. The terminology has shifted in recent years — some providers now prefer "Service Provider" over "Access Point," but they mean the same thing in practice.

A Peppol ID is your unique identifier on the network, assigned by your Access Point. It's typically based on your business registration number or VAT ID with a scheme prefix — for example, a Dutch business might have a Peppol ID using scheme 0106 (KVK number) or 9944 (VAT number). Your Peppol ID is what other businesses use to address invoices to you, similar to how an email address routes messages.

Cost models vary widely:

Well-known Access Point providers include Storecove (Dutch, ISO 27001 certified, REST API with 30+ country coverage), Pagero (now part of Thomson Reuters, strong multi-country compliance), Tradeshift, Unifiedpost (owner of Banqup), Tickstar (accredited in Europe, Australia/New Zealand, and Singapore), and B2Brouter. Most offer integration with major accounting software and ERPs — DATEV, SAP, Microsoft Dynamics, Exact, and others.

The minimum viable setup for sending Peppol invoices: register with an Access Point → get your Peppol ID → connect your invoicing software (or use the provider's web interface) → validate your first invoice format → send. Most providers offer test environments so you can verify everything works before going live.

The PDF Reality — Why You Still Need to Read Unstructured Invoices

Here's the part most Peppol explainers skip: even if every European country adopted mandatory Peppol tomorrow, a significant percentage of the invoices hitting your accounts payable inbox would still be PDFs.

Belgium's January 2026 mandate applies to domestic B2B transactions between Belgian VAT-registered businesses. It does not apply to invoices from a US supplier. It does not apply to a German SME that falls below the €800,000 turnover threshold until 2028. It does not apply to B2C transactions at all. The result, as businesses in Italy discovered after their 2019 mandate: compliance means the tax authority gets the data, but it doesn't mean your AP team stops receiving PDFs from the world outside the mandate's scope.

This is not a temporary gap. It's a structural feature of a global economy where mandates are national but supply chains are international. The "last mile" of e-invoicing — the point where every incoming document is structured, machine-readable, and auto-posted to your ERP — will remain incomplete for years. Even when ViDA's cross-border mandate arrives in 2030, non-EU suppliers, micro-business exemptions, and legacy systems will keep PDFs flowing.

The practical implication for AP teams is that the Peppol mandate solves one problem (government tax reporting) while creating a parallel processing challenge: you now have two types of invoices arriving through two different channels, and they all need to end up in the same accounting system with the same data quality. An invoice that arrives as Peppol XML imports automatically. An invoice that arrives as a PDF requires extraction — reading the supplier name, invoice number, line items, VAT breakdown, and totals — before it can join the same dataset.

Tools like ImageToTable.ai bridge this gap: upload a PDF invoice, define the columns you need extracted (Invoice Number, Supplier, Net Amount, VAT, Total), and get structured data that matches the schema of what's arriving via Peppol — without manual entry. It doesn't replace a Peppol Access Point. It handles what the Access Point can't: the world of unstructured documents that no mandate can fully eliminate. One workflow. Two input types. Same output.

Frequently Asked Questions

Is Peppol the same as UBL?

No. UBL (Universal Business Language) is an XML schema — a document format. Peppol uses UBL 2.1 as the syntax for BIS Billing 3.0 invoices, but Peppol itself is the network and governance framework. You can create a UBL invoice without ever touching Peppol. You cannot send a Peppol invoice without it being UBL (or CII in some cases).

Can I just send a PDF through Peppol?

No. Peppol transports structured XML documents. A PDF is not a structured e-invoice — it doesn't have tagged fields that a receiving system can parse automatically. You can attach a PDF as a supplementary file alongside a Peppol XML invoice (for human readability), but the PDF itself is not the invoice for compliance purposes. The structured XML is what satisfies the legal requirement.

Is Peppol free to use?

The Peppol network itself has no usage fee. However, you need an Access Point to connect, and Access Point providers are commercial entities that charge for their services. Some offer free tiers (receive-only, or a small number of sends per month). Competitive paid plans range from a few cents per invoice to monthly subscriptions. You'll also need invoicing software that can generate UBL XML — many accounting platforms already include this.

How do I register on Peppol?

You don't register with Peppol directly. You register through a certified Access Point provider, who assigns your Peppol ID and registers you in the SMP directory. This is similar to getting an email address — you don't register with "the email system," you sign up with a provider (Gmail, Outlook) who gives you an address that works across the entire email network.

I'm a freelancer with 5 invoices a month. Do I need Peppol?

It depends entirely on who you invoice, not how many. If your clients are all domestic B2B in a country without a mandate, not yet. If you invoice a Belgian company, yes — Belgium's mandate applies regardless of your size as the issuer. If you invoice EU government entities, yes. The cost of entry is low enough (a few euros per invoice via pay-per-use Access Points) that complying with a single customer's requirement doesn't require a major investment.

Can I receive Peppol invoices without sending them?

Yes. You can register with an Access Point for receive-only, get a Peppol ID, and have all incoming Peppol invoices delivered to your system without ever sending one yourself. This is common for businesses whose customers are subject to mandates while they themselves are not obligated to issue e-invoices.

When do I need to be ready by?

Check your customer's country mandate. The European timeline for 2026–2027 has multiple concurrent deadlines: Belgium (already active), Germany (receiving since January 2025, sending phased from 2027 for large businesses, 2028 for all), France (phased from September 2026 to September 2027), and Poland (July 2026). See our full mandate timeline for country-by-country dates and legal citations.