Reference
BT-28 Seller trading name
Trading or brand name of the seller when it differs from the legal seller name.
Quick answer
Who issued the invoice and how the recipient can identify that business reliably.
In plain language
Trading or brand name of the seller when it differs from the legal seller name.
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.
What goes wrong often
Avoid values like: , AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Examples in context
This field helps recipients recognize the seller under the market-facing name they actually know.
Optional according to EN 16931-1.
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
Since Version:
Optional
XML Implementation
/Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedLegalOrganization/ram:TradingBusinessNameWhy the standard cares about this field
Business Context
This field helps recipients recognize the seller under the market-facing name they actually know.
Legal Requirement
Optional according to EN 16931-1.