The Peppol Network Explained: E-Invoicing for E-Commerce Sellers

What Is the Peppol Network?

Peppol stands for Pan-European Public Procurement On-Line. Despite the name, it is no longer limited to Europe or to public procurement: it is an international network that lets businesses and government bodies exchange structured electronic documents — above all e-invoices — in a single, agreed standard. Think of it as a universal postal system for business documents, where every participant speaks the same language and every message is delivered securely to the right address.

The Peppol network meaning is best understood by contrast with email. If you email a PDF invoice, your customer receives an image of a document that a human (or fragile OCR) still has to read and re-key into their accounting system. With Peppol, you send a structured data file that the receiving system can read and book automatically — no typing, no scanning, no manual matching.

Peppol is governed by OpenPeppol, a non-profit association, and is overseen in each country by a national authority (in many EU countries the same body that runs the e-invoicing rules for government suppliers). Because the standards are open and the same everywhere, an invoice you create in the Netherlands can be delivered to a buyer in Belgium, Germany, or beyond without either side building a custom integration.

For e-commerce and marketplace sellers, Peppol matters most when you sell B2B or to the public sector. Many governments now mandate e-invoicing through Peppol for their suppliers, and a growing number of large retailers and wholesalers expect it too. If you only sell to consumers, you may not need Peppol today — but the direction of travel across the EU is clearly towards structured e-invoicing for B2B.

The 4-Corner Model: How Peppol Delivers Documents

The heart of the Peppol network is the 4-corner model. It describes the four parties involved in delivering a single document, and understanding it removes most of the confusion around how Peppol actually works:

• Corner 1 — the sender: you, the seller, who creates the invoice in your invoicing software.
• Corner 2 — the sender's access point: a certified provider that puts your invoice onto the Peppol network.
• Corner 3 — the receiver's access point: the certified provider used by your customer.
• Corner 4 — the receiver: your customer, who receives the invoice directly into their accounting or ERP system.

The clever part is that corners 1 and 4 never have to talk to each other directly. You only ever connect to your own access point (corner 2). Your access point handles the secure transport to your customer's access point (corner 3), which delivers it to them (corner 4). It is exactly like sending a letter: you hand it to your post office, and the recipient's post office delivers it — you do not need to know how the two postal services route the mail between them.

This architecture is why Peppol scales so well. Once you are connected to one access point, you can reach every other participant on the network. You do not need a separate connection or agreement for each customer — a single link to your provider opens the door to the entire Peppol directory of organisations.

Access Points: Your On-Ramp to the Network

An access point is a certified service provider that connects you to the Peppol network. It is the only part of the infrastructure you ever interact with, and the good news is that you almost never run one yourself. Instead, your invoicing software or service provider is the access point on your behalf.

Access points are certified by OpenPeppol and must meet strict requirements: they speak the standard transport protocol (Peppol uses a secure protocol called AS4), they validate documents against the agreed formats, and they handle delivery, acknowledgements, and error handling. This certification is what guarantees that an invoice sent from one provider will be accepted by any other provider on the network.

For a typical online seller, the practical reality is simple: you create an invoice in your software exactly as you do today, and the software — acting as, or connected to, an access point — handles the conversion to the correct Peppol format and the secure delivery. You do not configure servers, manage certificates, or learn the AS4 protocol.

When choosing how to connect, what matters is that your invoicing platform is connected to a certified access point, supports the current Peppol BIS Billing 3.0 specification, and can both send and receive documents. Receiving matters increasingly: suppliers may start sending you purchase orders or invoices via Peppol, and you want them to arrive cleanly rather than bounce.

What Is a Peppol ID?

Every participant on the network has a Peppol ID — formally a participant identifier. This is the address that tells the network exactly which organisation a document should be routed to, much like a phone number or a postal address for electronic invoices.

A Peppol ID is built from two parts: a scheme (which identification system is being used) and the identifier itself. The scheme is usually an official registration system — for example a national company number, a Chamber of Commerce number, or a VAT identification number. So a Dutch business might be identified by its KvK number, while another country's participant might use its VAT number under the relevant scheme code.

When you send an invoice, your access point looks up the recipient's Peppol ID in the Peppol directory (the Service Metadata Locator and publisher infrastructure) to find which access point serves them and which documents they accept. This is also how a Peppol check works: before sending, you can verify that a customer is actually registered on the network and capable of receiving the document type you want to send.

You generally obtain and register your own Peppol ID through your access point or invoicing provider when you onboard. Once registered, your ID is published in the directory so other participants can find and send to you.

BIS Billing 3.0 and the EN 16931 Standard

