Which e-invoice formats are usable in Germany in 2026?

First answer: what counts as an e-invoice in Germany

The German BMF FAQ defines an e-invoice as a structured electronic format that enables electronic processing and complies with EN 16931 or is interoperable with it. A plain PDF is still an electronic document, but since January 1, 2025 it is classified as a “non-e-invoice” (sonstige Rechnung), not as a structured e-invoice.

That is why the practical question is not "Can I email a PDF?" but "Can my process generate structured invoice data that the recipient can process and a validator can check?"

The formats most teams should care about

For The formats most teams should care about, review these points before moving on.

• XRechnung: the standard choice for many German public-sector workflows and other XML-first processes where the recipient needs structured data rather than a PDF-led document.
• ZUGFeRD / Factur-X: useful when you need a human-readable PDF plus embedded structured invoice data in one document.
• UBL: relevant for PEPPOL or recipient channels that standardize on UBL syntax.
• CII: relevant where your tooling or recipient ecosystem is built around Cross Industry Invoice syntax.

How to choose the right format

For How to choose the right format, this sequence gives the practical order of work.

1. Start with the recipient requirement, not your preferred format. Some recipients or channels are explicit.
2. Choose XRechnung when the target process is a German public-sector workflow or another XML-first process that does not rely on the PDF itself.
3. Choose ZUGFeRD when the recipient wants a readable PDF and your team still needs structured data for automation and validation.
4. Choose UBL or CII when your transmission channel, PEPPOL setup, or trading partner ecosystem already standardizes on that syntax.
5. Validate the output with the relevant rule set before you decide the format is ready for production.

What does not solve the problem on its own

For What does not solve the problem on its own, review these points before moving on.

• Sending a standard PDF and assuming it has become compliant because it was created electronically.
• Picking one format globally without checking the recipient channel or buyer requirement.
• Manually editing XML after validation failures instead of fixing the source data or mapping logic.
• Skipping a review step for invoices with weak source quality, discounts, mixed VAT treatments, or missing buyer identifiers.

Official baseline for Germany

Use the BMF FAQ on Germany’s mandatory e-invoicing rules from January 1, 2025 as the legal baseline for domestic B2B invoicing. For practical rollout, pair that legal view with your recipient requirements, validator output, and internal exception process.

Test the format before you lock the rollout

Invoice-Converter.com lets teams test XRechnung, ZUGFeRD, and UBL conversion paths against real invoice inputs so you can decide based on recipient fit and validator results, not guesswork.