Reference
Markdown exportBT-74 Invoicing period end date
End date of the period to which the invoice applies.
Quick answer
End date of the period to which the invoice applies.
Delivery and payment
Delivery dates, payment means, and the operational context around settlement.
In plain language
End date of the period to which the invoice applies.
End date of the period to which the invoice applies.
Together with BT-73 this closes the billed service period and makes recurring charges understandable for the receiver.
What you usually enter here
ISO 8601 date format (YYYY-MM-DD)
Typical valid values include: 2026-04-30, 2026-01-31
Optional according to EN 16931-1.
What goes wrong often
Avoid values like: 30.04.2026, 2026/04/30
Examples in context
Together with BT-73 this closes the billed service period and makes recurring charges understandable for the receiver.
Optional according to EN 16931-1.
Valid Examples
Use these points as the practical checks for this section.
- 2026-04-30
- 2026-01-31
Invalid Examples
Use these points as the practical checks for this section.
- 30.04.2026
- 2026/04/30
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-74
Data Type:
date
Cardinality:
0..1
Requirement:
Optional
Since Version:
Optional
XML Implementation
/Invoice/cac:InvoicePeriod/cbc:EndDate/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeDelivery/ram:BillingSpecifiedPeriod/ram:EndDateTimeWhy the standard cares about this field
Business Context
Together with BT-73 this closes the billed service period and makes recurring charges understandable for the receiver.
Legal Requirement
Optional according to EN 16931-1.