# BR-DE-23-a: Credit transfer group (BG-17) for codes 30, 58

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

When the payment means code (BT-81) is 30 or 58 (credit transfer), the credit transfer group, BG-17, must be present: `cac:PayeeFinancialAccount` in UBL, `ram:PayeePartyCreditorFinancialAccount` in CII, with the account to pay into. 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-81, BG-17
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-23-a 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-23-a] Wenn BT-81 "Payment means type code" einen Schlüssel für Überweisungen enthält (30, 58), muss BG-17 "CREDIT TRANSFER" übermittelt werden.
```

## What it checks

When the payment means code (BT-81) is 30 or 58 (credit transfer), the credit transfer group, BG-17, must be present: `cac:PayeeFinancialAccount` in UBL, `ram:PayeePartyCreditorFinancialAccount` in CII, with the account to pay into.

## Why invoices fail it

Code 58 is written as a default while the IBAN is missing.

## How to fix it

Add the seller’s account (IBAN in BT-84), or use the code of the actual payment means.

## 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-23-a and 2 other rules, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| [BR-61](/einvoice-rules/br-61) | error | `/ubl:Invoice/cac:PaymentMeans` | If the Payment means type code (BT-81) means SEPA credit transfer, Local credit transfer or Non-SEPA international credit transfer, the Payment account identifier (BT-84) shall be present. |
| **BR-DE-23-a** | error | `/ubl:Invoice/cac:PaymentMeans` | Wenn BT-81 "Payment means type code" einen Schlüssel für Überweisungen enthält (30, 58), muss BG-17 "CREDIT TRANSFER" übermittelt werden. |
| [BR-DE-19](/einvoice-rules/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
  …
    <cac:PaymentMeans>
      <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
+     <cac:PayeeFinancialAccount>
+       <cbc:ID>DE02120300000000202051</cbc:ID>
+     </cac:PayeeFinancialAccount>
    </cac:PaymentMeans>
    <cac:TaxTotal>
  …
```

## 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:    cac:PayeeFinancialAccount
```

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

## 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-21: Specification identifier not XRechnung’s](https://veriport.io/einvoice-rules/br-de-21)
- [BR-DE-22: Attachment file names not unique](https://veriport.io/einvoice-rules/br-de-22)
- [BR-DE-23-b: Card or direct debit data with a transfer code](https://veriport.io/einvoice-rules/br-de-23-b)
- [BR-DE-24-a: Card group (BG-18) for codes 48, 54, 55](https://veriport.io/einvoice-rules/br-de-24-a)
- [BR-49: Payment means type code (BT-81) missing](https://veriport.io/einvoice-rules/br-49)
- [BR-61: Payment account (BT-84) for codes 30 and 58](https://veriport.io/einvoice-rules/br-61)
- [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)
