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

PEPPOL vs bilateral exchange: when to pick which?

PEPPOL is not always the right answer. For a low partner count and stable relationships, a classical bilateral exchange often remains cheaper and more flexible. Four criteria to decide without dogmatism.

Two B2B exchange models

The bilateral model is the oldest: two organisations agree on a format (EDIFACT, X12, UBL, proprietary JSON), a transport protocol (AS2, OFTP2, SFTP, HTTPS) and an onboarding strategy (certificate exchange, URL configuration). Each partnership is its own project, typically 2-10 person-days depending on complexity.

The PEPPOL model, formalised in 2008 and industrialised in the 2010s, offers a shared 4-corner infrastructure: the sender has a single relationship with their Access Point (Corner C2), which automatically discovers the destination Corner C3 via an SMP/SML registry. Onboarding new partners is reduced to registering their PEPPOL identifier in their access point's directory.

Four criteria to decide

1. Partner onboarding cost

For bilateral exchange, average onboarding for a new EDIFACT partner costs typically 2-5 person-days on the technical side, plus 1-2 person-days on the functional side to align business segments. Multiplied by 50 partners, this becomes a full-time annual project.

For PEPPOL, onboarding a new partner (already on the network) is nearly free: just ask the access point to emit toward the recipient's PEPPOL identifier. No certificate exchange, no bilateral URL configuration. This is one of PEPPOL's most significant operational gains for those with many partners.

2. Network effects

PEPPOL has network properties: the more participants the network has, the more unit value being on it brings. In 2026, OpenPEPPOL counts more than 500 certified access points and several hundred thousand registered identifiers in Europe. A new entrant accesses all those potential participants automatically.

Bilateral exchange has no such network effect: each partnership is a fixed incremental cost. For an SME with only 5-10 EDI partners, that is irrelevant. For a retailer with 4,000 suppliers, the gap is massive.

3. Governance and conformance

PEPPOL imposes governance: access points must pass certification, formats must conform to OpenPEPPOL profiles, X.509 security is mandated. This is a strength when one needs a shared normative frame. It is a constraint when business needs fall outside the standard profiles.

Bilateral exchange imposes nothing: two partners can agree on any format, any transport, any acknowledgment mechanism. Flexibility is total; shared conformance is nil.

4. Business flexibility

Bilateral exchange allows adding proprietary fields (non-standard EDIFACT segments, XML extensions, arbitrary JSON data) without constraint. This is valuable for specialised industries (pharma with EPCIS, automotive with VDA), or for enriched data not covered by standards (internal codes, technical IDs, logistics metadata).

PEPPOL imposes profiles: BIS Billing 3.0, BIS Order 3.0, etc. Extensions are possible via cbc:AdditionalDocumentReference or cac:AdditionalItemProperty, but they are not portable — only the recipient that knows how to read them will use them.

Typical cases

Cases favouring PEPPOL:

  • European public invoicing. The BIS Billing 3.0 profile on PEPPOL is mandated or recommended in most EU jurisdictions.
  • Large number of partners. From a few dozen partners up, the access point's amortisation becomes obvious.
  • Changing partners. If partners come and go frequently (marketplaces, public procurement), PEPPOL saves the bilateral onboarding effort on each rotation.
  • Regulatory conformance as priority. OpenPEPPOL requirements on security, signing, archival are audited and guaranteed.

Cases favouring bilateral:

  • Low volume, stable partners. 5-10 suppliers worked with for 10 years: PEPPOL brings no improvement.
  • Non-standard business needs. Pharma with EPCIS, automotive VDA with proprietary messages: PEPPOL profiles do not cover those.
  • Very large payloads. Automotive CAD, architectural plans, ZIP manifests: bilateral OFTP2 or SFTP fits better than PEPPOL AS4.
  • Non-EU geographies. Asia, South America, Middle East have their own infrastructure; PEPPOL stays minority there.

The hybrid model in practice

Most large European enterprises have a hybrid model in 2026: PEPPOL for public invoicing and new EU partners, bilateral AS2/OFTP2/SFTP for historical partners and specific needs. Routing between the two is handled by an internal hub or by an access point that also speaks bilateral EDI.

Further reading