What it means
This rule checks a non-empty format attribute on udt:DateTimeString under ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime against the profile's date format list. Use 102 for YYYYMMDD. A missing or empty format value does not fail this code-list test; the date value and other structural requirements are separate checks.
Why it matters
The format code declares how software should interpret the delivery date. This rule checks that declaration, not the date's factual accuracy or VAT implications.
How to fix it
Correct the delivery date output in your export or ask your software supplier to correct it. In CII XML, write the intended date as YYYYMMDD in ram:ApplicableHeaderTradeDelivery/ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime/udt:DateTimeString and set format="102". Regenerate and recheck your invoice.
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
Value of '@format' is not allowed. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000583 still fails, and which other rules do.
Related rules
- FX-SCH-A-000584 Include one receiving advice identifier
- FX-SCH-A-000585 Use a listed delivery location scheme
- FX-SCH-A-000586 Use a listed delivery country code
- FX-SCH-A-000587 Use a listed VAT breakdown category
- FX-SCH-A-000588 Use a listed VAT point date code
- FX-SCH-A-000589 Use a listed VAT exemption reason code