# BR-61: Payment account (BT-84) for codes 30 and 58

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

When the payment means type code (BT-81) is 30 (credit transfer) or 58 (SEPA credit transfer), the payment account identifier, BT-84, must be given: `cac:PayeeFinancialAccount/cbc:ID` in UBL, `ram:PayeePartyCreditorFinancialAccount/ram:IBANID` or `ram:ProprietaryID` in CII. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **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-61 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-61]-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.
```

## What it checks

When the payment means type code (BT-81) is 30 (credit transfer) or 58 (SEPA credit transfer), the payment account identifier, BT-84, must be given: `cac:PayeeFinancialAccount/cbc:ID` in UBL, `ram:PayeePartyCreditorFinancialAccount/ram:IBANID` or `ram:ProprietaryID` in CII.

## Why invoices fail it

The invoice asks for a transfer but the seller’s IBAN is missing, often because it is printed only in the PDF footer.

## How to fix it

Write the seller’s IBAN in BT-84, or use another payment means code (1, 10, 48, 59…) when no transfer is requested.

## 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 EN 16931 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-61.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **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. |

```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 CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: cac:PaymentMeans
test:    (exists(cac:PayeeFinancialAccount/cbc:ID) and ((normalize-space(cbc:PaymentMeansCode) = '30') or (normalize-space(cbc:PaymentMeansCode) = '58') )) or ((normalize-space(cbc:PaymentMeansCode) != '30') and (normalize-space(cbc:PaymentMeansCode) != '58'))
```

```xpath
context: //ram:SpecifiedTradeSettlementPaymentMeans[ram:TypeCode='30' or ram:TypeCode='58']/ram:PayeePartyCreditorFinancialAccount
test:    (ram:IBANID) or (ram:ProprietaryID)
```

## 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-56: Tax representative VAT identifier (BT-63)](https://veriport.io/einvoice-rules/br-56)
- [BR-57: Deliver-to country code (BT-80) missing](https://veriport.io/einvoice-rules/br-57)
- [BR-62: Seller electronic address scheme (BT-34-1)](https://veriport.io/einvoice-rules/br-62)
- [BR-63: Buyer electronic address scheme (BT-49-1)](https://veriport.io/einvoice-rules/br-63)
- [BR-DE-19: IBAN (BT-84) invalid for code 58](https://veriport.io/einvoice-rules/br-de-19)
- [BR-DE-20: Debited IBAN (BT-91) invalid for code 59](https://veriport.io/einvoice-rules/br-de-20)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [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

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
