FaeBill
Wissen

E-invoice error classes: when validation shows green – and tax disadvantages still loom

FaeBill Blog Team
•

Translated from the German original (updated 9 November 2026)

This article is also available in German. Read the German version

E-invoice on a tablet – correct validation does not protect against tax-relevant error classes

Imagine this: your bookkeeper loads an incoming e-invoice (an invoice issued, transmitted and received in a structured electronic format that enables automatic electronic processing) into the KoSIT (Koordinierungsstelle für IT-Standards, Coordination Office for IT Standards) validator. The result? Green light, no errors. You book the invoice and deduct the input VAT – and months later the tax office (Finanzamt) finds that the VAT rate was wrong. Input VAT deductible only in the amount of the tax legally owed, back payment, possibly interest.

Since the second administrative guidance letter of the Federal Ministry of Finance (BMF-Schreiben) of 15 October 2025 (as at November 2026), exactly this scenario has been officially described and recognised as a risk. With this letter, the Federal Ministry of Finance (BMF) introduced a three-tier classification of e-invoice error classes – and the legal consequences of the individual classes differ considerably from one another.

This article explains what this means in practice for businesses that receive or issue e-invoices.

The three e-invoice error classes at a glance

The BMF letter of 15 October 2025 distinguishes three categories of faulty e-invoices. The key point: not every error is visible to the technical validator – and not every valid data set is an invoice that is correct for tax purposes.

E-invoice error classesType of errorDetectable by validator?Legal consequence
Class 1Format error (EN 16931 syntax violated)YesNo valid e-invoice document
Class 2Business rule error (mandatory fields missing/logically contradictory)Mostly yesIn principle still an e-invoice; not proper if mandatory details are affected
Class 3Content errors (VAT rate / date of supply / recipient)NoTechnically valid but risky for tax purposes

Let us look at e-invoice error classes 1 to 3 in detail.

Error class 1: format errors – the document is technically not an e-invoice

Format errors exist when the transmitted document violates the syntax rules of the European standard EN 16931 on electronic invoicing. Specifically: the XML document does not conform to the prescribed schema, contains impermissible character encodings or cannot be processed as a structured invoice by the recipient's system at all.

Examples of format errors:

  • Wrong XML namespace or missing mandatory declarations
  • Binary attachments that do not comply with the permitted embedding format
  • A ZUGFeRD PDF in which the XML attachment is corrupted or unreadable
  • Use of an XML syntax that does not conform to the prescribed schema of EN 16931

Legal consequence: A document with format errors does not count as an e-invoice within the meaning of Section 14(1) sentences 3–6 of the German VAT Act (Umsatzsteuergesetz, UStG) (as at November 2026). It is an “other invoice” (paper invoice or electronic invoice in a non-structured format, e.g. a plain PDF) – in other words, what used to be a normal PDF before 2025. For issuers, this means: the obligation to issue e-invoices (where it already applies) has not been met. For recipients: they are in principle entitled to refuse acceptance until a correct e-invoice is provided.

Detectability: Format errors are reliably detected by technical validators – for example the KoSIT validator for XRechnung, the German CIUS (Core Invoice Usage Specification) of EN 16931, maintained by KoSIT, or the FeRD profile checker for ZUGFeRD, the German hybrid e-invoice standard published by FeRD (Forum elektronische Rechnung Deutschland).

Important: Passing a validator test only means that there is no format error. It is not an official check result and not an official confirmation of correctness for tax purposes. KoSIT is expressly not a certification body — a validator pass is not an official seal of approval.

Error class 2: business rule errors – mandatory fields are missing or contradictory

Business rule errors (business rule violations) occur when the XML document is formally structured correctly but violates the content requirements of EN 16931 or of the profile used. Typical cases:

  • Missing mandatory fields: An XRechnung data set without a Leitweg-ID, the routing identifier for German public-sector invoice recipients (BT-10, Buyer reference), in the B2G sector.
  • Mathematical inconsistency: The sum of the invoice line net amounts does not match the stated sum of invoice line net amounts (BT-106) (business rule BR-CO-10).
  • Contradictory details: The tax amount and the taxable amount do not match the stated VAT rate.
  • Missing mandatory field in the profile: In the EN 16931 profile, certain BT fields (Business Terms) are mandatory; if they are missing, the Schematron rule is violated.

