# BR-62 Seller electronic address must have a scheme identifier

The Seller electronic address (BT-34) shall have a Scheme identifier that names the electronic address scheme.

## Problem Description

> **ERROR**: EN 16931 core business rule (CEN)

## Context and Significance

This is an EN 16931 core rule. The scheme identifier (BT-34-1) tells the recipient how to read the seller electronic address: as an e-mail address, a GLN, a company registration number or a VAT number. The error usually appears when the address is exported without the schemeID attribute. The value must also belong to the EAS code list (BR-CL-25), so an invented code fails there. The buyer-side counterpart is BR-63.

## Solution

Set the schemeID attribute on the seller cbc:EndpointID to a code from the EAS code list, for example EM for an e-mail address, 0088 for a GLN, 0009 for a French SIRET or 0106 for a Dutch KvK number. In CII, set ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID/@schemeID.

- [Validate XML](/en/xrechnung-validator?source=resource&rule=BR-62)
- [Convert invoice](/en/pdf-to-xrechnung?source=resource&rule=BR-62)

## Valid Examples

- BT-34 = seller@example.com with schemeID="EM"

## Invalid Examples

- BT-34 EndpointID present but with no schemeID attribute

## Code Examples

### Valid XML
```
<cac:AccountingSupplierParty>
  <cac:Party>
    <cbc:EndpointID schemeID="EM">seller@example.com</cbc:EndpointID>
  </cac:Party>
</cac:AccountingSupplierParty>
```

### Invalid XML
```
<cac:AccountingSupplierParty>
  <cac:Party>
    <cbc:EndpointID>seller@example.com</cbc:EndpointID>
  </cac:Party>
</cac:AccountingSupplierParty>
```

## Affected Fields

- [BT-34 Seller electronic address](/resources/xrechnung/bt-34-seller-electronic-address)

## Related Rules

- [BR-63](/resources/kosit-validator-errors/br-63-buyer-electronic-address-scheme-required)

## Validation Tools

- [Official KoSIT Validator](https://github.com/itplr-kosit/validator): Run the official KoSIT validator with the XRechnung configuration to check EN 16931 and XRechnung rules.
- [Convert PDF to XRechnung](/pdf-to-xrechnung): Find validation errors during conversion and review each correction.

## Related Resources

- [Official Specification](https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/)
- [Test Suite](https://github.com/itplr-kosit/xrechnung-testsuite)
- [All validation errors](/resources/kosit-validator-errors): Overview of the EN 16931, XRechnung and Peppol validation rules explained here.