# BR-61 Credit transfer account identifier is required

If the payment means type code (BT-81) means credit transfer (code 30) or SEPA credit transfer (code 58), the payment account identifier (BT-84) must be present.

## Problem Description

> **ERROR**: EN 16931 core business rule (CEN)

> **Where BR-61 is checked**
>
> A validator checks an e-invoice in stages. First the file must be well-formed XML that matches the UBL or CII schema (XSD). Then the EN 16931 business rules run: BR core rules, BR-CO calculations, BR-CL code lists, BR-DEC decimals and VAT-category rules such as BR-S. Next come the national or network rules that BT-24 selects: BR-DE for XRechnung, PEPPOL-EN16931 for Peppol BIS Billing. The report lists every failed rule: one error means reject, warnings alone still mean accept. BR-61: EN 16931 core rule, reported in the stage “EN 16931 rules”.

## Solution

Add cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:ID in UBL, or ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeePartyCreditorFinancialAccount/ram:IBANID in CII (ram:ProprietaryID for an account without IBAN). For a SEPA credit transfer, this is the IBAN. If the invoice is not paid by credit transfer, use the correct payment means code instead.

- [Check XML for free](/en/xrechnung-validator?source=resource&rule=BR-61)

## Context and Significance

This is an EN 16931 core rule. With payment means code 30 or 58, the buyer needs the account to pay into: without BT-84 the buyer cannot execute the transfer, even if the payment terms are otherwise complete. BR-61 differs from BR-50: BR-61 checks that codes 30 and 58 come with an account identifier at all, BR-50 checks that an account group which is present does not have an empty identifier. In practice, the error occurs when the ERP sets the payment method to credit transfer but the seller IBAN is not included in the export.

## Valid Examples

- PaymentMeansCode 58 with PayeeFinancialAccount ID DE89370400440532013000

## Invalid Examples

- PaymentMeansCode 58 without any payee financial account

## Code Examples

### Valid XML
```
<cac:PaymentMeans>
  <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
  <cac:PayeeFinancialAccount>
    <cbc:ID>DE89370400440532013000</cbc:ID>
  </cac:PayeeFinancialAccount>
</cac:PaymentMeans>
```

### Invalid XML
```
<cac:PaymentMeans>
  <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
</cac:PaymentMeans>
```

## Affected Fields

- [BT-81 Payment means type code](/resources/xrechnung/bt-81-payment-means-type-code)
- [BT-84 Payment account identifier](/resources/xrechnung/bt-84-payment-account-identifier)

## Related Rules

- [BR-50](/resources/kosit-validator-errors/br-50-credit-transfer-account-identifier-required)
- [BR-49](/resources/kosit-validator-errors/br-49-payment-means-type-code-required)
- [BR-DE-19](/resources/kosit-validator-errors/br-de-19-sepa-payment-account-must-be-valid-iban)

## Validation Tools

- [Official KoSIT Validator](https://github.com/itplr-kosit/validator): Run the official KoSIT validator with the XRechnung configuration to check EN 16931 and XRechnung rules.
- [Convert PDF to XRechnung](/pdf-to-xrechnung): Find validation errors during conversion and review each correction.

## Related Resources

- [Official Specification](https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/)
- [Test Suite](https://github.com/itplr-kosit/xrechnung-testsuite)
- [All validation errors](/resources/kosit-validator-errors): Overview of the EN 16931, XRechnung and Peppol validation rules explained here.
