Skip to main content
Exostruction
Back to overview
Juljan Blischke4 min read

E-Invoicing in Germany 2027: What Businesses Need to Prepare Now

From 1 January 2027, German businesses above 800,000 euros in turnover must issue e-invoices. Deadlines, formats and how to prepare.

Guide
E-Invoicing in Germany 2027: What Businesses Need to Prepare Now

From 1 January 2027, domestic German businesses with more than 800,000 euros in prior-year turnover must issue their B2B invoices as e-invoices, and from 1 January 2028 this applies to everyone. All businesses have had to be able to receive e-invoices since 1 January 2025. A PDF sent by email does not meet that standard. Anyone who creates invoices from in-house software, Excel or a legacy system has only a few weeks left to switch. This article sorts out the deadlines, explains the accepted formats and shows where things break in practice.

What applies from 2027

The legal basis is Section 14 of the German VAT Act (UStG) as amended by the Growth Opportunities Act. An e-invoice is an invoice in a structured electronic format that can be processed automatically. The obligation covers transactions between domestic businesses (B2B). The tax authorities' interpretation is set out in the FAQ and circulars of the Federal Ministry of Finance.

A PDF invoice sent by email has no longer counted as an e-invoice since 2025. It is now only an "other invoice".

The difference is not a detail. In an e-invoice the content sits in the file as data, in a PDF it is just a picture of that data.

Who has to issue e-invoices and when

DateWhat applies
since 1 January 2025All businesses must be able to receive e-invoices. When issuing, paper and PDF are still allowed with the recipient's consent.
1 January 2027Issuing obligation for businesses with total turnover above 800,000 euros in the prior year, so for 2027 measured against 2026 turnover.
1 January 2028Issuing obligation for all businesses in domestic B2B trade.

Until the end of 2027, invoices may still be issued via EDI with the recipient's consent. Small-amount invoices up to 250 euros gross, tickets for passenger transport and invoices from small businesses under Section 19 UStG remain exempt. A small business that switches to regular VAT taxation falls under the obligation from that point on.

What counts as an e-invoice

The relevant standard is the European norm EN 16931. Two formats that implement it are common in Germany.

FormatStructureTypical use
XRechnungpure XML without PDFpublic authorities and large customers with ERP systems
ZUGFeRD 2.0.1 and laterPDF with embedded XMLsmall and medium-sized businesses, mixed recipients

ZUGFeRD comes with several profiles. According to the finance ministry, the MINIMUM and BASIC-WL profiles are not sufficient. If you do not know what the recipient expects, the EN 16931 profile is usually the safest choice. The specification is maintained by the Forum elektronische Rechnung Deutschland.

Where invoice processes break in practice

As software developers, we keep seeing the same weak points when we analyse such processes. This is our assessment from project experience, not a requirement of the law:

  • Invoice without data: It is created as a Word template, an Excel sheet or a PDF export. There is no structured data behind it from which valid XML could be generated.
  • Incomplete master data: VAT ID, tax categories, payment terms or buyer references are missing or typed as free text. A validator rejects that, a human never noticed before.
  • Special cases: Credit notes, cancellations and partial invoices are not modelled cleanly in the legacy system.
  • No central inbox: Incoming invoices end up in individual mailboxes, are not checked and are not stored consistently.
  • Archive: The structured data set should be retained, not just the PDF view. This should be settled before the switch, ideally with your tax advisor.

Most of these points can be solved without a rebuild: with a clean interface between the existing software and a module that generates, validates and archives invoice data.

Ready in six steps

  1. Check 2026 turnover. The 800,000 euro threshold decides whether the issuing obligation starts in 2027 or 2028.
  2. Map your invoice sources. Accounting, ERP, industry software, in-house tools and Excel lists: where does an outgoing invoice really originate?
  3. Choose a format. ZUGFeRD with the EN 16931 profile or XRechnung, agreed with your most important customers.
  4. Clean up master data. Maintain mandatory fields completely and in structured form.
  5. Automate generation and validation. Pull data from the source systems via APIs and integrations and validate against EN 16931 before sending.
  6. Settle inbox and archive. A central mailbox, machine processing and audit-proof storage.

Where your processes are too specific for standard software, we build web applications that generate and check invoices. For the inventory beforehand, our IT consulting is available. If you face similar time pressure from software obligations, our article on the Cyber Resilience Act covers the next deadline that clients should keep in view.

Share

Frequently asked questions

  • It depends on prior-year turnover. In 2025 and 2026, other invoices such as paper or PDF are allowed with the recipient's consent. In 2027 this only applies to businesses with total turnover of up to 800,000 euros in the prior year. From 2028, the e-invoice is the standard in domestic B2B trade, apart from the statutory exemptions.

  • Invoices from small businesses under Section 19 UStG are exempt from the issuing obligation. A small business that switches to regular VAT taxation has to issue e-invoices from that point on. All businesses must be able to receive e-invoices.

  • The relevant figure is total turnover of the prior year, so for 2027 it is your 2026 turnover. If it is 800,000 euros or less, you may still issue other invoices in 2027. From 1 January 2028 the obligation applies to everyone. Waiting until then is still risky, because format, master data and testing take time.

Author of this article

JB

Juljan Blischke

Co-Founder & Engineering

Certified application developer. Has been building web applications, APIs and internal tools for years.

This article is for general information only and does not replace individual legal, tax, or business advice. Prices, timelines, and assessments are non-binding estimates provided without guarantee.