# BT-35 Seller Address Line 1

The main address line identifying the seller's postal address. Typically contains street name and number.

## Quick answer

> **Seller details**: Who issued the invoice and how the recipient can identify that business reliably.

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

## In plain language

Use this field for the seller street, building, or post-box line when it forms part of the postal address.

## What you usually enter here

Free text for street and number

Typical valid values include: Musterstraße 123, Hauptplatz 45a, Am Marktplatz 1-3, Industrieallee 78

BT-35 is optional. BR-08 requires the seller postal address group BG-5, not this street line by itself.

## Where the field sits

BT-35 belongs to the Seller part of the invoice. UBL 2.1 Syntax: Invoice › cac:AccountingSupplierParty › cac:Party › cac:PostalAddress › cbc:StreetName. CII (UN/CEFACT) Syntax: rsm:CrossIndustryInvoice › rsm:SupplyChainTradeTransaction › ram:ApplicableHeaderTradeAgreement › ram:SellerTradeParty › ram:PostalTradeAddress › ram:LineOne.

## What goes wrong often

Avoid values like: Str. 123, AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

## Valid Examples

- Musterstraße 123
- Hauptplatz 45a
- Am Marktplatz 1-3
- Industrieallee 78
- Bahnhofstraße 12

## Invalid Examples

- Str. 123
- AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

## Related Fields

- [BT-27 Seller Name](/resources/xrechnung/bt-27-seller-name)
- [BT-36 Seller address line 2](/resources/xrechnung/bt-36-seller-address-line-2)
- [BT-37 Seller City](/resources/xrechnung/bt-37-seller-city)
- [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-35

### Data Type:
text

### Cardinality:
0..1

### Requirement:
Optional

### Max Length:
100 characters

## XML Implementation

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

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

## Create an XRechnung from your PDF

The converter reads the invoice and shows the fields it found before download, so you can check and correct the values. No PDF? Fill in the XRechnung directly in the form.

- [Convert invoice](/en/pdf-to-xrechnung)
- [Fill in XRechnung in the form](/en/create-xrechnung)

Trying it and buying a single conversion work without an account. Subscriptions from €10/month with annual billing (excl. taxes), or €5 per conversion (excl. taxes) without a subscription.

## FAQ

### How should I format German street addresses?
Follow German postal standards: "Straßenname Hausnummer" (e.g., "Musterstraße 123", "Am Marktplatz 45a"). Include apartment/suite numbers if relevant.

### What if the address doesn't fit in one line?
Use the primary street and number in Address Line 1. Additional information like building names or complex numbers can go in Address Line 2 (BT-36).

### Should I include PO Box information here?
No, if using a PO Box, put it in Address Line 1 as "Postfach [number]" but ensure this is the actual business address. Physical addresses are preferred for business registration.

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