Skip to content

BT-73: Invoicing Period Start Date

Start date of the invoicing period covering the invoice.

BT-73Conditional RequirementEN 16931-1 / XRechnung 3.0 / ZUGFeRD 2.3

Technical Specification

Requirement & Cardinality
0..1(Conditional)

Conditional (0..1), typical for recurring service contracts

Data Type
Date (ISO 8601: YYYY-MM-DD)

Semantic data format according to European Standard EN 16931-1

XML Syntax Mappings
UBL 2.1(XRechnung / Peppol BIS)
Invoice/cac:InvoicePeriod/cbc:StartDate
UN/CEFACT CII D16B(ZUGFeRD 2.3 / Factur-X)
rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:BillingSpecifiedPeriod/ram:StartDateTime/udt:DateTimeString

What does BT-73 mean?

BT-73 records the beginning of the service period for subscriptions, retainers, and maintenance contracts. Combined with BT-74 (end date).

XML Syntax & Code Example

OASIS UBL 2.1 (XRechnung)
<cac:InvoicePeriod>
  <cbc:StartDate>2026-08-01</cbc:StartDate>
  <cbc:EndDate>2026-08-31</cbc:EndDate>
</cac:InvoicePeriod>

Business Rules & Schematron Checks

BR-CO-19

If both Invoicing period start date (BT-73) and end date (BT-74) exist, BT-74 shall not precede BT-73.

Check BT-73 in your invoice

Use the XML paths above to locate BT-73. A snippet illustrates this field; it is not a complete invoice. After correcting a value in the source application, export and check the entire file again.

Official specifications and rule sets

Requirements depend on the invoice profile and version. Consult the matching specification for mandatory fields, code lists and rules; Peppol-specific requirements do not automatically apply to every ZUGFeRD invoice.

Create compliant E-Invoices easily

Create XRechnung and ZUGFeRD invoices in Billance and check the exported file locally. Use this guide to understand BT-73 and review your invoice details before sending.