ValidateFin
Back to blog
Germany / E-Rechnung16 min readBy Eliel Nicaise

E-Invoicing in Germany from 2027: the €800,000 Threshold, the Transitional Rules and the New BMF Letter

On 1 January 2027, the e-invoice becomes mandatory for German businesses above €800,000. What that figure really measures, the December invoice that no exemption covers, the two ZUGFeRD profiles that do not count, and the BMF's line between format errors and business-rule errors — quoted from the law and from the BMF letters of 2024, 2025 and 15 October 2026.

Who must issue e-invoices in Germany from 1 January 2027?

From 1 January 2027, a business established in Germany whose total turnover (Gesamtumsatz, § 19 (2) UStG) exceeded €800,000 in 2026 must issue its invoices to other businesses established in Germany as e-invoices, in a structured format that conforms to EN 16931 — such as XRechnung, or ZUGFeRD from version 2.0.1 with the MINIMUM and BASIC-WL profiles excepted. A business at or below €800,000 may still use paper, or a PDF with the recipient's consent, for transactions carried out in 2027 and invoiced by 31 December 2027; EDI remains possible for everyone until that date. Invoices up to €250, small businesses under § 19 UStG and supplies to consumers are outside the obligation. Receiving e-invoices has been mandatory for every business established in Germany since 1 January 2025. Issuing another type of invoice where an e-invoice was required is not an administrative offence, but it is not a proper invoice for input VAT purposes.

Validate your file right now

Free, instant and 100% in your browser - no file is ever uploaded.

Open the XRechnung Validator

What actually changes on 1 January 2027

Since 1 January 2025, German law has defined an e-invoice as an invoice issued, transmitted and received in a structured electronic format, and has required it between businesses established in Germany (§ 14 UStG). Receiving was never phased in: every domestic business has had to be able to receive e-invoices from day one. Issuing, by contrast, came with three temporary exemptions in § 27 (38) UStG — and the first of them expires on 31 December 2026.

Exemption (§ 27 (38) UStG)Who may use itWhat may still replace an e-invoice
No. 1 — until 31 December 2026Every business, for transactions carried out in 2025 or 2026Paper, or another electronic format such as a PDF if the recipient agrees
No. 2 — until 31 December 2027A business whose Gesamtumsatz in the previous calendar year did not exceed €800,000, for transactions carried out in 2027Paper, or a PDF if the recipient agrees
No. 3 — until 31 December 2027Every business, for transactions carried out in 2027An EDI format that does not meet EN 16931, if the recipient agrees
From 1 January 2028Every businessNothing — only the permanent exceptions remain (see below)

“Abweichend von § 14 Absatz 1 und 2 kann eine Rechnung […] bis zum 31. Dezember 2027 für einen nach dem 31. Dezember 2026 und vor dem 1. Januar 2028 ausgeführten Umsatz auf Papier oder vorbehaltlich der Zustimmung des Empfängers in einem elektronischen Format, das nicht § 14 Absatz 1 Satz 6 entspricht, übermittelt werden, wenn der Gesamtumsatz (§ 19 Absatz 2) des die Rechnung ausstellenden Unternehmers im vorangegangenen Kalenderjahr nicht mehr als 800 000 Euro betragen hat”

§ 27 (38) No. 2 UStG — German VAT Act, current version on gesetze-im-internet.de
In plain words: for a transaction carried out in 2027, an invoice on paper — or as a PDF, if the customer agrees — remains allowed until the end of 2027, provided the issuer's Gesamtumsatz in 2026 was €800,000 or less.

On 1 January 2027 the obligation therefore becomes real for every business above €800,000. Everyone else keeps the option for transactions carried out in 2027 — with one exception, the December case below. The same date also ends a grace period of the BMF's letter of 15 October 2026: for e-invoices issued until 31 December 2026, the BMF does not object if they meet only its 2024 and 2025 letters. From 1 January 2027, the additional requirements of the new letter apply as well.

The €800,000 test is not your accounting turnover

The law does not say “turnover”. It says Gesamtumsatz, and refers to its definition in § 19 (2) UStG — the figure behind the German small-business scheme. Four consequences are easy to miss, and each changes who is caught on 1 January 2027.

Counted on payments received, net of VAT

