# BT-59 Payee name

Name of the party that should receive the payment if it is not the seller.

## Quick answer

> **Delivery and payment**: Delivery dates, payment means, and the operational context around settlement.

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

## In plain language

This field is needed in factoring, shared-service, or treasury setups where the payee differs from the seller entity.

## What you usually enter here

Payee legal or business name

Typical valid values include: ABC Factoring GmbH

Required by BR-17 when BG-10 Payee differs from BG-4 Seller. Otherwise optional.

## Where the field sits

BT-59 belongs to the Payment part of the invoice. UBL 2.1 Syntax: Invoice › cac:PayeeParty › cac:PartyName › cbc:Name. CII (UN/CEFACT) Syntax: rsm:CrossIndustryInvoice › rsm:SupplyChainTradeTransaction › ram:ApplicableHeaderTradeSettlement › ram:PayeeTradeParty › ram:Name.

## What goes wrong often

Relevant rule codes: BR-17

## Valid Examples

- ABC Factoring GmbH

## Related Fields

- [BT-60 Payee identifier](/resources/xrechnung/bt-60-payee-identifier)
- [BT-61 Payee legal registration identifier](/resources/xrechnung/bt-61-payee-legal-registration-identifier)
- [BT-84 Payment account identifier](/resources/xrechnung/bt-84-payment-account-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-59

### Data Type:
text

### Cardinality:
0..1

### Requirement:
Optional

### Max Length:
200 characters

## XML Implementation

### UBL 2.1 Syntax
```
/Invoice/cac:PayeeParty/cac:PartyName/cbc:Name
```

### CII (UN/CEFACT) Syntax
```
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:Name
```

## Validation Rules

### BR-17
BR-17

## Check whether your XRechnung sets BT-59 correctly

Upload the XML file to the free validator. It applies the KoSIT rules for XRechnung 3.0 and names each finding with its rule ID, for this field for example BR-17. Creating a new invoice instead? The converter checks the invoice against the same rules and shows the findings before download.

- [Validate XML](/en/xrechnung-validator)
- [Convert invoice](/en/pdf-to-xrechnung)

Free, no account needed. XML file up to 2 MB.

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