Peppol & Peppol-BIS for German Companies: What You Really Need to Know

Peppol comes up in almost every e-invoicing conversation — and it is almost always misunderstood. Many German companies assume Peppol is a competing invoice format they must adopt. It is not. Peppol is a delivery network, and understanding that distinction is the key to making sensible decisions about your e-invoicing setup.

> Short answer: Peppol is a four-corner delivery network, not a file format. The file it carries (for example Peppol BIS Billing 3.0) is a CIUS of EN 16931, just like XRechnung. Peppol is not mandatory for B2B invoicing in Germany — the German mandate concerns formats, not transport.

What Peppol actually is

Peppol (Pan-European Public Procurement OnLine) is an infrastructure for exchanging business documents. It uses a four-corner model:

1. Corner 1 — the sender (you)
2. Corner 2 — your Access Point
3. Corner 3 — the recipient's Access Point
4. Corner 4 — the recipient

You connect once to an Access Point. From then on you can reach any other participant on the network without negotiating a separate connection for each partner. This is the same principle that makes email universal: you do not peer with every mailbox individually.

Format vs. transport: the distinction that matters

The German e-invoice mandate under § 14 UStG (introduced by the Wachstumschancengesetz of March 2024) requires a structured format that complies with EN 16931 — for example ZUGFeRD or XRechnung. It says nothing about how the file reaches the recipient. You may send it by email, upload it to a portal, or route it through Peppol.

Peppol BIS Billing 3.0 is a CIUS (Core Invoice Usage Specification) of EN 16931, built on UBL 2.1. XRechnung is the German CIUS on the same standard (it permits both UBL and CII syntax). Because they share the EN 16931 core, a well-formed Peppol invoice and a well-formed XRechnung carry the same semantic fields — the same mandatory business terms.

The German Peppol Authority: KoSIT

Every country that participates in Peppol has a national Peppol Authority. In Germany this is KoSIT — the same coordination body that maintains the XRechnung standard and publishes the KoSIT validator. That overlap is deliberate: it keeps the German CIUS and the Peppol profile aligned. If you already validate against KoSIT rules, you are close to Peppol conformance.

Is Peppol mandatory in Germany?

No. This is the most persistent myth. The mandate is about formats, not transport. A ZUGFeRD file emailed as a PDF/A-3 attachment fully satisfies § 14 UStG. You never have to touch Peppol to be compliant for domestic B2B.

That said, Peppol is spreading for practical reasons:

• Reach — one connection reaches many trading partners
• Reliability — signed transport receipts confirm delivery
• Cross-border — Peppol is the de-facto channel for EU cross-border exchange (see cross-border e-invoicing and ViDA)

When Peppol makes sense for you

Peppol is worth considering when:

• You invoice many customers who are already on Peppol (common in the Nordics, Benelux, and Italy)
• You supply the public sector across several EU countries
• You want automated delivery confirmation rather than hoping an email arrived

For a small business issuing a handful of invoices a month, an emailed ZUGFeRD file is entirely sufficient. There is no compliance benefit to Peppol — only an operational one at scale.

How to get onto Peppol

You do not join Peppol directly. You engage a certified Access Point provider, who registers you in the Peppol directory under a participant identifier (in Germany typically your VAT ID or Leitweg-ID scheme). Your ERP or accounting software then hands finished invoice files to the Access Point for routing.

The invoice content still has to be a valid EN 16931 document. That is the part that matters most — a broken invoice on a perfect network is still a broken invoice.

Where TaxLayer fits

TaxLayer focuses on the format layer: turning an existing PDF into a validated EN 16931 file. Whether you then email that file, upload it to the OZG-RE for public-sector recipients, or hand it to a Peppol Access Point is your choice.

Getting the content right first

Before you worry about Peppol transport, make sure your invoice content is valid. A CIUS-conformant file passes on any channel; an invalid one fails everywhere.

TaxLayer converts your PDF invoices into validated ZUGFeRD or XRechnung files that share the EN 16931 core with Peppol BIS Billing 3.0. The first two conversions each month are free — no credit card required.