Skip to content

BR-DE-20: IBAN of the debited account for SEPA direct debit (BT-91) is invalid

Official message

[BR-DE-20] "Debited account identifier" (BT-91) soll eine korrekte IBAN enthalten, wenn in "Payment means type code" (BT-81) mit dem Code 59 SEPA als Zahlungsmittel gefordert wird.

XRechnung (CII) · Warning · Message language: German · Version: xrechnung-3.0.2-validator-configuration-2026-08-31

[BR-DE-20] "Debited account identifier" (BT-91) soll eine korrekte IBAN enthalten, wenn in "Payment means type code" (BT-81) mit dem Code 59 SEPA als Zahlungsmittel gefordert wird.

XRechnung (UBL) · Warning · Message language: German · Version: xrechnung-3.0.2-validator-configuration-2026-08-31
Severity
Warning Note: this does not make the invoice invalid, but it should be checked.
Applies to
XRechnung (CII), XRechnung (UBL)
Affected fields
BT-91, BT-81

What does this mean?

If SEPA direct debit (code 59 in BT-81) is the payment means, the debited account identifier (BT-91) should be a valid IBAN. The given identifier does not have the IBAN format or its check digits are wrong. The message is a warning.

Typical causes

A typo or transposed digits in the buyer's IBAN make the check digits wrong.
A national account number was entered instead of the IBAN.
The seller's own IBAN was entered instead of the IBAN of the account to be debited.

How to fix the error

Take the IBAN of the account to be debited from the buyer's SEPA mandate and enter it correctly; spaces are allowed and are removed before the check.
CII: ram:SpecifiedTradeSettlementPaymentMeans/ram:PayerPartyDebtorFinancialAccount/ram:IBANID, UBL: cac:PaymentMeans/cac:PaymentMandate/cac:PayerFinancialAccount/cbc:ID.
Generate and validate the invoice again.

In E-Rechnungsfreund

In the invoice form ("Experte" view), section "Zahlungsmittel (BG-16)" (payment means), correct the field "Lastschrift-Konto (BT-91)" of the payment means with "Zahlungscode (BT-81)" 59.

Example

Wrong

<ram:SpecifiedTradeSettlementPaymentMeans>
  <ram:TypeCode>59</ram:TypeCode>
  <ram:PayerPartyDebtorFinancialAccount>
    <ram:IBANID>1234567890</ram:IBANID>
  </ram:PayerPartyDebtorFinancialAccount>
</ram:SpecifiedTradeSettlementPaymentMeans>

Correct

<ram:SpecifiedTradeSettlementPaymentMeans>
  <ram:TypeCode>59</ram:TypeCode>
  <ram:PayerPartyDebtorFinancialAccount>
    <ram:IBANID>DE02120300000000202051</ram:IBANID>
  </ram:PayerPartyDebtorFinancialAccount>
</ram:SpecifiedTradeSettlementPaymentMeans>
For developers: test expression per syntax

XRechnung (CII) (CII)

Context: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans[normalize-space(ram:TypeCode) = '59']

not(normalize-space(ram:TypeCode) = '59') or xr:checkIBAN(string(ram:PayerPartyDebtorFinancialAccount/ram:IBANID))

XRechnung (UBL) (UBL)

Context: /ubl:Invoice/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = '59'] | /cn:CreditNote/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = '59']

not(normalize-space(cbc:PaymentMeansCode) = '59') or xr:checkIBAN(string(cac:PaymentMandate/cac:PayerFinancialAccount/cbc:ID))

Related validation rules

  • BR-DE-1: Payment instructions (BG-16) are missing
  • BR-DE-10: Deliver to city (BT-77) is missing
  • BR-DE-11: Deliver to post code (BT-78) is missing
  • BR-DE-14: VAT category rate (BT-119) is missing in the VAT breakdown
  • BR-DE-15: Buyer reference (BT-10) is missing
  • BR-DE-16: Seller VAT ID, tax number or tax representative is missing

Last updated:
Explanation of the validation rule, not legal or tax advice.