# BT-37 Seller City

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

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

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

## Invalid Examples

- M
- AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

## Related Fields

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

- [BT-35 Seller Address Line 1](/resources/xrechnung/bt-35-seller-address-line-1)
- [BT-36 Seller address line 2](/resources/xrechnung/bt-36-seller-address-line-2)
- [BT-38 Seller Post Code](/resources/xrechnung/bt-38-seller-post-code)
- [BT-39 Seller country subdivision](/resources/xrechnung/bt-39-seller-country-subdivision)
- [BT-40 Seller Country Code](/resources/xrechnung/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](https://erechnungsvalidator.service-bw.de/)
- [Invoice Converter](/pdf-to-xrechnung)
- [XRechnung Standard](https://xeinkauf.de/xrechnung/)
- [Test Suite](https://github.com/itplr-kosit/xrechnung-testsuite)