There are two reactions to the words "e-invoice". The first: panicked googling, days before the deadline. The second: calm preparation, six months early, because you know that pressure leads to bad software decisions.
If you're reading this, you're probably in the second group. Good. Here's what you actually need to know — without legal jargon, but with all the facts relevant to trade businesses.
What changes on 1 January 2027?
From the deadline, all businesses in Germany with annual revenue above 800,000 € must be able to issue e-invoices to their corporate customers. One year later, on 1 January 2028, the obligation applies to all B2B businesses — regardless of revenue.
The receiving obligation has been active since 1 January 2025: when your customer sends you an e-invoice, you must be able to accept it. What many trade businesses don't realise: a PDF invoice by email does not satisfy the e-invoicing mandate. E-invoice means structured data — machine-readable, validatable, automatable.
The receiving obligation for e-invoices has applied to all B2B businesses since 1 January 2025. Anyone still able to receive only PDF invoices is, strictly speaking, already non-compliant.
Which formats are mandatory?
Two formats are accepted in Germany — both meet the European standard EN 16931:
- ZUGFeRD 2.0 (Factur-X): Hybrid format. You see a perfectly normal PDF, but embedded inside is a machine-readable XML file. Advantage: humans and machines can both read the invoice.
- XRechnung 3.0: Pure XML, no visualisation. Mandatory for invoices to public authorities (federal, state, municipal). Optional in the B2B private sector.
In practice: anyone who can issue ZUGFeRD 2.0 is covered for 99 % of use-cases. Only if you regularly invoice public authorities do you also need XRechnung.
ZUGFeRD vs. XRechnung — which fits which business?
If your customer is a typical private or commercial client (developer, architectural firm, industrial company), ZUGFeRD is enough. You send a PDF as usual — the recipient sees everything as normal, and their accounting software reads the XML automatically.
If you supply municipalities, schools, hospitals, universities or federal authorities, XRechnung is mandatory. It's submitted via central portals (e.g. ZRE federal portal or Peppol) — not by email.
We switched three weeks before the deadline. It was worth it — without lead time the pressure would have been heavy, and pressure is the enemy of good software decisions.
How do you prepare?
The good news: if your current software supports e-invoices, there's little to do. The bad news: many vertical solutions simply don't — or only with expensive add-on modules. Here are the five steps, in order:
- Software audit: ask your provider directly: "Does your software produce ZUGFeRD 2.0 to EN 16931, included at no extra charge?" If the answer is wishy-washy, it's usually "no".
- Clarify intake: where do incoming e-invoices land? A dedicated mailbox (e.g.
invoices@your-company.com) is enough for ZUGFeRD; XRechnung arrives via portals. - Run a test invoice: generate a ZUGFeRD invoice and validate it for free at the KoSIT validator. 0 errors = passed.
- Inform your team: whoever writes invoices needs to know that nothing changes in the user interface — the magic happens in the background. Still: explaining once saves five follow-up questions.
- Plan the transition: until 31.12.2026, PDF invoices remain permissible (and beyond, if the recipient consents). But relying on that is risky.
From 1 January 2027, PDF invoices are no longer e-invoices in the legal sense — even when sent by email. ZUGFeRD is the elegant bridge: it looks like a PDF but is also structured XML data. You meet the mandate without changing your workflow.
Meistify is KoSIT-validated.
ZUGFeRD 2.0 and XRechnung 3.0 with no configuration, no upcharge. Every invoice automatically becomes a compliant e-invoice — you don't have to change anything. 14-day free trial.
Try Meistify for freeWhat happens if you don't comply?
If you can't issue e-invoices from the deadline, you face two concrete risks:
First: corporate customers can refuse your PDF invoice — and you have no claim to payment until you deliver a compliant e-invoice. This isn't theoretical; larger companies are already enforcing it.
Second: at tax audits, faulty invoice documentation can lead to input-VAT corrections and fines. The exact amount varies by case — but the reputational damage with business partners often weighs heavier than the fine.
In short: prepare in time and stay calm. Wait, and you buy yourself problems.
Frequently asked
No. The e-invoicing mandate applies exclusively to B2B transactions between businesses based in Germany. Invoices to private customers remain free in form — paper or PDF still works.
Small-amount invoices up to 250 € are exempt from the mandate. A simple receipt with the legally required fields is enough.
Yes — if the XML conforms to the ZUGFeRD 2.0 standard (EN 16931 profile or higher). That's the whole point of ZUGFeRD: visually a familiar PDF, technically a valid e-invoice.
It depends heavily on the provider. Some vertical software charges four- to five-figure fees for add-on modules; other providers (Meistify included) deliver e-invoicing as standard. Ask specifically — and get the answer in writing.