# BR-DE-30: Creditor identifier (BT-90) for a direct debit

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

When an XRechnung contains direct debit information (BG-19), it must give the bank-assigned creditor identifier, BT-90 (the SEPA Gläubiger-ID): in UBL a `cac:PartyIdentification/cbc:ID` with `schemeID="SEPA"` under the seller (`cac:AccountingSupplierParty/cac:Party`) or the payee (`cac:PayeeParty`), in CII `ram:CreditorReferenceID`. 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:** error
- **Business terms:** BT-90, BG-19
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-30 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-DE-30] Wenn "DIRECT DEBIT" BG-19 vorhanden ist, dann muss "Bank assigned creditor identifier" BT-90 übermittelt werden.
```

## What it checks

When an XRechnung contains direct debit information (BG-19), it must give the bank-assigned creditor identifier, BT-90 (the SEPA Gläubiger-ID): in UBL a `cac:PartyIdentification/cbc:ID` with `schemeID="SEPA"` under the seller (`cac:AccountingSupplierParty/cac:Party`) or the payee (`cac:PayeeParty`), in CII `ram:CreditorReferenceID`.

## Why invoices fail it

The mandate reference is written but the seller’s creditor identifier is not.

## How to fix it

Write the seller’s SEPA creditor identifier (DE98ZZZ09999999999 form).

## 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-30.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-DE-30** | error | `/ubl:Invoice` | Wenn "DIRECT DEBIT" BG-19 vorhanden ist, dann muss "Bank assigned creditor identifier" BT-90 übermittelt werden. |

```diff
  …
      <cac:Party>
        <cbc:EndpointID schemeID="EM">rechnung@hartmann-webdesign.example</cbc:EndpointID>
+       <cac:PartyIdentification>
+         <cbc:ID schemeID="SEPA">DE98ZZZ09999999999</cbc:ID>
+       </cac:PartyIdentification>
        <cac:PostalAddress>
          <cbc:StreetName>Lindenstraße 14</cbc:StreetName>
  …
```

## 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 | /cn:CreditNote
test:    not(cac:PaymentMeans/cac:PaymentMandate) or (cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID='SEPA'] | cac:PayeeParty/cac:PartyIdentification/cbc:ID[@schemeID='SEPA'])
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    (($BT-89-path or $BT-91-path) and $BT-90-path) or $BG-19-not-existing
```

## 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-27: Seller telephone (BT-42) with fewer than 3 digits](https://veriport.io/einvoice-rules/br-de-27)
- [BR-DE-28: Seller e-mail (BT-43) malformed](https://veriport.io/einvoice-rules/br-de-28)
- [BR-DE-31: Debited account (BT-91) for a direct debit](https://veriport.io/einvoice-rules/br-de-31)
- [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)
