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-37

Reference

Markdown export

BT-37 Seller City

The common name of the city, town or village where the seller's address is located

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#

The common name of the city, town or village where the seller's address is located

Seller details

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

In plain language#

The common name of the city, town or village where the seller's address is located

The common name of the city, town or village where the seller's address is located

Critical component for postal delivery and geographic identification of the seller's business location

What you usually enter here#

Free text for city name

Typical valid values include: München, Berlin, Hamburg, Frankfurt am Main

Mandatory field for complete address specification according to EN 16931 and German postal regulations

What goes wrong often#

Avoid values like: M, AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Relevant rule codes: BR-CO-26

Examples in context#

Critical component for postal delivery and geographic identification of the seller's business location

Mandatory field for complete address specification according to EN 16931 and German postal regulations

Valid Examples#

Use these points as the practical checks for this section.

  • München
  • Berlin
  • Hamburg
  • Frankfurt am Main
  • Düsseldorf
  • Stuttgart

Invalid Examples#

Use these points as the practical checks for this section.

  • M
  • AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Related Fields#

Critical component for postal delivery and geographic identification of the seller's business location

BT-35 Seller Address Line 1
BT-36 Seller address line 2
BT-38 Seller Post Code
BT-39 Seller country subdivision
BT-40 Seller Country Code

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-37

Data Type:

text

Cardinality:

1..1

Requirement:

Mandatory

Max Length:

50 characters

Since Version:

XRechnung 1.0+

XML Implementation#

UBL 2.1 Syntax
/Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:CityName
CII (UN/CEFACT) Syntax
/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:CityName

Validation Rules#

BR-CO-26

BR-CO-26

Why the standard cares about this field#

Business Context

Critical component for postal delivery and geographic identification of the seller's business location

Legal Requirement

Mandatory field for complete address specification according to EN 16931 and German postal regulations

FAQ#

Should I use the official city name or common name?

Use the official postal city name as recognized by Deutsche Post. For cities with districts, use the main city name unless the district has its own postal identity.

What about cities with special characters or umlauts?

Include German umlauts and special characters as they appear officially (ä, ö, ü, ß). Most electronic systems now support these characters properly.

How should I handle compound city names?

Use the complete official name including connecting words (e.g., "Frankfurt am Main", "Neustadt an der Weinstraße"). Don't abbreviate unless space is critically limited.

Official sources and tools#

KoSIT Validator
Invoice Converter
XRechnung Standard
Test Suite
BT-36BT-38
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