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

PEPPOL network economics in 2026: costs, operators, alternatives

As ViDA and Directive 2014/55 generalise e-invoicing in Europe, PEPPOL becomes the de facto rail for millions of companies. The question is no longer "should we be on PEPPOL?" but "via which operator, at what cost, with what alternatives?".

Reminder: the PEPPOL 4-corner model

PEPPOL relies on a 4-corner network: sender (corner 1) → their Access Point (corner 2) → recipient Access Point (corner 3) → recipient (corner 4). Access points discover each other via the SMP directory network (Service Metadata Publisher, one per AP) and SML (Service Metadata Locator, central for OpenPEPPOL). Transport is AS4 eDelivery (CEF / Digital Europe Building Block). Security relies on X.509 certificates issued by an OpenPEPPOL PKI.

The network is governed by OpenPEPPOL AISBL, international not-for-profit association under Belgian law since 2012, which edits BIS specifications, runs the PKI, accredits APs, and maintains SML infrastructure. It defines the network's technical economics.

OpenPEPPOL membership tiers

To operate a commercial PEPPOL AP, OpenPEPPOL membership is required. Categories and annual fees (published on openpeppol.eu/join-openpeppol):

  • Authority member — only for public authorities / peppol authorities (one per adhering country), free.
  • Service provider member — to operate a commercial AP. Annual cost tiered by PEPPOL revenue (typically 4 000-30 000 EUR/year per tier).
  • End user member — for very large user organisations wanting to participate in governance. Optional.
  • Associated member — for parties wanting to be informed without voting rights. Modest cost.

Beyond the fee, operating an AP requires: an X.509 AP certificate issued by the OpenPEPPOL PKI (annual renewal), a production SMP (can be outsourced), AS4 compliance audits (performed by the country authority), and adherence to deployed BIS profiles.

End-user pricing models

On the end-user side, two models dominate in 2026. (1) Subscription — monthly/annual payment with included volume then overage. Typical of large corporate platforms (Pagero, Comarch, Basware, SAP Concur). 2026 range: 50-200 EUR/month flat + 0.02-0.15 EUR per message above included volume. (2) Pay-as-you-go — no flat fee, per-message payment. Suited to SMEs and occasional usage. 2026 range: 0.05-0.50 EUR/message sent, reception often free or at 0.01 EUR.

The marginal cost per PEPPOL message for an AP, regardless of sales model: ~0.005-0.02 EUR (compute, storage, ACK, legal archival). Everything else is margin or support. For large senders, negotiation hinges on these margins.

Comparison of the main 2026 operators

  • Pagero (acquired by Thomson Reuters in 2024) — global coverage (PEPPOL + numerous LATAM/APAC/MEA local mandates), enterprise target. Premium pricing, strong multi-country capability.
  • Storecove — Dutch operator, EU and UK focus, API first, transparent pay-as-you-go model (~0.17 EUR per doc sent), free for reception. Well-rated for API documentation and absence of lock-in.
  • B2Brouter — Spanish operator, very competitive pricing, strong in Spain and France, offers free plan up to 12 docs/year and starter plan at ~75 EUR/year.
  • Sovos — global tax compliance leader, PEPPOL within a broader portfolio (ZATCA, India IRP, LATAM CFDI, etc.). Enterprise multinational target.
  • Comarch — Polish vendor, strong in Central Europe and Germany, negotiated pricing, solid ERP integration.
  • OpusCapita — Nordic roots, strong Scandinavian presence, good national e-invoicing coverage.
  • Tradeshift — procure-to-pay orientation, PEPPOL included in their Connect network.
  • SAP Document and Reporting Compliance — native solution for SAP S/4HANA customers, covers PEPPOL and increasingly more national mandates.
  • Workato, Boomi, MuleSoft — iPaaS with PEPPOL extension via operator partnership (typically Storecove or Basware in backend).
  • Cleo, Stedi — classical EDI orientation, add PEPPOL as a channel among AS2/SFTP/API.

Open source self-host option

For very large volumes (millions of messages/month) or strong sovereignty requirements, some organisations operate their own AP. Available open source stacks:

  • Phase4 — Java reference implementation of AS4 for PEPPOL, maintained by Philip Helger. Production-ready since 2018.
  • OpenAS4 / Domibus — CEF / Digital Europe eDelivery project, open, official European support.
  • Holodeck B2B — Java AS4 implementation maintained by Chasquis Consulting, alternative to phase4.

Typical operational costs of a self-hosted AP: cloud infrastructure ~500-2 000 EUR/month (compute, storage, legal archival), 0.2-0.5 FTE support and monitoring, PEPPOL certificate ~500 EUR/year, OpenPEPPOL membership 4-30 kEUR/year, audits ~5-10 kEUR/year. Total 30-80 kEUR/year of fixed costs plus team cost. Profitable from ~500 000 messages/year, below that a commercial operator remains cheaper.

Alternatives to all-PEPPOL

PEPPOL is not a universal obligation (except specific national mandates). For very high volume flows between two fixed partners, bilateral AS2 remains simpler and cheaper (no membership, no SMP, just a URL and a certificate). That is why US large retail (Walmart, Target, Kroger) remains mostly on AS2 + X12 without considering migration.

For convergence with REST API, some platforms (Stedi, internal API gateways) expose their flows as signed webhooks or OAuth-secured REST, in parallel with PEPPOL. Useful for modern partners used to REST. Technical cost is different (no AS4, no SMP/SML) but non-repudiation guarantees must be reimplemented in application code.

Conclusion: rationalise, not saturate

PEPPOL economics in 2026 is no longer experimental. The network operates at scale, pricing stabilises, operators consolidate (Pagero/Reuters, Quadient/Symtrax). The right 2026-2028 arbitration depends less on operator choice and more on volume and ERP strategy: above 1 million messages/year, negotiate hard or consider self-hosting; below, choose a no-lock-in operator that follows your partners (see our article on EDI lock-in). For the global network analysis, see our article on the OpenPEPPOL architecture.