Germany E-Invoicing 2026–2027:
What Finance Teams Need Before January 2027

The Legal Foundation: Wachstumschancengesetz and §14 UStG

Germany's e-invoicing mandate is not a guideline or an industry recommendation. It is an amendment to the country's VAT Act (Umsatzsteuergesetz, UStG) enacted by the Wachstumschancengesetz (Growth Opportunities Act), which the Bundesrat approved on March 22, 2024 and which became law on March 27, 2024 (published in Bundesgesetzblatt BGBl. I 2024 Nr. 108). The e-invoicing provisions sit inside Article 23 of this law.

The core change is to §14 UStG (gesetze-im-internet.de), which redefines what constitutes a valid invoice for domestic B2B transactions. Under §14 Absatz 1 Satz 3 UStG, an electronic invoice (elektronische Rechnung, or E-Rechnung) now means: a document issued, transmitted, and received in a structured electronic format that enables electronic processing. A PDF sent by email — even if generated by accounting software — does not satisfy this definition. It has no structured data layer, no machine-readable semantic markup, and cannot be automatically parsed by the recipient's ERP without re-extracting the content.

The obligation to actually issue e-invoices sits in §14 Absatz 2 Satz 2 Nr. 1 UStG n.F. — for domestic B2B transactions between businesses established in Germany, the invoice must be issued as a structured electronic invoice. The administrative implementation was detailed in two BMF letters (BMF-Schreiben) from October 15, 2024 and October 15, 2025, with the BMF FAQ on E-Rechnung most recently updated in March 2026.

Germany secured an EU derogation for this mandate through a Council Implementing Decision dated July 25, 2023, which permits the country to proceed with domestic B2B e-invoicing ahead of the ViDA (VAT in the Digital Age) framework's full application. The mandate is explicitly aligned with European standard EN 16931 and the syntax list under Directive 2014/55/EU.

The precision matters. In a German tax audit (Betriebsprüfung), "the regulation requires e-invoicing" does not defend a finding. "§14 Absatz 2 Satz 2 Nr. 1 UStG, as amended by Wachstumschancengesetz (BGBl. I 2024 Nr. 108), requires structured EN 16931-compliant electronic invoices for domestic B2B transactions" does. The regulation reference is the compliance posture.

The Three-Phase Timeline — and What Each Phase Means in Practice

The mandate does not switch on all at once. It rolls out in three phases across four calendar years, with the key differentiator being company size measured by prior-year total turnover (Gesamtumsatz). The following table maps each phase to the specific obligation it creates.

Sources: §14 UStG; BMF E-Rechnung FAQ (March 2026); EU eInvoicing Country Sheet — Germany.

Three important clarifications that many overviews skip:

The €800,000 threshold is based on the previous calendar year's total turnover. If your 2026 turnover exceeded €800,000, you must issue e-invoices from January 2027. If it did not, your issuance deadline is January 2028 — unless your 2027 turnover crosses the threshold, in which case your obligation begins the following year.

Receiving is already mandatory, with no exceptions. Even a Kleinunternehmer (small entrepreneur — small-scale entrepreneur) under §19 UStG must be able to receive structured e-invoices. The "small business exemption" only applies to issuing. Since January 1, 2025, providing an email address that can accept XML file attachments technically satisfies the letter of the law — but it leaves the recipient with an unreadable file and a manually handled exception every time a supplier goes electronic.

Small-value invoices (<€250) and transport tickets are excluded. Under §33 and §34 UStDV (Umsatzsteuer-Durchführungsverordnung), invoices below €250 and tickets functioning as invoices for transportation services are exempt from the structured format requirement. Tax-exempt services under §4 Nr. 8-29 UStG (e.g., certain financial and insurance services) are also excluded.

Germany's phased rollout positions it ahead of the ViDA timeline for domestic e-invoicing, which sets a compliance deadline of January 1, 2035. But the cross-border Digital Reporting Requirement (DRR) under ViDA takes effect from July 1, 2030 — which means German businesses that become e-invoicing capable for domestic purposes now will have already solved the harder technical problem before the cross-border obligation arrives. For the full European timeline across all member states, see our Europe E-Invoicing 2026–2027 overview.

