Your ERP can generate a PDF invoice. It might even produce a Factur-X or ZUGFeRD file. But can it send that invoice directly to a Norwegian supplier, a Belgian contracting authority, and an Italian administration, without anyone touching an email or web portal?
That’s exactly what PEPPOL enables. And in 2026, this is no longer a gadget for multinationals: it’s infrastructure that most European countries are integrating into their e-invoicing obligations.
This guide explains what PEPPOL is, why it’s becoming essential, which ERPs are already compatible, and how to prepare your system in three steps.
PEPPOL in 60 Seconds: The Postal Network for Digital Invoicing
Origins and Basic Principles
PEPPOL (Pan-European Public Procurement OnLine) was born in 2008 from a pilot project funded by the European Commission. The initial goal: enable businesses to respond to public tenders from any EU country via a standardized exchange network.
Since then, the project has far exceeded the public procurement framework. PEPPOL is now governed by OpenPEPPOL, an international non-profit association based in Brussels. The network connects 3.7 million participants across 120 countries (Peppol Directory, data as of April 18, 2026). It’s the world’s largest open B2B e-invoicing exchange network.
The operating principle is comparable to the SWIFT network for bank payments. Each company connects to the network via a certified Access Point (the equivalent of a bank in the SWIFT analogy). Once connected, it can send and receive structured documents (invoices, credit notes, purchase orders) with any other connected entity, regardless of the country or Access Point used by the recipient.
PEPPOL vs Factur-X vs ZUGFeRD vs UBL: Don’t Confuse Network and Format
The confusion is common, including among ERP vendors. Here’s the fundamental distinction:
- PEPPOL is a transport network. It routes documents from point A to point B via certified Access Points. It doesn’t define document content, it transports it.
- UBL (Universal Business Language) and CII (Cross Industry Invoice) are data formats. These are XML syntaxes that structure invoice content (amount, VAT, line items, parties).
- Factur-X and ZUGFeRD are hybrid containers: a human-readable PDF with an embedded XML file (in CII syntax). They’re designed to work without an exchange network, through simple email or portal upload.
- EN 16931 is the European semantic standard that defines mandatory fields for an electronic invoice. PEPPOL BIS, Factur-X, and ZUGFeRD all comply with it.
In summary: PEPPOL transports UBL or CII documents compliant with EN 16931. Factur-X and ZUGFeRD encapsulate CII in a PDF. Both approaches are complementary, not competitive. A well-prepared ERP handles both.
For a detailed guide on the hybrid PDF/XML standard, see our article on ZUGFeRD and Factur-X.
Map of PEPPOL Adoption in Europe in 2026
Countries Where PEPPOL is Mandatory for B2G
B2G (Business-to-Government) was the first adoption ground. In 2026, almost all EU countries require or accept invoices via PEPPOL for public procurement:
- Norway, Denmark, Sweden, Finland: historical pioneers. Denmark imposed electronic invoicing for public contracts as early as 2005 via NemHandel, now integrated with PEPPOL. Norway, a founding member of OpenPEPPOL, requires PEPPOL for all public transactions (Qvalia, Peppol Global Reach 2026).
- Belgium: all invoices to public entities go through Mercurius, connected to PEPPOL, since 2024.
- Italy: the SDI (Sistema di Interscambio) is the national platform, but supports PEPPOL exchanges for B2G and B2B.
- Germany: federal public entities accept invoices via PEPPOL in XRechnung format since 2020.
- France: Chorus Pro, the national B2G platform, supports PEPPOL. The DGFiP was designated national PEPPOL authority in July 2025 (Qvalia).
Countries Extending PEPPOL to B2B
This is the major movement of 2026. Several countries are shifting from B2G obligation to B2B obligation:
| Country | B2B Deadline | PEPPOL Standard | Details |
|---|---|---|---|
| Belgium | January 1, 2026 | Mandatory | All VAT-registered companies must issue and receive via PEPPOL BIS 3.0 (fiskaly) |
| Poland | February-April 2026 | KSeF + PEPPOL | Large companies in February, all others April 1st via KSeF (Qvalia) |
| France | September 2026 | PEPPOL supported | Reception mandatory for all companies, progressive issuance via certified PDPs or Chorus Pro |
| Spain | Second half 2026 | In progress | B2B extension via Ley Crea y Crece, PEPPOL among accepted channels |
| Germany | January 2027 (issuance) | PEPPOL supported | Reception mandatory since January 2025, issuance from 2027 for companies above €800,000 revenue |
Belgium is the most emblematic case: since January 1, 2026, PEPPOL is the default channel for B2B. Even when an alternative platform is used, every Belgian company must be technically capable of issuing and receiving via PEPPOL. Penalties are graduated: €1,500 for a first offense, €3,000 for the second, €5,000 for the third within three months (Vertex, Belgium’s 2026 E-Invoicing Regulations).
Timeline of Deadlines 2026-2030
The ViDA directive (VAT in the Digital Age), adopted by the EU in March 2025, accelerates convergence. It requires Member States to transpose e-invoicing and digital reporting rules into national law by December 31, 2026, with go-live planned for July 1, 2030 for real-time VAT reporting (Peppol.nl, ViDA approved).
PEPPOL is the natural candidate to serve as common infrastructure for this harmonized reporting. Several Member States (France, Netherlands, Belgium) have already chosen PEPPOL as the foundation of their national e-invoicing architecture.
For a complete overview of deadlines by country, read our guide on mandatory electronic invoicing in Europe.
Technical Architecture: How an ERP Connects to the PEPPOL Network
The Role of the Access Point
An Access Point (AP) is a provider certified by OpenPEPPOL that serves as intermediary between your ERP and the network. Its role:
- Receive outgoing documents from your ERP (invoices, credit notes, purchase orders)
- Validate their compliance with PEPPOL BIS 3.0 format
- Route the document to the recipient’s Access Point via AS4 protocol
- Acknowledge receipt and report validation or delivery errors
Major Access Points in Europe in 2026 include Basware, Pagero (acquired by Thomson Reuters in 2024), Storecove, Unifiedpost, Qvalia, Billit, and EDICOM. The choice depends on your invoice volume and geographical coverage.
For a Belgian or Nordic SME with moderate volume, providers like e-invoice.be offer a pay-per-use model starting at €0.18 per invoice at scale, without monthly subscription (e-invoice.be, Best Peppol Access Points 2026). For mid-market companies with thousands of monthly invoices, Basware or Pagero offer complete automation platforms with custom pricing.
PEPPOL BIS 3.0 Formats: Structure and Validations
PEPPOL BIS (Business Interoperability Specification) 3.0 is the document profile used on the network. It’s based on UBL 2.1 (for invoices and credit notes) and complies with EN 16931 semantic standard.
In practice, your ERP must produce a UBL 2.1 XML file containing:
- PEPPOL identification of issuer and recipient (PEPPOL ID number, based on VAT number or national identifier)
- Tax data compliant with destination country (VAT rates, regime, exemptions)
- Invoice lines with product codes, quantities, unit prices
- Totals and VAT breakdown in standardized format
The document goes through Schematron validation rules before being accepted on the network. An invoice that doesn’t comply with BIS 3.0 rules is rejected by the Access Point before transmission. This is both a constraint (your ERP must produce clean XML) and a guarantee (you’ll never receive a malformed invoice).
ERP to Access Point Integration: API, EDI or Native Connector
Three connection modes exist between your ERP and the Access Point:
Native connector: some ERPs directly integrate a PEPPOL module. Odoo, Visma, Fortnox, and Exact offer native connectors that generate BIS 3.0 XML and send it to a partner Access Point without manual intervention.
REST API: most Access Points expose a REST API. Your ERP sends invoicing data in JSON or XML, the Access Point handles conversion to UBL 2.1 and transmission. This is the preferred mode for ERPs without native PEPPOL module.
EDI/middleware: for legacy ERPs or complex architectures (multi-ERP, multi-entity), EDI middleware (Boomi, MuleSoft, SAP Integration Suite) orchestrates flows between ERP and Access Point, with data mapping and error handling.
ERPs Already PEPPOL-Compatible in 2026
SAP and Oracle: Via Their Proprietary Networks
SAP offers PEPPOL integration via SAP Business Network (formerly Ariba Network). The PEPPOL Exchange Service, launched in 2022, functions as an integrated Access Point: invoices issued from S/4HANA or SAP Business ByDesign are automatically converted to PEPPOL BIS 3.0 and routed on the network (SAP Help Portal, Peppol Integration). For SMEs on SAP Business One, integration typically goes through a third-party Access Point via API.
Oracle connects its customers to the PEPPOL network via Oracle Integration Cloud. The setup requires middleware that transforms Oracle E-Business Suite or Fusion Cloud data into UBL 2.1 XML before transmission to a certified Access Point.
Odoo, Sage, Microsoft Dynamics 365: Native vs Add-on
Odoo has integrated a native PEPPOL module in recent versions. Three modules to install (Accounting, Electronic Invoicing, PEPPOL) enable BIS 3.0 invoice generation and reception directly from the accounting interface (Synconics, PEPPOL 2026).
Microsoft Dynamics 365 offers integrated e-document capabilities in Business Central and Finance & Operations. PEPPOL integration is available via partner connectors (Pagero, Storecove) or middleware like PeppolNavigator Enterprise (PeppolNavigator).
Sage (X3, Intacct, Sage 300) supports PEPPOL via Access Point partners. Integration isn’t native but done through API or third-party connector. Coverage varies by Sage version and country of operation.
Nordic and Dutch ERPs: Natively PEPPOL
ERPs developed in PEPPOL pioneer countries have a structural advantage:
- Visma (Norway): native PEPPOL connector in all its accounting solutions. Visma processes millions of invoices via the network annually.
- Fortnox (Sweden): PEPPOL integrated by default. Outgoing invoices are automatically sent in BIS 3.0 to connected recipients.
- Exact (Netherlands): native PEPPOL module with support for Dutch and Belgian Access Points.
These vendors don’t need add-ons or middleware. PEPPOL compatibility is part of their technical DNA, making them references for integration.
For a detailed comparison of these solutions, see our article on Nordic and Dutch ERPs.
Roadmap to Make Your ERP PEPPOL-Ready
Step 1: Map Your B2G and Cross-Border B2B Flows
Before touching technology, map your flows:
- How many invoices do you issue and receive monthly, by country?
- Which countries are involved? If you invoice in Belgium, PEPPOL compliance is already mandatory. If you invoice in France, the deadline is September 2026.
- Which public markets do you target? A supplier to the Norwegian, Swedish, or Belgian state must be on PEPPOL.
- Which customers or suppliers are already connected to the network? Check in the Peppol Directory if your partners are listed.
This mapping determines your integration scope and urgency level.
Step 2: Choose a Certified OpenPEPPOL Access Point
Selection criteria:
- Geographic coverage: an Access Point covering Belgium, France, and Scandinavia isn’t the same as one covering only the Netherlands.
- ERP compatibility: verify the Access Point offers a connector or API compatible with your ERP. If you’re on SAP, the native PEPPOL Exchange Service may suffice. If you’re on a UK ERP (Access Group, Advanced, Pegasus), a third-party Access Point with REST API will be necessary.
- Pricing model: pay-per-use (suitable for SMEs with variable volume) vs subscription + volume (suitable for mid-market with predictable flows).
- Validation support: the Access Point must validate your documents before sending and provide actionable error reports.
The list of certified providers is available at peppol.org/members.
Step 3: Test with PEPPOL Testbed Before Production
OpenPEPPOL provides a test environment (Testbed) that allows you to:
- Send dummy invoices and verify they pass BIS 3.0 validations
- Test document reception and integration into your ERP
- Identify mapping errors (missing fields, incorrect VAT codes, malformed PEPPOL identifiers)
Never go to production without validating at least one complete issuance-reception cycle on the Testbed. PEPPOL validation errors block invoice delivery, meaning your customer receives nothing, with no clear notification in your ERP if integration is misconfigured.
Budget: €3,000 to €15,000 for Standard SME Integration
Investment depends on your starting point:
- ERP with native connector (Odoo, Visma, Fortnox): cost is limited to configuration and Access Point fees. Count €0.18 to €0.25 per invoice in pay-per-use (e-invoice.be), meaning a few hundred euros annually for a typical SME.
- ERP without native connector (Sage, UK ERPs, legacy systems): need to develop or buy a connector, configure UBL 2.1 mapping, and set up the Access Point. Typical budget: €5,000 to €15,000 in initial integration, plus recurring Access Point fees.
- Multi-ERP or multi-entity: add EDI middleware (Boomi, MuleSoft) and budget €15,000 to €30,000 depending on flow complexity.
In all cases, ROI is rapid if you process significant volume of cross-border invoices: elimination of manual entry, reduced disputes, automatic compliance in each covered country.
Key Takeaways
PEPPOL isn’t just another standard to add to the stack. It’s the transport infrastructure that connects all national standards together. In 2026, with Belgium requiring PEPPOL for B2B, France and Poland following suit, and the ViDA directive harmonizing everything by 2030, not preparing your ERP amounts to ignoring the e-invoicing obligation itself.
To go deeper, see our complete guide on mandatory electronic invoicing in Europe and our comparison of Nordic and Dutch ERPs natively PEPPOL-compatible. If you want to understand the hybrid PDF/XML standard used in France and Germany, our article on ZUGFeRD and Factur-X completes the picture.
