E-Invoicing
E-Invoice
Definition
An e-invoice in the strict sense is an invoice that is issued and received in a structured, machine-readable format and enables automatic electronic processing. In the German context, particularly following the Growth Opportunities Act, e-invoice explicitly refers to structured formats (XRechnung, ZUGFeRD/Factur-X, Peppol BIS), while pure PDF invoices no longer qualify. Hybrid formats such as ZUGFeRD count as e-invoices because they contain the XML structured data.
Background & context
Since the Growth Opportunities Act (2024), the term e-invoice has acquired a precise legal meaning. From 2025, the German VAT Act distinguishes three categories: the e-invoice in the narrow sense (structured, EN 16931-compliant, machine-processable — e.g. XRechnung or ZUGFeRD from the EN 16931 profile), the 'other invoice' (all other electronic formats such as plain PDF, JPG, or paper invoice) and special cases. The key point: from 2025, an invoice sent as a PDF by email is no longer an e-invoice in the legal sense, but an 'other invoice'. A true e-invoice must be issued, transmitted and received in a structured electronic format and enable automatic electronic processing. Hybrid formats such as ZUGFeRD count as e-invoices because the structured XML part is legally authoritative — the PDF part is merely a viewing component. For input VAT deduction and GoBD-compliant archiving, the structured data set must be retained in its original form.
In practice — a worked example
From 2025, a craft business issues an invoice to a business customer. If it only sends a PDF by email, it formally fails to meet the new B2B requirement — this is an 'other invoice'. If instead it produces a ZUGFeRD invoice (EN 16931 profile) or an XRechnung, a true e-invoice exists. Important for the recipient: from 1 January 2025, every domestic business must be able to receive such structured e-invoices and archive them in a GoBD-compliant way — regardless of whether it issues e-invoices itself yet.
Common mistakes
- •From 2025 a PDF no longer counts as an e-invoice — the structured data must be present in machine-readable form.
- •Receiving obligation often underestimated: from 2025 every business must be able to receive e-invoices, even though the issuing obligation only takes effect later.
- •Archive the e-invoice in its original form (XML), not just a printout — otherwise the input VAT deduction may be lost under GoBD.
Frequently asked questions
Is a PDF invoice an e-invoice?
No. From 2025, a plain PDF counts legally as an 'other invoice', not an e-invoice. Only structured, EN 16931-compliant formats (XRechnung, ZUGFeRD from the EN 16931 profile) are true e-invoices.
From when must I issue e-invoices?
In B2B, the issuing obligation applies in stages by company size from 2027/2028; the receiving obligation already applies from 2025. In B2G, the obligation has existed since 2020 depending on the authority.
Does ZUGFeRD count as an e-invoice?
Yes, provided the EN 16931 (or higher) profile is used. The embedded structured XML part is authoritative and machine-processable; the PDF serves only for viewing.