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

- Date: 2026-04-20
- Reading time: 7 min read

A practical Germany format guide for April 2026: when to use XRechnung, ZUGFeRD, UBL or CII, what still counts as a non-structured invoice, and how to choose safely.

## Article overview

        This article explains Which e-invoice formats are usable in 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.

This guide is for businesses invoicing German customers that need a practical answer, not a format list copied from standards documents.

As of April 20, 2026, Germany already requires businesses to be able to receive structured e-invoices for domestic B2B transactions. The issuing transition remains time-limited, so 2026 is the year to decide which structured formats you can actually produce, validate, and support in operations.

        ## 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.

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

The German BMF FAQ ties the legal definition to a structured electronic format that enables electronic processing and is compliant with EN 16931 or interoperable with it. A plain PDF is still a digital document, but in this context it is generally treated as another type of invoice, not the target structured e-invoice format.

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

## The formats most teams should care about

- **XRechnung**: the strongest fit for German public-sector and strict XML workflows where the recipient expects structured German invoice syntax.
- **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

- Start with the recipient requirement, not your preferred format. Some recipients or channels are explicit.
- Choose XRechnung when the target process is German public-sector or another strict XML workflow that does not rely on the PDF itself.
- Choose ZUGFeRD when the recipient wants a readable PDF and your team still needs structured data for automation and validation.
- Choose UBL or CII when your transmission channel, PEPPOL setup, or trading partner ecosystem already standardizes on that syntax.
- 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

- 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 mandatory e-invoicing from January 1, 2025](https://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.html) 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 trial XRechnung, ZUGFeRD, and UBL conversion paths against real invoice inputs so you can decide based on recipient fit and validator results, not guesswork.

[Compare conversion paths](/en/convert)