Technical June 8, 2026 11 min read

XRechnung vs ZUGFeRD: Choosing the Right E-Invoice Format in Germany

Germany accepts two structured e-invoice formats under its mandate — XRechnung and ZUGFeRD. Choosing the wrong one costs time, money, and compliance headaches. This technical guide breaks down every difference so you can decide with confidence.

InvoStaq Engineering Team

E-invoicing standards & technical architecture

Germany's e-invoicing mandate is built on a format-based approach, not a network-based one like Belgium's Peppol mandate. This means any structured electronic invoice that complies with the European standard CEN EN 16931 is legally valid. In practice, two formats dominate the German market: XRechnung and ZUGFeRD.

Since January 1, 2025, every business in Germany must be able to receive structured e-invoices. From January 2027, businesses with revenue exceeding €800,000 must also issue them — with all remaining businesses following by January 2028. Choosing the right format now is critical for a smooth transition.

2 Formats

XRechnung & ZUGFeRD

3.5M+

Businesses affected

EN 16931

Core EU standard

Jan 2027

Issuance mandate (>€800K)

Germany's E-Invoice Format Landscape

Unlike countries that mandate a single format or network, Germany's Wachstumschancengesetz (Growth Opportunities Act) defines an e-invoice as any structured electronic format compliant with CEN EN 16931 — the European Norm for the semantic data model of e-invoices. This means PDFs, scanned images, and even Word documents do not qualify. Only machine-readable structured data counts.

What Qualifies as an E-Invoice in Germany?

XRechnung

Pure XML format based on UN/CEFACT Cross Industry Invoice (CII). Mandatory for B2G since 2020.

ZUGFeRD 2.x (Comfort/Extended/XRechnung profile)

Hybrid PDF/A-3 with embedded XML. Profiles at Comfort level or above are EN 16931 compliant.

Factur-X

The Franco-German standard identical to ZUGFeRD at technical level. Accepted as EN 16931 compliant.

PDF, Word, scanned documents

Not structured data — not accepted as e-invoices under the mandate. Can still be used during transition only with recipient consent.

ZUGFeRD Minimum/Basic WL profiles

These lower profiles do not contain sufficient structured data to meet EN 16931 requirements.

The CEN EN 16931 standard defines the semantic data model — the required fields and business rules — for European e-invoices. Both XRechnung and ZUGFeRD implement this standard, but they do so in fundamentally different ways. Understanding these differences is essential for choosing the right approach for your business.

XRECHNUNG VS ZUGFERD — FORMAT ARCHITECTUREXRechnungPure XML · CII Format<rsm:CrossIndustryInvoice><ram:SellerTradeParty>...</><ram:BuyerTradeParty>...</><ram:ApplicableHeaderTrade...></rsm:CrossIndustryInvoice>B2G MandatoryCEN EN 16931 CoreMachine-readable onlyValidated by KoSITZRE/OZG-RE portalsZUGFeRD 2.xHybrid PDF/A-3 + XMLPDF/A-3Visual invoiceHuman-readableEmbedded XMLfactur-x.xmlMachine-readableB2B PreferredFactur-X compatibleHuman + machine readable5 profiles availableGoBD compliantCEN EN 16931Shared Core StandardXRechnungB2G StandardZUGFeRDB2B PopularEN 16931Core StandardJan 2027+Compliance Target

XRechnung Deep Dive

XRechnung ("X-Invoice") is Germany's national implementation of the CEN EN 16931 standard. Developed by KoSIT (Koordinierungsstelle für IT-Standards) under the Federal Ministry of the Interior, it is the mandatory format for B2G (Business-to-Government) invoicing in Germany since November 2020.

Pure XML Format

XRechnung is a pure XML file based on the UN/CEFACT Cross Industry Invoice (CII) syntax. There is no visual component — the invoice data is entirely machine-readable. For human viewing, XSL stylesheets transform the XML into a PDF or HTML visualization, but this rendering is not part of the standard itself.

KoSIT Validation

