# BR-63

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

> The Buyer electronic address (BT-49) shall have a Scheme identifier.

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

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

The Buyer electronic address (BT-49) must have a Scheme identifier. The message starts with "The", not "Each", and says "shall have a Scheme identifier". It ends with a period. The context is the buyer party endpoint id. The published test checks that the schemeID attribute exists. It does not check the scheme value.

## What to change

When a buyer electronic address (BT-49) is sent, give that endpoint id a scheme identifier.

## Illustration

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

**Fails the stated condition.** The buyer endpoint id has no schemeID attribute.

**Passes the stated condition.** That endpoint id has a schemeID attribute.

## Published context and test

Copied from the source. Not reimplemented on this page.

```
cac:AccountingCustomerParty/cac:Party/cbc:EndpointID
```

```
exists(@schemeID)
```

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