PEPPOL vs XRechnung is a comparison that confuses many German businesses because the two terms operate at different levels: PEPPOL is a network and a format standard; XRechnung is a German invoice format. Comparing PEPPOL vs XRechnung directly is like comparing a postal network to a letter format — they are not mutually exclusive. An XRechnung can be sent via PEPPOL; a PEPPOL BIS Billing 3.0 invoice can be sent by email. The PEPPOL vs XRechnung question only becomes meaningful when you are choosing between two specific things: XRechnung (as a format) transmitted by email vs PEPPOL BIS Billing 3.0 transmitted via the PEPPOL network. This guide unpacks both dimensions — format and network — and provides a clear decision framework for German businesses choosing their e-invoicing approach.
PEPPOL vs XRechnung confusion typically arises in one of three scenarios: a German business setting up e-invoicing for the first time and receiving conflicting advice about which format to use; a B2G supplier trying to understand whether they need PEPPOL or can use the ZRE portal directly; or a business receiving a supplier portal requirement that specifies “XRechnung via PEPPOL” and not understanding what that means technically. All three scenarios resolve once you understand that PEPPOL is a delivery network (analogous to a logistics carrier) and XRechnung is an invoice format (analogous to a parcel type). The EN 16931 formats Germany framework allows both XRechnung and PEPPOL BIS Billing 3.0 as valid B2B e-invoice formats, and both can be transmitted via PEPPOL or directly by email.
Key Takeaways
- PEPPOL vs XRechnung is not an either/or choice — XRechnung is a format; PEPPOL is a delivery network. You can send XRechnung via PEPPOL, or PEPPOL BIS Billing 3.0 by email.
- PEPPOL BIS vs XRechnung as formats: Both are EN 16931 compliant; XRechnung adds German-specific CIUS rules (Leitweg-ID, German VAT rules); PEPPOL BIS is the international standard valid across 40+ countries.
- XRechnung via PEPPOL is the standard method for German B2G invoicing — the ZRE federal portal accepts PEPPOL delivery, and XRechnung is the expected format for federal authority invoices.
- XRechnung CIUS is Germany’s national Core Invoice Usage Specification — a set of additional rules layered on top of EN 16931 that makes XRechnung a German national standard derived from the European base standard.
- PEPPOL or email e-invoice: Both transmission methods satisfy the German B2B mandate — the mandate requires an EN 16931 compliant format, not a specific delivery channel.
What Is the Difference Between PEPPOL and XRechnung?
PEPPOL vs XRechnung at the fundamental level: PEPPOL is a global e-business network governed by OpenPEPPOL; XRechnung is a German XML invoice format. PEPPOL specifies how documents are exchanged (the four-corner model, AS4 message protocol, participant identifiers); XRechnung specifies what the invoice document contains (EN 16931 fields plus German-specific extensions). When someone says “we use PEPPOL for invoicing,” they mean they transmit invoices via the PEPPOL network, usually in PEPPOL BIS Billing 3.0 format. When someone says “we use XRechnung,” they mean they generate invoices in the XRechnung XML format, which they may transmit by email, via a portal, or via PEPPOL. The PEPPOL vs XRechnung distinction is network vs format.
PEPPOL or email e-invoice is the actual transmission choice German businesses face. Once you have decided on the invoice format (XRechnung, ZUGFeRD, or PEPPOL BIS Billing 3.0), the transmission question is whether to email the file to the buyer or route it via the PEPPOL network. For B2B transactions, email is the most common transmission channel in Germany — the vast majority of German B2B e-invoices are currently delivered as email attachments. PEPPOL transmission is preferred for B2G (mandatory or standard for government portal submission), for high-volume B2B where delivery confirmation and automation are important, and for cross-border invoicing where the receiver is in another PEPPOL country. The EN 16931 formats Germany mandate is satisfied by the invoice format, not the transmission channel.
Network vs Format: Understanding the Two Dimensions of PEPPOL vs XRechnung
EN 16931 formats Germany — the formats that satisfy the domestic B2B mandate — are XRechnung, ZUGFeRD (at EN 16931+ profile), and PEPPOL BIS Billing 3.0. These are format options. PEPPOL is a network that can carry any of these formats. The relationship between the format dimension and the network dimension is independent: you choose a format, and separately you choose a transmission channel. PEPPOL vs XRechnung as a comparison conflates the two dimensions. The correct comparison at each dimension is: format dimension (XRechnung vs PEPPOL BIS Billing 3.0 vs ZUGFeRD) and network dimension (PEPPOL vs email vs portal). German businesses should make both decisions explicitly and independently.
PEPPOL BIS vs XRechnung at the format level: the differences are in scope and specificity. XRechnung CIUS adds German-specific fields and rules — particularly the Leitweg-ID in BT-10 for B2G routing, and specific German VAT category handling — on top of the 52 EN 16931 mandatory Business Terms. PEPPOL BIS Billing 3.0 adds PEPPOL-specific rules applicable across all PEPPOL countries without German national specifics. Both achieve EN 16931 compliance. For invoices staying within Germany (domestic B2B and B2G), XRechnung is the more precise format — it carries German-specific fields that PEPPOL BIS 3.0 does not include natively. For invoices crossing borders via PEPPOL, PEPPOL BIS Billing 3.0 is the more universally understood format — receivers in Netherlands, Belgium, or France may not support XRechnung CIUS extensions.
| Dimension | XRechnung | PEPPOL BIS Billing 3.0 | Implication for German Businesses |
| Type | Invoice format (XML) | Invoice format (XML) | Both are formats, not networks — transmission method is a separate choice |
| Standard basis | EN 16931 + German CIUS | EN 16931 + PEPPOL CIUS | Both satisfy German B2B mandate; XRechnung has German-specific extensions |
| Geographic scope | Germany only | 40+ PEPPOL countries | PEPPOL BIS for cross-border; XRechnung for domestic (esp. B2G) |
| Leitweg-ID support | Built-in (BT-10, mandatory for B2G) | Not standard; requires extension field | XRechnung preferred for German B2G invoicing |
| Syntax | UBL 2.1 or CII | UBL 2.1 (primary) | CII support varies in non-German PEPPOL systems |
| Transmission via PEPPOL | Yes — XRechnung via PEPPOL works | Yes — native PEPPOL format | Both can go over PEPPOL; PEPPOL BIS is the native format |
| B2G acceptance (German) | Required by ZRE and most OZG-RE portals | Accepted when sent via PEPPOL to PEPPOL-connected portal | XRechnung is the standard; PEPPOL BIS works via PEPPOL |
PEPPOL BIS Billing 3.0 vs XRechnung: Feature-by-Feature Comparison
PEPPOL BIS vs XRechnung on mandatory content: the core 52 EN 16931 Business Terms are identical across both formats — both require invoice number, invoice date, seller and buyer details, supply date, net amounts, VAT breakdowns, and totals. The differences lie in optional and extension fields. XRechnung CIUS adds the BuyerReference field (BT-10) as a conditional requirement for B2G (where it must contain the Leitweg-ID), and adds German-specific VAT handling rules that prevent certain combinations not allowed under German VAT law. PEPPOL BIS Billing 3.0 adds PEPPOL-specific business rules around document-level allowances and charges, specific line-item restrictions, and PEPPOL-required code list values. Neither set of extensions is visible to the human reader — they only matter at the validation and schema level.
PEPPOL BIS vs XRechnung on software support: XRechnung is the mandatory format for German public sector invoicing, so every German B2G-capable invoicing system supports XRechnung. PEPPOL BIS Billing 3.0 is a standard format for PEPPOL cross-border transmission, and PEPPOL access points typically support the relevant format requirements. In practice, most enterprise ERP systems with German e-invoicing modules support both. The selection between them is therefore usually a customer requirement decision, not a software capability decision. Your largest B2G customers (federal and state procurement offices) require XRechnung. Your PEPPOL-connected B2B customers may accept either format. Advintek Norway can help businesses explore e-invoicing integration and digital invoice management solutions suited to their requirements.
Is XRechnung PEPPOL-Compatible? The CIUS Explained
XRechnung CIUS (Core Invoice Usage Specification) is the mechanism by which XRechnung relates to both EN 16931 and PEPPOL. EN 16931 defines the base standard; a CIUS is a country- or sector-specific set of additional rules layered on top. XRechnung is Germany’s national CIUS of EN 16931. PEPPOL BIS Billing 3.0 is PEPPOL’s CIUS of EN 16931. Both are derived from the same base standard, which is why they are structurally similar and why XRechnung can be transmitted over the PEPPOL network without format transformation.
XRechnung via PEPPOL works because PEPPOL’s transport layer is format-agnostic — it routes XML documents without parsing their content. A PEPPOL access point that supports XRechnung wraps the XRechnung XML in a PEPPOL AS4 envelope and routes it to the receiver’s access point. The receiver’s access point delivers the XRechnung XML unchanged. Whether the receiver’s system then validates the XRechnung against the German CIUS rules (beyond the base EN 16931 rules) depends on the receiver’s validation configuration. German federal portals (ZRE) validate fully against XRechnung CIUS; commercial B2B PEPPOL receivers may validate only against base EN 16931 or PEPPOL BIS Billing 3.0 rules. This means XRechnung via PEPPOL for B2G is fully supported; XRechnung via PEPPOL for non-German B2B receivers may generate unexpected CIUS-extension validation warnings.
PEPPOL vs Sending XRechnung by Email: Which Is More Compliant?
PEPPOL or email e-invoice from a compliance perspective: both are equally compliant with the German B2B mandate. The mandate requires the invoice to be transmitted electronically; it does not specify the electronic channel. Email delivery of an XRechnung XML attachment, or email delivery of a ZUGFeRD PDF, satisfies the electronic transmission requirement. PEPPOL transmission of the same invoice also satisfies it. Neither channel is “more compliant” than the other — the format compliance (EN 16931 mandatory fields, correct profile) is what determines compliance, not the delivery mechanism.
The PEPPOL or email decision is therefore operational rather than regulatory. Email is simpler and cheaper for low-volume invoicing: no access point contract, no PEPPOL registration, no integration project. But email has no structured delivery confirmation — if the buyer’s email system bounces the invoice or routes it to spam, you have no automated notification. PEPPOL provides a structured delivery receipt from the receiver’s access point, which is valuable for high-volume invoicing and AP automation. The EN 16931 formats Germany mandate does not mandate delivery confirmation, but large buyers often require it. If your customer’s purchase order terms require electronic invoice delivery confirmation, PEPPOL satisfies that requirement more robustly than email.
Which Should Your Business Choose: PEPPOL or XRechnung?
The PEPPOL vs XRechnung decision framework follows three questions. First: what format does your primary customer base require? If German B2G: choose XRechnung. If cross-border PEPPOL: choose PEPPOL BIS Billing 3.0. If domestic B2B with PDF-familiar customers: choose ZUGFeRD (EN 16931 profile) with the option to add XRechnung for customers who prefer XML. Second: what transmission channel do you need? If email is sufficient (most domestic B2B): email with XRechnung or ZUGFeRD satisfies the mandate. If B2G at volume or cross-border: PEPPOL access point is the efficient solution. Third: does your current ERP or invoicing platform support PEPPOL integration? If yes, PEPPOL BIS Billing 3.0 via PEPPOL may be the most future-proof choice. If not, XRechnung via email satisfies the German mandate without any PEPPOL integration.
For most German SMEs below €800,000 annual turnover, the PEPPOL vs XRechnung question resolves as follows: implement ZUGFeRD or XRechnung generation in your existing accounting software, transmit by email, and satisfy the 2028 mandate with minimal additional investment. For large German enterprises with significant B2G revenue or cross-border invoice flows, a PEPPOL access point Germany integration with PEPPOL BIS Billing 3.0 or XRechnung capability is the more scalable and future-proof solution. The EN 16931 formats Germany mandate is flexible enough to accommodate both paths — the regulatory requirement does not push either SMEs or enterprises toward PEPPOL unless operational or commercial requirements do.
| Business Profile | Recommended Format | Transmission Channel | Rationale |
| German SME, B2B only, <€800K turnover | ZUGFeRD (EN 16931 profile) | Simplest implementation; PDF familiarity; satisfies 2028 mandate | |
| German SME, B2B only, >€800K turnover | ZUGFeRD or XRechnung | 2027 deadline; format choice based on software support; email sufficient | |
| German business with B2G revenue | XRechnung (mandatory for B2G) | PEPPOL or ZRE portal | XRechnung required for federal B2G; PEPPOL more efficient at volume |
| German enterprise, cross-border invoicing | PEPPOL BIS Billing 3.0 (cross-border) + XRechnung (domestic B2G) | PEPPOL | PEPPOL BIS for international; XRechnung for domestic B2G; one PEPPOL integration covers both |
| German business in automotive/logistics supply chain | XRechnung or PEPPOL BIS 3.0 (per OEM requirement) | PEPPOL or EDI (per OEM requirement) | Large OEMs often specify format and channel — follow customer requirement |
Frequently Asked Questions
1. Can I send PEPPOL BIS Billing 3.0 via email instead of PEPPOL?
Yes — PEPPOL BIS Billing 3.0 is a format, not a delivery method. You can email a PEPPOL BIS Billing 3.0 XML file as an attachment. Whether the receiver’s system validates it as a PEPPOL BIS Billing 3.0 document depends on their configuration.
2. Does PEPPOL vs XRechnung matter for the 2027 German B2B mandate?
Both satisfy the mandate equally. XRechnung, PEPPOL BIS Billing 3.0, and ZUGFeRD (EN 16931+) are all valid E-Rechnungen under §14 UStG. The mandate does not prefer one EN 16931 format over another.
3. What is XRechnung CIUS in simple terms?
XRechnung CIUS is the set of additional rules that Germany adds to the base EN 16931 European standard to create the German national e-invoice format. Think of EN 16931 as the foundation and XRechnung CIUS as the German-specific layer on top.
4. My PEPPOL receiver rejects my XRechnung — what is happening?
The receiver’s PEPPOL access point may be validating against PEPPOL BIS Billing 3.0 rules rather than XRechnung CIUS rules. Ask the receiver whether they accept XRechnung, or switch to PEPPOL BIS Billing 3.0 format for that counterparty.
5. Is XRechnung via PEPPOL better than XRechnung via email for B2G?
For high-volume B2G invoicing, PEPPOL provides structured delivery confirmation and automated portal processing that email does not. For low-volume B2G (fewer than 20 invoices per month), direct portal submission via ZRE may be simpler than maintaining a full PEPPOL access point integration.
Source by:
Image by Gemini
