Validation rules

BR-61 — EN 16931 rule

The payment means is a credit transfer (code 30 or 58), so a payment account identifier (IBAN, BT-84) is required.

Rule: BR-61 — official EN 16931 / XRechnung rule
Severity: error
Business term: BT-84 — Payment account IBAN
Field in your JSON: invoice.payment.iban
Detected by: tier 3 — KoSIT validator (authoritative)
Reachability: Triggerable from your request JSON (generate & validate)

normbill's pre-flight raises the equivalent XRechnung finding (BR-DE-23-a) at tier 1, before the KoSIT validator sees the document.

How to fix it

Set invoice.payment.iban, or use a means_code that is not a credit transfer.

BR-61 auf Deutsch — was bedeutet der Fehler?

Als Zahlungsart ist eine Überweisung (Code 30 oder 58) angegeben, dann ist eine Kontokennung (IBAN, BT-84) Pflicht.

So beheben Sie den Fehler

Setzen Sie invoice.payment.iban — oder verwenden Sie einen means_code, der keine Überweisung ist.

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-DE-19 — The payment account identifier (BT-84) does not look like a valid IBAN — for SEPA credit transfers (means…
BR-62 — The seller electronic address (BT-34) has no scheme identifier.

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.