E-Invoicing from 2027: Why Your Invoice Processing Is Already Overdue

Any company with more than €800,000 in taxable turnover in 2026 must send B2B invoices as e-invoices from January 1, 2027 — not as PDF, not as a scan, but as structured XML conforming to EN 16931. Anyone who leaves this until 2027 has created a problem for themselves that was entirely avoidable. The technical switch takes longer than a legal deadline allows, and the obligation to receive and process e-invoices has already applied to every company since 2025 — if that part isn't handled cleanly yet, the gap already exists today.

What actually becomes mandatory in 2027

What becomes mandatory in 2027 is the obligation to issue e-invoices for companies with prior-year turnover above €800,000 — the obligation to receive them has existed for years already. The legal basis is Germany's Growth Opportunities Act (Wachstumschancengesetz), with transitional rules set out in § 27 para. 38 of the German VAT Act (UStG). The timeline: since January 1, 2025, every domestic B2B business must be able to receive and process e-invoices. Until December 31, 2026, invoices may still be sent as paper or — with the recipient's consent — as PDF. From January 1, 2027, businesses above the €800,000 threshold must issue e-invoices. Businesses below it have until the end of 2027. From January 1, 2028, the obligation applies to everyone without exception. Anyone who thinks this all starts in 2027 has already missed the first stage.

Who exactly falls above the threshold

What counts is the issuer's taxable total turnover for 2026 under § 19 para. 2 UStG — not profit, not the B2B share alone, and not the turnover of the invoice recipient. That's a common misconception: it doesn't matter how big your customer is, only how big your own total turnover was. A company with €750,000 in turnover and a single million-euro client still falls under the longer transition period. Exceptions to the issuing obligation apply to small-value invoices up to €250 gross, to B2C transactions, to certain VAT-exempt supplies under § 4 UStG, and permanently to small businesses under § 34a of the VAT Implementation Ordinance (UStDV) — though even they must still be able to receive and process e-invoices. EDI procedures may, under current guidance, continue to be used even beyond 2028.

Which format actually counts

Legally compliant means exclusively a structured electronic format conforming to the European standard EN 16931 — a scan or a plain PDF does not meet this definition, however convenient it looks. In Germany, two formats have become established: XRechnung as a pure XML file, and ZUGFeRD as a PDF/A-3 file with embedded XML. Even expert sources disagree on the exact permitted version numbers — the reliable rule is to check for the current, EN-16931-compliant version before sending, rather than relying on a specific version number. Anyone still emailing PDF invoices and considering that sufficient is confusing readability with machine-readability.

What input VAT deduction actually requires

A formal error on an invoice does not automatically void the input VAT deduction under ECJ and German Federal Fiscal Court (BFH) case law, provided the substantive requirements are met — deduction may not be denied on purely formal grounds. That's the good news, and some guides inflate it into a reassurance it doesn't warrant. Because possessing an invoice with VAT separately stated is itself a substantive requirement, not merely a formal one (BFH, October 20, 2016, V R 26/15). Anyone who fails to issue or receive a proper e-invoice from 2027 doesn't have a formatting issue — they risk the basis of the deduction itself. A recent ruling (BFH, May 30, 2025, case V B 61/23) tightens the situation further for EDI and informal invoices. Relying on "it'll probably be fine" means betting money on a legal position that is currently getting stricter, not looser.

Why preparation starts now, not in 2027

The obligation to issue e-invoices doesn't just affect sending — it affects the entire chain before it: capture, coding, approval, posting. A system that currently passes invoices through as PDF or paper and only converts them into accounting entries at the end has to rebuild that chain — and that can't be done in the final weeks before the deadline, when thousands of other mid-sized companies are searching for the same fix at the same time. A company that already runs its invoice processing in a structured, GoBD-compliant way, seamlessly through to posting, only needs to extend its input and output formats for e-invoicing — not reinvent the process. A document and accounting system that reads invoices via OCR and AI vision, automatically generates posting proposals with accounts and tax codes, and documents all of this in a GoBD-compliant way through to the DATEV export can be extended directly to handle XRechnung and ZUGFeRD as additional input and output formats — because the structure an e-invoice demands anyway (accounts, tax codes, allocation, traceability back to the source) is already the underlying principle of such a system, not an added burden. Anyone wanting to check where they stand should ask one question: can the current system ingest an XRechnung, code it, and post it without a manual break — or would someone have to type the XML content into an existing form by hand? If the answer is the latter, there isn't a year and a half of lead time left — there's considerably less.