What is Peppol? How the e-invoicing network actually works

A customer in Belgium tells you they can only accept invoices over Peppol. You look it up, and find a dozen pages explaining the Peppol network, every one of them written by a company that would like to sell you access to it. None of them answers the only question you have, which is whether you actually need to do anything.

So here is the version without the sales pitch. This post covers how a document gets from your accounting system into your customer's, who governs the network, and the two questions the vendor pages tend to blur:

1. Is Peppol genuinely mandatory for your business?
2. Do you need your own Access Point?

On that second one, before we start: almost certainly not.

What is Peppol?

Peppol stands for Pan-European Public Procurement On-Line, which now undersells it on both counts. It began in EU public procurement, it is no longer limited to the public sector, and it is no longer only European.

The most useful thing to understand first is what Peppol is not. It is not a portal, a platform, or software you log into. OpenPeppol, the organization behind it, describes it as "an enabler" whose "network and document specifications integrate global business processes by standardising the way information is structured and exchanged."

In practice it is two things at once:

• A set of specifications. Peppol BIS (Business Interoperability Specifications) defines how a compliant document is structured, so that a system receiving it knows how to read it.
• A network. An agreed way for that document to travel from one business to another, across providers and across borders.

You never open an account with Peppol. You connect through an accredited service provider, and so does the business you are invoicing. When that Belgian customer says they can only accept invoices over Peppol, they mean their provider will accept a structured document delivered through the network, and will not accept a PDF by email.

How the network works: the four-corner model

The architecture has a name, and understanding it answers most of the practical questions at once.

The four corners are:

1. The sender. You.
2. The sender's service provider. You hand your invoice to them.
3. The receiver's service provider. They interoperate with yours.
4. The receiver. Their provider delivers it to them.

Neither of you deals with the other's software.

OpenPeppol puts the significance plainly: the model enables "buyers and suppliers to connect via any Peppol-accredited Service Provider".

Why four corners rather than three

A three-corner network puts both parties on the same provider's platform. That works until your customer uses a different provider, at which point somebody has to change systems or maintain a second connection.

Four corners removes that. Your provider and your customer's provider interoperate by agreement, so you connect once and reach every participant on the network. This is the entire argument for Peppol over bilateral integrations, and it is why the network grew.

How your invoice finds the right destination

Two components handle the routing, and they are worth knowing by name because they explain why the system works without a central hub.

• The Service Metadata Publisher (SMP) holds a participant's details: which documents they can receive and where those documents should be delivered.
• The Service Metadata Locator (SML) is the lookup layer that points a sender's provider to the right SMP.

Both are mandatory specifications in the Peppol eDelivery network. The practical version: your provider looks up your customer, learns what they can accept and where to send it, then delivers. You see none of this.

The five-corner model

Where a country runs continuous transaction controls, a fifth corner joins the picture: the tax authority. The network carries a copy of the document to the authority as well as to the buyer.

This is the direction of travel as EU reporting requirements tighten. The regulatory timeline sits in our guide to digital reporting requirements in the EU rather than here.

Who runs Peppol?

A network this open needs somebody deciding who is allowed to join it, and the answer surprises people who assume Peppol is a government system.

It is not. OpenPeppol is a non-profit international association established under Belgian law, formally OpenPeppol AISBL, based in Brussels and operating in that form since 2012. The wider initiative dates from 2008. It is a membership organization, not an EU institution and not a company.

Beneath it sit Peppol Authorities, which operate at national level, accredit service providers in their jurisdiction and adapt specifications to local requirements. Where a country has none, OpenPeppol "acts as the Peppol Authority in jurisdictions where no Peppol Authority exists".

The authorities are mostly government bodies:

Country	Peppol Authority
France	Directorate General of Public Finances
Germany	KoSIT
Australia	Australian Tax Office
Singapore	IMDA

For you as a business, the practical consequence is this: nobody owns your connection. Accreditation sits with providers, so you can change provider without changing your address on the network.

Peppol IDs, VAT numbers and GLNs

That address is a Peppol ID, and confusing it with a tax number causes a surprising amount of onboarding friction.

A Peppol ID, or participant identifier, is how the network addresses your business. It is not a tax identifier, although it is frequently built from one.

The format is {scheme code}:{identifier}, where the scheme code specifies what kind of identifier follows:

• A German business using its VAT number appears as 9930:DE123456789
• A company identified by its GLN uses 0088:5060012340001

A VAT number, a company registration number or a GLN can each sit inside a Peppol ID under the appropriate scheme, as defined in the Electronic Address Scheme code list maintained by OpenPeppol.

Two things follow, and both are common failure points:

• Giving a customer your VAT number when they asked for your Peppol ID does not answer their question, even though the VAT number may be part of the answer.
• Being VAT registered does not put you on the network. Registration happens through a service provider, who publishes your capabilities so that other participants can find you.

The failure this produces is quiet and confusing. A supplier tells their customer "we're set up for Peppol", the customer's provider looks them up on the network, finds nothing published against that identifier, and the invoice never arrives. Nobody gets an error worth reading. The supplier had registered for VAT and assumed that was the same thing.

