What it means
Checks that ram:IssueDateTime inside rsm:ExchangedDocument has no udt:DateTime child. It does not check whether udt:DateTimeString is present or correctly formatted. The warning can occur even when DateTimeString is also present.
Why it matters
The EN 16931 CII mapping represents the invoice date using udt:DateTimeString with format code 102, meaning YYYYMMDD. The separate udt:DateTime element is not used for this field.
How to fix it
Remove udt:DateTime from ram:IssueDateTime inside rsm:ExchangedDocument. If udt:DateTimeString is missing, add it there; otherwise keep the existing element. Set its format attribute to 102 and use the intended invoice date in YYYYMMDD form, without separators or a time. Recheck the file.
Once the file is corrected, check it again for free: Validate an invoice against EN 16931
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice
The rule as published
DateTime should not be present Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (CII) | 1.3.17 |
| XRechnung 3.0 (CII) | 3.0.2 |
| NLCIUS (CII) | 1.0.3.13 |
| France CTC (CII) | 1.4.0-04 |
Check your file
Drop your e-invoice to see whether CII-SR-015 still fails, and which other rules do.