# BR-63: Buyer electronic address scheme (BT-49-1)

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

The buyer’s electronic address, BT-49 (`cbc:EndpointID` under the customer party, `ram:URIUniversalCommunication/ram:URIID` under `ram:BuyerTradeParty`), must carry an EAS scheme identifier in `schemeID`. 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-49
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-63 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-63]-The Buyer electronic address (BT-49) shall have a Scheme identifier.
```

## What it checks

The buyer’s electronic address, BT-49 (`cbc:EndpointID` under the customer party, `ram:URIUniversalCommunication/ram:URIID` under `ram:BuyerTradeParty`), must carry an EAS scheme identifier in `schemeID`.

## Why invoices fail it

A Leitweg-ID or e-mail address is written as the buyer’s endpoint without the scheme.

## How to fix it

Add the EAS scheme of the buyer’s address: 0204 for a Leitweg-ID, EM for an e-mail, 0208 for a Belgian enterprise number.

## 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-63.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-63** | error | `/ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID` | The Buyer electronic address (BT-49) shall have a Scheme identifier. |

```diff
  …
    <cac:AccountingCustomerParty>
      <cac:Party>
-       <cbc:EndpointID>buchhaltung@mustermann.example</cbc:EndpointID>
+       <cbc:EndpointID schemeID="EM">buchhaltung@mustermann.example</cbc:EndpointID>
        <cac:PostalAddress>
          <cbc:StreetName>Industrieweg 7</cbc:StreetName>
  …
```

## 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:AccountingCustomerParty/cac:Party/cbc:EndpointID
test:    exists(@schemeID)
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    normalize-space(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniversalCommunication[1]/ram:URIID/@schemeID) != '' or not (rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniversalCommunication)
```

## 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-61: Payment account (BT-84) for codes 30 and 58](https://veriport.io/einvoice-rules/br-61)
- [BR-62: Seller electronic address scheme (BT-34-1)](https://veriport.io/einvoice-rules/br-62)
- [BR-64: Item standard identifier scheme (BT-157-1)](https://veriport.io/einvoice-rules/br-64)
- [BR-65: Item classification scheme (BT-158-1)](https://veriport.io/einvoice-rules/br-65)
- [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)
