What is Electronic Invoicing Over The Peppol Network?
Electronic invoicing over the Peppol network is the structured, machine-readable exchange of invoices between businesses (and between businesses and governments) through a federation of certified Access Points. Instead of emailing PDFs or maintaining bespoke EDI links, you connect once to a Peppol-certified provider and reach every other Peppol participant — across more than 30 jurisdictions — using one open standard.
1. What the Peppol network actually is
Peppol — Pan-European Public Procurement On-Line — is an open, standards-based document exchange framework now governed globally by OpenPeppol AISBL. It was originally created to harmonize cross-border procurement in Europe, and is today used in production by tax authorities, governments, large enterprises, and SMEs across Europe, the Middle East, Asia-Pacific, and beyond.
Peppol is not a single piece of software. It is a published rulebook plus a set of certified service providers. Anyone — buyer, supplier, government — can join the network by registering through one of those certified providers. From that moment on, that participant can receive Peppol documents from any other participant in the network.
2. The four-corner model in plain terms
Every Peppol invoice flows through four roles, often called the four corners:
- Corner 1 — Sender. The supplier's ERP, billing, or accounting system that generates the invoice data.
- Corner 2 — Sending Access Point (AP). A certified provider that receives the invoice from Corner 1, validates it, discovers where to send it, and transmits it.
- Corner 3 — Receiving Access Point. A certified provider on the buyer's side that accepts the AS4 message, verifies it, and hands it to the buyer's system.
- Corner 4 — Receiver. The buyer's accounts-payable, ERP, or finance platform.
The advantage of this model is reach. Corners 1 and 4 only ever talk to their own AP; the APs handle interoperability with every other AP on the network. This is why Peppol scales so well compared to point-to-point EDI.
3. UBL 2.1 and Peppol BIS Billing 3.0
The invoice format used on Peppol is built on UBL 2.1, the OASIS Universal Business Language standard. On top of UBL, Peppol publishes Peppol BIS Billing 3.0, which is a specific business-rule profile that aligns with the European EN 16931 e-invoicing standard.
For specific jurisdictions, additional PINT profiles and national CIUS packs apply on top of the baseline. Examples include PINT for Oman, Australia, New Zealand, Japan, Malaysia, and Singapore, and national CIUS packs such as XRechnung in Germany. Validation of all of these is layered: structural XML, business rules, code lists, baseline Schematron, and finally jurisdictional Schematron. A modern global e-invoicing platform applies all of these automatically.
4. SMP and SML discovery
Before a sending AP can deliver an invoice, it has to find out where the receiver lives on the network. This is what the Service Metadata Publisher (SMP) and Service Metadata Locator (SML) do.
The SML is a single global DNS-based registry that, given a participant identifier (such as 9959:xxxxxxxxx), points to the SMP that hosts that participant's metadata. The SMP, in turn, lists every document type and process the participant can receive, plus the AS4 endpoint URL and the receiver's certificate. Discovery is real-time and cryptographically anchored.
5. AS4 transport — what actually moves between Access Points
Peppol uses the AS4 messaging protocol for delivery between Access Points. AS4 is built on Web Services and ebMS 3.0, and provides authenticated, encrypted, signed, and reliably-acknowledged message exchange. Every successful send produces a non-repudiable receipt that both APs retain.
This is what makes Peppol auditable. Tax authorities, internal audit, and finance teams can reconstruct exactly what was sent, by whom, to whom, when, and with which receipt — using cryptographic evidence rather than email logs.
6. Why electronic invoicing over Peppol is replacing PDF and EDI
Electronic invoicing over Peppol is fundamentally different from emailing a PDF. A PDF is a picture of an invoice for humans; a Peppol invoice is structured data for machines. That difference is what enables straight-through processing, real-time validation, working-capital optimization, and tax-authority reporting in jurisdictions with continuous transaction controls.
Compared with traditional EDI, Peppol replaces dozens of bilateral connections with a single connection to one certified provider. That single connection then reaches every participant on the network — current and future. For organizations with global operations, this is the practical foundation of multi-country e-invoicing strategy. For real examples of how organizations are adopting it, see our customer case studies or the Peppol API integration guide.
7. Country-specific compliance — Oman, the EU, and beyond
Peppol is increasingly the rail used by national tax authorities to operate continuous transaction controls. Oman's Fawtara CTC programme, for example, uses Peppol for invoice transport and a parallel Tax Data Document (TDD) submission to the Oman Tax Authority. Similar patterns are emerging across Europe under the VAT in the Digital Age (ViDA) initiative.
The implication is strategic: choosing a Peppol-aligned platform now positions your organization to satisfy current and upcoming mandates with minimal additional integration work.
8. Getting started in practice
Most organizations follow a three-step adoption path: register a Peppol participant ID with a certified provider, integrate the provider's API to your ERP or billing system, then enable jurisdictions one at a time as you onboard buyers and suppliers. With a modern provider, the sender side can be live in days, with multi-country expansion sequenced over weeks rather than quarters.
Frequently Asked Questions
What is the Peppol network?
Peppol is an open, standards-based network governed by OpenPeppol AISBL that lets organizations exchange structured electronic documents — most commonly invoices and credit notes — through certified Access Points using a four-corner model and AS4 transport.
How does electronic invoicing over Peppol work in practice?
The sender's accounting system creates a UBL 2.1 invoice, the sender's Peppol Access Point validates it and looks up the receiver in the SMP, then transmits the document over AS4 to the receiver's Access Point, which delivers it into the buyer's system. All four roles together form the four-corner model.
What is the difference between Peppol and DBNAlliance?
Peppol is the global open framework rooted in Europe and adopted across 30+ jurisdictions, while DBNAlliance is the U.S. B2B e-invoicing exchange framework. Both use open-network design principles, and modern providers bridge the two.
Do I need a Peppol participant ID?
Yes. To send or receive over Peppol, your organization must be registered as a Peppol participant — typically using your VAT or tax registration number — through a certified Access Point provider. Your Access Point publishes your participant metadata to the SMP so other senders can discover you.