Skip to main content

BT-28 Seller trading name

Trading or brand name of the seller when it differs from the legal seller name.

BT-28 (Seller trading name) is the commercial or "doing business as" name shown to customers when it differs from the legal name (BT-27). Optional under EN 16931. Useful for groups that invoice under a parent legal entity but trade under a brand. Example: Muster Trading.

BT-28 · EN 16931 / XRechnung 3.x

BT Reference Card

Key EN 16931 and XRechnung facts for this business term.

BT code
BT-28
Name
Seller trading name
Cardinality
Optional (O)
Business group
BG-4 SELLER
Data type
Text
Example value
Muster Trading

Seller details

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

Quick actions

In plain language

Trading or brand name of the seller when it differs from the legal seller name.

This field helps recipients recognize the seller under the market-facing name they actually know.

What you usually enter here

Trading or brand name

Typical valid values include: Invoice Converter

Optional according to EN 16931-1.

Where the field sits

Seller
UBL 2.1 Syntax
  1. Invoice
  2. cac:AccountingSupplierParty
  3. cac:Party
  4. cac:PartyName
  5. cbc:NameBT-28
CII (UN/CEFACT) Syntax
  1. rsm:CrossIndustryInvoice
  2. rsm:SupplyChainTradeTransaction
  3. ram:ApplicableHeaderTradeAgreement
  4. ram:SellerTradeParty
  5. ram:SpecifiedLegalOrganization
  6. ram:TradingBusinessNameBT-28
BT-28 belongs to the Seller part of the invoice. UBL 2.1 Syntax: Invoice › cac:AccountingSupplierParty › cac:Party › cac:PartyName › cbc:Name. CII (UN/CEFACT) Syntax: rsm:CrossIndustryInvoice › rsm:SupplyChainTradeTransaction › ram:ApplicableHeaderTradeAgreement › ram:SellerTradeParty › ram:SpecifiedLegalOrganization › ram:TradingBusinessName.

What goes wrong often

Avoid values like: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Valid Examples

  • Invoice Converter

Invalid Examples

  • AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

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

Data Type:

text

Cardinality:

0..1

Requirement:

Optional

Max Length:

200 characters

XML Implementation

UBL 2.1 Syntax
/Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name
CII (UN/CEFACT) Syntax
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedLegalOrganization/ram:TradingBusinessName

Next step

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.

Download requires an account. Subscriptions from €10/month with annual billing (excl. taxes), or €5 per conversion (excl. taxes) without a subscription.

Official sources and tools