Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français

E-Rechnung in Germany: 2025–2027 Timeline and What Your ERP Must Do

Mandatory reception since January 2025, mandatory issuance from 2027–2028: complete guide to Germany's E-Rechnung mandate, XRechnung, ZUGFeRD formats, and an 8-step ERP compliance checklist.

E-Rechnung in Germany: 2025–2027 Timeline and What Your ERP Must Do

Since 1 January 2025, every business established in Germany has been legally required to receive structured electronic invoices. This is not a recommendation — it is a statutory obligation under the Wachstumschancengesetz, passed by the Bundesrat on 22 March 2024 (BGBl. 2024 I Nr. 108).

The real blind spot: many businesses based in the UK, Ireland, the Netherlands, and across the EU that invoice German B2B customers are still unaware of this. Your German customer may already be entitled to demand a structured invoice from you. And from 2027 onwards, they will have to issue structured invoices too — which changes how you will need to process them.

This guide covers the full regulatory timeline, the technical formats (XRechnung and ZUGFeRD), their impact on leading ERP platforms, and an 8-step compliance checklist you can start on today.

Why Germany Is Mandating B2B Electronic Invoicing

The Wachstumschancengesetz and Its Fiscal Rationale

The German Growth Opportunities Act (Wachstumschancengesetz) introduced mandatory structured B2B e-invoicing independently of the rest of the European Union — and well ahead of the ViDA (VAT in the Digital Age) schedule planned for 2030.

The stated rationale is fiscal: the Bundesministerium der Finanzen (BMF) estimates VAT fraud at several tens of billions of euros per year in Germany. Structured invoicing enables automated cross-referencing of flows between sellers and buyers, making carousel fraud virtually impossible at scale.

Unlike countries that opted for a centralised clearance model — where invoices pass through a government-mandated platform — Germany chose a direct peer-to-peer approach: no mandatory central platform, but standardised technical formats that trading partners exchange directly or via intermediaries of their choice.

Who Is Affected

The obligation applies to businesses established in Germany or with a permanent establishment (Betriebsstätte) on German territory, for their domestic B2B transactions (between German VAT-registered entities).

Businesses based in the UK, Netherlands, or elsewhere that export to Germany without a local establishment are not directly subject to the mandatory issuance obligation under German law. However, their German customers may contractually require structured invoices as early as 2026 — this is already becoming standard in German procurement terms and RFP documentation.

The Exact Timeline: Who Needs to Be Ready, and When

The schedule defined by the BMF in its official E-Rechnung FAQ is as follows:

DateObligationWho Is Affected
1 January 2025RECEIVE structured e-invoicesAll businesses established in Germany
1 January 2027ISSUE structured e-invoicesBusinesses with prior-year turnover above €800,000
1 January 2028ISSUE structured e-invoicesAll other businesses established in Germany

EDI exception: Pre-existing EDI formats (EDIFACT, etc.) remain valid until 31 December 2027, provided both parties agreed to this exchange method before the law came into force.

The reception obligation since January 2025 is often underestimated. It means that if a German supplier sends you an XRechnung or ZUGFeRD invoice, your system must be able to read, validate, and process it automatically — not simply receive an unintelligible XML file in a mailbox.

XRechnung vs ZUGFeRD 2.3: Germany’s Two Recognised Formats

Both formats comply with the European standard EN 16931, which defines the common semantic data model across all EU member states. They are the only two formats recognised by the BMF as satisfying Germany’s structured e-invoice obligation.

XRechnung: Pure XML for Machine-to-Machine Processing

XRechnung is a pure XML format, not human-readable without dedicated software. It exists in two variants: UBL (Universal Business Language) and CII (Cross Industry Invoice), both accepted.

This format has been used for B2G invoicing (public sector procurement) since 2020 and is now extending to B2B. Its defining characteristic is rigour: every field is strictly defined, structural errors are immediately detectable, and automated processing on the recipient’s side is optimal.

The trade-off: XRechnung cannot be read directly by a human. Viewing an XRechnung invoice requires a dedicated viewer (several free tools exist, including the official KoSIT viewer). For businesses accustomed to PDF invoices, this represents a significant shift.

ZUGFeRD 2.3: The Hybrid Format for a Smoother Transition

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) version 2.3 is a hybrid format: a human-readable PDF/A-3 file with an embedded CII XML payload. This is exactly the same approach as the Factur-X standard used in France and Belgium.

In practice, ZUGFeRD and Factur-X are interoperable at the EXTENDED profile level: a business already Factur-X-compliant can issue valid ZUGFeRD invoices for German customers with minor configuration adjustments in its ERP.

ZUGFeRD is significantly easier to adopt for SMEs: the invoice remains readable by humans, the XML is simply embedded in the PDF. Human validation steps remain possible before moving to full automation.

The practical choice: for SMEs starting their compliance journey, ZUGFeRD 2.3 is the path of least resistance. For larger organisations with automated ERP-to-ERP flows, XRechnung offers superior processing rigour.

Impact on Leading ERP Platforms

Major ERP vendors have all integrated — or are integrating — XRechnung and ZUGFeRD support. The overview below is indicative: always verify the exact version and configuration requirements with your vendor or implementation partner.

SAP S/4HANA and SAP Business One: XRechnung and ZUGFeRD support is available via SAP Notes and recent updates. SAP also offers integration with the Peppol network for cross-border flows.

Microsoft Dynamics 365 Business Central and Finance: E-invoicing support has been available since the 2024 Wave 2 updates. Microsoft’s electronic invoicing module uses the standard EU framework and covers XRechnung natively on German configurations.

