# BT-34 Seller Electronic Address

Electronic address of the seller for routing and delivery of electronic invoices

> BT-34 (Seller electronic address) is the seller's routing address used by Peppol and other e-delivery networks, and must carry a scheme identifier from the EAS code list. Optional in base EN 16931 but mandatory in XRechnung and Peppol BIS Billing. BR-62 requires the scheme attribute so the address type is unambiguous. Example: EM:sales@seller.de.
>
> BT-34 · EN 16931 / XRechnung 3.x

## BT Reference Card

Key EN 16931 and XRechnung facts for this business term.

- **BT code**: BT-34
- **Name**: Seller Electronic Address
- **Cardinality**: Mandatory (M) — XRechnung; Optional (O) — EN 16931
- **Business group**: BG-4 SELLER
- **Data type**: Identifier
- **Example value**: EM:sales@seller.de
- **Common error**: BR-62: The Seller electronic address (BT-34) shall have a Scheme identifier. A missing or invalid EAS scheme code (e.g. EM for email, 0088 for GLN) fails validation even when the address value itself is correct.
- **XRechnung note**: XRechnung and Peppol BIS Billing 3.0 promote BT-34 from optional to mandatory (PEPPOL-EN16931-R020), because the seller routing address is needed to deliver the invoice over the network.

## Seller details

Who issued the invoice and how the recipient can identify that business reliably.

- [Validate XML](/en/xrechnung-validator?source=resource&bt=BT-34)
- [Convert invoice](/en/pdf-to-xrechnung?source=resource&bt=BT-34)

## In plain language

Electronic address of the seller for routing and delivery of electronic invoices

Required by XRechnung 3.0.1+. Direct XRechnung delivery can use a valid EAS address such as EM for email. Peppol delivery requires the registered Peppol participant identifier and scheme.

## What you usually enter here

Valid EAS scheme code followed by a colon and the electronic address value

Typical valid values include: EM:seller@company.com, 9930:DE123456789, 0088:4012345000016, 0204:991-12345-73

Optional (0..1) in base EN 16931, but mandatory under XRechnung and Peppol BIS Billing 3.0, which require a routable seller electronic address (enforced by rule PEPPOL-EN16931-R020)

## Where the field sits

BT-34 belongs to the Seller part of the invoice. UBL 2.1 Syntax: Invoice › cac:AccountingSupplierParty › cac:Party › cbc:EndpointID. CII (UN/CEFACT) Syntax: rsm:CrossIndustryInvoice › rsm:SupplyChainTradeTransaction › ram:ApplicableHeaderTradeAgreement › ram:SellerTradeParty › ram:URIUniversalCommunication › ram:URIID.

## What goes wrong often

Avoid values like: DE123456789, EM:not-an-email, 123456789, GLN:4012345000016

Relevant rule codes: PEPPOL-EN16931-R020, BR-62

## Valid Examples

- EM:seller@company.com
- 9930:DE123456789
- 0088:4012345000016
- 0204:991-12345-73

## Invalid Examples

- DE123456789
- EM:not-an-email
- 123456789
- GLN:4012345000016

## Related Fields

- [BT-49 Buyer Electronic Address](/resources/xrechnung/bt-49-buyer-electronic-address)
- [BT-23 Business Process Type Identifier](/resources/xrechnung/bt-23-business-process-type-identifier)
- [BT-29 Seller identifier](/resources/xrechnung/bt-29-seller-identifier)
- [BT-30 Seller legal registration identifier](/resources/xrechnung/bt-30-seller-legal-registration-identifier)

## XML mapping and field facts

Open the technical reference if you need XML paths, validator rule codes, legal wording, or schema-specific mapping details.

### Field ID:
BT-34

### Data Type:
text

### Cardinality:
1..1

### Requirement:
Mandatory

### Max Length:
50 characters

### Since Version:
XRechnung 3.0.1+

## XML Implementation

### UBL 2.1 Syntax
```
/Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID
```

### CII (UN/CEFACT) Syntax
```
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID
```

## Validation Rules

### PEPPOL-EN16931-R020
Seller Electronic Address (BT-34) must be provided

### BR-62
Seller Electronic Address must contain scheme ID and value

## Check whether your XRechnung sets BT-34 correctly

Upload the XML file to the free validator. It applies the KoSIT rules for XRechnung 3.0 and reports a missing address or scheme with its rule ID (PEPPOL-EN16931-R020, BR-62). Creating the invoice from a PDF? The converter requires the address before download and shows its scheme (EM for e-mail unless you choose another).

- [Validate XML](/en/xrechnung-validator)
- [Convert invoice](/en/pdf-to-xrechnung)

Free, no account needed. XML file up to 2 MB.

## FAQ

### What is a Seller Electronic Address?
It is a standardized electronic identifier that enables automated routing and delivery of invoices through electronic networks like Peppol.

### Which scheme identifiers are commonly used?
Common schemes include 9930 (German VAT ID), 0088 (GLN/EAN), 0060 (DUNS), and 0204 (Leitweg-ID).

### Do I need a Peppol registration?
Only for Peppol delivery. Direct XRechnung delivery can use another valid EAS scheme, such as EM for an email address.

## Official sources and tools

- [KoSIT Validator](https://erechnungsvalidator.service-bw.de/)
- [XRechnung Standard](https://xeinkauf.de/xrechnung/)
- [Test Suite](https://github.com/itplr-kosit/xrechnung-testsuite)