Validation rules

BR-DE-19 — XRechnung rule

The payment account identifier (BT-84) does not look like a valid IBAN — for SEPA credit transfers (means code 58) XRechnung expects one.

Rule: BR-DE-19 — official EN 16931 / XRechnung rule
Severity: warning
Business term: BT-84 — Payment account IBAN
Field in your JSON: invoice.payment.iban
Detected by: tier 1 — normbill pre-flight (also in the playground)
Reachability: Triggerable from your request JSON (generate & validate)

normbill's tier-1 pre-flight already warns on IBANs with a broken checksum (NB-IBAN-CHECKSUM) before the document reaches the validator.

How to fix it

Double-check invoice.payment.iban against your bank details.

BR-DE-19 auf Deutsch — was bedeutet der Fehler?

Die Kontokennung (BT-84) sieht nicht wie eine gültige IBAN aus — bei SEPA-Überweisungen (Code 58) erwartet die XRechnung eine. Der Validator meldet eine Warnung.

So beheben Sie den Fehler

Prüfen Sie invoice.payment.iban gegen Ihre Bankdaten.

Related rules

BR-DE-23-a — Payment means is a credit transfer (code 30/58) but no payment account (IBAN, BT-84) is given.
BR-DE-25-b — Payment means is a SEPA direct debit (code 59), so a payee account (BG-17) must not be present. normbill…
NB-IBAN-CHECKSUM — The IBAN fails its checksum — this is almost certainly a typo.
BR-50 — A credit-transfer payment account is present but its account identifier (IBAN, BT-84) is empty.
BR-61 — The payment means is a credit transfer (code 30 or 58), so a payment account identifier (IBAN, BT-84) is…
BR-DE-18 — A payment-terms line starting with # is not a valid Skonto segment — XRechnung requires the exact format…

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.