Validation rules

BR-DE-20 — XRechnung rule

The debited account identifier (BT-91) does not look like a valid IBAN — for SEPA direct debits (means code 59) XRechnung expects one.

Rule
BR-DE-20 — official EN 16931 / XRechnung rule
Severity
warning
Detected by
tier 1 — normbill pre-flight (also in the playground)
Reachability
Triggerable from your request JSON (generate & validate)

Tier 1 reports the equivalent finding as NB-IBAN-CHECKSUM on invoice.payment.debited_iban.

How to fix it

Correct invoice.payment.debited_iban, or use a credit-transfer payment means.

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

Die Kennung des belasteten Kontos (BT-91) sieht nicht wie eine gültige IBAN aus — bei SEPA-Lastschriften (Code 59) erwartet die XRechnung eine.

So beheben Sie den Fehler

Korrigieren Sie invoice.payment.debited_iban — oder verwenden Sie eine Überweisungs-Zahlungsart.

Related rules

  • BR-DE-19 — The payment account identifier (BT-84) does not look like a valid IBAN — for SEPA credit transfers (means…
  • BR-DE-21 — The specification identifier (BT-24) is not syntactically an XRechnung customization id.
  • BR-DE-18 — A payment-terms line starting with # is not a valid Skonto segment — XRechnung requires the exact format…
  • BR-DE-22 — Two embedded attachments share the same filename — every attached document's filename must be unique within…
  • BR-DE-17 — This invoice type code is not recommended in XRechnung.
  • BR-DE-16 — A seller VAT identifier (BT-31), tax registration number (BT-32) or seller tax representative (BG-11) is…

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.

Spotted something?

Bug, missing feature, wrong validation result — tell us. The page you're on is attached automatically; email optional.