# BR-49

Quoted from a public specification. This page is not a validator, and it is not tax, legal, or accounting advice.

- Country: EU
- Syntax: UBL
- Severity: fatal
- Statement language: en
- Last verified: 2026-10-18

## Official statement

> A Payment instruction (BG-16) shall specify the Payment means type code (BT-81).

Source: https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/BR-49/

Peppol BIS Billing 3.0, May 2026 release, EN 16931 model bound to UBL

Severity note: fatal, from the Flag column of the Peppol BIS Billing 3.0 UBL rules index retrieved 2026-10-18.

## Plain-language reading

A Payment instruction (BG-16) must specify the Payment means type code (BT-81). The message starts with "A", not "Each". It says "shall specify", not "shall have". It ends with a period. It does not say "Document level". The context is the payment means. The published test checks that cbc:PaymentMeansCode exists. It does not require a particular code.

## What to change

Put a payment means type code (BT-81) on the payment instruction.

## Illustration

Illustration of the condition in the official statement. Not an example published by the source.

**Fails the stated condition.** A payment means element has no payment means code.

**Passes the stated condition.** That payment means element has a payment means code.

## Published context and test

Copied from the source. Not reimplemented on this page.

```
cac:PaymentMeans
```

```
exists(cbc:PaymentMeansCode)
```

[All rule notes](https://einvoicegoblin.com/rules/index.md) · [JSON](https://einvoicegoblin.com/rules/BR-49.json) · [HTML](https://einvoicegoblin.com/rules/BR-49/) · [llms.txt](https://einvoicegoblin.com/llms.txt) · [Invoice page](https://einvoicegoblin.com/) · [Privacy](https://einvoicegoblin.com/privacy.html)