Reference
Markdown exportBT-74 Invoicing period end date
End date of the period to which the invoice applies.
Quick answer
Delivery and payment
Delivery dates, payment means, and the operational context around settlement.
Quick actions
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
- 2026-04-30
- 2026-01-31
Invalid Examples
- 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:EndDateTimeNext step
Create an XRechnung from your PDF
The converter reads the invoice and shows the fields it found before download, so you can check and correct the values. No PDF? Fill in the XRechnung directly in the form.
Download requires an account. Subscriptions from €10/month with annual billing (excl. taxes), or €5 per conversion (excl. taxes) without a subscription.
Why 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.