PEPPOL-EN16931-F001

fatalPeppol BIS Billing 3.0profileCIIUBL

A date MUST be formatted YYYY-MM-DD.

Why it fails

A date is not written as YYYY-MM-DD.

How to fix it

Use the plain calendar date with no time and no timezone: 2026-08-22. An ISO timestamp, a slash-separated date or a local format all fail. In CII the equivalent is DateTimeString format="102", i.e. 20260822.

What the validator checks

CII — context udt:DateTimeString

normalize-space(@format) = '102' and string-length(text()) = 8 and matches(normalize-space(text()), '20[0-9]{6}')

UBL — context cbc:IssueDate | cbc:DueDate | cbc:TaxPointDate | cbc:StartDate | cbc:EndDate | cbc:ActualDeliveryDate

string-length(text()) = 10 and (string(.) castable as xs:date)

Related rules

Part of PEPPOL-EN16931 — Peppol BIS Billing 3.0.

• PEPPOL-EN16931-CL001
• PEPPOL-EN16931-CL002
• PEPPOL-EN16931-CL003
• PEPPOL-EN16931-CL006
• PEPPOL-EN16931-CL007
• PEPPOL-EN16931-CL008
• PEPPOL-EN16931-P0100
• PEPPOL-EN16931-P0101
• PEPPOL-EN16931-P0104
• PEPPOL-EN16931-P0105
• PEPPOL-EN16931-P0106
• PEPPOL-EN16931-P0107
• PEPPOL-EN16931-P0108
• PEPPOL-EN16931-P0109
• PEPPOL-EN16931-P0110
• PEPPOL-EN16931-P0111
• PEPPOL-EN16931-P0112
• PEPPOL-EN16931-R001
• PEPPOL-EN16931-R002
• PEPPOL-EN16931-R003
• PEPPOL-EN16931-R004
• PEPPOL-EN16931-R005
• PEPPOL-EN16931-R006
• PEPPOL-EN16931-R007

Validate an invoice against this rule →

This is a Peppol BIS Billing 3.0 rule: an invoice can be perfectly valid EN 16931 and still be rejected by it.