FISCAL SOLUTIONS...
News
Public Germany Author: Ivana Picajkić
Germany is expanding the role of XRechnung as a core structured e-invoicing format, moving from public-sector use to a mandatory standard for domestic B2B transactions between 2025 and 2028, based on EU Directive 2014/55/EU and national legislation. Businesses must adapt their systems and processes to handle XML-based invoices, ensure compliance with EN 16931 standards, and manage proper transmission, validation, and archiving to meet VAT and audit requirements.
Category:

Fiscal subject related

Views: 20
Content accuracy validation date: 24.04.2026
Content accuracy validation time: 08:26h

Germany is strengthening its e-invoicing framework by making X-Rechnung increasingly important for both public-sector and private-sector invoicing. Originally introduced as the official electronic invoice format for public authorities, X-Rechnung is now becoming a central part of Germany’s broader VAT compliance and digitalization strategy, with domestic B2B e-invoicing being phased in between 2025 and 2028.

X-Rechnung is Germany’s official structured electronic invoice format. It is an XML-only invoice standard based on the European standard EN 16931, which means it is made for automatic processing by systems rather than for human reading. Unlike hybrid formats such as ZUGFeRD, X-Rechnung does not include a PDF component.

X-Rechnung is a key part of Germany’s digital invoicing framework. It was first developed for Business-to-Government (B2G) invoicing, where a single standardized format was needed for public administrations. Over time, it has evolved into a much broader compliance tool and is now being extended into the domestic B2B sphere, meaning that businesses in Germany must prepare for a future in which structured e-invoices become the standard form of invoicing.

The legal basis for X-Rechnung combines EU law and German national law.

At EU level, the foundation is Directive 2014/55/EU on electronic invoicing in public procurement, which led to the creation of EN 16931, the European standard defining the semantic model for electronic invoices. The directive requires public entities across the EU to be able to receive and process compliant e-invoices.

At German level, the directive was implemented through the E-Rechnungsgesetz and E-Rechnungsverordnung, which define an electronic invoice as one issued, transmitted, and received in a structured electronic format that allows automatic processing. As a result, unstructured formats such as PDF or paper do not qualify as electronic invoices under this framework. The law also established X-Rechnung as the standard for invoicing public bodies.

In addition, Germany’s Growth Opportunities Act 2024 amended the VAT framework to gradually introduce mandatory structured e-invoicing for domestic B2B transactions:

  1. from 1 January 2025, all taxable businesses must be able to receive electronic invoices,
  2. from 1 January 2027, businesses with annual turnover above €800,000 must issue electronic invoices,
  3. from 1 January 2028, the obligation to issue structured electronic invoices will apply to all businesses.

During the transition period, paper and PDF invoices may still be used only under limited conditions, such as where the recipient agrees. The domestic B2B mandate does not generally apply to B2C invoices or purely cross-border invoices.

X-Rechnung is built on a strict technical foundation to ensure legal compliance and automated processing.

It fully follows the EN 16931 semantic model, meaning that it contains all the core invoice data required under EU and German VAT rules in a standardized way. This includes invoice identification data, seller and buyer data, VAT information, invoice lines, tax totals, payment details, and references to related documents.

X-Rechnung is a pure XML format intended for system-to-system processing. ZUGFeRD is a hybrid PDF/XML format, meaning it combines a human-readable PDF with embedded structured XML data. Because of this, ZUGFeRD is often more practical where users still want a visible PDF, while X-Rechnung is more suitable for full automation.

X-Rechnung is the standard used for public-sector invoicing, while ZUGFeRD has been more common in private-sector B2B use cases. However, both formats are accepted for the future domestic B2B e-invoicing mandate, provided they comply with EN 16931. The formats share the same data core, so conversion between them is possible in many cases.

Generating a compliant XML file is not enough; the invoice must also be sent through an accepted channel.

For public-sector invoicing, Germany uses central invoice submission platforms such as ZRE and OZG-RE. These portals allow suppliers to upload invoices or send them through automated channels. In B2G invoicing, the Leitweg-ID is essential because it routes the invoice to the correct authority.

Accepted transmission methods include:

  1. web portal upload,
  2. web services or APIs,
  3. email with XML attachment, and
  4. the Peppol network.

The move to X-Rechnung has important consequences for businesses.

Companies must update ERP, billing, and accounting systems so they can generate, send, receive, and process structured invoices. They also need to ensure that all required master data, such as VAT numbers and routing data, is available and accurate.

This also means process changes. Businesses need new workflows for sending e-invoices, monitoring whether they are accepted or rejected, and handling incoming XML invoices.

X-Rechnung can improve VAT compliance because it forces structured and complete invoice data, but it also increases responsibility.

Electronic invoices must also be archived in their original electronic form for the applicable retention period. Printing the invoice and storing only a paper version is not sufficient. During audits, tax authorities may require both the original XML and a readable rendering. Because X-Rechnung is structured, it can make audits easier, but only if the company has stored and managed the files correctly.

Missing mandatory information, incorrect date formatting, invalid tax data, or calculation errors can lead to invoice rejection. A rejected invoice may not be considered properly issued for VAT purposes, which can affect payment and the customer’s ability to deduct input VAT. If corrections are needed, they generally must be made through corrected electronic invoices or credit notes, not by switching back to paper.

 

Other news from Germany