Validation rules
BR-G-01 — EN 16931 rule
Lines or document-level allowances/charges use VAT category "G" (export outside the EU), so the VAT breakdown (BG-23) must contain exactly one export entry.
- Rule
BR-G-01— official EN 16931 / XRechnung rule- Severity
- error
- Business term
BT-151— Line VAT category- Field in your JSON
invoice.lines[*].vat_category- Detected by
- tier 3 — KoSIT validator (authoritative)
- Reachability
- Triggerable from your request JSON (generate & validate)
normbill derives one breakdown per category and rate, so generated documents only violate this when G is used with more than one rate — which already violates BR-G-05.
How to fix it
Give every G line, allowance and charge the same VAT rate 0 (line.vat: 0) — normbill then emits exactly one G breakdown.
BR-G-01 auf Deutsch — was bedeutet der Fehler?
Positionen oder Nachlässe/Zuschläge verwenden die Kategorie "G" (Ausfuhr in ein Drittland), also muss die Umsatzsteueraufschlüsselung (BG-23) genau einen Ausfuhr-Eintrag enthalten. Bei normbill passiert das nur, wenn G mit mehr als einem Steuersatz verwendet wird.
So beheben Sie den Fehler
Verwenden Sie für alle G-Positionen, -Nachlässe und -Zuschläge denselben Steuersatz 0 (line.vat: 0) — normbill erzeugt dann genau eine G-Aufschlüsselung.
Related rules
BR-O-11— VAT category "O" (not subject to VAT) cannot be mixed with other VAT categories on the same invoice…BR-CO-04— An invoice line is not categorized with a VAT category code (BT-151).BR-AE-01— Lines or document-level allowances/charges use VAT category "AE" (reverse charge), so the VAT breakdown…BR-B-01— VAT category "B" (Italian split payment) is only allowed on domestic Italian invoices — every country code…BR-B-02— VAT category "B" (Italian split payment) must not be combined with category "S" (standard rated) on the same…BR-E-01— Lines or document-level allowances/charges use VAT category "E" (exempt), so the VAT breakdown (BG-23) must…
Official sources
- XRechnung specification (KoSIT / xeinkauf.de)
- KoSIT validator on GitHub and the XRechnung validator configuration
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.