§ 19 (2) defines the Gesamtumsatz as “die nach vereinnahmten Entgelten berechnete Summe” of the taxable supplies: the sum calculated on the consideration actually received, not on the invoices issued. And the Entgelt is the consideration minus the VAT.

Some exempt supplies and all asset sales are left out

Supplies exempt under § 4 No. 8 (i), No. 9 (b) and Nos. 11 to 29 are deducted, and so are the exempt supplies of § 4 No. 8 (a) to (h), No. 9 (a) and No. 10 when they are merely ancillary. Sales of fixed assets are not counted at all.

A VAT group counts as one

For an Organschaft, the turnover of the whole group is decisive, not that of the member issuing the invoice (BMF letter of 15 October 2024, para. 64).

Self-billing turns the test around

For a self-billed invoice (Gutschrift), what counts is the Gesamtumsatz of the business issuing the self-bill — the customer. For an invoice issued by an outside service provider, it is the principal's (same para. 64).

The year of reference is the previous calendar year: for 2027, the Gesamtumsatz of 2026. That year closes the day before the rule applies, so a business close to €800,000 may not know on 1 January which side of the line it stands on.

Who is not concerned

The obligation only arises where an invoice must be issued to a business, for its business, between two parties established in Germany. Outside that frame, or within one of the permanent exceptions, another type of invoice remains possible after 2027 too.

Both parties must be established in Germany

Seat, management, a permanent establishment involved in the supply or, failing a seat, residence (§ 14 (2) UStG). If either party is not established in Germany, there is no obligation. According to the BMF's FAQ, a foreign business registered for VAT in Germany without a fixed establishment there may say so on its invoice, to explain why it sends no e-invoice.

Invoices up to €250

Small-amount invoices (§ 33 UStDV) may always be another type of invoice. What counts is the gross total of the invoice, even when it bills several supplies (BMF letter of 15 October 2024, para. 23).

Small businesses under § 19 UStG

Their invoices may always be another type of invoice (§ 34a UStDV). They must nevertheless be able to receive e-invoices (Section 14.1 (5) UStAE).

Tickets, consumers and exempt supplies

Passenger tickets (§ 34 UStDV), supplies to consumers, and supplies exempt under § 4 Nos. 8 to 29 UStG — for which there is no invoicing obligation in the first place.

Receiving has no exception

Every business established in Germany has had to be able to receive e-invoices since 1 January 2025, with no transitional period. An e-mail inbox is enough (Section 14.1 (5) UStAE).

The December trap: a 2026 service invoiced in January 2027

Exemption No. 1 sets two conditions, and the second is the one that catches people out: the transaction must have been carried out before 1 January 2027, and the invoice must be transmitted by 31 December 2026.

“Abweichend von § 14 Absatz 1 und 2 kann eine Rechnung […] bis zum 31. Dezember 2026 für einen nach dem 31. Dezember 2024 und vor dem 1. Januar 2027 ausgeführten Umsatz auf Papier oder vorbehaltlich der Zustimmung des Empfängers in einem elektronischen Format, das nicht § 14 Absatz 1 Satz 6 entspricht, übermittelt werden”

§ 27 (38) No. 1 UStG
In plain words: paper or PDF is allowed for a 2025–2026 transaction only if the invoice goes out by 31 December 2026.

Now take work carried out in December 2026 and invoiced on 10 January 2027. Exemption No. 1 no longer applies, because the invoice is transmitted after 31 December 2026. Exemption No. 2 does not apply either, because it only covers transactions carried out after 31 December 2026. Read literally, that invoice falls under no exemption at all: unless a permanent exception applies, it must be an e-invoice — whatever the issuer's turnover, including below €800,000.

This is our reading of the text. Neither the three BMF letters nor the BMF's FAQ, updated on 29 October 2026, address this exact case, so check it with your tax adviser. Only EDI users have an argument the other way: the BMF letter of 15 October 2024 (para. 65) allows EDI until the end of 2027 for a transaction carried out “bis dahin” (by then) — wording broader than No. 3 of the law. If you intend to keep sending paper or PDF invoices in 2027, the question disappears when December's work is invoiced before 31 December.

