What it means
For udt:DateTimeString with format set to 205, the XPath expects YYYYMMDDHHMM, with no separators and with surrounding whitespace allowed. It checks month 01 to 12, day 01 to 31, hour 00 to 23 and minute 00 to 59, but not whether the date exists in the calendar. The official description specifies YYYYMMDDHHMMSS, which conflicts with this test.
Why it matters
Your date-time value should preserve its intended precision and agree with its declared format. Removing information solely to satisfy an inconsistent test can change what your file records.
How to fix it
Find the flagged udt:DateTimeString and check its format attribute against the intended timestamp. Correct any wrong value from your source data. If a correctly encoded timestamp including seconds is flagged, ask whoever maintains your XML export or rule implementation to resolve the format 205 mismatch for your Factur-X or ZUGFeRD version. Do not strip seconds or time-zone information merely to clear this finding. Recheck the corrected file.
Once the file is corrected, check it again for free: Validate a ZUGFeRD invoice
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice Beta
The rule as published
Date time string with format attribute 205 shall be YYYYMMDDHHMMSS. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether BR-FXEXT-CII-DT-097A still fails, and which other rules do.