XRechnung vs ZUGFeRD vs PDF: Decision Guide for Germany in 2026

Article overview

This article explains XRechnung vs ZUGFeRD vs PDF: Decision Guide for Germany in 2026 as a practical reference for European e-invoicing. It defines the topic in plain language, places it in the compliance context, and connects the explanation to invoice formats such as XRechnung, ZUGFeRD/Factur-X, UBL, and CII.

Use the article as a starting point before changing a finance or ERP workflow: identify the applicable country rule or standard, decide which structured format is expected, validate the generated XML, and keep a documented exception process for invoices that require manual review.

Which invoice format fits your workflow in Germany?

Electronic invoicing has become a crucial aspect of modern business operations, particularly in Germany where specific standards and regulations are in place. This article provides a comprehensive comparison of three prevalent invoicing formats: XRechnung, ZUGFeRD, and traditional PDF invoices. Understanding the differences between these formats is essential for businesses to ensure compliance, streamline operations, and optimize their invoicing processes.

If you need the formal rules, start with our XRechnung standards guide. If you already know your target format, jump straight to PDF to XRechnung or PDF to ZUGFeRD. This page is for the decision in between.

1. XRechnung: The Standard for German B2G Invoicing

XRechnung is a structured, XML-based e-invoicing standard specifically designed for business-to-government (B2G) transactions in Germany. It's mandatory for all invoices sent to federal public authorities and is increasingly being adopted by regional and local governments.

Key Features of XRechnung:

• Format: Pure XML (no human-readable component)
• Use Case: Mandatory for B2G invoicing to German federal authorities
• Standard: Based on the European standard EN 16931
• Syntaxes: Supports UBL (Universal Business Language) and CII (Cross Industry Invoice)
• Leitweg-ID: Requires a Leitweg-ID for routing invoices within the public sector
• Automation: Enables fully automated invoice processing

2. ZUGFeRD: The Hybrid Format for B2B and Potential B2G

ZUGFeRD (Zentraler User Guide für elektronische Rechnungen in Deutschland) is a hybrid e-invoicing format that combines a human-readable PDF/A-3 document with an embedded XML file containing structured invoice data. It's primarily used for business-to-business (B2B) transactions but can also be accepted by some public sector entities if they support it.

Key Features of ZUGFeRD:

• Format: Hybrid (PDF/A-3 with embedded XML)
• Use Case: Primarily B2B, potentially B2G (if accepted)
• Standard: Compliant with the European standard EN 16931
• Profiles: Offers different profiles (Basic, Comfort, Extended) with varying levels of data richness
• Human-Readable: Provides a visual representation of the invoice (PDF) alongside machine-readable data (XML)
• Archiving: The PDF/A-3 component ensures long-term archiviability

3. PDF Invoices: The Traditional Format Losing Ground

PDF invoices have long been the standard for electronic invoicing due to their ease of creation and visual familiarity. However, they lack the structured data required for automated processing and are no longer sufficient for B2G transactions in Germany. They can still be used for B2B transactions if agreed upon.

Key Features of PDF Invoices:

• Format: PDF (Portable Document Format)
• Use Case: Traditionally used for B2B and B2G, now generally not acceptable for German federal B2G
• Standard: No specific e-invoicing standard
• Human-Readable: Easily readable by humans
• Machine-Readability: Requires OCR (Optical Character Recognition) for data extraction, which can be error-prone
• Automation: Not suitable for fully automated processing without additional tools

XRechnung vs. ZUGFeRD vs. PDF: Head-to-Head Comparison

Feature	XRechnung	ZUGFeRD	PDF
Format	XML only	Hybrid (PDF/A-3 + XML)	PDF
Primary Use Case	Mandatory for German B2G	B2B, potentially B2G	B2B (if agreed), not B2G
Human Readability	No	Yes (PDF)	Yes
Machine Readability	Yes (XML)	Yes (XML)	No (Requires OCR)
Standard	EN 16931 based	EN 16931 compliant	No specific standard
Automation	Fully automated	Fully automated	Limited automation

Choosing the Right Format: Key Considerations

The optimal invoicing format depends on your specific business context:

• B2G Transactions: If you invoice German federal government entities, XRechnung is mandatory.
• B2B Transactions: For B2B, you have more flexibility. ZUGFeRD is a good choice if you want a human-readable format alongside machine-readable data. PDF can still be used if both parties agree, but it's not recommended for automated processing.
• Automation Needs: If you prioritize fully automated invoice processing, XRechnung (for B2G) or ZUGFeRD (for B2B) are the best options.
• Recipient Requirements: Always consider the specific requirements of your invoice recipients. Some may have preferences or limitations regarding accepted formats.
• Future-Proofing: With the trend towards increased e-invoicing adoption and potential B2B mandates in the future, transitioning to structured formats like XRechnung or ZUGFeRD can be a strategic move.

How Invoice-Converter.com Can Help

Invoice-Converter.com provides comprehensive solutions to simplify your e-invoicing processes, regardless of the format you choose:

• PDF to XRechnung Conversion: Our core service accurately converts your PDF invoices into compliant XRechnung files, ensuring seamless B2G transactions.
• PDF to ZUGFeRD Conversion: We can also convert your PDFs to ZUGFeRD, providing a hybrid solution for your B2B needs.
• XRechnung to PDF: Do you receive XRechnung invoices that need to be converted to PDF to ensure they are readable by humans? We also provide this service.
• Format Validation: We validate your converted files to ensure they meet all the necessary requirements and standards.

How to use this guide

Use the article as a starting point before changing a finance or ERP workflow: identify the applicable country rule or standard, decide which structured format is expected, validate the generated XML, and keep a documented exception process for invoices that require manual review.