Peppol vs XRechnung — Which Format Do You Need?
Key Takeaway
- Peppol BIS 3.0 is a pan-European e-invoicing format and network — the default choice for cross-border invoicing across the EU.
- XRechnung is Germany's national CIUS (Core Invoice Usage Specification) — a stricter version of EN 16931 with German-specific rules.
- Both are EN 16931 compliant. XRechnung invoices can be sent over the Peppol network. They are not competing standards — they are different layers of the same ecosystem.
Side-by-Side Comparison
| Aspect | Peppol BIS 3.0 | XRechnung |
|---|---|---|
| Scope | Pan-European | Germany (national CIUS) |
| XML Syntax | UBL 2.1 only | UBL 2.1 or CII |
| Governing Body | OpenPeppol AISBL (Brussels) | KoSIT (Bremen, Germany) |
| When to Use | Cross-border EU invoicing, B2G/B2B in Peppol countries | German B2G (mandatory), German B2B (from 2025) |
| Country Focus | 30+ countries (EU, EEA, Singapore, Australia) | Germany |
| EN 16931 Compliance | Yes — implements EN 16931 via UBL | Yes — CIUS adds stricter rules on top of EN 16931 |
| Special Requirements | Peppol participant IDs for network delivery | Leitweg-ID (routing ID) for B2G; buyer reference mandatory |
When to Use Peppol BIS 3.0
Peppol BIS 3.0 is the right choice when you are invoicing across borders or when your trading partner's country has adopted Peppol as its primary e-invoicing infrastructure. This includes:
- Cross-border B2B and B2G within the EU — Peppol is the default interoperability layer.
- Belgium, Netherlands, Denmark, Sweden, Finland, Norway, Luxembourg — countries where Peppol is the primary or mandatory e-invoicing channel.
- Any scenario where you need a single format that works across multiple EU countries without country-specific adaptations.
Peppol BIS 3.0 uses exclusively UBL 2.1 syntax. It adds its own business rules (such as requiring Peppol endpoint identifiers) but stays within the boundaries of EN 16931. If you are not specifically required to use a national format, Peppol BIS 3.0 is the safest pan-European default.
When to Use XRechnung
XRechnung is Germany's mandatory e-invoicing standard. You need it in these scenarios:
- German B2G invoicing: Since November 2020, all invoices to German federal government agencies must be in XRechnung format, submitted via the ZRE (Zentraler Rechnungseingang) or OZG-RE portals. A Leitweg-ID routing number is required.
- German B2B invoicing: Germany's B2B e-invoicing mandate (effective from January 2025) requires EN 16931-compliant invoices. XRechnung is the primary national format, though ZUGFeRD at the EN 16931 profile is also accepted.
- German state and municipal invoicing: Most German federal states (Bundeslaender) require XRechnung for their own B2G procurement, often with state-specific Leitweg-ID schemes.
XRechnung supports both UBL 2.1 and CII syntax. In practice, UBL is more common for XRechnung because it aligns with the Peppol ecosystem. The standard is maintained by KoSIT (Koordinierungsstelle fuer IT-Standards) in Bremen.
Can XRechnung Travel on Peppol?
Yes. This is one of the most important points to understand. XRechnung and Peppol are not mutually exclusive — they work together. An XRechnung invoice in UBL 2.1 syntax can be sent over the Peppol network, and this is in fact the recommended delivery method for German B2G invoicing.
The German government's ZRE portal accepts invoices delivered via Peppol. When you send an XRechnung-compliant UBL invoice through Peppol, the invoice satisfies both XRechnung validation rules (German CIUS) and Peppol BIS 3.0 transport requirements. The Peppol network is the delivery infrastructure; XRechnung is the content standard.
However, a standard Peppol BIS 3.0 invoice is not automatically XRechnung-compliant. XRechnung adds requirements that Peppol does not mandate — most notably the Leitweg-ID for B2G and a mandatory buyer reference. If you are sending to a German government entity, you must ensure your invoice meets XRechnung rules, not just Peppol rules.
Decision Flowchart
Use this text-based decision tree to determine which format you need:
- Is your recipient a German government agency?
Yes → Use XRechnung (UBL syntax). Include the Leitweg-ID. Send via Peppol or upload to ZRE/OZG-RE. - Is your recipient a German business (B2B)?
Yes → Use XRechnung or ZUGFeRD EN 16931. Both satisfy the German B2B mandate. XRechnung is recommended for fully automated processing. - Is your recipient in another EU country that uses Peppol?
Yes → Use Peppol BIS 3.0. Check whether the destination country has a CIUS with additional requirements. - Are you invoicing across multiple EU countries?
Yes → Use Peppol BIS 3.0 as your default, and add country-specific fields (like Leitweg-ID for Germany) where required. - Does your recipient need a human-readable PDF alongside the data?
Yes → Consider ZUGFeRD/Factur-X (hybrid PDF+XML) instead of pure XML.
How InvoicePeppol Helps
InvoicePeppol converts your PDF invoices into both Peppol BIS 3.0 and XRechnung-compliant XML. Our AI extracts invoice data and generates validated UBL 2.1 XML that meets EN 16931 requirements. Whether you need pan-European Peppol format or Germany-specific XRechnung, we handle the technical details.
Frequently Asked Questions
Can I send XRechnung outside Germany?
XRechnung is specifically designed for the German market and contains Germany-specific rules (like the Leitweg-ID). While the underlying data is EN 16931 compliant and can be understood by any EN 16931-capable system, recipients outside Germany will not expect or require XRechnung-specific fields. For non-German recipients, use Peppol BIS 3.0 or the recipient country's preferred format instead.
Is Peppol accepted for German B2G?
Yes, but with an important nuance. The Peppol network is an accepted delivery channel for German B2G invoices. However, the content of the invoice must comply with XRechnung rules, not just generic Peppol BIS 3.0 rules. In practice, this means sending an XRechnung-compliant UBL invoice via Peppol — which satisfies both requirements simultaneously. A plain Peppol BIS 3.0 invoice without a Leitweg-ID would be rejected.
Which should I use for German B2B?
Germany's B2B e-invoicing mandate requires EN 16931-compliant invoices. Both XRechnung and ZUGFeRD (at the EN 16931 or XRechnung profile) satisfy this requirement. XRechnung is the better choice if your trading partner has automated invoice processing. ZUGFeRD is preferable when the recipient also needs a human-readable PDF. See our Germany e-invoicing guide for full details on the mandate timeline.
Do I need separate software for each format?
No. Because both Peppol BIS 3.0 and XRechnung are based on EN 16931 and can use UBL 2.1 syntax, a single tool can handle both. The difference is in the validation rules and a few additional fields. InvoicePeppol generates XML that meets both sets of requirements, so you do not need to maintain separate workflows.
Ready to convert your invoices?
InvoicePeppol converts your PDF invoices to compliant e-invoicing XML in seconds. AI-powered extraction, manual review, and instant download.