XRechnung vs ZUGFeRD: Not an Either/Or Decision

The two compliant formats under Germany's mandate are XRechnung and ZUGFeRD. Both conform to EN 16931 — but they deliver invoice data in fundamentally different ways, and choosing between them is not a matter of picking one and ignoring the other. Most businesses will need to handle both, because different suppliers will use different formats.

XRechnung: Pure XML, No Visual Layer

XRechnung is Germany's national Core Invoice Usage Specification (CIUS) of EN 16931, maintained by KoSIT (Koordinierungsstelle für IT-Standards). It is a pure XML format — no PDF, no visual rendering, just structured data fields organized according to a strict schema. The current mandatory version is XRechnung 3.0.1 (effective February 1, 2024), which introduced three mandatory fields absent from earlier versions: BT-23 (Business Process Type), BT-34 (Seller Electronic Address), and BT-49 (Buyer Electronic Address). A preliminary XRechnung 4.0 was released for testing in 2026, based on UBL 2.5 and CII D25A syntaxes, but no mandatory adoption date has been set.

XRechnung has been the mandatory format for B2G (business-to-government) invoicing since November 27, 2020. For B2B, it is one of two approved formats. The practical consequence: if you already invoice public authorities in Germany, you are already generating XRechnung and the B2B mandate introduces no new format burden on the issuing side.

ZUGFeRD: Hybrid PDF with Embedded XML

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid format maintained by FeRD (Forum elektronische Rechnung Deutschland). It combines a human-readable PDF/A-3 document with an embedded structured XML layer — so the same file can be read by a person and parsed by an ERP system. The current version is ZUGFeRD 2.2, and it is technically identical to the French Factur-X standard (the Franco-German cooperation on this format means ZUGFeRD and Factur-X are the same specification, just with localized naming).

Critical detail: Not every ZUGFeRD file is a compliant e-invoice. ZUGFeRD defines five conformance profiles — MINIMUM, BASIC, COMFORT (EN16931), EXTENDED, and XRECHNUNG. Only the COMFORT/EN16931 profile and above satisfy Germany's B2B e-invoicing requirements. A supplier sending a ZUGFeRD invoice in the BASIC profile has sent what looks like an e-invoice — a hybrid PDF with embedded XML — but it does not meet the legal definition under §14 UStG. This is the compliance trap most small businesses will encounter first.

Side-by-Side Comparison

A June 2025 BMF letter introduced an important interpretive rule for ZUGFeRD hybrid invoices: the structured XML part takes precedence over the human-readable PDF layer. If there is any discrepancy between the two representations, the XML data governs for VAT purposes. This reverses the prior rule where the PDF was treated as the authoritative version. It also means that input VAT deduction (Vorsteuerabzug) under §15 UStG can only be based on the machine-readable data — if the XML is incomplete or non-compliant, the recipient cannot claim the VAT deduction even if the PDF layer looks correct.

What the Mandate Does NOT Require (That Many Assume It Does)

Three features of other European e-invoicing regimes are frequently — and incorrectly — attributed to Germany's mandate. Clarifying these is more useful than adding another layer of technical specification, because these misconceptions are what generate unnecessary compliance anxiety in small and medium finance teams.

No Leitweg-ID for B2B

The Leitweg-ID (buyer reference routing ID) is a structured identifier used to route invoices to the correct public authority within German federal, state, and municipal administration. It consists of three segments separated by hyphens — a fixed prefix (up to 12 characters), a unique sub-identifier (up to 30), and a check digit (2). It is only required for B2G invoices sent via the federal ZRE or state OZG-RE submission portals.

For B2B transactions, no Leitweg-ID is required. The BMF FAQ explicitly confirms this. If a format field for a buyer reference exists in your B2B invoice template, a placeholder value is sufficient. Businesses do not need to register for or obtain any routing identifier to exchange e-invoices with commercial counterparties.

No Government Clearance Platform

