# Germany e-invoicing update 2026: what changed and what did not

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

A practical Germany e-invoicing update for April 2026: the BMF FAQ refresh, the dates that still hold, and the workflow decisions teams should make before 2027.

## Article overview

        This article explains Germany e-invoicing update 2026: what changed and what did not 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.

This page is for teams that know Germany is moving toward mandatory domestic B2B e-invoicing and want a practical update as of April 20, 2026.

The important news is not a surprise delay or a new deadline. Germany is now in the implementation window: businesses have been required to receive structured e-invoices since January 1, 2025, the BMF FAQ was updated on March 23, 2026, and the next major deadline remains January 1, 2027 for issuers whose prior-year turnover exceeded EUR 800,000.

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

## What changed in 2026

For What changed in 2026, review these points before moving on.

- The BMF FAQ was updated in March 2026, which is useful because teams now have a more current official explanation of the domestic B2B obligation and the transition rules.
- The market conversation has shifted from “Is this really happening?” to “Can our ERP, extraction, mapping, and validation process handle live invoice volumes before 2027?”
- More businesses are treating 2026 as the year to deliver structured invoicing capability instead of waiting for the next legal deadline.
## What did not change

For What did not change, review these points before moving on.

- Domestic B2B recipients in Germany still need to be able to receive structured e-invoices from January 1, 2025.
- The general transition window for alternative invoice forms still runs through December 31, 2026, with a longer runway through December 31, 2027 for issuers whose prior-year turnover does not exceed EUR 800,000.
- A plain PDF is still not the target structured e-invoice format.
- Human review is still necessary for weak source invoices, missing buyer data, and validation failures.
## What this means for finance and ERP teams now

For What this means for finance and ERP teams now, this sequence gives the practical order of work.

- Identify which German sales flows are in scope and which recipients already expect structured formats.
- Decide whether each flow should land in XRechnung, ZUGFeRD, or another EN 16931-compatible syntax.
- Add validation and exception handling before go-live rather than after the first rejected invoices arrive.
- Train operations teams on buyer references, tax IDs, payment data, and the difference between a readable PDF and structured invoice data.
## Where teams still get it wrong

For Where teams still get it wrong, review these points before moving on.

- Treating 2026 as a waiting year instead of an implementation year.
- Assuming a readable PDF is enough because the recipient can visually inspect it.
- Treating validation as a final checkbox instead of part of the invoice workflow.
- Underestimating the workload of rejected invoices and leaving exception ownership unclear.
## Official source to monitor

Use the [BMF FAQ on mandatory e-invoicing](https://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.html), updated March 23, 2026, as the official reference point. For the wider European context, pair it with your own country-by-country rollout map rather than assuming Germany represents every market.

## Use 2026 to prove the workflow before 2027

Invoice-Converter.com helps teams test structured German invoice output from existing PDF or ERP flows, validate the result, and build an exception process before the next issuing deadline.

[Test a German e-invoice workflow](/en/pdf-to-xrechnung)

## FAQ

### Did Germany move the 2027 and 2028 issuing thresholds?

Not in the official materials reviewed here. As of April 20, 2026, the milestones remain January 1, 2027 for issuers whose prior-year turnover exceeded EUR 800,000 and January 1, 2028 for all remaining issuers after the transition period.

### Is 2026 still a transition year?

Yes, but it should be treated as an implementation year. Waiting until late 2026 would compress mapping, validation, training, and exception handling into an avoidable rush.

### Should teams replace the ERP first or add a bridge process?

Many teams move faster with a bridge process that converts, validates, and reviews invoices beside the current ERP while the deeper ERP changes are still being planned.

## Official references

- [BMF E-Rechnung FAQ](https://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.html)
- [Federal Central Tax Office](https://www.bzst.de/)