Routing a document is only half the story — both sides also have to agree on what the document looks like. That is where EN 16931 and Peppol BIS Billing 3.0 come in.

EN 16931 is the European standard that defines the semantic model of an electronic invoice: which fields must be present (supplier and buyer details, VAT amounts, line items, totals), what they mean, and the business rules they must satisfy. It is the common backbone that makes cross-border e-invoicing possible. National e-invoicing rules across the EU are built on top of EN 16931.

Peppol BIS Billing 3.0 is Peppol's implementation of that standard — a Business Interoperability Specification that turns the abstract model into a concrete, exchangeable file. In practice this file is UBL XML (Universal Business Language), the same structured invoice format used widely across European e-invoicing. If you have already worked with UBL invoices, a Peppol invoice will feel familiar — it is UBL constrained and validated to the Peppol rules.

The benefit of this layering is interoperability: because everyone follows the same EN 16931 semantics and BIS Billing 3.0 structure, an invoice produced by one system can be understood and booked by any other, regardless of country or software. The cost is precision — a BIS Billing 3.0 file must pass strict validation, so a single missing VAT field or malformed identifier will be rejected. This is why validating your file before sending is essential, and why good invoicing software does it for you automatically. You can learn more about the underlying format in our UBL invoice format guide.

Why Peppol Matters for Marketplace and Webshop Sellers

Peppol can sound like something only large enterprises deal with, but it is increasingly relevant to ordinary online sellers — especially as B2B and public-sector e-invoicing mandates expand across the EU.

• Selling to government or public bodies: Many EU governments require their suppliers to send e-invoices via Peppol. If you win a public-sector customer, a PDF will not be accepted — you need a structured Peppol invoice.
• B2B and wholesale customers: Larger retailers and distributors often want invoices delivered straight into their ERP via Peppol, and may make it a condition of doing business.
• Faster payment and fewer errors: Because a Peppol invoice is booked automatically, there is no re-keying, fewer disputes, and typically faster payment than a PDF that sits in someone's inbox.
• Future-proofing: With the EU's wider push towards structured e-invoicing and digital reporting, building the habit now means you are ready as more requirements arrive.

Crucially, none of this requires you to change how you actually run your shop. The order still comes in from your marketplace or webshop; the difference is purely in how the resulting invoice is delivered. With the right software, choosing "send via Peppol" is no harder than choosing "send as PDF". And for the VAT logic behind those invoices — destination rates, reverse charge, OSS — the same engine that powers your cross-border VAT compliance applies whether the invoice goes out as PDF or as a Peppol document.

How to Start Sending Peppol E-Invoices

Getting onto the Peppol network is far simpler than the terminology suggests. You do not build infrastructure; you connect through a provider and start sending. The essentials are: use software connected to a certified access point, register your own Peppol ID, confirm your customer's ID, and validate every document before it goes out.

The most common mistakes are avoidable. Sending a PDF when the customer expects a structured Peppol document means your invoice simply will not be accepted. Skipping the directory lookup means a document can fail to route. And ignoring validation means a missing VAT or identifier field gets your file rejected at the access point. Each of these is exactly the kind of repetitive, rules-based work that software should handle for you — not something to manage in spreadsheets.

If you receive a paper or PDF invoice from a supplier that you need to turn into structured data, our PDF to UBL conversion guide walks through how that works, and the PDF to UBL tool does the conversion in seconds. Before sending any structured invoice, run it through a UBL validator so you know it will pass the Peppol checks.

Send Compliant Peppol Invoices Automatically with Winkel Factuur

Doing structured e-invoicing by hand — formatting UBL, looking up Peppol IDs, validating against EN 16931 — is exactly the kind of work that should be invisible. Winkel Factuur is built for marketplace and webshop sellers who need correct, compliant invoices on every channel without becoming e-invoicing specialists:

• Invoice automation: Orders from bol.com, Amazon, Shopify, and WooCommerce are turned into invoices automatically, with structured formats including UBL ready for electronic delivery.
• Branded multi-marketplace invoices: Every document carries your own branding, whether it goes out as a PDF or as a structured e-invoice.
• Correct VAT and VIES logic: Destination VAT rates, reverse charge wording, and VAT number validation against VIES are applied automatically, so the data inside every Peppol invoice is right.
• Review journeys, buy-box and stock alerts: Automated review requests, buy-box loss monitoring, and stock alerts help you grow while compliance runs in the background.
• Profit & VAT dashboard: See your margins and VAT position across every channel in one place.
• Accounting integrations: All invoice and VAT data flows straight into Exact Online, AFAS, Twinfield, and Snelstart — no re-entry.

Instead of reading Peppol specifications, you let the platform create, validate, and deliver compliant invoices while you keep selling.