Skip to content

BR-62: Seller electronic address scheme identifier (BT-34-1) is missing

Official message

[BR-62] The Seller electronic address (BT-34) shall have a Scheme identifier.

EN 16931 (CII) · Error · Message language: English · Version: xrechnung-3.0.2-validator-configuration-2026-08-31

[BR-62] The Seller electronic address (BT-34) shall have a Scheme identifier.

EN 16931 (UBL) · Error · Message language: English · Version: xrechnung-3.0.2-validator-configuration-2026-08-31

[BR-62] The Seller electronic address (BT-34) shall have a Scheme identifier.

Factur-X / ZUGFeRD EN 16931 · Error · Message language: English · Version: Factur-X 1.08 / ZUGFeRD 2.4
Severity
Error The invoice is invalid and may be rejected by the recipient.
Applies to
EN 16931 (CII), EN 16931 (UBL), Factur-X / ZUGFeRD EN 16931
Affected fields
BT-34

What does this mean?

If a seller electronic address (BT-34) is given, it must have a scheme identifier (BT-34-1) stating what kind of address it is. The attribute schemeID is missing; CII also rejects an empty attribute, UBL only a missing one.

Typical causes

The electronic address, e.g. an e-mail address or Peppol ID, was given without a scheme.
CII: The first electronic address is checked; a scheme on a further address only is not sufficient.

How to fix the error

State the scheme code from the EAS code list for the electronic address, e.g. EM for an e-mail address, 0204 for a German Leitweg-ID or 0088 for a GLN.
CII: ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID/@schemeID, UBL: cac:AccountingSupplierParty/cac:Party/cbc:EndpointID/@schemeID.
Generate and validate the invoice again.

In E-Rechnungsfreund

In the invoice form ("Experte" view), section "Verkäufer (BG-4)" (seller), select the appropriate scheme in the field "EAS-Schema der elektron. Adresse (BT-34-1/49-1)" (EAS scheme of the electronic address). If no scheme is selected, the address from "Elektronische Adresse (BT-34/49)" is output without a scheme.

Example

Wrong

<ram:SellerTradeParty>
  ...
  <ram:URIUniversalCommunication>
    <ram:URIID>invoice@example-ltd.com</ram:URIID>
  </ram:URIUniversalCommunication>
  ...
</ram:SellerTradeParty>

Correct

<ram:SellerTradeParty>
  ...
  <ram:URIUniversalCommunication>
    <ram:URIID schemeID="EM">invoice@example-ltd.com</ram:URIID>
  </ram:URIUniversalCommunication>
  ...
</ram:SellerTradeParty>
For developers: test expression per syntax

EN 16931 (CII) (CII)

Context: /rsm:CrossIndustryInvoice

normalize-space(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication[1]/ram:URIID/@schemeID) != '' or not (rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication)

EN 16931 (UBL) (UBL)

Context: cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

exists(@schemeID)

Factur-X / ZUGFeRD EN 16931 (CII)

Technical ID in the source: FX-SCH-A-000158

Context: /rsm:CrossIndustryInvoice

normalize-space(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication[1]/ram:URIID/@schemeID) != '' or not (rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication)

Related validation rules

  • BR-01: Specification identifier (BT-24) is missing
  • BR-02: Invoice number (BT-1) is missing
  • BR-03: Invoice issue date (BT-2) is missing
  • BR-04: Invoice type code (BT-3) is missing
  • BR-05: Invoice currency code (BT-5) is missing
  • BR-06: Seller name (BT-27) is missing

Last updated:
Explanation of the validation rule, not legal or tax advice.