# BR-DE-19: IBAN (BT-84) invalid for code 58

Source: https://veriport.io/einvoice-rules/br-de-19 (published 2026-11-17)

When the payment means code is 58 (SEPA credit transfer), the payment account identifier, BT-84, should be a valid IBAN: right length for its country and correct mod 97 check digits. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [XRechnung 3.0 rules](/einvoice-rules/xrechnung), XRechnung 3.0.2 schematron 2.6.0
- **Severity:** warning
- **Business terms:** BT-81, BT-84
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-19 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is a warning: the invoice stays valid, but should be corrected.

```text
[BR-DE-19] "Payment account identifier" (BT-84) soll eine korrekte IBAN enthalten, wenn in "Payment means type code" (BT-81) mit dem Code 58 SEPA als Zahlungsmittel gefordert wird.
```

## What it checks

When the payment means code is 58 (SEPA credit transfer), the payment account identifier, BT-84, should be a valid IBAN: right length for its country and correct mod 97 check digits. It is a warning.

## Why invoices fail it

A national account number, an IBAN with spaces or a typo, or a non-SEPA account is sent with code 58.

## How to fix it

Write the IBAN without spaces and check its digits; for a non-SEPA account use code 30 (credit transfer).

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as XRechnung 3.0 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-DE-19.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-DE-19** | warning | `/ubl:Invoice/cac:PaymentMeans` | "Payment account identifier" (BT-84) soll eine korrekte IBAN enthalten, wenn in "Payment means type code" (BT-81) mit dem Code 58 SEPA als Zahlungsmittel gefordert wird. |

```diff
  …
      <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
      <cac:PayeeFinancialAccount>
-       <cbc:ID>DE02120300000000202052</cbc:ID>
+       <cbc:ID>DE02120300000000202051</cbc:ID>
      </cac:PayeeFinancialAccount>
    </cac:PaymentMeans>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from XRechnung 3.0.2 schematron 2.6.0. An `assert` fails when its test is false.

Text and test: © KoSIT, Apache License 2.0. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = ('30','58')] | /cn:CreditNote/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = ('30','58')]
test:    not(normalize-space(cbc:PaymentMeansCode) = '58') or xr:checkIBAN(string(cac:PayeeFinancialAccount/cbc:ID))
```

```xpath
context: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans[normalize-space(ram:TypeCode) = ('30','58')]
test:    not(normalize-space(ram:TypeCode) = '58') or xr:checkIBAN(string(ram:PayeePartyCreditorFinancialAccount/ram:IBANID))
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-DE-17: Invoice type code outside the XRechnung list](https://veriport.io/einvoice-rules/br-de-17)
- [BR-DE-18: Skonto in payment terms (BT-20) malformed](https://veriport.io/einvoice-rules/br-de-18)
- [BR-DE-20: Debited IBAN (BT-91) invalid for code 59](https://veriport.io/einvoice-rules/br-de-20)
- [BR-DE-21: Specification identifier not XRechnung’s](https://veriport.io/einvoice-rules/br-de-21)
- [BR-61: Payment account (BT-84) for codes 30 and 58](https://veriport.io/einvoice-rules/br-61)
- [BR-49: Payment means type code (BT-81) missing](https://veriport.io/einvoice-rules/br-49)
- [All XRechnung 3.0 rules](https://veriport.io/einvoice-rules/xrechnung)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- XRechnung — the German CIUS of EN 16931 (standard, versions and bundles; version 3.0.2 in force) — https://xeinkauf.de/xrechnung/ (2026-10-28)
- Validator configuration XRechnung v2026-08-31 (XRechnung 3.0.2, CEN schematron 1.3.16, xrechnung-schematron 2.6.0) — https://github.com/itplr-kosit/validator-configuration-xrechnung/releases/tag/v2026-08-31 (2026-10-28)
- XRechnung schematron (xrechnung-schematron) and the XRechnung validator configuration: licence, Apache License 2.0 (LICENSE files; NOTICE of the configuration: « Copyright 2020 Koordinierungsstelle für IT-Standards ») — https://github.com/itplr-kosit/xrechnung-schematron/blob/master/LICENSE (2026-11-17)