Two neighbouring cases, on the other hand, are settled. Advance and partial-payment invoices issued before your own e-invoice deadline do not have to be e-invoices, even if the work and the payment come later (BMF letter of 15 October 2026, para. 2). And a continuing invoice — a rental contract, for example — validly issued as another type of invoice before 1 January 2027 need not be reissued as long as its particulars do not change (BMF letter of 15 October 2024, para. 46).

What counts as an e-invoice: XRechnung, ZUGFeRD — and two profiles that do not

§ 14 (1) UStG requires a structured electronic format that conforms to the European standard EN 16931 or — between parties who agree on it — another format, EDI for instance, from which the required particulars can be extracted correctly and completely into a format that conforms to EN 16931 or is interoperable with it. The BMF's guidance names the German formats:

XRechnung

Purely structured XML, in UBL or CII syntax: the German CIUS of EN 16931. The VAT Application Decree states that it meets the requirements of § 14 (1) sentence 6 No. 1 UStG (Section 14.1 (13) UStAE).

ZUGFeRD from version 2.0.1 — except MINIMUM and BASIC-WL

A hybrid format: a PDF with an embedded XML file. These two profiles are excluded by name (Section 14.1 (14) UStAE): they carry only part of the EN 16931 data. The other profiles fall within the admissible formats.

Any other EN 16931 format

The list is not limited to German formats: any format that conforms to EN 16931 is admissible, and which one you use is a matter of contract between the parties (Section 14.1 (12) UStAE).

“Bei einem hybriden Format bilden die im strukturierten Teil vorliegenden Rechnungsdaten den führenden Teil. Im Fall von Abweichungen zwischen den strukturierten Rechnungsdaten und den sonstigen Informationen im Bildteil gehen die Daten des strukturierten Teils denen der Bilddatei vor.”

Section 14.4 (3) of the VAT Application Decree (UStAE), as amended by the BMF letter of 15 October 2025
In plain words: in a ZUGFeRD invoice, the XML is the invoice. If the PDF shows something else, the XML prevails.

That reverses the old habit of reading the picture. The same letter adds that input VAT can only be deducted from the structured part, and that a PDF image carrying different particulars may count as a further invoice (Section 14c.1 (4a) UStAE). To read the XML itself, the tax administration offers a free viewer on ELSTER (e-rechnung.elster.de).

And which EN 16931 field carries which mandatory particular of § 14 (4) UStG? KoSIT and FeRD publish a mapping table, which the tax administration recommends using in its current version (BMF letter of 15 October 2026, paras. 8 and 9).

Format error, business-rule error, content error: the BMF's three categories

This is the part of the guidance that matters most to anyone who validates invoices, and the letter of 15 October 2026 sharpened it. The BMF separates three kinds of defect, and they do not have the same consequence.

DefectWhat it is, with the BMF's own examplesVAT consequence
Format error (Formatfehler)The file does not conform to the admissible syntaxes or their technical specifications — or, for a format agreed between the parties, does not allow correct and complete extraction (BMF letter of 15 October 2025, para. 6a)Not an e-invoice: the file is another type of invoice. Where an e-invoice was required, it is not a proper invoice.
Business-rule error (Geschäftsregelfehler) on another fieldThe file breaks a business rule of its format without touching a mandatory VAT particular. The BMF's example: no value in BT-10 “Buyer reference” in an XRechnung (para. 6b)“umsatzsteuerlich unbeachtlich” — irrelevant for VAT (para. 35a). The file remains, in principle, an e-invoice.
Business-rule error on a mandatory VAT particularThe rule that fails protects a particular required by § 14 (4) UStG — for instance a tax amount that does not match the stated rate (para. 6b)A content error (Inhaltsfehler): not a proper invoice, to be corrected (para. 35a; letter of 15 October 2026, para. 22)
Content error that no rule detectsA particular that is wrong but consistent. The BMF's example: an incorrect VAT rate (para. 35a)Not a proper invoice, although validation reports nothing

“Umsatzsteuerlich stellt eine Datei, die einen Geschäftsregelfehler (aber keinen Formatfehler) aufweist, dennoch prinzipiell eine E-Rechnung im Sinne von § 14 UStG dar.”

BMF letter of 15 October 2026, para. 23
In plain words: for VAT purposes, breaking a business rule does not stop a file from being an e-invoice. Breaking the format does.

