# BT-41 Seller contact point

Name of the contact person or department on the seller side.

> BT-41 (Seller contact point) names the contact department or person within the seller organisation, inside BG-6 Seller contact. Optional under EN 16931. XRechnung makes the seller contact group mandatory, so BT-41 must be present alongside the contact telephone and email. Example: Accounts Receivable, Invoicing Team.
>
> BT-41 · EN 16931 / XRechnung 3.x

## BT Reference Card

Canonical EN 16931 / XRechnung facts for this business term — citable from this anchor.

- **BT code**: BT-41
- **Name**: Seller contact point
- **Cardinality**: Mandatory (M) — XRechnung; Optional (O) — EN 16931
- **Business group**: BG-6 SELLER CONTACT
- **Data type**: Text
- **Example value**: Accounts Receivable, Invoicing Team
- **Common error**: BR-DE-5: The Seller contact point (BT-41) must be present. XRechnung requires the seller contact group, so an invoice omitting the contact name is rejected even though EN 16931 treats it as optional.
- **XRechnung note**: XRechnung promotes the Seller contact (BG-6) to mandatory, requiring BT-41 (name), BT-42 (telephone) and BT-43 (email); BT-41 specifically is enforced by BR-DE-5.

## Quick answer

Name of the contact person or department on the seller side.

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

- validate
- convert

## In plain language

Name of the contact person or department on the seller side.

Name of the contact person or department on the seller side.

This gives the buyer a clear human contact for questions about the invoice or the underlying delivery.

## What you usually enter here

Person or department name

Typical valid values include: Accounts Receivable

Optional according to EN 16931-1.

## What goes wrong often

Avoid values like:

## Examples in context

This gives the buyer a clear human contact for questions about the invoice or the underlying delivery.

Optional according to EN 16931-1.

## Valid Examples

- Accounts Receivable

## Related Fields

This gives the buyer a clear human contact for questions about the invoice or the underlying delivery.

- [BT-42 Seller contact telephone number](/resources/xrechnung/bt-42-seller-contact-telephone-number)
- [BT-43 Seller contact email address](/resources/xrechnung/bt-43-seller-contact-email-address)

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

### Data Type:
text

### Cardinality:
0..1

### Requirement:
Optional

### Max Length:
100 characters

### Since Version:
Optional

## XML Implementation

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

### CII (UN/CEFACT) Syntax
```
/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedTradeContact/ram:PersonName
```

## Why the standard cares about this field

### Business Context
This gives the buyer a clear human contact for questions about the invoice or the underlying delivery.

### Legal Requirement
Optional according to EN 16931-1.

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