Validation rules

BR-04 — EN 16931 rule

The invoice type code (BT-3) is missing.

Rule: BR-04 — official EN 16931 / XRechnung rule
Severity: error
Business term: BT-3 — Invoice type code
Field in your JSON: invoice.type_code
Detected by: tier 3 — KoSIT validator (authoritative)
Reachability: Only reachable when validating your own XML — normbill-generated documents cannot trigger it

invoice.type_code defaults to 380 in the request schema, so generated documents always carry BT-3.

How to fix it

Add cbc:InvoiceTypeCode with a UNTDID 1001 code, e.g. 380 for a commercial invoice.

BR-04 auf Deutsch — was bedeutet der Fehler?

Der Rechnungstyp-Code (BT-3) fehlt.

So beheben Sie den Fehler

Ergänzen Sie cbc:InvoiceTypeCode mit einem UNTDID-1001-Code, z. B. 380 für eine Handelsrechnung.

Related rules

BR-DE-17 — This invoice type code is not recommended in XRechnung.
BR-CL-01 — Type code 381 (credit note) is not allowed in the UBL Invoice syntax — UNTDID 1001 lists 381 only for UBL…
BR-03 — The issue date (BT-2) is missing or empty.
BR-05 — The invoice currency code (BT-5) is missing.
BR-02 — The invoice number (BT-1) is missing or empty.
BR-06 — The seller name (BT-27) is missing or empty.

Official sources

Every 422 from the API lists the rule id, the path in your request JSON, a plain-language message and a suggested fix — see the docs overview for the report format.

Or try it live: drop any XRechnung XML on the free validator — same KoSIT-backed report, no account.