InvoiceConvertor

Home / Guides / Fixing XRechnung Validation Errors with the Current KoSIT Rules

Technical & Standards

Fixing XRechnung Validation Errors with the Current KoSIT Rules

As of 15 November 2026, XRechnung 3.0 remains in force through at least 31 July 2027; the current production technical bundle is 3.0.2. XRechnung 4.0.0, published as a pre-version in September 2026, is not the production version. Confirm the required recipient configuration before validating or sending a file.

Diagnose the validation layer first

XRechnung validation is versioned. A document may be well-formed XML yet fail its XSD, a core EN 16931 business rule, a German XRechnung rule, code-list validation or a recipient’s processing requirement. KoSIT’s configuration bundles the relevant artifacts, and its FAQ notes that updated European rules can cause a previously accepted file to be rejected later.

Common investigation areas include missing mandatory business terms, invalid identifiers or code values, date/currency syntax, inconsistent taxable amounts and totals, missing buyer references, and values that do not fit the selected profile. Rounding differences can also matter because validation applies specified calculation rules.

A disciplined fix loop

InvoiceConvertor’s local checks are a limited semantic pre-check. It does not bundle the official KoSIT validator or claim XRechnung certification.

Official sources

Frequently asked questions

Why can a previously accepted XRechnung fail now?

KoSIT and European validation artifacts change; the current configuration may introduce or raise the severity of rules.

Does passing a local pre-check prove recipient acceptance?

No. Use the recipient’s required current validator and transmission process.