Validation rules

BR-DE-25-b — XRechnung rule

Payment means is a SEPA direct debit (code 59), so a payee account (BG-17) must not be present. normbill applies the same check to classic direct debit (code 49), because a direct-debit document carries no payee account.

Rule
BR-DE-25-b — official EN 16931 / XRechnung rule
Severity
error
Business term
BT-84 — Payment account IBAN
Field in your JSON
invoice.payment.iban

How to fix it

Remove invoice.payment.iban / bic / account_name — the debited account belongs in debited_iban (BT-91).

BR-DE-25-b auf Deutsch — was bedeutet der Fehler?

Als Zahlungsart ist eine SEPA-Lastschrift (Code 59) angegeben, dann dürfen Empfängerkontoangaben (BG-17) nicht übermittelt werden. normbill wendet dieselbe Prüfung auf die klassische Lastschrift (Code 49) an, weil ein Lastschrift-Dokument kein Empfängerkonto trägt.

So beheben Sie den Fehler

Entfernen Sie invoice.payment.iban / bic / account_name — das belastete Konto gehört in debited_iban (BT-91).

Related rules

  • BR-DE-23-a — Payment means is a credit transfer (code 30/58) but no payment account (IBAN, BT-84) is given.
  • 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-19 — The payment account identifier (BT-84) does not look like a valid IBAN — for SEPA credit transfers (means…

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.