# BR-CL-16: Payment means code (BT-81) not UNTDID 4461

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

The payment means type code, BT-81, must come from UNTDID 4461. 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
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CL-16 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-CL-16]-Payment means in an invoice MUST be coded using UNCL4461 code list
```

```text
[BR-CL-16]-Payment means in an invoice MUST be coded using UNTDID 4461 code list
```

## What it checks

The payment means type code, BT-81, must come from UNTDID 4461.

## Why invoices fail it

An internal payment method key or a text (« SEPA ») is written as code.

## How to fix it

Use the UNTDID 4461 code: 58 SEPA credit transfer, 30 credit transfer, 59 SEPA direct debit, 48 bank card, 54 credit card, 10 cash, 1 not defined.

## 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-CL-16.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CL-16** | error | `/ubl:Invoice/cac:PaymentMeans/cbc:PaymentMeansCode` | Payment means in an invoice MUST be coded using UNCL4461 code list |

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

## 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/cbc:PaymentMeansCode
test:    ( ( not(contains(normalize-space(.),' ')) and contains( ' 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 74 75 76 77 78 91 92 93 94 95 96 97 98 ZZZ ',concat(' ',normalize-space(.),' ') ) ) )
```

```xpath
context: ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode
test:    ((not(contains(normalize-space(.), ' ')) and contains(' 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 74 75 76 77 78 91 92 93 94 95 96 97 98 ZZZ ', concat(' ', normalize-space(.), ' '))))
```

## 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-CL-14: Country code not ISO 3166-1](https://veriport.io/einvoice-rules/br-cl-14)
- [BR-CL-15: Item country of origin not ISO 3166-1](https://veriport.io/einvoice-rules/br-cl-15)
- [BR-CL-17: VAT category code not UNTDID 5305](https://veriport.io/einvoice-rules/br-cl-17)
- [BR-CL-18: Line VAT category code not UNTDID 5305](https://veriport.io/einvoice-rules/br-cl-18)
- [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)
