ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

— May 18, 2026 · 9 min read

Why PEPPOL won the small-business invoice race

Between 2010 and 2025, ten initiatives claimed to unify SME e-invoicing in Europe: ebInterface, FatturaPA, Factur-X, Tradeshift, Basware Open Network, Tungsten, the defunct e-SENS, etc. In 2026, only one is the de facto rail: PEPPOL. Here is why.

Context: 15 years of fragmentation

The electronic B2B invoice problem is old: each EU country has, at some point, imposed a local format for B2G flows or recommended it for B2B. Italy with SdI/FatturaPA since 2014, Hungary with NAV Online 2018, France with Chorus Pro 2017, Spain with FACe and Suministro Inmediato de Información 2017, Poland with KSeF 2022, Portugal with Saft. Each mandate had its own proprietary format, archiving obligations, APIs.

For intra-EU B2B, several initiatives attempted cross-cutting standardisation: e-SENS (2013-2017, Horizon 2020 funded) which laid the technical foundations; OpenPEPPOL (created in 2012 at the end of the PEPPOL pilot 2008-2012); Tradeshift (private commercial network, founded 2010 in Denmark); Basware Open Network (private Finland); and the semantic standard EN 16931 published by CEN in 2017.

The technical choices that made the difference

1. Open 4-corner model

Before PEPPOL, private networks (Tradeshift, Basware) imposed a 2-corner model: sender and receiver had to be customers of the same operator. It was functional but created massive lock-in. PEPPOL imposed 4-corner: sender (corner 1) → its Access Point (corner 2) → recipient's AP (corner 3) → recipient (corner 4). APs discover each other via a public SMP/SML directory. Consequence: the sender does not depend on the recipient's operator choice — just both being on PEPPOL is enough. Same paradigm as SMTP email, and that is what scales.

2. AS4 eDelivery as transport

Choosing AS4 eDelivery (CEF/Digital Europe Building Block, based on ebMS 3.0 and OASIS) as transport protocol is counter-intuitive in retrospect — AS4 is more complex than AS2 or a simple REST over HTTPS. But it offers: native non-repudiation via WS-Security signatures, NRR (Non-Repudiation of Receipt) acknowledgements, transport-layer mTLS, and a standard carried by the EU itself (decision 2015/2240 on Building Blocks). In 2026, AS4 eDelivery is also used by eHealth Digital Service Infrastructure and eJustice eCODEX, consolidating the investment at pan-EU scale.

3. UBL 2.1 as semantic format

OASIS Universal Business Language 2.1 (and 2.3 in 2026), with publicly available XSD schemas, was chosen as pivot format. The sectoral specification PEPPOL BIS Billing 3 (2017, regularly revised) imposes a strict subset of UBL aligned on EN 16931. This gives: a schema usable by any standard XML parser, uniform European semantics, and direct compatibility with directive 2014/55 B2G.

4. OpenPEPPOL AISBL governance

OpenPEPPOL is a non-profit international association under Belgian law, governed by a Coordinating Committee elected by its members and thematic Working Groups. This multi-stakeholder governance (Member States, commercial operators, large end users, SMEs, academia) prevented takeover by a single actor. Compare with Tradeshift or Basware, private commercial companies subject to their capital investors (Tradeshift merged with Mirakl in 2024, Basware acquired by Accel-KKR in 2022).

What tipped the balance in 2024-2025

Three events consolidated PEPPOL as the de facto rail for SME B2B in Europe:

  • ViDA adopted on 11 March 2025 by the ECOFIN Council. The regulation explicitly references EN 16931 (therefore UBL/PEPPOL BIS) as the technical foundation for intra-EU B2B on 1 July 2030. Without saying it, ViDA elects PEPPOL as the default rail.
  • Key country decisions: Belgium (Hermes January 2026, PEPPOL-based), France (PDP September 2026 accepting PEPPOL on receipt), Germany (XRechnung B2B 2027 on PEPPOL), Netherlands (Simplerinvoicing renamed PEPPOL e-Invoicing 2025), Sweden (Svefaktura migrated to PEPPOL BIS since 2023). Not a single European country bet against PEPPOL.
  • Adoption outside the EU: Singapore InvoiceNow (2019), Australia/New Zealand PEPPOL Authority (2019), Japan Qualified Invoice 2023, Malaysia LHDN MyInvois 2024. PEPPOL becomes a global de facto standard, securing technological investments.

Why the others lost

  • Private networks (Tradeshift, Basware Open Network, OpenText): vendor lock-in unacceptable for tax administrations. None obtained a state mandate.
  • National formats (FatturaPA, Austrian ebInterface): by construction non-pan-European, fragment the single market.
  • e-SENS: funded pilot project that laid technical bricks (eDelivery, eID), but handed the baton to OpenPEPPOL for the operational phase.
  • Factur-X: PDF/A-3 + XML CII hybrid format very popular in France and Germany (ZUGFeRD), remains relevant for France-Germany B2B but does not provide the transport network — it is complementary to PEPPOL, not competing.

What remains uncertain in 2026

PEPPOL has won the transport+semantic layer, but three questions remain open:

  • Operator (AP) economic model: prices have stabilised downward (EUR 0.05-0.17 per message), margins compressed (see our article PEPPOL network economics 2026), consolidation underway (Pagero/Thomson Reuters, Sovos/Symtrax/Quadient).
  • 5-corner for tax authorities: PEPPOL extends its 4-corner model toward a 5-corner where the tax authority is a systematic recipient (to comply with ViDA DRR). PEPPOL CTC spec published 2024, rollout in progress.
  • Post-quantum: PEPPOL PKI certificates will need to migrate to ML-DSA/ML-KEM (FIPS 204/203) by 2030. Roadmap under discussion in the PKI Working Group.

References

Further reading: our foundation "PEPPOL network explained" and foundation "EU e-invoicing roadmap".