The letter is candid that the technical view differs: by that view, any violated business rule of the core data model means the file no longer conforms to EN 16931. In practice, a receiving system may reject such a file on that ground. For VAT, the BMF calls that view “nicht maßgebend”: not decisive. Both statements are true at once, which is exactly why a validation report has to be read layer by layer.

Our validators run the two layers in that order: first the XML schema of the syntax (UBL 2.1 or CII D16B), then the business rules in Schematron (BR-*, BR-CO-*, BR-DE-* and so on). A schema error means the file does not match its syntax — the clearest case of a format error. An error carrying a BR code is a business-rule error, and whether it is also a content error depends on the field it protects.

“Ein Unternehmer kann sich bei Beachtung der Sorgfaltspflichten eines ordentlichen Kaufmanns auf das technische Ergebnis einer Validierung (hinsichtlich des Formats und der Geschäftsregeln) durch eine geeignete Validierungsanwendung verlassen. Zum Nachweis bietet es sich an, den Validierungsbericht aufzubewahren.”

BMF letter of 15 October 2025, para. 35a
In plain words: exercising due care, you may rely on a suitable validator's verdict on format and business rules — and it is advisable to keep the report as evidence.

The same paragraph sets the limit: validation “ersetzt nicht”, does not replace, the recipient's duty to check that the invoice is complete and correct — a wrong VAT rate passes every rule. And the BMF names no validator: its FAQ states that, for reasons of equal treatment, it cannot recommend any particular one. That applies to ValidateFin too.

What happens if you get it wrong

A good deal of alarm is in circulation. The official position is more measured, and more precise.

No fine for the issuer

Issuing another type of invoice where an e-invoice was required is not an administrative offence under § 26a (2) No. 1 UStG (BMF letter of 15 October 2026, para. 28).

The recipient's input VAT is at risk in principle

Such an invoice is not a proper invoice and, “dem Grunde nach” — in principle — gives no right to deduct input VAT (BMF letter of 15 October 2024, para. 56).

…with two ways out

The issuer can correct it by issuing an e-invoice that refers specifically and unambiguously to the original, with retroactive effect (para. 57). Without a correction, the particulars of a correct and complete invoice of another type will, according to the BMF, regularly satisfy the conditions for deduction on objective evidence (para. 58).

Good faith, within limits

Deduction is not refused solely because of the wrong format if the recipient could assume that the issuer was entitled to a transitional rule — but known facts count, such as the issuer's size or the volume of business done with it the year before (para. 59).

Whatever the tax position, the customer also has a civil-law claim to an invoice that meets the requirements — including when the data set it received falls short of a required e-invoice (Section 14.1 (10) UStAE). In practice, that is what will drive the switch: customers asking for the file they are entitled to.

What no validator can tell you

A validator that seemed to answer everything would be guessing. Four questions genuinely cannot be settled by reading an invoice file:

Which side of €800,000 you are on

The Gesamtumsatz comes from your books, not from an XML file. No tool that reads invoices can tell you whether exemption No. 2 is open to you.

Content errors that break no rule

A wrong VAT rate, a vague description of the service, an agreed discount left unmentioned: the BMF itself notes that such errors can exist when validation finds nothing (letter of 15 October 2025, para. 35a).

Whether your customer is in scope

Whether the buyer is a business acting for its business, and established in Germany, is a fact about the buyer, not about the file.

A report to file away

The BMF suggests keeping the validation report. Our validators show their result on screen, layer by layer, but do not produce a report file you could archive — and no validator, ours included, is approved or recommended by the BMF.

That is why our tools state what they did not check, instead of showing a green badge that implies more than it proves.

Check your invoice before 1 January

Drop an XRechnung (UBL or CII) or a ZUGFeRD PDF and see, layer by layer, whether it breaks the schema, a business rule, or neither — including the MINIMUM and BASIC-WL profiles the BMF excludes. Everything runs in your browser: no invoice is uploaded.

Official sources

Every rule on this page was read in the law or in the BMF's letters themselves, not in a summary. The links point to the publishers: the Federal Ministry of Finance (bundesfinanzministerium.de) and the federal statute database (gesetze-im-internet.de).

German statutes and the BMF's administrative letters are official works that enjoy no copyright protection (§ 5 (1) UrhG); they are quoted verbatim, with their reference. The BMF's FAQ is linked and summarised, not reproduced. ValidateFin is not affiliated with, nor endorsed by, the German Federal Ministry of Finance.