Unlike Italy (Sistema di Interscambio, SdI), France (PPF/PA network), or Belgium (Peppol-based clearance), Germany has adopted a decentralized operating model for B2B e-invoicing. There is no central government platform through which invoices must be routed or validated before delivery. Invoices are exchanged directly between trading partners through any mutually agreed channel — email, Peppol, EDI, direct API — as long as the structured format meets EN 16931 requirements.

This is a meaningful difference for Mittelstand companies. In France, every business must register with an approved platform (Plateforme Agréée) and the government directory tracks every recipient. In Germany, the government stays out of the B2B transmission path. The trade-off: there is no official validation layer catching format errors before an invoice reaches your counterparty. The sender — and only the sender — is responsible for ensuring compliance.

Peppol Is Optional, Not Mandated

Germany supports Peppol (Pan-European Public Procurement Online) as a delivery network, and the Peppol BIS 3.0 format is recognized as EN 16931-compliant. But unlike Belgium — where Peppol is the mandatory exchange protocol — Germany does not require businesses to connect to the Peppol network. B2B e-invoices can be delivered via email attachment, secure file transfer, or any other agreed channel. Peppol access points are available for businesses that want automated routing, but they are a convenience choice, not a compliance requirement.

The Mittelstand Reality: DATEV, Lexware, and the Hybrid Transition

The majority of Germany's 3.6 million businesses are small and medium enterprises (Mittelstand) — and the overwhelming majority of them run their accounting on one of two software stacks: DATEV or Lexware. This is not a market preference; it is a structural feature of German accounting. The Steuerberater (tax advisor) relationship is the anchor of most Mittelstand financial operations, and the dominant platform in that profession is DATEV. A tool that exports cleanly to DATEV is usable. A tool that does not is operationally invisible.

This creates a specific tension for the e-invoicing mandate. The law says structured XML. The Steuerberater still processes PDFs through DATEV. The finance team sits in between, needing to receive XRechnung and ZUGFeRD from suppliers while their own outgoing invoicing — if they are below the €800,000 threshold — can remain on PDF until 2028.

The adaptation challenge for most Mittelstand companies is not "which format to choose." It is that their AP process is built around reading PDFs: the finance clerk opens the attachment, reads the amount and due date, enters it into Lexware or DATEV, and files the PDF. When a supplier starts sending XRechnung — an XML file that renders as raw code when opened — that workflow breaks. The data is actually more structured and more complete than the PDF ever was, but it is inaccessible without a parser.

Only an estimated 20–25% of German businesses were sending e-invoices as of early 2026, and approximately one-third reported being able to receive them. The gap between 25% and 100% is the operational transition that will unfold through 2027–2028 — and the finance teams that prepare a workflow for handling both XML and PDF inputs before their suppliers switch will avoid the scramble that hits when a key supplier goes electronic without warning.

The German invoice processing ecosystem already carries significant manual entry costs. As we explored in detail in our analysis of the German invoice manual entry problem, each paper or PDF invoice that arrives in an unstructured format requires 3–5 minutes of rekeying — a cost that multiplies quickly when invoice volumes scale. The e-invoicing mandate is designed to eliminate this at the structural level, but only if the receiving end has the capability to process structured data on arrival.

What Finance Teams Should Do Now — a 5-Step Roadmap

This is not a checklist designed for a DAX corporation with a dedicated compliance team and a six-figure ERP budget. It is written for the finance manager at a Mittelstand company with 50–500 employees, an existing Lexware or DATEV installation, and instructions from the Geschäftsführer not to disrupt month-end close.

Frequently Asked Questions

Is a PDF sent by email a valid e-invoice in Germany?

No. Under §14 Absatz 1 Satz 3 UStG, as amended by the Wachstumschancengesetz, a valid electronic invoice must be issued, transmitted and received in a structured electronic format that enables electronic processing. A PDF — even when digitally generated and emailed — does not contain structured data. It is a visual representation, not a machine-readable data structure. During the transition periods (through December 31, 2026 for all businesses, and through December 31, 2027 for SMEs ≤€800,000), PDFs can still be sent with recipient consent — but they are classified as "other invoices" (sonstige Rechnungen), not e-invoices.

Which format should I use — XRechnung or ZUGFeRD?

