What Is E-Invoicing? A Plain-Language Explanation

You've probably heard that Germany is making e-invoicing mandatory, and now you're wondering what that actually means. The term gets thrown around a lot, and most explanations manage to be both too technical and somehow still vague. Let's sort that out.

The Short Answer

An e-invoice (elektronische Rechnung) is an invoice that:

Is created in a structured digital format (XML)
Gets transmitted electronically
Can be processed automatically by software — no human needs to read it first

The key word is structured. A machine needs to extract the data from it reliably — line items, tax amounts, payment details, all of it — without any guesswork.

And no, a PDF is not an e-invoice. I know, I know. But a PDF is essentially a picture of an invoice. Your accounting software can display it, but it can't automatically pull out the numbers without OCR, which is basically "expensive guesswork that's mostly fine until it isn't."

Why Is Germany Doing This?

Good question. A few reasons:

VAT fraud is expensive — Germany estimates roughly €11 billion lost annually to VAT fraud. Structured invoices create a verifiable paper trail that's much harder to manipulate.
Manual data entry is a waste of time — e-invoices flow directly into accounting systems without anyone retyping numbers.
The whole EU is heading this way — Germany's mandate is part of a broader European push. Getting compliant now means you're ahead of the curve, not scrambling later.

What Formats Actually Qualify?

Under German law, e-invoices must comply with the European standard EN 16931. In practice, that means one of three formats:

XRechnung

Pure XML — there's no visual component
Germany's national standard, mandatory for B2G (government invoices) since 2020
Looks like raw XML to humans — not readable without tooling, but that's fine because it's designed for machines, not people

ZUGFeRD 2.x

A PDF with embedded XML data inside it
The idea: humans open the PDF and see a normal invoice, machines read the XML underneath
Has to use Profile "EN 16931" or "XRechnung" to actually be compliant (more on the profile trap below)

Peppol BIS Billing 3.0

XML sent through the Peppol network — think of it as a secure, standardized postal system for invoices
Big in Scandinavia, gaining traction in Germany
Requires signing up with a Peppol Access Point provider

What Does NOT Count as an E-Invoice?

❌ Paper invoices
❌ PDF files, even if emailed
❌ Scanned paper invoices
❌ Word or Excel documents
❌ ZUGFeRD profiles "Minimum", "Basic WL", or "Basic" — these don't meet EN 16931 and will not be accepted

That last one is a common gotcha. If your software generates ZUGFeRD but you've never checked which profile, it's worth verifying now.

So What Do I Actually Need to Do?

Already overdue (January 2025): You need to be able to receive e-invoices. At minimum, that's an email address that accepts XML attachments and some software that can do something with them. Most modern accounting tools handle this — check your settings.

Coming up (2027/2028): You'll need to send e-invoices too. That requires software that can generate proper XRechnung or ZUGFeRD 2.x output.

Next Steps

Check your current software — does it actually support e-invoicing? Compare solutions →
Get the full picture on deadlines — Germany 2025 mandate guide →
See where you stand — Take the free readiness assessment →

This guide is updated as the regulations evolve. If something's changed and I haven't caught up yet, drop me a note.