# BR-49: Payment means type code (BT-81) missing

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

A payment instruction (BG-16: `cac:PaymentMeans` in UBL, `ram:SpecifiedTradeSettlementPaymentMeans` in CII) must state how payment is made, with a UNTDID 4461 code in BT-81 (`cbc:PaymentMeansCode`, `ram:TypeCode`). 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, BG-16
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-49 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-49]-A Payment instruction (BG-16) shall specify the Payment means type code (BT-81).
```

## What it checks

A payment instruction (BG-16: `cac:PaymentMeans` in UBL, `ram:SpecifiedTradeSettlementPaymentMeans` in CII) must state how payment is made, with a UNTDID 4461 code in BT-81 (`cbc:PaymentMeansCode`, `ram:TypeCode`).

## Why invoices fail it

Bank details are written in the payment group without the code that says what they are for.

## How to fix it

Write the code: 58 SEPA credit transfer, 30 credit transfer, 59 SEPA direct debit, 48 or 54 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 CII. 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-49.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-49** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans` | A Payment instruction (BG-16) shall specify the Payment means type code (BT-81). |

```diff
  …
        <ram:InvoiceCurrencyCode>EUR</ram:InvoiceCurrencyCode>
        <ram:SpecifiedTradeSettlementPaymentMeans>
+         <ram:TypeCode>58</ram:TypeCode>
          <ram:PayeePartyCreditorFinancialAccount>
            <ram:IBANID>DE02120300000000202051</ram:IBANID>
  …
```

## 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(cbc:PaymentMeansCode)
```

```xpath
context: //ram:SpecifiedTradeSettlementPaymentMeans
test:    (ram:TypeCode)
```

## 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-47: VAT breakdown category code (BT-118) missing](https://veriport.io/einvoice-rules/br-47)
- [BR-48: VAT breakdown rate (BT-119) missing](https://veriport.io/einvoice-rules/br-48)
- [BR-50: Payment account (BT-84) for a credit transfer](https://veriport.io/einvoice-rules/br-50)
- [BR-51: Full card number (BT-87) on the invoice](https://veriport.io/einvoice-rules/br-51)
- [BR-DE-1: Payment instructions (BG-16) required](https://veriport.io/einvoice-rules/br-de-1)
- [BR-DE-19: IBAN (BT-84) invalid for code 58](https://veriport.io/einvoice-rules/br-de-19)
- [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)
