Reference
Markdown exportBT-45 Buyer trading name
Trading or brand name of the buyer when it differs from the legal buyer name.
Quick answer
Trading or brand name of the buyer when it differs from the legal buyer name.
Buyer details
Who receives the invoice and which buyer records or routing data must match.
In plain language
Trading or brand name of the buyer when it differs from the legal buyer name.
Trading or brand name of the buyer when it differs from the legal buyer name.
This helps the seller address the invoice with the name the buyer actually uses in day-to-day business.
What you usually enter here
Trading or brand name
Typical valid values include: City Utilities
Optional according to EN 16931-1.
What goes wrong often
Avoid values like:
Examples in context
This helps the seller address the invoice with the name the buyer actually uses in day-to-day business.
Optional according to EN 16931-1.
Valid Examples
Use these points as the practical checks for this section.
- City Utilities
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-45
Data Type:
text
Cardinality:
0..1
Requirement:
Optional
Max Length:
200 characters
Since Version:
Optional
XML Implementation
/Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyName/cbc:Name/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:SpecifiedLegalOrganization/ram:TradingBusinessNameWhy the standard cares about this field
Business Context
This helps the seller address the invoice with the name the buyer actually uses in day-to-day business.
Legal Requirement
Optional according to EN 16931-1.