Every XRechnung must pass KoSIT's official validation tool (the XRechnung Schematron rules). This checks not just XML schema compliance but also business rules — like ensuring VAT calculations are mathematically correct and mandatory fields (Leitweg-ID for B2G, payment terms, tax categories) are populated.

B2G Delivery via ZRE/OZG-RE

For government invoices, XRechnung files are submitted through the ZRE (Zentrale Rechnungseingangsplattform) for federal entities or OZG-RE platforms for state/municipal bodies. Each entity has a Leitweg-ID (routing ID) that directs the invoice to the correct department.

Version Management

XRechnung follows a strict versioning cycle. The current version (3.0.x) is released biannually by KoSIT, with transition periods allowing both old and new versions. Your ERP or compliance platform must track version updates to avoid rejection from government portals.

When XRechnung Is the Right Choice

XRechnung is the only option for B2G invoicing. If your business invoices federal, state, or municipal government entities in Germany, you must use XRechnung submitted through the appropriate ZRE or OZG-RE portal. For B2B, XRechnung is a valid choice if your trading partners' systems can process pure XML — but the lack of a human-readable component means recipients without automated processing may prefer ZUGFeRD.

ZUGFeRD Deep Dive

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is Germany's hybrid e-invoicing format. A ZUGFeRD 2.x invoice is a PDF/A-3 document with a structured XML file (factur-x.xml) embedded as an attachment. This dual nature — human-readable PDF plus machine-readable XML — makes it uniquely practical for the German B2B market.

ZUGFeRD Profiles Explained

ZUGFeRD defines five profiles, each with increasing levels of structured data. The profile determines how much information is in the embedded XML versus only in the visual PDF:

1

Minimum

Not Compliant

Basic reference data only (invoice number, date, total). Insufficient for EN 16931 compliance. Used primarily as a bridge format for businesses beginning their e-invoicing journey.

2

Basic WL (Without Lines)

Not Compliant

Adds seller/buyer data and VAT breakdown but omits line-item detail. Still below EN 16931 requirements. Suitable for simplified invoicing only.

3

Basic

Not Compliant

Includes line items with descriptions and amounts. Close to EN 16931 but missing some mandatory business terms. Not sufficient for the German mandate.

4

Comfort (EN 16931)

EN 16931 ✓

Full CEN EN 16931 compliance. Contains all mandatory business terms, tax calculations, and payment information. This is the minimum profile accepted under Germany's e-invoicing mandate.

5

Extended

EN 16931 ✓

Superset of Comfort with additional fields for industry-specific data (e.g., construction, logistics). Fully EN 16931 compliant plus extra structured data for advanced automation.

XRechnung Profile

EN 16931 ✓

A special ZUGFeRD profile that embeds an XRechnung-formatted XML inside the PDF/A-3 container. This gives you the best of both worlds: visual PDF for humans, XRechnung XML for machines and B2G submission.

ZUGFeRD & Factur-X: The Franco-German Alliance

ZUGFeRD 2.x and France's Factur-X standard are technically identical. The FeRD (Forum elektronische Rechnung Deutschland) and France's FNFE-MPE jointly developed the specification. A ZUGFeRD Comfort invoice generated in Germany can be processed by a Factur-X system in France and vice versa. This interoperability is a significant advantage for businesses operating across the Franco-German border.

Head-to-Head Comparison

Here's how XRechnung and ZUGFeRD stack up across every dimension that matters for your implementation decision:

CriterionXRechnungZUGFeRD 2.x
File formatPure XML (CII)PDF/A-3 + embedded XML
Human readableNo (needs XSLT rendering)Yes (visual PDF included)
Machine readableYes (native XML)Yes (embedded factur-x.xml)
B2G accepted✓ Mandatory✓ XRechnung profile only
B2B accepted✓ (if EN 16931 compliant)✓ (Comfort+ profiles)
File sizeSmall (5–50 KB typical)Larger (PDF + XML, 100 KB–2 MB)
Validation toolKoSIT ValidatorMustangproject / FeRD tools
ERP integrationXML parsing onlyPDF viewer + XML parsing
Archiving (GoBD)XML archived (8 years)PDF/A-3 archived (8 years)
Cross-borderEU CII syntax (broad support)Factur-X compatible (FR/DE)
Learning curveHigher (XML-only)Lower (familiar PDF + XML)

