Do you operate in Germany? If so, you've probably already heard about the e-invoicing mandate, even if the details are still a bit fuzzy. This guide covers what is actually required, when it kicks in, and what to think about if you haven't already started your journey to compliance.
The mandate generally applies to domestic B2B transactions between businesses established in Germany. Exceptions include invoices to consumers, small-value invoices of €250 or less including VAT, certain transport tickets, certain VAT-exempt supplies, and supplies made by businesses using Germany's small-business VAT exemption (Kleinunternehmer). With any e-Invoicing mandate, you should determine which transactions are relevant for you at the outset.
The deadline that matters most
Receiving structured e-invoices has already been mandatory for businesses established in Germany since January 1, 2025, including those using the Kleinunternehmer exemption.
Issuance is being phased in:
- From January 1, 2027, the requirement generally applies to in-scope transactions for businesses with prior-calendar-year turnover exceeding €800,000.
- From January 1, 2028, it extends to all remaining in-scope businesses. Existing exemptions still apply.
Through the end of 2026, transitional rules permit paper invoices or, with the recipient's consent, other electronic formats such as ordinary PDFs. A separate transition permits qualifying EDI arrangements to continue through the end of 2027 with recipient consent.
For businesses facing the January 2027 deadline, that date is closer than it might feel.
Which invoicing scenarios do you need to support?
Knowing which types of invoices your business issues is a useful starting point for sizing up the work:
| Document type | When you'd use it |
|---|---|
| Invoice | The everyday case, one seller, one buyer. This is almost everything most businesses send. |
| Credit note | Reducing or refunding an amount, whether for a return, a dispute, or correcting an overcharge. |
| Corrected invoice | Replacing an earlier invoice that had an error, referencing the original so it's properly superseded. |
| Prepayment invoice | Billing a deposit or down payment ahead of delivery, with the final invoice settling up afterward. |
| Debit note | A supplementary charge after the fact, for example a price increase agreed later. Less common, but still supported. |
These are business scenarios to discuss with your implementation team; how each is represented will depend on your chosen format and system capabilities.
If your business mainly issues ordinary invoices and the occasional credit note, your document requirements may be relatively straightforward. But document types are only part of the picture. The overall effort also depends on your tax scenarios, data quality and the systems involved in creating those documents.
The real challenge isn't the connection, it's the content
Chances are you already have a working relationship with most of your trading partners: invoices go out, invoices get received, and operations run. Those existing connections may still work. What needs attention is the structure and completeness of the invoice data moving through them.
The hard part is making sure what travels across that connection is actually a compliant e-invoice. A PDF that looks right to a person, or an EDI exchange that works for your commercial process, does not by itself establish compliance.
Your ERP or billing systems need to provide the required data, represent the applicable tax treatment correctly, and produce a document that meets the relevant format and validation rules. That includes details such as tax categories, exemption information where applicable, and references to earlier invoices.
Getting that right means pulling the right data out of your systems, mapping it into the required structure, and checking its accuracy before anything is sent. Technical validation is part of that process, but it cannot establish whether the underlying tax treatment is correct.
This is where significant implementation risk can sit. A trading partner connection that has worked for years can still carry a non-compliant document if the data behind it is incomplete or incorrectly mapped.
How it actually gets sent
Two commonly used formats for structured e-invoices in Germany are:
- XRechnung: a structured XML file built for machines to read.
- ZUGFeRD: a PDF/A-3 invoice that is readable by humans, with structured XML data embedded for machine interpretation.
Both support the underlying European standard, EN 16931, and can satisfy Germany's e-invoicing requirements when the appropriate version and profile are used and the invoice contains the required data. They are not the only permitted options.
With Germany opting for a decentralized model for domestic B2B e-invoicing, there is no single system acting as the gatekeeper through which invoices must pass. Businesses can exchange invoices directly with their trading partners, including by email or a system-to-system connection, or use an established invoice exchange network.
Businesses can also use a third-party e-invoicing platform to handle formatting and transmission on their behalf. Depending on the provider, that platform may deliver invoices directly to customers or through an exchange network.
If Germany is your first e-invoicing implementation and you also operate in other jurisdictions with upcoming mandates, consider whether a platform supporting multiple countries fits your broader requirements.
For most companies, the real decision goes beyond the format: it's how to adapt your current setup to produce and exchange compliant invoices. That may mean updating your billing and ERP platforms to exchange invoices directly, or integrating them with a third-party provider.
Either way, there is work to be done, even if your existing systems already support some of the requirements. The complete process, from source data and validation through delivery, exception handling and retention, needs to be tested before your applicable deadline.
Are you ready?
If you're still unsure whether your systems, data and processes line up with the new mandate, you're not alone. For businesses facing the January 1, 2027 deadline, year-end close and holiday schedules leave a narrowing window for implementation and testing.
Securing time from key decision makers and business teams now is just as important as getting the technology ready. These are often the same people who will be tied up with year-end activities when you need their input, testing and sign-off.
Whether you're already in the midst of implementation and need direction, or ready to get started, Cirrius Digital can help you assess the gaps, align your systems and data, and prepare for your applicable deadline.
Reach out or explore our e-invoicing services.