Germany's E-Invoicing Mandate 2027: What SMEs Must Do Now – and How to Turn the Obligation into an Automation Advantage

The countdown is on: on January 1, 2027 – less than six months from now – the transition period ends for a large part of the German economy. Businesses with more than €800,000 in prior-year revenue must then issue their domestic B2B invoices as genuine e-invoices; one year later, everyone else follows. And let's clear up the most widespread misconception right away: a PDF is not an e-invoice. If you email PDF invoices today and feel prepared, you aren't.

The good news: the mandate is also the best opportunity in years to properly clean up the entire invoicing process. An e-invoice is a structured data record – and structured data is exactly what automation feeds on. If you think "fulfil the obligation", you replace a PDF with an XML file. If you think "improve the process", you eliminate the typing, matching and chasing along the way. This guide covers deadlines, formats, exemptions – and the roadmap for the second, smarter path.

The deadlines: who must do what, and when?

Germany's e-invoicing obligation – introduced by the Growth Opportunities Act (Wachstumschancengesetz) – arrives in three stages for domestic B2B transactions:

Important for self-assessment: the €800,000 threshold refers to total prior-year revenue – if you exceed it in 2026, you are in scope from January 2027. And even businesses that only have to send from 2028 are already receiving: the share of suppliers sending XRechnung or ZUGFeRD grows every month.

XRechnung, ZUGFeRD, EN 16931: the formats in brief

A legal e-invoice is a structured data record compliant with the European standard EN 16931 – invoice data that software can read without a human retyping anything. Two formats dominate in Germany:

The pragmatic choice for most SMEs: ZUGFeRD as the default, because customers still see a readable invoice, and XRechnung wherever it is required. Both fulfil the standard – what matters is that your systems generate and process the formats cleanly. This is exactly where compliance ends and real progress begins.

Exemptions: who is (partially) out of scope

• Small traders under § 19 UStG are permanently exempt from the mandatory sending of e-invoices and may continue issuing other invoice types – but like everyone else, they must be able to receive e-invoices.
• Small-value invoices up to €250 and passenger tickets may remain informal.
• B2C business is not affected – the mandate only covers transactions between domestic businesses.
• EDI channels remain usable, provided the required data can be extracted correctly and completely from 2028 – existing EDI connections should be reviewed in good time.

A side note that carries weight: the retention period has been shortened to eight years – and what must be archived is the structured data record itself, in a GoBD-compliant, immutable way. An email folder called "Invoices" does not meet that bar.

The thinking error: fulfilling the obligation instead of improving the process

Many businesses will solve the mandate like this: activate the new module in their invoicing software, tick the ZUGFeRD box, done. That is legal – and a wasted opportunity. Because the expensive part of invoicing was never the invoice format. Expensive are the manual steps around it: retyping incoming invoices, matching receipts to the right transaction, chasing approvals, reconciling payments, writing payment reminders.

The e-invoice fundamentally changes the starting position: for the first time, invoice data arrives structured and machine-readable – amounts, line items, tax rates, order reference, all cleanly in the data record. Retyping and error-prone extraction from scanned PDFs disappear not through expensive AI tricks but by law. On this foundation, the rest becomes a workflow:

This is how a compliance deadline becomes a project with a return: the mandate provides the occasion and the structured data, the automation provides the saved hours. How the entire invoicing and bookkeeping of a small business can be automated is covered in depth in our guide to accounting automation for small businesses – and the invoice automation product page gives an overview of the building block.

Your roadmap to January 2027

Six months is enough – if you start now and work in the right order:

Frequently asked questions

Does the German e-invoicing mandate also apply to small businesses?

Half of it does. Every domestic business – including small businesses under the § 19 UStG small-trader rule – has had to be able to receive e-invoices since January 1, 2025; an email inbox is formally sufficient. The sending obligation, however, permanently exempts small traders: they may continue to issue other invoice types such as PDF or paper. If you plan to grow, switch early anyway – larger business customers increasingly demand e-invoices from their suppliers.

Is a PDF invoice an e-invoice?

No – this is the single biggest misconception of the whole reform. A legal e-invoice is a structured data record compliant with the European standard EN 16931 that software can process automatically. A normal PDF is just a digital picture of an invoice and counts as an "other invoice", which will no longer be permitted in domestic B2B transactions from 2027/2028. Compliant formats are XRechnung (pure XML) and ZUGFeRD from version 2.x (PDF with embedded XML).

What happens if I don't send e-invoices from 2027?

Your invoice then no longer qualifies as a proper invoice for VAT purposes. The most immediate consequence hits your customers: their input VAT deduction is at risk – which is why larger buyers will foreseeably reject non-compliant invoices or delay payment. Add possible findings in tax audits. The real risk is therefore less a fine and more a very tangible payment and customer problem.

XRechnung or ZUGFeRD – which format should an SME choose?

For most SMEs, ZUGFeRD from version 2.x is the pragmatic standard: a PDF with an embedded XML data record – people see the familiar invoice, software reads the structured data. XRechnung is pure XML without a visual file and is mandatory for German public-sector clients anyway. In practice: ZUGFeRD as your default, XRechnung wherever authorities or large clients require it. Both fulfil EN 16931.

Is an email inbox enough to receive e-invoices?

Yes – according to the German Federal Ministry of Finance's FAQ, an email inbox satisfies the reception obligation. The more interesting question is the process behind it: an XML invoice sitting unread in an inbox helps nobody. The real gain comes when incoming e-invoices are automatically parsed, validated, matched to the order and handed over to DATEV or your accounting software – which is exactly where automation starts, and the mandate is the perfect occasion for it.