If you invoice public authorities in Germany, XRechnung is mandatory for B2G. If you invoice other businesses domestically, ZUGFeRD (in its COMFORT/EN16931 profile or higher) is the more practical choice for most companies because it produces a human-readable PDF alongside the structured data — your recipient can read the invoice normally even without a parser. However, your software choice will largely determine this decision: if your accounting package generates ZUGFeRD 2.x, use that. If it generates XRechnung, use that. The important decision is not the format — it is ensuring the format's conformance profile meets the EN 16931 requirement.

I am a Kleinunternehmer (small entrepreneur). Do I need to do anything?

Yes — you must be able to receive structured e-invoices from your German suppliers. The Kleinunternehmer exemption under §19 UStG does not exempt you from the §14 UStG reception obligation. You are not currently required to issue e-invoices until 2028 (unless your turnover exceeds €800,000), but if a German supplier sends you an XRechnung or ZUGFeRD invoice, you must be able to process it.

Can I claim VAT deduction from a PDF invoice after 2027?

Only if the supplier is still within their transition window. After January 1, 2027, businesses above the €800,000 threshold must issue e-invoices. If such a supplier sends you a PDF, the invoice does not meet the legal requirements of §14 UStG — and your input VAT deduction (Vorsteuerabzug) under §15 UStG may be denied. A June 2025 BMF letter further clarified that VAT deduction can only be based on machine-readable structured data. This is the most financially significant risk of non-compliance: it converts a format error into a direct cost equal to the invoice's VAT amount. After January 1, 2028, the same rule applies regardless of supplier size.

What if I do not have an ERP system that reads XRechnung?

You are not alone — a significant portion of Mittelstand companies run accounting on Lexware or DATEV without an enterprise AP automation layer. The minimum viable approach for receiving e-invoices without an ERP parser is to use a document extraction tool that can extract data from PDF-formatted documents — including the visual layer of ZUGFeRD hybrid PDFs, screenshots of XRechnung invoices rendered in a viewer, and traditional paper or PDF invoices — then output the combined results in a single spreadsheet or CSV that your accounting software can import. This bridges the gap between "must receive XML" and "can only process PDFs" without replacing your existing software stack. The French mandate, which follows a similar trajectory, faces the same challenge — see France E-Invoicing 2026 for the comparable experience with Factur-X and the PPF/PA network.

What happens if the XML data and the PDF layer disagree in a ZUGFeRD invoice?

The XML governs. A June 2025 BMF letter established that the structured data layer takes legal precedence over the visual PDF rendering in hybrid invoices. If the two representations differ — for example, the PDF shows a 19% VAT rate but the XML encodes a 7% rate — the recipient must process the XML value. This rule also applies to the recipient's input VAT deduction claim: the deduction must be based on the XML data, not the visible PDF.

How long must I keep e-invoices and in what format?

Under §14b Absatz 1 UStG, both incoming and outgoing invoices must be retained for 8 years (10 years under commercial law, Handelsrecht). For e-invoices, the structured XML part must be preserved in its original, unaltered form. A PDF rendering alone does not satisfy the retention obligation. The archiving system must comply with GoBD principles: field-level audit trail, immutability, versioning, and machine readability for tax audit access.

The Real Deadline Is Not January 2027

The mandate's official dates get the headlines, but the date that matters to your AP team is the day your first key supplier switches to e-invoicing — and that date can be any day between now and 2028, because suppliers above the €800,000 threshold are free to transition early. Preparation is not about meeting a single regulatory deadline. It is about making sure that when the switch arrives unannounced, the invoice does not sit unread in a finance inbox while the payment clock ticks.

The good news for most Mittelstand finance teams is that the German mandate is structurally simpler than its French or Italian counterparts: no clearance platform, no mandatory network, relaxed transition periods, and formats built on the same EN 16931 standard your software vendors have been updating toward since 2020. The adaptation is incremental, not architectural. The risk is not the regulation itself — it is assuming that "2028" or "€800,000" means you have nothing to do until then. Receiving is already mandatory. The suppliers are already transitioning. The format confusion is already generating AP exceptions. The time to build a receiving workflow for structured invoices is before your first one lands.