Sage Intacct and Sage X3: ZUGFeRD and XRechnung support is available in recent service packs for configurations with the German accounting module. Validate with your Sage partner based on your specific version.

Odoo 18: Odoo’s invoicing module supports ZUGFeRD on German configurations. The Odoo community also offers open-source modules for XRechnung.

Datev: Germany’s leading accounting software vendor is natively compliant from day one. If your German customers use an accounting firm, there is a strong chance their accountant is on Datev — which facilitates structured exchanges.

Interim Solutions for Multi-ERP Environments

For organisations operating multiple ERP systems, or where a near-term upgrade of the primary ERP is complex, specialist platforms such as Basware, Esker, Pagero, and Sovos offer conversion connectors to XRechnung/ZUGFeRD. These solutions act as a proxy between your ERP (which generates a standard PDF) and the recipient (who expects structured XML). Pricing is typically volume-based, which suits limited cross-border flows.

What to Do If You Sell to Germany Without a Local Establishment

If your business is based in the UK, Ireland, or elsewhere and invoices German B2B customers without a permanent establishment in Germany, you are not directly subject to the mandatory issuance obligation under German law.

However, three practical risks apply:

  1. Contractual pressure: German customers may include XRechnung or ZUGFeRD as a mandatory requirement in their purchase terms from 2026. Non-compliance can result in payment delays or contract termination.

  2. Competitive disadvantage: German procurement processes are increasingly including e-invoicing capability as a selection criterion. Non-compliant suppliers will progressively be excluded.

  3. Regulatory cascade: if you have a subsidiary or subcontractor established in Germany, that entity will be subject to the issuance obligation. Value-chain compliance becomes a de facto requirement.

The practical recommendation: if more than 10% of your B2B revenue comes from German partners, treating ZUGFeRD compliance as an investment now is reasonable. If your business is already Factur-X-compliant (mandatory in France since September 2026), the adaptation for ZUGFeRD is minor.

8-Step Compliance Checklist

1. Map your German B2B flows Identify all invoices issued to German VAT-registered counterparties, and all invoices received from German suppliers. Note volumes, ERP systems involved, and formats currently in use.

2. Verify your ERP’s native support Ask your vendor or implementation partner whether the currently deployed version natively supports XRechnung and/or ZUGFeRD 2.3 on the German configuration. Do not assume — check the release notes or official documentation.

3. Activate the module or engage an intermediary Based on the answer, either enable the native module (often a configuration option) or evaluate a specialist platform for the flows involved.

4. Clean up your master data Structured invoicing requires clean reference data: valid VAT numbers, normalised addresses, IBANs, standardised payment terms. A test transmission will immediately expose gaps in your master data.

5. Validate formats with three German pilot customers Test in real conditions before a general rollout. One pilot customer who validates your XRechnung or ZUGFeRD output saves you from a production incident at scale.

6. Train your finance and order management teams Staff who process invoices need to understand the new workflows: how to view an XRechnung file, how to handle a format rejection, how to archive correctly.

7. Check GoBD compliance of your archiving German e-invoices must be stored in a tamper-proof manner for 10 years for tax documents, in line with the GoBD (Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form). Verify that your DMS or digital vault is configured accordingly. Non-fiscal commercial documents require 6 years.

8. Monitor regulatory developments Additional implementing regulations are expected through 2026–2027. Subscribe to BMF publications and check the official FAQ regularly. The framework is stable in its broad lines, but technical clarifications continue to be issued.

France vs Germany: Two Electronic Invoicing Architectures

The comparison is useful for businesses operating in both countries.

AspectFranceGermany
ModelCentralised (Chorus Pro for B2G; accredited PDPs + PPF for B2B)Direct peer-to-peer (no mandatory central platform)
B2B formatsFactur-X (hybrid), UBL, CIIZUGFeRD (hybrid), XRechnung (pure XML)
InteroperabilityFactur-X = ZUGFeRD at EXTENDED levelZUGFeRD = Factur-X; XRechnung = UBL/CII
Archiving10 years (Article L123-22 of the French Commercial Code)10 years (fiscal), 6 years (commercial) under GoBD
Reception startSeptember 2026January 2025
Issuance startSeptember 2026 (large enterprises)January 2027 (turnover > €800,000)

The architectural difference is significant: in France, your ERP must connect to an accredited PDP that acts as intermediary. In Germany, you exchange directly with your trading partner — which simplifies the technical flow but requires both parties to manage their own compliance.

A business generating revenue in both France and Germany will need to manage two separate compliance frameworks. The good news: the technical formats (Factur-X/ZUGFeRD) are largely compatible, and a well-configured ERP can handle both countries from the same module.

Act Now Rather Than Wait for the 2027 Mandate

The window between 2025 and 2027 is an opportunity, not merely a waiting period. Businesses that address E-Rechnung compliance in 2025–2026 will have a concrete advantage: invoices accepted without friction, compliant archiving, and clean master data ahead of the general rollout.

Those who wait until 2027 will face the familiar end-of-deadline crunch: implementation partners fully booked, vendors behind on updates, German customers already refusing PDF invoices by late 2026.

To go deeper on the technical formats, read our ZUGFeRD and Factur-X: The Hybrid PDF/XML Standard for European Electronic Invoicing guide. For the full European regulatory overview, see our Mandatory E-Invoicing in Europe: What Every ERP Must Know Before 2027 guide. And if you have already mapped your German flows and need a concrete ERP action plan, our article on B2B e-invoicing in Germany: ERP action plan for 2026 covers the operational steps to move forward without delay.