Peppol vs EDI: what supply chain teams need to know

What is Peppol?

Peppol (Pan-European Public Procurement Online) is an international network and set of specifications that let businesses and public authorities exchange structured documents such as invoices, orders and despatch advices through certified Access Points, without needing a direct, custom-built connection to every trading partner. Peppol lets businesses and public authorities exchange structured business documents the same way, regardless of which software or country they use. It started as an EU public procurement project and is now governed by OpenPeppol, with authorities operating it across Europe, Australia, Singapore and beyond.

Peppol vs EDI: the core difference

Traditional EDI runs on private, negotiated agreements: you build a connection (direct or through a VAN) to each partner, agree on a specific EDIFACT or X12 subset, and maintain that mapping for the life of the relationship. Traditional EDI required point-to-point connections between trading partners or through a Value-Added Network, and each new partner is a new project. Peppol flips that model. You connect once to a certified Access Point, and that Access Point can reach every other participant on the network, regardless of who their Access Point provider is.

Mechanically, this runs on what's called the four-corner model: corner 1 is the sender's system, corner 2 is the sender's Access Point, corner 3 is the receiver's Access Point, corner 4 is the receiver's system. Invoice recipients need to be registered with the Service Metadata Publisher server, and when a participant is registered, the SMP server contacts the Service Metadata Locator server, which is centrally operated by Peppol. Think of SML/SMP lookup as doing the job an ISA qualifier or VAN routing table does for you today, except it's a public, queryable directory instead of a bilateral setup sheet. Once the sending Access Point knows where to deliver, the message travels over AS4, a transport protocol that handles signing, encryption and delivery acknowledgement automatically. The document itself is UBL 2.1, formatted to Peppol BIS specifications and built on the EN 16931 semantic standard, playing the same structural role that EDIFACT or X12 segments play in your existing EDI flows.

Where Peppol shows up beyond invoicing

Most people who've heard of Peppol know it only as an e-invoicing network. That's a mistake if you sit on the logistics or supply chain side, because OpenPeppol maintains a full logistics document set that overlaps directly with transactions you already handle in EDI. The specifications cover Advanced Despatch Advice, Advanced Despatch Advice with Receipt Advice, Weight Statement, Transport Execution Plan with Request, Transport Execution Plan Only, and Waybill, which OpenPeppol describes as the digital equivalent of a CMR, issued once per stage of the route.

• Advanced Despatch Advice — functionally close to an EDI 856, notifying the receiver about goods being shipped and delivery timing.
• Waybill — the digital CMR, with one instance per leg of a multi-stage route.
• Transport Execution Plan (Request and Only) — booking and confirming transport, comparable territory to an EDI 204/990 exchange.
• Transportation Status — status updates in the same space as an EDI 214.
• Weight Statement — a proof-of-quantity document used for bulk goods alongside the despatch advice.

If you run a TMS or carrier connectivity layer, this matters regardless of whether you ever touch an invoice. Platforms like Cargoson, alongside Transporeon, Alpega and Descartes, already have to normalize inbound shipment data whether it arrives via EDI, API or a Peppol logistics message. The transport protocol changes; the need to reconcile a despatch advice against a purchase order doesn't.

How the four corners actually move a document

Strip away the acronyms and the flow is straightforward. A seller's ERP generates an invoice and hands it to its Access Point (corner 2). The sender Access Point converts the seller's native format into Peppol BIS Billing 3.0, validates it against schematron rules, signs and encrypts the message, looks up the recipient via SML and SMP, and transmits over AS4. The buyer's Access Point (corner 3) verifies the signature, decrypts and validates the document, sends an acknowledgement back, and forwards it to the buyer's ERP (corner 4) in the format that system expects. Every Peppol participant carries an identifier made of a scheme code and a value, commonly a VAT or company registration number, so the sending Access Point doesn't need to know anything about the buyer's internal systems to find them. That's the practical difference from EDI: you're not negotiating a trading partner agreement before the first document moves, you're querying a directory.

When you need Peppol, when you keep EDI, when you need both

Neither network is going away, and for most mid-to-large companies the honest answer is you'll run both for years. Many organisations successfully run both EDI and Peppol in parallel, and the decision on which to prioritize for a given partner comes down to volume, mandate exposure and how customized the relationship already is.

Belgium's B2B mandate has been in force since January 1, 2026, France's obligation for large and mid-sized companies starts September 1, 2026, and Poland's KSeF mandate is rolling out between February and April 2026. Providers you already know from the EDI side, including SPS Commerce, TrueCommerce and Cleo, now offer Peppol Access Point services alongside their EDI stacks, precisely because their customers need both running at once rather than a rip-and-replace.

FAQ

Is Peppol replacing EDI? No. It solves a different problem, an open discovery network versus a private bilateral agreement, and most companies with existing EDI relationships keep them running alongside new Peppol connections.

Do I need a Peppol Access Point if none of my customers require it? No. You only need one when a mandate country requires it or a specific partner asks for it.

Is Peppol only for invoices? No. Peppol Logistics covers despatch advices, waybills, weight statements and transport status, territory that overlaps with EDI 856, 214 and 204.

What format does Peppol use? UBL 2.1 under Peppol BIS Billing 3.0, built on the EN 16931 semantic standard.

Which countries mandate Peppol right now? Belgium's B2B mandate is live, France and Poland follow through 2026, and Singapore's InvoiceNow runs on Peppol standards under IMDA governance.