XRechnung vs ZUGFeRD: Which e-invoice format should you use?

Last updated: 25 de September de 2026

The hardest question one can ask themselves since “To be or not to be”, am I right? The upcoming e-invoicing regulation for B2B transactions in Germany has everyone on edge, which is completely understandable. I mean, we are talking a full 180º change in how German businesses operate.

You do know your stuff — mostly because every compliance SaaS has thrown tons of information at you — and you feel almost ready. However, within the vortex of the regulation, there is a question that still stands: which format suits the needs of my company better? Both XRechnung and ZUGFeRD (version 2.1+) comply with the European standard EN 16931, and both fulfill the legal requirements of Germany’s e-invoicing mandate. However, they are not interchangeable.

Let’s find the answer together, shall we?

Table of contents Is it truly your choice? Let your clients decide Sending to a German Public Administration? Use XRechnung Sending to a German B2B client? You can choose the comfort of ZUGFeRD Sending your invoices cross-border? Meet the secret third option: Peppol BIS 3.0 At a Glance: XRechnung vs ZUGFeRD vs Peppol The road to format management happiness: Automate the process

Is it truly your choice? Let your clients decide

The biggest misconception in B2B invoicing is assuming the sender picks the standard. In reality, compliance is defined at the point of ingestion.

Here is a chart that will give you a quick answer to your question:

Where is your invoice going?
PUBLIC SECTOR (Federal / State)	GERMAN PRIVATE ENTERPRISE	CROSS-BORDER / MULTINATIONAL
Requires strict pure-data XML	Needs visual PDF for AP & raw XML	Requires standard network routing
XRechnung (UBL or CII XML)	ZUGFeRD 2.1 (Profile: EN 16931)	Peppol BIS Billing 3.0 (via Peppol Network)

Now let’s dig a little deeper. As you just saw, depending on your use case there is one format or the other recommended (or even — spoiler alert — mandatory).

Sending to a German Public Administration? Use XRechnung

If your customer is a German federal authority, state administration, or municipal entity (basically, if it is a B2G transaction), XRechnung is mandatory. You can take my word for it, but let me explain why.

Under public procurement law (E-Rechnungs-Verordnung), German public administrations require a pure, structured XML file (no human-designed PDF visual layer allowed as the primary document). Furthermore, these invoices require specific routing codes known as a Leitweg-ID to route the document to the correct department within public portals like ZRE or OZG-RE.

• The Syntax: XRechnung can be expressed in either UBL (Universal Business Language) or UN/CEFACT CII (Cross Industry Invoice).

But what if you are stubborn or you just make a mistake and send a ZUGFeRD invoice? Prison.

Just kidding. In reality, if the public-sector system expects a native XML invoice that complies with specific federal business rules, a standard hybrid PDF invoice will simply be rejected.

So, basically: wrong format, rejected invoice.

Sending to a German B2B client? You can choose the comfort of ZUGFeRD

If you are invoicing a standard private German company — especially an SMB or mid-market firm where finance teams still review invoices manually — ZUGFeRD is the practical gold standard.

ZUGFeRD is a hybrid format that packages a human-readable PDF/A-3 document with an embedded machine-readable XML data stream inside. If your buyer has upgraded to an automated ERP, their system extracts and books the raw XML without human intervention. If they are still manually reviewing purchases, their accounts payable team simply opens the PDF and reads it normally.

One may call it a win-win situation.

Sending your invoices cross-border? Meet the secret third option: Peppol BIS 3.0

If you are dealing with multinational enterprises or customers in other European countries (e.g., France, Belgium, Scandinavia), point-to-point email attachments of XRechnung or ZUGFeRD won’t suffice.

Large buyers and European trade partners route invoices through the Peppol eDelivery Network. Peppol uses Peppol BIS Billing 3.0 (a UBL-based format mapped directly to EN 16931). It provides verified sender and receiver identification, end-to-end delivery tracking, and zero reliance on spam-vulnerable email attachments.

At a Glance: XRechnung vs ZUGFeRD vs Peppol

Feature	XRechnung	ZUGFeRD 2.1	Peppol BIS Billing 3.0
Document Type	Pure structured data (XML)	Hybrid (PDF/A-3 with embedded XML)	Pure structured data (UBL XML)
Human Readable?	No (requires viewer software)	Yes (standard PDF viewer)	No (parsed by recipient software)
Primary Target	German B2G (Public Sector)	German domestic B2B	Pan-European B2B & B2G
Mandate Ready?	Yes (EN 16931 CIUS compliant)	Yes (Only with EN 16931 profile)	Yes (EN 16931 compliant)
Delivery Mechanism	Portals (ZRE/OZG-RE), Peppol, Email	Email attachment, API	Peppol Access Point

The road to format management happiness: Automate the process

Let’s be real, most finance or administration teams already understand these three use cases. The difficult part is having to remember which use case they are dealing with, and managing them manually can easily lead to human error.

The solution? Find a platform that shares your vision: you shouldn’t have to be a format expert to get paid.

Here is where B2Brouter can help you.

Instead of forcing your accounting team or developers to build complex conversion rules for UBL, CII, and PDF/A-3, B2Brouter decouples your invoicing data from the delivery standard. Meaning that you need to configure your recipient preferences once and our system — either via API or using the platform directly — automatically routes the required format every time you create an invoice for said recipient.

Furthermore, when you add a customer to your B2Brouter directory, you set their delivery channel (e.g., German Federal Authority with Leitweg-ID, private SMB via email, or Enterprise via Peppol ID). B2Brouter automatically compiles the exact document required.

In the end, the 2027 e-invoicing mandate isn’t about memorizing XML schemas — it’s about making sure your billing process remains automated, compliant, and friction-free. Stop worrying about whether to send an XRechnung XML, a ZUGFeRD PDF, or a Peppol document.

You pick the recipient; B2Brouter picks the format.