Peppol and E-Invoicing in Germany: What the Network Is and When You Need It

Anyone reading up on German e-invoicing runs into Peppol sooner or later, usually in a sentence that makes it sound compulsory. For B2B invoicing in Germany it is not, and the confusion has a simple cause: Peppol gets mentioned in the same breath as XRechnung and ZUGFeRD, even though it is a completely different kind of thing.

XRechnung and ZUGFeRD are formats: they define how an invoice is structured. Peppol is a network: it defines how a document travels securely from A to B. Format and transport route are two separate decisions.

This article explains how Peppol works, what an access point is, how a Peppol ID differs from a Leitweg-ID, and in which cases you need to think about any of it.

The short version

• Peppol is a transport network, not a format. It carries XRechnungen, among other things, but does not replace them.
• Peppol is not mandatory for B2B invoicing in Germany. An e-invoice as an email attachment meets the obligation just as well.
• It matters mainly for public authorities and for larger companies that have connected their invoice intake to it.
• Access runs through an access point, normally via a service provider. Running your own is only worth it at very high volumes.
• A Peppol ID and a Leitweg-ID are not the same thing: the Peppol ID addresses a participant on the network, the Leitweg-ID addresses an authority inside the receiving platform.

What Peppol actually is

Peppol stands for Pan-European Public Procurement On-Line and comes out of European public procurement. It is a rulebook plus a network: participants agree on shared document specifications and a secure transmission route, so an invoice can find its way from one company to another without bilateral arrangements.

The analogy that holds up best: Peppol is to the e-invoice what the mobile network is to an SMS. The SMS is the format, the network makes sure it arrives, and you agree nothing with the recipient because both sides are connected to the same network.

The four-corner model

Peppol works with four parties:

1. The sender creates the invoice in their software.
2. Their access point takes it and hands it to the network.
3. The recipient's access point takes it off the network.
4. The recipient gets it in their system.

Sender and recipient therefore never talk directly; they always go through their respective access points. The benefit: one connection reaches every participant on the network, instead of a separate interface per customer.

What is an access point?

An access point is the technical gateway to the network. Without one, nothing goes in or out. Invoice issuers in Germany have three options:

• Through a service provider. The normal case. Many invoicing and accounting vendors run an access point or are connected to one.
• Through the federal administration's access point. Usable for invoices to federal authorities.
• With your own access point. Technically possible, but it involves certification and ongoing operation. That only pays off at very high invoice volumes.

Peppol ID vs Leitweg-ID: the most common mix-up

Both are addressing identifiers, but at different levels — and this is exactly where invoices get lost in practice:

The practical rule: you always need the Leitweg-ID for invoices to authorities, even when you submit by email or portal. You only need the Peppol ID when the transport runs over Peppol. How the Leitweg-ID gets into the invoice is covered in the guide to creating an XRechnung.

Do you need Peppol?

For the vast majority of freelancers and small companies: no.

• Plain B2B sending to companies: an email attachment containing an XRechnung or ZUGFeRD meets the legal requirement. The BMF has stated this explicitly.
• Invoices to federal authorities: Peppol is one of several routes. ZRE and OZG-RE also accept invoices by upload or web service.
• Larger corporate customers with connected invoice intake: if a customer explicitly requires Peppol, you need a provider with an access point. That is a question of transport, not of your invoicing program.

Peppol becomes genuinely useful when you invoice many authorities or corporate customers regularly and want to avoid negotiating a route with each recipient.

For the sake of clarity about our own product: Norman generates e-invoices in the XRechnung and ZUGFeRD formats and receives and archives incoming e-invoices. A Peppol connection is not currently part of that. If a customer explicitly requires delivery over Peppol, you will need an access point provider in addition.

Peppol and the 2027 and 2028 obligations

Peppol is nowhere a precondition for the German e-invoicing mandate. The mandate says what format an invoice must be in — structured per EN 16931 — not by what route it reaches the recipient. So anyone switching for 1 January 2027 or 2028 decides on the format first, and only then whether email is enough.

Looking further out, the network still has an argument in its favour: the EU's "VAT in the Digital Age" (ViDA) package aims at digital reporting of cross-border supplies, and the infrastructure envisaged for it is closely modelled on the Peppol approach. If you already work heavily with the public sector, you are not building something that becomes worthless in a few years.

Which stage of the obligation applies to you is settled in five questions by the e-invoicing mandate check.

Frequently asked questions

Is Peppol an invoice format?

No. Peppol is a transport network with its own rules for exchanging documents. An XRechnung stays an XRechnung whether it reaches the recipient via Peppol, by email, or through a portal.

Do I need Peppol for the e-invoicing obligation?

No. The obligation concerns the format of the invoice, not the transmission route. For B2B sending, an email with the structured invoice attached is sufficient.

What does a Peppol access point cost?

It depends on the provider and is usually billed as a base fee plus volume. For most companies there is no separate line item at all, because access is included in their invoicing or accounting tool. Running your own access point only pays off at very high volumes.

What is the difference between a Peppol ID and a Leitweg-ID?

The Peppol ID addresses a participant on the Peppol network and is issued by the access point provider. The Leitweg-ID addresses an authority inside the invoice receiving platform, is issued by that authority, and sits in the invoice data set in field BT-10. For invoices to authorities you always need the Leitweg-ID; the Peppol ID only when sending over the network.

Can I send an XRechnung to authorities without Peppol?

Yes. Federal authorities accept invoices through ZRE and OZG-RE by upload or web service as well. Peppol is one of several permitted routes, not the only one. You need the Leitweg-ID either way.

Is Peppol only for the public sector?

No. Peppol comes out of public procurement but is open to any business, from sole trader to large group. In practice, adoption in German B2B is still lower than in dealings with public authorities.

Conclusion

Peppol is a transport network that solves a real problem: reaching many recipients without agreeing an interface with each one. For the German e-invoicing mandate, though, it is not a precondition, and for ordinary B2B sending by email you do not need it.

So decide in this order: format first, route second. With Norman, XRechnung and ZUGFeRD come straight out of your ordinary invoices, and incoming e-invoices are read and archived GoBD-compliant. For transport over Peppol you would need an access point provider in addition — for ordinary B2B email you would not.