A UBL date uses the wrong format · BR-TMP-6
- Severity · Warning
- Applies to · UBL
- Editorial review pending
KoSIT expects the affected UBL date fields to use a four-digit year followed by month and day, separated by hyphens. The check covers fields such as issue and due dates and period boundaries. The pinned configuration reports this as a warning.
As of
Who can correct it?
The sender can correct the invoice.
How to fix it
- Export the affected date as YYYY-MM-DD with two digits each for month and day. Keep the underlying date.
- XML fields in the affected group · UBL cbc:IssueDate, cbc:DueDate, cbc:StartDate, cbc:EndDate, cbc:ActualDeliveryDate, cbc:TaxPointDate, cbc:PaymentDueDate
Rule text and source
Paraphrase · The covered UBL date fields must use YYYY-MM-DD.
Message to the sender
Subject: Invoice {invoiceNumber} – A UBL date uses the wrong format
Hello,
could you clarify a detail on your invoice {invoiceNumber} dated {issueDate} (BR-TMP-6)? KoSIT expects the affected UBL date fields to use a four-digit year followed by month and day, separated by hyphens. Export the affected date as YYYY-MM-DD with two digits each for month and day. Keep the underlying date.
Could you send us the corrected invoice?
Thank you and kind regardsExample
The date 9 November 2026 should be exported as 2026-11-09. The value 2026-11-09Z adds a time zone and triggers the warning.
UBL
cbc:IssueDate
Fails the rule
<cbc:IssueDate>2026-11-09Z</cbc:IssueDate>
Corrected
<cbc:IssueDate>2026-11-09</cbc:IssueDate>Rule versions
KoSIT · XRechnung Schematron 2.6.0