Frequently Asked Questions

From when must businesses in Germany issue e-invoices?

Receiving has been mandatory since 1 January 2025 for every business established in Germany. Issuing to other domestic businesses becomes mandatory from 1 January 2027 for businesses whose Gesamtumsatz in 2026 exceeded €800,000. The others may keep using paper or, with the recipient's consent, a PDF for transactions carried out in 2027 and invoiced by 31 December 2027, and EDI remains possible for everyone until that date. From 1 January 2028, no exemption remains. One case escapes this calendar on a literal reading: work carried out in December 2026 and invoiced in 2027.

How is the €800,000 threshold calculated?

On the previous calendar year's Gesamtumsatz as defined in § 19 (2) UStG: the sum of taxable supplies calculated on the consideration received, net of VAT, minus certain exempt supplies, with sales of fixed assets left out. For a VAT group (Organschaft) the whole group counts; for self-billing, the Gesamtumsatz of the business issuing the self-bill (BMF letter of 15 October 2024, para. 64).

Can a business below €800,000 still send PDF invoices in 2027?

Yes, for transactions carried out in 2027 and invoiced by 31 December 2027, provided its Gesamtumsatz in 2026 did not exceed €800,000 — and a PDF still needs the recipient's consent, which can be tacit. One case escapes the rule on a literal reading: work carried out in December 2026 and invoiced in 2027 is covered by no exemption. From 1 January 2028, no exemption remains.

Which ZUGFeRD versions and profiles count as an e-invoice?

ZUGFeRD from version 2.0.1, in every profile except MINIMUM and BASIC-WL, which the VAT Application Decree excludes by name (Section 14.1 (14) UStAE). In a ZUGFeRD invoice the embedded XML is the leading part: where it differs from the PDF, the XML prevails.

Does the obligation apply to a foreign company invoicing German customers?

Not unless it has its seat, its management or a permanent establishment involved in the supply in Germany: the obligation only applies when both parties are established in Germany (§ 14 (2) UStG). A VAT registration alone does not make a business established there; according to the BMF's FAQ, it may say so on its invoice. Without an obligation, an e-invoice remains possible with the recipient's consent.

Do businesses need a Leitweg-ID for B2B e-invoices?

No. The Leitweg-ID only routes invoices to public authorities. Where a format makes BT-10 “Buyer reference” mandatory — XRechnung does — the BMF's FAQ states that a placeholder such as “-” is enough for VAT purposes in B2B.

Is there a fine for not issuing an e-invoice?

No. According to the BMF, issuing another type of invoice where an e-invoice was required is not an administrative offence under § 26a UStG (letter of 15 October 2026, para. 28). But that invoice is not a proper invoice for the recipient's input VAT deduction, and the recipient has a civil-law claim to a compliant one.

What is the difference between a format error and a business-rule error?

A format error means the file does not conform to its syntax or its technical specifications — or, for a format agreed between the parties, does not allow correct and complete extraction: it is then not an e-invoice at all, but another type of invoice. A business-rule error means the file breaks one of its format's logical rules: for VAT it remains, in principle, an e-invoice, and the error only matters when it concerns a mandatory particular under § 14 (4) UStG (BMF letters of 15 October 2025, paras. 6a, 6b and 35a, and of 15 October 2026, paras. 22 and 23).

Does a validation report protect me?

In part. The BMF says that a business exercising due care may rely on the technical result of a suitable validator as regards format and business rules, and that it is advisable to keep the report (letter of 15 October 2025, para. 35a). It does not cover content errors that no rule detects, such as a wrong VAT rate, and it does not replace the recipient's own check. The BMF names no validator.

What did the BMF letter of 15 October 2026 change?

It supplements the 2024 and 2025 letters. Among other points: advance invoices issued before a business's e-invoice deadline need not be e-invoices; final invoices may net earlier payments through BT-113 and BT-22 until 30 June 2030; where an e-invoice is required, its correction must be an e-invoice too; a business-rule error is not a format error; and issuing another type of invoice instead of an e-invoice is not an administrative offence. E-invoices issued until 31 December 2026 that meet only the earlier letters are not objected to.