PEPPOL vs XRechnung — Which E-Invoice Format Should You Use?
PEPPOL BIS 3.0 and XRechnung are both based on EN 16931 and UBL 2.1 — but they serve different purposes. PEPPOL is a cross-border EU network and format; XRechnung is Germany's stricter B2G-specific CIUS. Understanding the difference saves you from rejected invoices and unnecessary format switches.
What it is: A UBL 2.1 invoice format + transport network. PEPPOL is both the format (Business Interoperability Specification, BIS 3.0) and the 4-corner network of access points that route invoices between ERPs.
Where it's used: Cross-border EU B2B and B2G invoicing. All EU member states. Mandatory for many public sectors (Norway, Netherlands, Singapore, Australia).
Mandatory in Germany for: Cross-border EU invoices, PEPPOL-connected public buyers. Not typically required for domestic B2B.
XRechnung 3.x
What it is: The German B2G CIUS of EN 16931. A stricter subset of PEPPOL BIS 3.0 with additional mandatory fields and tighter validation rules (BR-DE-* for UBL, CII-DE-* for CII).
Where it's used: Germany only, exclusively for public-sector invoicing (B2G). Submitted via ZRE, OZG-RE or state portals.
Mandatory for: All invoices to German federal, state and most municipal buyers. Not used for B2B.
Are they compatible?
XRechnung can travel over PEPPOL
XRechnung UBL invoices are structurally valid PEPPOL-compatible documents — they carry the XRechnung CustomizationID URN but use the same UBL 2.1 base as PEPPOL BIS 3.0. Many PEPPOL access points (Basware, Storecove, OpenPEPPOL partners) accept and deliver XRechnung invoices as a standard service. German federal and state portals also accept XRechnung delivered via a PEPPOL access point — the underlying transport is irrelevant to the format check.
XRechnung is stricter than PEPPOL
A valid XRechnung invoice is always a valid EN 16931 invoice — but not necessarily a valid PEPPOL BIS 3.0 invoice (the ProfileID differs). A valid PEPPOL BIS 3.0 invoice may not pass XRechnung validation: the Leitweg-ID (cbc:BuyerReference) is mandatory in XRechnung but optional in PEPPOL, and the seller electronic address requirements differ. When in doubt, generate XRechnung if invoicing a German public-sector buyer. aiDoks generates XRechnung in both UBL 2.1 and CII syntax — use CII for SAP, DATEV, and other systems that import CII directly.
What about the German B2B mandate?
For the German B2B e-invoicing mandate (2025–2027), XRechnung is not the required format — it is a B2G-specific format. German B2B requires EN 16931-compliant structured invoices: PEPPOL BIS 3.0 UBL, CII, or ZUGFeRD/Factur-X all qualify. PEPPOL is the most natural choice for businesses already in the PEPPOL network.
PEPPOL vs XRechnung: FAQ
What is the difference between PEPPOL and XRechnung?
PEPPOL (Pan-European Public Procurement Online) is a cross-border transport network plus a set of format specifications. PEPPOL BIS Billing 3.0 is the PEPPOL invoice format, based on UBL 2.1 + EN 16931. XRechnung is the German B2G Core Invoice Usage Specification (CIUS) of EN 16931 — a stricter subset of EN 16931 with additional mandatory fields (Leitweg-ID, specific VAT formats). XRechnung is a format; PEPPOL is both a network and a format.
Can XRechnung invoices be transported over the PEPPOL network?
Yes. XRechnung UBL invoices are fully PEPPOL-compatible — they carry the XRechnung CustomizationID URN but otherwise conform to PEPPOL's UBL 2.1 structure. German federal and state portals accept XRechnung delivered via a PEPPOL access point. Many PEPPOL access points (Basware, Storecove, OpenPEPPOL partners) support XRechnung delivery as a standard service.
Which format should I use for invoices to German public authorities?
Use XRechnung. German B2G is explicitly the XRechnung use case. You also need the Leitweg-ID assigned by the buyer, which PEPPOL BIS invoices do not require. If your software generates PEPPOL BIS 3.0 invoices, switching to XRechnung typically means changing the CustomizationID and adding the BuyerReference (Leitweg-ID) — aiDoks handles both profiles from the same form.
Is PEPPOL used in Germany for B2B invoicing?
Yes, PEPPOL is growing in German B2B, particularly in supply-chain-intensive industries (automotive, retail). The German B2B e-invoicing mandate from 2025/2027 accepts EN 16931-compliant structured invoices in multiple formats: UBL, CII, or ZUGFeRD/Factur-X hybrid. PEPPOL BIS 3.0 UBL qualifies. XRechnung is not typically used for B2B — it is a B2G-specific format.
Is one format stricter than the other?
XRechnung is stricter than PEPPOL BIS 3.0. XRechnung adds BR-DE-* rules on top of EN 16931 (for example: mandatory Leitweg-ID, mandatory seller electronic address, German-specific VAT number formats). A valid XRechnung invoice is always a valid EN 16931 invoice, but a valid PEPPOL BIS 3.0 invoice may not pass XRechnung validation (because the Leitweg-ID and seller endpoint rules may not be satisfied).
Can aiDoks validate and generate both formats?
Yes. The aiDoks validator auto-detects whether an invoice is PEPPOL BIS 3.0 or XRechnung from the CustomizationID URN and applies the correct rule pipeline. The generator supports both profiles from the same form — switch between PEPPOL and XRechnung with the output profile selector. For XRechnung, the form additionally reveals the Buyer Reference (Leitweg-ID) field.