Do I need both Peppol and XRechnung for German invoicing?

For German government (B2G): yes — XRechnung format via Peppol network. For German B2B: you need Peppol as the delivery network, but you can use either XRechnung or Peppol BIS 3.0 as the format. Both are accepted under the mandate.

Is XRechnung sent via Peppol?

Yes. XRechnung invoices are typically delivered via the Peppol network. The XRechnung specification defines the format; Peppol provides the delivery infrastructure. Your Access Point handles the network transport.

What is a Leitweg-ID?

The Leitweg-ID is a routing identifier used in German government invoicing. It identifies the specific government department or entity that should receive the invoice. It’s required by XRechnung rule BR-DE-15 and maps to BT-10 (Buyer Reference) in the EN 16931 data model.

Can I use Peppol BIS instead of XRechnung for German B2B?

Yes. Germany’s B2B e-invoicing mandate accepts any EN 16931-compliant format. Peppol BIS 3.0 is EN 16931-compliant. The practical difference: XRechnung adds German-specific rules (BR-DE-*) that Peppol BIS doesn’t require. For B2B, Peppol BIS is sufficient unless the receiver specifically asks for XRechnung.

Which validation rules apply to XRechnung on Peppol?

Three layers: EN 16931 base rules (BR-01 through BR-65), German CIUS rules (BR-DE-01 through BR-DE-26), and Peppol network rules (PEPPOL-EN16931-R001 through R080). All three must pass for the invoice to be accepted.

Peppol vs XRechnung: Understanding the Network vs Format Distinction

Side-by-Side Comparison

Feature	Peppol	XRechnung
What it is	A delivery network (infrastructure)	A format specification (CIUS of EN 16931)
Scope	Pan-European — 39+ countries	Germany only
XML syntax	UBL 2.1 (primary) or CII	UBL 2.1 or CII — both supported
Standard base	EN 16931 + Peppol-specific rules	EN 16931 + German-specific rules (BR-DE-*)
Transport	AS4 protocol via certified Access Points	No transport — format only (typically delivered via Peppol)
German B2G	Required as delivery channel	Required as format specification
German B2B mandate	Primary delivery network	Accepted format (alongside Peppol BIS, ZUGFeRD)
Validation rules	PEPPOL-EN16931-R001 through R080	BR-DE-01 through BR-DE-26
Buyer reference (BT-10)	Required (PEPPOL-EN16931-R010)	Required for B2G (BR-DE-15), maps to Leitweg-ID
Cross-border use	Works across all Peppol member countries	Germany-specific — other countries have their own CIUS

Peppol

Peppol (Pan-European Public Procurement Online) is a federated network for exchanging structured electronic documents. It uses a four-corner model: your Access Point sends the invoice to the receiver’s Access Point via the AS4 transport protocol. The network handles routing, delivery receipts, and participant discovery.

Peppol has its own invoice format — Peppol BIS Billing 3.0 — which is a CIUS of EN 16931 with additional Peppol-specific rules. But Peppol is primarily infrastructure, not a format. It’s the highway, not the car.

XRechnung

XRechnung is Germany’s national CIUS (Core Invoice Usage Specification) of the EN 16931 standard. It adds German-specific rules on top of EN 16931: a buyer reference (Leitweg-ID for government), seller contact information, payment means restrictions, and other requirements specific to German business and government practices.

XRechnung supports both UBL 2.1 and CII syntaxes. The current version is XRechnung 3.0. It’s maintained by KoSIT (Koordinierungsstelle für IT-Standards), the German coordination office for IT standards.

Key Differences Explained

Network vs. format

This is the core distinction. Peppol is infrastructure — it moves documents from sender to receiver. XRechnung is a specification — it defines what data an invoice must contain and how it must be structured. An XRechnung invoice travels via the Peppol network. They’re layers, not alternatives.

Geographic scope

Peppol operates in 39+ countries. XRechnung is Germany-only. If you invoice across EU borders, you use the Peppol network with the appropriate country CIUS (XRechnung for Germany, BEvCIUS for Belgium, etc.).

Validation rule sets

Both add rules on top of EN 16931, but different rules. Peppol adds network-level requirements (business process identifier, buyer reference). XRechnung adds German requirements (Leitweg-ID, seller email, specific payment means). An XRechnung invoice sent via Peppol must pass both rule sets.

When to Use Peppol

·Sending or receiving e-invoices to/from any EU country
·Belgian B2B invoicing (Peppol is mandatory)
·Any cross-border EU e-invoicing
·When the receiver expects Peppol BIS 3.0 format specifically

When to Use XRechnung

·Invoicing German federal government entities (Leitweg-ID required)
·Invoicing German state/municipal government (requirements vary by state)
·When a German receiver explicitly requires XRechnung format
·When you need to comply with German-specific validation rules (BR-DE-*)

Can You Use Both?

For German government invoicing, you must use both: XRechnung format delivered via the Peppol network. This means your invoice must pass EN 16931 base rules, XRechnung BR-DE-* rules, AND Peppol PEPPOL-EN16931-R* rules — three layers of validation. For German B2B, you can use either XRechnung or Peppol BIS 3.0 format, both delivered via Peppol.