Legal consequence: According to the BMF (letters of 15 October 2025, para. 35a, and 15 October 2026, paras. 22 et seq.), a business rule error alone does not deprive the document of its status as an e-invoice. However, if the error concerns mandatory VAT invoice details under Section 14(4) UStG, the invoice is not proper. The input VAT deduction is then at risk. It is not lost automatically; the invoice can be corrected under Section 31(5) UStDV. Nobody can guarantee that the deduction will be preserved in an individual case. (as at November 2026)

By letter of 15 October 2026 (III C 5 – S 7287-a/00019/021/017, paras. 22 et seq.), the BMF confirmed that a business rule error without a format error in principle does not affect the document's status as an e-invoice within the meaning of Section 14 UStG; the invoice is proper only if the mandatory details under Sections 14 and 14a UStG are correct and complete.

Detectability: Most business rule errors are detected by technical validators – the KoSIT validator explicitly checks the Schematron rules of the XRechnung specification. However, validation is profile-dependent: anyone who checks a data set against the wrong profile may not receive an error signal.

Note on ZUGFeRD profiles: The ZUGFeRD profiles MINIMUM and BASIC WL are syntactically correct XML documents but do not contain all mandatory EN 16931 details. According to the BMF letter of 15 October 2024, they therefore do not qualify as e-invoices within the meaning of Section 14 UStG but as other invoices (as at November 2026). From ZUGFeRD profile BASIC upwards, the format requirements are met.

Error class 3: content errors – what the validator does not see

This is where the real pitfall lies, which the BMF letter of 15 October 2025 explicitly addresses: content errors can exist even though the validation shows no objections whatsoever.

A content error exists when the document is technically structured correctly and contains all mandatory fields – but the values entered are factually wrong. The validator cannot check whether the stated VAT rate matches the actual transaction or whether the period of supply has been stated correctly.

Examples of content errors:

  • Wrong VAT rate: The supply should be taxed at the reduced rate of 7%, but the invoice shows 19% – or vice versa.
  • Wrong date of supply: BT-72 (Actual delivery date) is filled in incorrectly, which makes allocation in the bookkeeping more difficult.
  • Wrong or missing tax number or VAT identification number of the supplier: The supplier's tax number (Steuernummer) or VAT identification number (BT-32 / BT-31) is one of the mandatory invoice details under Section 14(4) UStG; if it is wrong or missing, the recipient's input VAT deduction may be at risk.
  • Incorrect quantities or prices: typing errors that lead to a mathematically correct but factually wrong invoice amount.

Legal consequence: The document is technically a valid e-invoice. The tax consequences depend on the type of error:

  • In the case of an incorrect tax rate, the recipient's input VAT deduction may be lost in full or in part – the tax office (Finanzamt) only recognises the amount of tax actually owed by law.
  • In the case of incorrect recipient details, the input VAT deduction may likewise be refused if the recipient of the supply cannot be reliably identified (Section 15 UStG).
  • For the issuer, obligations to correct may arise (Section 14c UStG in the case of incorrectly stated VAT).

The fatal part: from a technical point of view, everything is in order. The error only becomes visible during a tax audit.

E-invoice error classes: consequences for businesses that receive invoices

Since 1 January 2025, all domestic businesses (i.e. established in Germany) have been obliged to be able to receive e-invoices – without a transitional period and without any requirement for consent (Section 14(1) sentence 5 in conjunction with Section 14(2) sentence 2 no. 1 UStG, as at November 2026). This also applies to small business owners under Section 19 UStG (German VAT Act).

With the arrival of mandatory e-invoicing, the question arises: what should you do if an e-invoice you have received contains errors? The answer – as described above – depends on the respective error class.

