Reference
Markdown exportBT-72 Actual delivery date
Date on which the goods were delivered or the service was actually performed.
Quick answer
Date on which the goods were delivered or the service was actually performed.
Delivery and payment
Delivery dates, payment means, and the operational context around settlement.
In plain language
Date on which the goods were delivered or the service was actually performed.
Date on which the goods were delivered or the service was actually performed.
Use this field when the performance date matters for payment terms, acceptance, warranty start, or auditability.
What you usually enter here
ISO 8601 date format (YYYY-MM-DD)
Typical valid values include: 2026-04-08, 2026-03-31
Optional according to EN 16931-1.
What goes wrong often
Avoid values like: 08.04.2026, 2026/04/08
Examples in context
Use this field when the performance date matters for payment terms, acceptance, warranty start, or auditability.
Optional according to EN 16931-1.
Valid Examples
Use these points as the practical checks for this section.
- 2026-04-08
- 2026-03-31
Invalid Examples
Use these points as the practical checks for this section.
- 08.04.2026
- 2026/04/08
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-72
Data Type:
date
Cardinality:
0..1
Requirement:
Optional
Since Version:
Optional
XML Implementation
/Invoice/cac:Delivery/cbc:ActualDeliveryDate/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeDelivery/ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime/udt:DateTimeStringWhy the standard cares about this field
Business Context
Use this field when the performance date matters for payment terms, acceptance, warranty start, or auditability.
Legal Requirement
Optional according to EN 16931-1.