Performance & Processing Considerations

From a technical performance perspective, XRechnung's pure XML format offers faster parsing — critical for businesses processing thousands of invoices daily. ZUGFeRD's PDF container adds overhead, but the visual component eliminates the need for separate invoice visualization systems.

For automated ERP processing, both formats ultimately provide the same structured data. The difference is in the delivery mechanism: XRechnung gives you the data directly, while ZUGFeRD wraps it in a PDF that also serves as the human-readable archive. For GoBD-compliant archiving, both are equally valid — the 8-year retention requirement applies to the structured data, and both formats satisfy this.

Choosing Your Format

The right format depends on your business profile, trading partners, and technical capabilities. Here's a decision framework:

You invoice government entities → XRechnung

Non-negotiable. German federal, state, and municipal bodies require XRechnung via ZRE/OZG-RE portals. Use the XRechnung format directly or the ZUGFeRD XRechnung profile if you want a visual PDF backup for your own records.

You trade primarily B2B within Germany → ZUGFeRD Comfort+

ZUGFeRD Comfort or Extended is the pragmatic choice for most B2B scenarios. Your trading partners get a visual PDF they can open in any PDF viewer, while their ERP systems can extract the embedded XML for automated processing. The dual nature eliminates the 'my customer can't read your format' problem.

You do both B2G and B2B → ZUGFeRD with XRechnung profile

The ZUGFeRD XRechnung profile gives you a single format that works everywhere. The embedded XML is XRechnung-compliant (accepted by ZRE/OZG-RE), while the PDF container makes it B2B-friendly. InvoStaq recommends this approach for businesses serving both sectors.

High-volume automated processing → XRechnung

If you process 10,000+ invoices monthly and your entire supply chain has automated ERP systems, XRechnung's lean XML format reduces processing overhead. The smaller file sizes and direct XML parsing are advantages at scale — but only if your recipients can handle XML-only invoices.

Cross-border with France → ZUGFeRD / Factur-X

ZUGFeRD and Factur-X are technically identical. If you trade heavily with French companies, ZUGFeRD Comfort invoices will be natively understood by their Factur-X-capable systems. This bilateral interoperability is a significant advantage over XRechnung for Franco-German trade.

Migration Strategy: Getting Ready for January 2027

If your business exceeds €800,000 in annual revenue, you must be ready to issue structured e-invoices by January 2027. Here is a practical migration timeline:

1Audit your current invoice format and ERP capabilities — identify gaps in EN 16931 compliance (Q2 2026)
2Select your target format (XRechnung, ZUGFeRD Comfort, or ZUGFeRD XRechnung profile) based on your business profile
3Implement or upgrade your ERP module — SAP (SAP Document Compliance), Dynamics 365 (InvoStaq plugin), Odoo (EDI module)
4Run test invoices through the KoSIT Validator (for XRechnung) or FeRD validation tools (for ZUGFeRD) in Q3 2026
5Coordinate with your top 20 trading partners to ensure they can receive your chosen format
6Set up GoBD-compliant archiving for 8-year retention of all structured invoices
7Go live with parallel running (old + new format) in Q4 2026, then cut over by January 2027

Don't Wait for January 2028

Even if your revenue is below €800,000, the January 2028 deadline for all businesses is closer than it appears. ERP vendor backlogs, consultant availability, and testing cycles mean starting 12–18 months before your deadline is prudent. Germany's receiving mandate has been live since January 2025 — if you can receive e-invoices, you already have half the infrastructure. Building the issuance capability should be your 2026 priority.

XRechnung & ZUGFeRD — One Platform

InvoStaq generates, validates, and routes both formats automatically. Our AI selects the correct format per recipient — XRechnung for B2G, ZUGFeRD for B2B — from a single API call.