Practical recommendation for receiving invoices:

  1. Technical validation is a minimum standard, not a quality certificate. In addition, rely on content checking processes: is the tax rate correct? Does the invoice amount match the quotation/order? Is the service period correct?
  2. For class 1 errors and for class 2 errors affecting mandatory details: You can refuse to accept the faulty invoice and ask the issuer to rectify it. A file with a format error is an “other invoice” (paper invoice or electronic invoice in a non-structured format, e.g. a plain PDF) – with correspondingly limited transitional options.
  3. For content errors (class 3): Clarify the facts with the issuer and request a corrected invoice. Since the BMF letter (administrative guidance) of 15 October 2025, the following applies: corrections to e-invoices must themselves be issued as e-invoices, with a clear reference to the original invoice (BT-25).
  4. Retention: Retain both the original faulty e-invoice and the corrected invoice. Since the Fourth Bureaucracy Relief Act (BEG IV), invoices and accounting vouchers must be retained for 8 years (Section 14b(1) sentence 1 UStG, Section 147(3) Fiscal Code (AO) as amended, as at November 2026).

According to the BMF, issuing an other invoice despite the obligation is not an administrative offence under Section 26a(2) no. 1 UStG (BMF letter of 15 October 2026, para. 28). For the recipient's input VAT deduction, however, the invoice is still not proper.

E-invoice error classes and the obligation to issue: what issuers need to bear in mind

