Reference
BT-70 Deliver to party name
Name of the party that physically receives the goods or services.
Quick answer
Delivery dates, payment means, and the operational context around settlement.
In plain language
Name of the party that physically receives the goods or services.
Name of the party that physically receives the goods or services.
Use this when the delivery recipient differs from the invoiced buyer or when the receiving location has its own name.
What you usually enter here
Free-text party or site name
Typical valid values include: Site Warehouse North, Bauhof Stadt Köln
Optional according to EN 16931-1.
What goes wrong often
Avoid values like: , AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Examples in context
Use this when the delivery recipient differs from the invoiced buyer or when the receiving location has its own name.
Optional according to EN 16931-1.
Valid Examples
- Site Warehouse North
- Bauhof Stadt Köln
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-70
Data Type:
text
Cardinality:
0..1
Requirement:
Optional
Max Length:
200 characters
Since Version:
Optional
XML Implementation
/Invoice/cac:Delivery/cac:DeliveryParty/cac:PartyName/cbc:Name/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeDelivery/ram:ShipToTradeParty/ram:NameWhy the standard cares about this field
Business Context
Use this when the delivery recipient differs from the invoiced buyer or when the receiving location has its own name.
Legal Requirement
Optional according to EN 16931-1.