Skip to main content
Invoice-Converter.comInvoice-Converter
BlogPricing
Convert InvoiceConvert
ConvertConvert Invoice
⌘K
Documentation overview
Glossary
Code Lists
XRechnung Fields
Invoice basics
BT-1
BT-2
BT-3
BT-5
BT-6
BT-7
BT-8
BT-10
BT-11
BT-12
BT-14
BT-15
BT-16
BT-17
BT-18
BT-19
BT-21
BT-22
BT-23
BT-24
BT-25
BT-26
Delivery and payment
BT-9
BT-13
BT-20
BT-59
BT-60
BT-61
BT-70
BT-71
BT-72
BT-73
BT-74
BT-75
BT-76
BT-77
BT-78
BT-79
BT-80
BT-81
BT-82
BT-83
BT-84
BT-85
BT-86
BT-87
BT-88
BT-89
BT-90
BT-91
Seller details
BT-27
BT-28
BT-29
BT-30
BT-31
BT-32
BT-33
BT-34
BT-35
BT-36
BT-37
BT-38
BT-39
BT-40
BT-41
BT-42
BT-43
BT-62
BT-63
BT-64
BT-65
BT-66
BT-67
BT-68
BT-69
Buyer details
BT-44
BT-45
BT-46
BT-47
BT-48
BT-49
BT-50
BT-51
BT-52
BT-53
BT-54
BT-55
BT-56
BT-57
BT-58
Discounts and charges
BT-92
BT-93
BT-94
BT-95
BT-96
BT-97
BT-98
BT-99
BT-100
BT-101
BT-102
BT-103
BT-104
BT-105
Taxes and totals
BT-106
BT-107
BT-108
BT-109
BT-110
BT-111
BT-112
BT-113
BT-114
BT-115
BT-116
BT-117
BT-118
BT-119
BT-120
BT-121
BT-122
BT-123
BT-124
BT-125
Line items
BT-126
BT-127
BT-128
BT-129
BT-130
BT-131
BT-132
BT-133
BT-134
BT-135
BT-136
BT-137
BT-138
BT-139
BT-140
BT-141
BT-142
BT-143
BT-144
BT-145
BT-146
BT-147
BT-148
BT-149
BT-150
BT-151
BT-152
BT-153
BT-154
BT-155
BT-156
BT-157
BT-158
BT-159
BT-160
BT-161
BT-162
BT-163
BT-164
BT-165
BT-185
BT-186
ZUGFeRD Profiles
  1. E-Invoicing Resources
  2. XRechnung Fields
  3. BT-34

Reference

Markdown export

BT-34 Seller Electronic Address

Electronic address of the seller for routing and delivery of electronic documents within the PEPPOL network

Quick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationValidation RulesWhy the standard cares about this fieldFAQOfficial sources and tools

Quick answer#

Electronic address of the seller for routing and delivery of electronic documents within the PEPPOL network

Seller details

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

In plain language#

Electronic address of the seller for routing and delivery of electronic documents within the PEPPOL network

Electronic address of the seller for routing and delivery of electronic documents within the PEPPOL network

Essential for electronic invoice routing in PEPPOL networks and automated processing. Required for all B2B and B2G electronic invoicing in compliance with XRechnung 3.0.1+

What you usually enter here#

Scheme identifier (4 digits) followed by colon and identifier value

Typical valid values include: 9930:DE123456789, 0088:4012345000017, 9906:1234567890123, 0204:7300010000001

Mandatory since XRechnung 3.0.1 (2024) for electronic address identification and PEPPOL network routing compliance

What goes wrong often#

Avoid values like: DE123456789, seller@company.com, 123456789, GLN:4012345000017

Relevant rule codes: BR-DE-31, BR-62

Examples in context#

Essential for electronic invoice routing in PEPPOL networks and automated processing. Required for all B2B and B2G electronic invoicing in compliance with XRechnung 3.0.1+

Mandatory since XRechnung 3.0.1 (2024) for electronic address identification and PEPPOL network routing compliance

Valid Examples#

Use these points as the practical checks for this section.

  • 9930:DE123456789
  • 0088:4012345000017
  • 9906:1234567890123
  • 0204:7300010000001

Invalid Examples#

Use these points as the practical checks for this section.

  • DE123456789
  • seller@company.com
  • 123456789
  • GLN:4012345000017

Related Fields#

Essential for electronic invoice routing in PEPPOL networks and automated processing. Required for all B2B and B2G electronic invoicing in compliance with XRechnung 3.0.1+

BT-49 Buyer Electronic Address
BT-23 Business Process Type Identifier
BT-29 Seller identifier
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
/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID

Validation Rules#

BR-DE-31

Seller Electronic Address (BT-34) must be provided

BR-62

Seller Electronic Address must contain scheme ID and value

Why the standard cares about this field#

Business Context

Essential for electronic invoice routing in PEPPOL networks and automated processing. Required for all B2B and B2G electronic invoicing in compliance with XRechnung 3.0.1+

Legal Requirement

Mandatory since XRechnung 3.0.1 (2024) for electronic address identification and PEPPOL network routing compliance

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 tax number), 0088 (EAN/GLN), 9906 (DUNS), and 0204 (Dutch KvK number).

How do I register for a PEPPOL electronic address?

Contact a certified PEPPOL Access Point provider who can assign and manage your electronic address for invoice exchange.

Official sources and tools#

KoSIT Validator
Invoice Converter
XRechnung Standard
Test Suite
BT-33BT-35
On this page
Quick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationValidation RulesWhy the standard cares about this fieldFAQOfficial sources and tools

Invoice-Converter.com

Empowering businesses across Europe to effortlessly comply with XRechnung regulations. Join hundreds who've automated their invoice conversion process.

20,000+ invoices processed
Fast & Secure
Trusted by hundreds

Features

Convert PDFs & create

  • PDF to XRechnung
  • PDF to UBL
  • PDF to XRechnung (CII)
  • PDF to ZUGFeRD
  • PDF to Factur-X
  • Create XRechnung
  • XRechnung to PDF

View & validate

  • XRechnung/XML Viewer
  • XRechnung Validator

Quick Links

  • Resources
  • Trust & Security Center
  • Developer API Documentation
  • Blog
  • FAQ
  • Pricing
  • Climate Contribution

Legal

  • Imprint
  • Privacy Policy
  • Data Processing Agreement
  • Terms & Conditions
  • Money-Back Guarantee

Get in Touch

contact@invoice-converter.com
Start Converting
© 2026 Invoice-Converter.com.Made with in Europe
GDPR Compliant
German Server