E-Invoicing Mandate: 2026 Datev Figures Reveal Urgent Need for Action

The legal mandate for receiving electronic invoices has been active for over a year, but the real bottleneck for mid-sized companies is imminent. While Datev processed over 51 million e-invoices in the first half of 2026 alone, a third of mid-sized businesses have never sent such a structured dataset. With the transition period for active sending expiring on December 31, 2026, the window of opportunity is closing for companies with a prior-year revenue exceeding 800,000 euros. Those who fail to transition to an end-to-end, DATEV-compatible document and accounting system now risk massive compliance violations and blocked payment flows starting in 2027.

Why the Mandate Forces Accounting Departments to Act Now

The discrepancy between technical reality and legal requirements is growing, as current market data proves. According to a report by ad-hoc-news.de, Datev processed over 51 million e-invoices in the first half of 2026. By comparison, the total for the entire year of 2025 was 64 million. Despite this rapid increase, Datev CEO Robert Mayr warns that mid-sized companies are lagging behind in their preparations for the upcoming transition phases. This warning is supported by a sevdesk study from June 2026: 33 percent of the surveyed companies have never sent an e-invoice, and only 42 percent send them regularly. These figures show that the mere readiness to receive, which has applied to all domestic B2B actors since January 1, 2025, has not led to automated processing.

What Becomes Legally Binding on January 1, 2027

Companies with a prior-year revenue of more than 800,000 euros must issue domestic B2B invoices exclusively as electronic invoices starting January 1, 2027. The Growth Opportunities Act (Wachstumschancengesetz) technically amended § 14 UStG for this purpose. The decisive factor for this threshold is the total revenue of the invoice issuer in the previous calendar year, not the revenue of the recipient or the value of a single invoice. The transition rule of the Federal Ministry of Finance, which allows the sending of paper invoices or simple PDFs, ends irrevocably on December 31, 2026, for this revenue class. There is no longer a grace period for receiving anyway: Since the beginning of 2025, every domestic company, including small businesses under § 19 UStG and clubs with a commercial sector, must be able to receive and process e-invoices.

The Difference Between PDF and Structured E-Invoices

A simple PDF file no longer meets the legal requirements for an e-invoice because it lacks a machine-readable structure. A true e-invoice under the new definition requires structured data formats such as XRechnung or ZUGFeRD, which can be automatically extracted and processed. While mere receipt via a standard email inbox is legally permissible, it does not solve the operational problem. If structured XML datasets have to be manually read or typed out, a massive amount of extra work is created. The legal regulations explicitly aim at the end-to-end automation of accounting, which cannot be achieved without appropriate system support.

How a Document and Accounting System Bridges the Gap

A modern document and accounting system turns a static document archive into a largely automated, DATEV-compatible accounting process. The process from receipt to booking occurs without media breaks. Incoming documents, whether structured e-invoices, PDFs, or paper receipts, are read via OCR and AI vision. The system reliably captures even handwriting and creates a complete booking proposal including accounts, splits, and tax keys. Instead of relying on rigid rules, the system is self-learning: Every confirmed or corrected booking trains the models, measurably increasing the proposal quality per creditor.

Decision-making relies on four sources that act as a safety net: defined rules, booking history, Machine Learning (ML), and Large Language Models (LLM). An orchestrator decides in a three-stage process whether a document is booked automatically, submitted for review, or processed manually. Nothing is blindly waved through. At the same time, the system allows questions to be asked directly to the archive. Inquiries such as those regarding pension insurance back payments from a specific year are answered in seconds, including a source link to every relevant notice.

Audit-Proof Archiving and GoBD Compliance in the System

Every automated document processing must be GoBD-compliant and have complete procedural documentation to remain audit-proof up to the DATEV export. Governance is not an afterthought in such systems, but built into the architecture. Approvals, logs, and limits are firmly integrated into the tool. Data sovereignty is maintained, as processing takes place via EU endpoints and sensitive data does not leave the defined framework. Risk classes, transparency requirements, and human oversight dictated by the EU AI Act are firmly established in the approval levels. Every action, from document capture to final booking, remains fully traceable through feedback loops and double-checks.