Reference
Markdown exportBT-26 Preceding invoice issue date
Issue date of the preceding invoice referenced in BT-25.
Quick answer
Invoice basics
Core document identifiers, dates, process identifiers, and high-level invoice context.
Quick actions
In plain language
The date helps recipients identify the exact earlier invoice when invoice numbers alone are not enough.
What you usually enter here
ISO 8601 date format (YYYY-MM-DD)
Typical valid values include: 2026-03-15
Optional according to EN 16931-1.
Where the field sits
- Invoice
- cac:BillingReference
- cac:InvoiceDocumentReference
- cbc:IssueDateBT-26
- rsm:CrossIndustryInvoice
- rsm:SupplyChainTradeTransaction
- ram:ApplicableHeaderTradeSettlement
- ram:InvoiceReferencedDocument
- ram:FormattedIssueDateTime
- qdt:DateTimeStringBT-26
What goes wrong often
Avoid values like: 15.03.2026
Valid Examples
- 2026-03-15
Invalid Examples
- 15.03.2026
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-26
Data Type:
date
Cardinality:
0..1
Requirement:
Optional
XML Implementation
/Invoice/cac:BillingReference/cac:InvoiceDocumentReference/cbc:IssueDate/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument/ram:FormattedIssueDateTime/qdt:DateTimeStringNext 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.
Trying it and buying a single conversion work without an account. Subscriptions from €10/month with annual billing (excl. taxes), or €5 per conversion (excl. taxes) without a subscription.