Is Peppol actually mandatory for your business?

Here is where vendor pages get vague, so let us be specific. Three different situations get called "Peppol compliance" and only one of them is a legal obligation of the kind people imagine.

Your situation	Is Peppol mandatory?	What actually applies
You invoice public sector buyers in the EU	Frequently yes, and it applies now	B2G e-invoicing is mandatory in many EU countries, and Peppol is often the required route
You invoice businesses	Usually no	National rules require e-invoicing. Peppol is one way to satisfy that, and some countries mandate their own platform instead or as well
A customer has asked for it	No	A commercial conversation, not a legal one. It may still be a good reason to connect, but it is not a compliance deadline

Take a SaaS business selling B2B into France and Germany, with no public sector customers. It has a genuine e-invoicing obligation in both countries and no Peppol obligation in either. Peppol may still be the least painful way to meet those two obligations with one connection, but that is an implementation choice, not the rule it is complying with. Reading it the other way round leads businesses to buy network access while leaving the underlying invoice data non-compliant.

That said, the line is getting harder to see, because Peppol is increasingly being adopted as the national transport layer rather than as an alternative to one. The UK, for example, has named Peppol its "core interoperability network for eInvoicing". Where that happens, complying with the mandate and using Peppol become the same act.

Which mandates apply to you is a separate question with a country-by-country answer. Our guide to e-invoicing covers where it is required, and we have detailed posts on France, Germany and Spain.

Do you need your own Access Point?

Almost certainly not, and this is the question the rest of the internet answers badly because most of the internet on this topic is written by Access Point operators.

You need access to the network. That is not the same as operating an Access Point. There are three routes, and they are not equally likely:

• Your invoicing or accounting software already connects. Either it holds accreditation or it works with a provider that does. For most small and mid-sized businesses this is the answer, and it involves buying nothing.
• You contract a certified service provider directly. Sensible at higher volumes, or where you have requirements your software does not cover.
• You become an accredited Access Point yourself. This means accreditation, an agreement with a Peppol Authority, technical conformance testing and ongoing obligations. It is a product decision for software vendors who intend to serve other businesses, not a compliance step.

If someone is quoting you for an Access Point, the first thing worth checking is whether the invoicing tool you already pay for reaches the network. Frequently it does.

Peppol or a national platform?

For businesses selling into several countries, this is the one genuine decision. Several countries run their own e-invoicing platform, and Peppol is sometimes an alternative to it, sometimes the route into it, and sometimes irrelevant because the national system is compulsory.

The choice usually comes down to how many countries you invoice in.

Your situation	Usually simpler	Why
One country, which runs its own platform	Connect to the national platform	A single integration, and it may be compulsory anyway
Three or more EU countries	Peppol	One connection instead of one integration per country
Selling B2G across borders	Peppol	Frequently the required route for public sector buyers
Non-EU seller invoicing EU customers	Peppol	Reaches participants without establishing locally in each country

Worth stressing: where a national platform is compulsory, Peppol does not remove that obligation. It changes how many integrations you maintain, not whether the rules apply.

Peppol outside Europe

The name has been misleading for years. Peppol Authorities now operate well beyond the EU, including Australia, Japan, Malaysia, New Zealand, Nigeria, Oman, Singapore, Taiwan and the United Arab Emirates.

The pattern repeats in each case. A national body, often the tax authority or a digital government agency, becomes the Peppol Authority. It accredits local service providers and publishes a local specification profile so that national requirements fit inside the international framework.

For a business selling across regions this is the strongest practical argument for the network. A single connection can reach participants in Europe, Asia and Oceania, which no per-country integration strategy achieves without multiplying work.

What Peppol does not do

Worth being blunt about the limits, because most of the confusion around this topic comes from expecting too much of it.

• It does not calculate VAT or decide the tax treatment of a sale. It transports a document you already got right.
• It does not replace your invoicing or accounting system. It is delivery, not creation.
• It is not a government portal, and being reachable on Peppol is not the same as having filed anything with anyone.
• It does not by itself make you compliant with a national mandate. The format, the content and the mandate are separate questions.
• It does not archive your invoices. Retention obligations still apply and still sit with you.

What has to be right before any of this matters is the document itself. Our guide to what a tax invoice must contain covers the requirements that no network will fix for you.

Getting the invoice right first

The hard part of e-invoicing is rarely the transport. It is producing a document that is correct before it is sent: the right tax treatment for the transaction, the right identifiers for both parties, and the right structured fields for the format the recipient expects.

That is the part Quaderno handles:

• Tax determined per transaction, based on what was sold and where the customer is.
• Customer tax numbers validated at the point of sale rather than chased afterwards.
• Invoices produced with the data that structured formats require already in place.

Peppol moves the invoice. Getting the invoice right in the first place is the harder half. Our guide to e-invoicing compliance covers the practices that keep you compliant as mandates roll out across the EU.