The obligation to issue e-invoices is being phased in (Section 27(38) UStG, as at November 2026):

  • Until 31 December 2026 (inclusive): all B2B businesses may still issue other invoices (paper; electronically only with the recipient's consent).
  • Until 31 December 2027 (inclusive): businesses whose total turnover in the previous calendar year (2026) did not exceed €800,000 may still issue other invoices.
  • From 1 January 2028: full obligation to issue e-invoices for all domestic B2B businesses, with permanent exemptions (including small business owners and small-amount invoices not exceeding €250).

Even if your obligation to issue does not yet apply: anyone who issues e-invoices voluntarily (which is already advisable today) should make sure that no content errors jeopardise the recipient's input VAT deduction. A validator pass does not protect the recipient from content errors – and can damage your business relationship.

Special attention: corrected invoices

If you have issued a faulty e-invoice, the BMF letter of 15 October 2025 expressly states: the corrected invoice must itself be issued as an e-invoice, with a clear reference to the original invoice number. A simple PDF correction sent by email is no longer sufficient once the obligation to issue applies. Plan your internal processes accordingly.

How FaeBill approaches error prevention

FaeBill creates e-invoices exclusively in the EN 16931-compliant ZUGFeRD profile and in the XRechnung format. The PHP backend checks mandatory fields on the server side before generation and returns HTTP 400 if mandatory fields are missing – no silent fallback, no incomplete document.

This helps you avoid class 1 and class 2 errors on the issuing side. Class 3 errors (content errors) – such as an incorrectly entered tax rate or a wrong service period – are the responsibility of the user making the entries. FaeBill helps here too: the system takes VAT rates from the master data, displays the totals transparently before creation and offers a preview before the document is finally generated.

Start for free and issue your first EN 16931-compliant e-invoices: Get started with FaeBill now

Frequently asked questions (FAQ)

Is an e-invoice that passes the KoSIT validator correct for tax purposes?

No – not necessarily. The KoSIT validator checks technical format conformity and business rules (e-invoice error classes 1 and 2). It cannot check whether the stated tax rate matches the economic facts or whether the service period is correct (error class 3). A validator pass is not a tax quality seal.

May I reject a faulty e-invoice?

In principle yes, if there is a format error (class 1): the document is then not an e-invoice within the meaning of Section 14 UStG. In the case of business rule errors (class 2), according to the BMF the document in principle remains an e-invoice; if the error concerns mandatory details, you should request a correction. For content errors (class 3), you should likewise ask the issuer to correct the invoice (as at November 2026).

Does a corrected invoice also have to be issued as an e-invoice?

Yes – the BMF letter of 15 October 2025 makes it clear: corrections to e-invoices must themselves be issued as e-invoices, with a reference to the original invoice number (BT-25, the business term for the preceding invoice reference). This applies as soon as the obligation to issue applies to the issuer.

How long must faulty e-invoices and corrected invoices be retained?

Since the Fourth Bureaucracy Relief Act (BEG IV), invoices and accounting vouchers must be retained for 8 years (Section 14b(1) sentence 1 UStG, Section 147(3) AO as amended, as at November 2026). This applies both to the original faulty invoice and to the corrected invoice – in the original structured format, not merely as a paper printout. Important: commercial books, annual financial statements and opening balance sheets remain subject to a 10-year period (Section 257 Commercial Code (HGB), Section 147(1) no. 1 AO) – the 8-year period applies specifically to invoices and accounting vouchers.

Which e-invoice error classes do the ZUGFeRD profiles MINIMUM and BASIC WL correspond to?

These profiles are syntactically correct XML but do not contain all mandatory EN 16931 details and therefore do not qualify as an e-invoice within the meaning of Section 14 UStG (BMF letter of 15 October 2024, as at November 2026). They do not fulfil the statutory obligation to issue e-invoices. From ZUGFeRD profile BASIC upwards, the format requirements can be met; in addition, the mandatory details under Section 14(4) UStG must be complete and correct.

Does mandatory e-invoicing also apply to small business owners?

Small business owners under Section 19 UStG (German VAT Act) are permanently exempt from the obligation to issue e-invoices under the Annual Tax Act 2024 (JStG 2024) (Section 34a sentence 4 UStDV as amended by the JStG 2024, as at November 2026). However, the obligation to be able to receive e-invoices has also applied to small business owners since 1 January 2025 – without a transitional period. The e-invoice error classes are also relevant for small business owners when, as recipients, they receive defective invoices.

Sources

Federal Ministry of Finance (BMF) — 15 October 2026 (letter III C 5 – S 7287-a/00019/021/017)

Legal position as at: November 2026

Note: Not tax or legal advice

This article is for general information only. It is not tax or legal advice for your individual situation and cannot replace such advice. It describes German and, where stated, EU law. Other jurisdictions are not covered. Although we research carefully, we cannot guarantee that the content is current, complete or correct. Legislation, case law and administrative guidance (for example, German Federal Ministry of Finance (BMF) circulars or EU initiatives such as ViDA) may change after publication. Please consult a German tax advisor (Steuerberater), a lawyer or another qualified professional for your specific situation. Our statutory liability remains unaffected.

Status: November 2026

Frequently Asked Questions

What happens if an e-invoice is defective?

Different types of error must be distinguished. If there is no e-invoice although one is required (e.g. a plain PDF), or if the file has a format error, there is no proper e-invoice. The input VAT deduction is then at risk. It is not lost automatically; the invoice can be corrected under Section 31(5) UStDV. Nobody can guarantee that the deduction will be preserved in an individual case. If mandatory invoice details under Section 14(4) UStG are missing, the invoice is likewise not proper and should be corrected.

Does an incorrect e-invoice jeopardise the input VAT deduction?

Yes, it can. If mandatory invoice details under Section 14(4) UStG are missing, or if there is no e-invoice although one is required, the input VAT deduction is at risk. It is not lost automatically; the invoice can be corrected under Section 31(5) UStDV. Nobody can guarantee that the deduction will be preserved in an individual case. Check incoming e-invoices for completeness automatically.

How do I correct a defective e-invoice?

A defective invoice is remedied by an invoice correction or a cancellation/corrected invoice in the same e-invoice format. A clear reference to the original invoice is important. Software with a cancellation function sets the necessary data fields correctly and automatically.

Do I have to check incoming e-invoices for errors?

Yes, in your own interest. Only an e-invoice that is correct in form and content reliably entitles you to deduct input VAT. An automatic check on receipt immediately reveals missing mandatory fields or format errors before they reach your accounts.

Ready for the 2025 E-Invoice Mandate?

Start now with FaeBill and create legally compliant ZUGFeRD invoices in minutes.