XRechnung (Germany) · Warning: the invoice still passes

BR-DE-17 The invoice type code isn't one XRechnung expects (warning)

What it means

XRechnung recommends a small set of invoice type codes (BT-3): 380 (normal invoice), 381 (credit note), 384 (correction), 389 (self-billing), 326 (partial invoice) and the construction codes 875, 876 and 877. This invoice uses another code. It is a warning: the invoice is not rejected for this alone, but some receivers do.

Common causes

  • A prepayment invoice (386), debit note (383) or another less common code is used.
  • The software maps its own document types to type codes in a way that doesn't fit XRechnung.

How to fix it

Check whether one of the recommended codes describes the document; for example, send a debit note as an invoice (380). Keep the other code only if the buyer agreed to it.

Who fixes it: The sender's invoicing software (the mapping of document types).

Invoice fields involved

BT-3

Related rules

This is our own plain-language explanation, not the official rule text. The official definition is in the first source below.

Stuck on this error in your own software? We can help: Integration help →

Sources

  1. XRechnung Schematron 2.6.0: XRechnung-UBL-validation.sch (KoSIT) (checked on )
  2. KoSIT validator configuration for XRechnung 3.0.2 (release 2026-08-31) (checked on )