What it means
The udt:DateTimeString inside ram:ApplicableHeaderTradeDelivery/ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime must have a format attribute. This rule checks only that the attribute exists, not its value or the date contents. It applies to the Basic WL, Basic, EN 16931 and Extended profiles of Factur-X and ZUGFeRD.
Why it matters
The format code declares how the delivery date is represented. Its presence alone does not establish whether the code is allowed or the date is correct.
How to fix it
Check your delivery date field and its XML export. If you generate the XML, use your date formatter to write YYYYMMDD and set format="102" on the delivery date's udt:DateTimeString. Export your corrected file and recheck it.
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
Attribute '@format' is required in this context. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 BASIC WL | 1.0.9-2 |
| Factur-X 1.09 BASIC | 1.0.9-2 |
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC WL | 2.5.2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000448 still fails, and which other rules do.
Related rules
- FX-SCH-A-000449 Use an allowed delivery date format code
- FX-SCH-A-000450 Give each despatch advice reference one number element
- FX-SCH-A-000451 Do not repeat the delivery location ID
- FX-SCH-A-000452 Do not repeat the delivery location's global identifier
- FX-SCH-A-000453 Add the delivery location identifier's scheme
- FX-SCH-A-000454 The delivery location identifier must use an allowed scheme