Where things stand right now
If your last serious look at this topic was 2024, a refresher is overdue. The Federal Ministry of Finance (BMF) has published a second guidance letter and updated its public question and answer catalogue since then.
1 Jan 2027
First wave of issuers loses the paper option
Section 27(38) of the German VAT Act
EUR 800,000
2026 turnover decides which wave you are in
Total turnover as defined in the German VAT Act
EUR 5,000
Maximum fine for not issuing an invoice, or issuing it late
Section 26a of the German VAT Act
Three points make up the current position. Everyone already has to be able to receive. Since 1 January 2025, domestic businesses need to be able to receive an e-invoice. The BMF is explicit that there are no exceptions to this, and that it applies even to small businesses that are themselves exempt from issuing one. The bar is low: according to the BMF, an email inbox is enough.
A PDF is no longer an electronic invoice. Since 1 January 2025 an e-invoice exists only where the invoice is issued, transmitted and received in a structured electronic format that permits electronic processing. In plain terms, that is a data file a computer can read field by field, not a picture of an invoice. A simple PDF does not qualify and is classed as a “sonstige Rechnung”, or other invoice, alongside paper.
Sending is still optional, for now. Transitional rules let issuers keep using other invoice formats. Paper can always be used. Another electronic format, such as a PDF by email, needs the recipient’s agreement, on the basis that a recipient cannot be expected to accept a format entirely unknown to them.
| Format | Structured data? | Counts as an e-invoice |
|---|---|---|
| XRechnung | Yes, a data file only | Yes |
| ZUGFeRD from 2.0.1 | Yes, the data file travels inside the PDF | Yes, except the MINIMUM and BASIC-WL profiles |
| EDI (direct system-to-system exchange) | Depends on the process | Only where the process meets the requirements |
| PDF by email | No | No, it counts as an “other invoice” |
| Scanned or posted paper | No | No, it counts as an “other invoice” |
What sits outside the obligation
Not every invoice is caught. The BMF lists several categories where the e-invoicing obligation does not apply at all, which is worth checking before assuming a wholesale system change is needed. Small-value invoices in particular cover a large share of transaction volume in some businesses.
| Outside the obligation | Note |
|---|---|
| Invoices to consumers | B2C is not in scope |
| Many VAT-exempt supplies | Check the specific exemption |
| Small amounts up to EUR 250 gross | Known in German as Kleinbetragsrechnungen |
| Travel tickets that count as invoices | Known in German as Fahrausweise |
| Supplies by businesses on the small business (Kleinunternehmer) scheme | The issuer is exempt, but must still be able to receive |
| Supplies to legal entities that are not businesses | Many associations and clubs fall here |
The date that matters: 1 January 2027
The transitional rules run out in stages, and the statute behind them is section 27(38) of the German VAT Act.
Every domestic business, with no exceptions, including small businesses that never have to issue one.
The 2026 figure decides whether the obligation starts in January 2027, which leaves no run-up time after the year end.
One further year, on total turnover as defined in section 19(2) of the VAT Act.
Where the EDI process does not already meet the e-invoice requirements. Recipient agreement is still needed.
Each transitional limb carries two conditions, not one. The invoice has to be sent inside the window and the supply has to have been carried out inside it. A supply carried out in January 2027 is outside the general rule even though the rule itself runs to 31 December 2026.
For supplies carried out in 2027, the 2026 figure decides whether you are in the first wave. The 2026 year end tells you whether you have a January 2027 obligation, with no run-up time in between.
Three details in the statute that are easy to miss
First, the general transitional rule has two conditions, not one. An invoice can still be sent on paper until 31 December 2026, or in another electronic format if the recipient agrees. That only holds for a supply carried out before 1 January 2027, meaning the goods were delivered or the service performed before that date. Both the supply and the invoice have to fall inside the window.
Second, the EUR 800,000 test looks backwards and uses a VAT definition. The extension into 2027 applies where the issuer’s total turnover, as defined in section 19(2) of the VAT Act, did not exceed EUR 800,000 in the preceding calendar year. It is not a headcount test, and it is not measured on the current year.
Third, the dates have not moved. They are written into the Act, and as at the date of publication the Act has not been amended to change them. If you are close to the threshold, or if you simply do not want to run two invoicing processes side by side, the sensible planning assumption is 1 January 2027. Our Germany e-invoicing guide sets out the mandate end to end, including the public sector (B2G) rules this article does not cover.
What the BMF has clarified since
The BMF issued a second guidance letter on 15 October 2025, amending its original letter of October 2024. Importantly, it wrote the rules into the VAT Application Decree, the rulebook that tax offices work from. It then updated its public FAQ, currently dated March 2026. Between them, four clarifications will affect day to day work.
| Clarification | What it means in practice |
|---|---|
| The details VAT law requires belong in the structured data | A reference pointing to an attachment that holds those details in unstructured form is not sufficient |
| In a hybrid invoice, the data leads | Where the data file and the readable PDF differ, the data file governs |
| Corrections follow the same rules | Where an e-invoice is required, the correction is an e-invoice too, using the invoice type designated for a correction |
| Retention attaches to the structured part | At least the structured part has to be kept intact in its original form, for eight years |
Everything mandatory has to be in the structured data
This is the one that catches people out. The BMF states that every detail VAT law requires on an invoice must sit in the structured part of the e-invoice. That covers items such as the VAT number, the invoice date and the amounts. The reasoning is simple: only then can the invoice be processed automatically. A reference in the structured data pointing to an attachment that holds those details in unstructured form is not sufficient.
Supplementary information can still go in an attachment. The BMF gives the example of a breakdown of timesheets as a PDF. The description of the supply in the structured data has to allow the supply to be identified clearly and easily checked.
There is a specific allowance for construction. For a construction service, the BMF currently accepts a structured description that lists the individual trades with their totals. The detailed breakdown can then sit in a human-readable annex, provided the structured part points to it unambiguously.
With hybrid invoices, the data wins
This reverses long standing practice. Previously, where a hybrid format such as ZUGFeRD, in which the data file travels inside a PDF, showed a difference between the data and the readable image, the image took priority. The BMF confirms that the relationship has now flipped: the structured data is the leading part, and where the two differ, the structured data governs.
Previous practice
Where the two layers disagreed, the readable image was treated as the invoice.
Since the letter of 15 October 2025
Where the two layers disagree, the structured data governs.
If the PDF and the data file inside it do not say exactly the same thing, the tax office relies on the data file. That is the version nobody in your business has ever looked at.
Corrections and retention
Where there is an obligation to issue an e-invoice, a correction has to be made as an e-invoice too, using the invoice type designated for a correction. During the transitional periods, a correction can still be made without using an e-invoice. The BMF also allows corrections of individual items to be made in a following e-invoice, provided the correcting document refers specifically and unambiguously to the original.
On retention, a business has to keep a copy of every incoming and outgoing invoice for eight years. For an e-invoice, at least the structured part has to be kept intact in its original form. GoBD are the German rules on keeping books and records digitally. The BMF adds that storing e-invoices outside a GoBD-compliant system does not, on its own, generally breach the retention requirement for VAT purposes. The BStBK FAQ translation goes into the archiving mechanics in more detail.
| Obligation | During the transition | Once you are in scope |
|---|---|---|
| Correcting an invoice | A correction can still be made without using an e-invoice | The correction is an e-invoice, using the designated correction type |
| Keeping the record | Eight years, all invoices | Eight years, with at least the structured part intact in its original form |
What happens if you get it wrong
The headline number is a fine of up to EUR 5,000. Under the German VAT Act it is an administrative offence to fail to issue an invoice, or to issue one late, where the law requires one. The ceiling for that offence is EUR 5,000. The same ceiling applies to a failure to keep an invoice for the eight-year period.
For most businesses the bigger exposure is elsewhere. Your customers can only reclaim the VAT on your invoice if it is a proper invoice. The BMF notes that as long as an “other invoice” may still be issued, it continues to count as a proper invoice for that purpose. That protection is tied to the transitional rules, so it narrows as they expire. In other words, your customers acquire a direct financial interest in your invoice being correct, which tends to concentrate minds faster than any fine.
There is also a contractual angle that rarely gets attention. Many supply agreements and standard terms still specify that invoices will be sent by post or as a PDF by email. Those clauses are worth reviewing before the obligation bites.
The fine is capped at EUR 5,000. The larger exposure is your customer’s ability to reclaim VAT, and that protection narrows as the transitional rules expire.
The second clock: the standard itself is changing
This is the part almost nobody has planned for. XRechnung is maintained by the Coordination Office for IT Standards (KoSIT) on behalf of the IT Planning Council. The version currently in force is XRechnung 3.0, with the technical package (bundle 3.0.2) most recently updated on 31 January 2026. That is what companies going live in January 2027 will be building against.
In an update published on 1 September 2026, KoSIT set out what happens next. The revised European standard, EN 16931-1:2026, has been ratified and has been available in English since March 2026, with the German translation due from DIN by 30 September 2026 at the latest. On the German side, KoSIT expects a preliminary version of the XRechnung 4.0 specification in September 2026, explicitly not for productive use, to give an early view of what is changing. The full technical package depends on further work at European level, since the files software needs to build and test against the new standard are still outstanding.
The timing point that matters for planning is this. KoSIT states that the existing and new versions of EN 16931-1 are expected to run in parallel until March 2029. The exact transition periods for XRechnung will be set within that window and announced when the 4.0 package is published. Read together, that means a German company hitting the 2027 deadline will go live on one version of the standard and migrate to another within the following two years.
| Area | What the revision brings |
|---|---|
| Delivery | More detailed delivery information |
| Orders | Several orders and deliveries on one invoice |
| Payment terms | New fields for cash discount and default interest |
| Receivables | New fields for third party receivables |
| Attachments | The option to send attachments in XML |
The third clock: your customers abroad are already there
Germany’s approach is deliberately open on how an invoice travels. The BMF says the law prescribes no particular transmission route. Its list of possibilities runs from email and an electronic interface to shared access to a central storage location within a group, handover on a USB stick, and download from an internet portal. The route in any given case is a commercial matter between the parties.
Germany’s neighbours have taken a different path. Belgium made structured e-invoicing compulsory between Belgian VAT-registered businesses on 1 January 2026. The Belgian Federal Public Service Finance states that those invoices have to be sent systematically via the Peppol network, with Peppol BIS as the principal reference. The general tolerance period for the first three months of 2026 has ended, with a narrower and temporary tolerance for self-billing that ran to 30 June 2026.
France started on 1 September 2026. Businesses have to use an approved platform, a plateforme agréée, to transmit and receive their electronic invoices and to send transaction and payment data to the administration. Receiving is the universal obligation from that date; issuing applies from 1 September 2026 to large and mid-sized enterprises, and from 1 September 2027 to SMEs and micro-enterprises. The French tax administration’s July 2026 start-up guide states that during the start-up phase, sanctions will not be applied to businesses that encounter difficulties but are on a serious path to compliance. The same guide says this is neither a postponement nor a suspension of the obligation. The date held; what is on offer is patience with documented effort rather than more time.
| Germany | Belgium | France | |
|---|---|---|---|
| Issuing compulsory from | 1 Jan 2027, then 1 Jan 2028 | 1 Jan 2026 | 1 Sep 2026, then 1 Sep 2027 |
| How the invoice travels | No prescribed route, including email | Systematically via Peppol | Through an approved platform |
| Format reference | XRechnung, ZUGFeRD from 2.0.1 | Peppol BIS | Formats and profiles under AFNOR XP Z12-012 |
Meeting the German rules does not make you compliant in your customer’s market. If you invoice Belgian or French business customers, their obligations set the requirement, not yours.
And then the European layer
The EU’s VAT in the Digital Age package was adopted on 11 March 2025 and is being rolled out progressively until January 2035. The European Commission confirms that digital reporting requirements will affect cross-border B2B transactions from 1 July 2030. By 1 January 2035, Member States that run a domestic real-time reporting obligation have to align their systems with the EU standards.
Germany has been open about where this is heading. The BMF states that a reporting system is closely connected to the introduction of mandatory e-invoicing. Planned for a later date, it would report certain invoice details electronically to the tax administration, transaction by transaction and close to the time of issue. It adds that e-invoicing prepares the ground for that system, and that the government will propose the necessary legislative changes in due course. The current rules will then be reviewed and adjusted where necessary against the requirements of the reporting system. The BMF’s July 2026 Action Plan against tax and financial crime is covered separately.
That last sentence is the honest answer to the question of whether 2027 is the end of the road. It is not.
- 1 Jan 2025Every business must be able to receive
- 1 Jan 2027First wave must issue
- 1 Jan 2028Transitional rules exhausted
- No date setTransaction-based VAT reporting
Umsatzsteuergesetz, sections 14 and 27(38)
- Mar 2026EN 16931-1:2026 ratified, English text available
- Sep 2026XRechnung 4.0 preliminary version, not for production
- By 30 Sep 2026German translation from DIN
- No date setXRechnung 4.0 bundle, waiting on CEN artefacts
- To Mar 2029Old and new versions run in parallel
EN 16931 and XRechnung, maintained by CEN and KoSIT
- 1 Jan 2026Belgium: structured B2B, sent via Peppol
- 1 Sep 2026France: all receive, large and mid-sized issue
- 1 Sep 2027France: SMEs and micro-enterprises issue
- 1 Jul 2030EU digital reporting, cross-border B2B
- 1 Jan 2035Domestic reporting systems align with EU standards
Belgium, France and the ViDA package
What to do in the next twelve months
The companies that will find 2027 easy are not the ones with the best invoicing software. They are the ones that treated this as a process change rather than a file format change, and started early enough to fix what broke.
The work divides into three kinds: establishing which wave you are in, fixing what your systems actually produce, and dealing with the parts of the problem that sit outside Germany. In rough order of urgency:
| Action | Why it matters | Do it by |
|---|---|---|
| Work out which wave you are in | The 2026 turnover figure decides whether the obligation starts in January 2027 | Now, and confirm at the 2026 year end |
| Check what your structured data contains | Required invoice details hidden in an attachment do not count | Before any go-live decision |
| Make the PDF and the XML agree | The structured data governs where the two differ | Before the first live invoice |
| Sort out corrections and credit notes | Usually the last process built and the first to fail in production | During implementation, not after |
| Ask your provider about XRechnung 4.0 | Whether it is on the roadmap, when, and whether it is covered by your current arrangement | At the next contract review |
| Map your cross-border flows | Belgium and France already mandate a specific channel | Ahead of 1 September 2027 |
| Review contracts and standard terms | Clauses promising paper or PDF invoices become unworkable | Before the obligation applies to you |
| Write down how it all works | Useful for audits, essential when the person who built the process leaves | As you go |
Bundesministerium der Finanzen, questions and answers on the introduction of mandatory e-invoicing, version dated March 2026.
Bundesministerium der Finanzen, letter of 15 October 2025 on mandatory e-invoicing and the amendment of the Umsatzsteuer-Anwendungserlass, amending the letter of 15 October 2024.
Umsatzsteuergesetz, section 14 (issuing invoices), section 26a (administrative fine provisions) and section 27(38) (transitional provisions), official consolidated text at gesetze-im-internet.de.
Koordinierungsstelle für IT-Standards, EN 16931: Aktueller Stand und Ausblick auf die Einführung der XRechnung 4.0, 1 September 2026, and the XRechnung versions and bundles page (Bundle 3.0.2, Fassung vom 31.01.2026).
Service Public Fédéral Finances, e-invoicing in Belgium and the notice ending the general tolerance period.
Direction générale des finances publiques, facturation électronique et plateformes agréées, and the practical start-up guide of July 2026; Ministère de l’Économie et des Finances, tout savoir sur la facturation électronique.
European Commission, Directorate-General for Taxation and Customs Union, VAT in the Digital Age.
This article is general information and not tax or legal advice. Speak to your adviser about your own circumstances.
Explore e-Invoice.app
Real-time compliance data, peer discussions, and cross-functional tools for every stakeholder.
Compare Countries
Side-by-side comparison of mandates, timelines, and technical requirements.
Open Compare ModeFind the Right Vendor
Get matched with e-invoicing vendors for your countries and ERP.
Start vendor match