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.

XRechnung vs ZUGFeRD vs Plain PDF: Decision Matrix

Choosing between XRechnung, ZUGFeRD (Factur-X), and plain PDF depends on recipient mandate rules, visual readability needs, and ERP processing capabilities in Germany.

1. XRechnung: German B2G Mandatory Specification

XRechnung is KoSIT's German Core Invoice Usage Specification (CIUS) for invoices sent to public-sector recipients. It contains structured invoice data in UBL 2.1 or UN/CEFACT CII syntax and does not include an embedded PDF visual layer.

• Syntax: Pure XML (UBL 2.1 or CII D16B).
• Routing: Public-sector workflows generally require the buyer reference (Leitweg-ID in BT-10) for routing through portals such as ZRE and OZG-RE.
• Validation: Validated against KoSIT Schematron rules prior to submission.

2. ZUGFeRD (Factur-X): Hybrid Standard for B2B and Flexible Processing

ZUGFeRD is the German name for the jointly developed ZUGFeRD/Factur-X standard. It combines a human-readable PDF/A-3 visual document with embedded structured invoice data based on the EN 16931 semantic model. Humans can inspect the PDF while accounting systems process the XML.

• Structure: PDF/A-3 container with embedded factur-x.xml.
• Profiles: Depending on the version, profiles include MINIMUM, BASIC, EN 16931, and EXTENDED.
• Use cases: Suitable for B2B and, where the recipient's rules permit it, B2G workflows.

3. Plain PDF Invoices: Non-Compliant Unstructured Data

Unstructured PDF invoices contain visual layout elements but lack structured invoice data. Under German e-invoicing rules, a plain PDF is not an E-Rechnung in the structured sense, although transitional rules and recipient consent can still allow its use.

• Processing: Requires OCR extraction, resulting in potential rounding and tax classification errors.
• Compliance Status: Not a substitute for the structured format required by a public-sector portal or, after the applicable transition period, by a domestic B2B issuing mandate.

German E-Invoicing Mandate Roadmap

Under current German tax legislation, businesses must align their invoicing workflows with the following timeline:

• January 1, 2025: Domestic businesses must be able to receive E-Rechnungen; an email inbox is sufficient for receipt.
• January 1, 2027: For domestic B2B transactions, the transition period ends for issuers whose previous-year turnover exceeds EUR 800,000.
• January 1, 2028: The transition period ends for other domestic B2B issuers, subject to statutory exceptions.

How Invoice Converter Simplifies Format Conversion

Invoice-Converter.com enables organizations to convert existing PDF invoices into validated XRechnung or ZUGFeRD XML files without replacing their core billing or ERP software:

• PDF to XRechnung: Extract header, tax, line items, and Leitweg-ID into pure XML.
• PDF to ZUGFeRD: Embed validated EN 16931 XML into PDF/A-3 containers.
• Automated Validation: Check outputs against official Schematron and EN 16931 rules before sending.

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.