What it means
In the Factur-X and ZUGFeRD Basic WL profiles, this rule checks format on the delivery date's ram:OccurrenceDateTime/udt:DateTimeString against the profile's format code list. An empty code value passes this test; FX-SCH-A-000448 separately requires the attribute to exist. This test does not inspect the date text.
Why it matters
The declared format needs to be recognised by the profile so software has a defined way to interpret the date. Checking the code alone does not establish that the date matches it.
How to fix it
In ram:ApplicableHeaderTradeDelivery/ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime, set format="102" on udt:DateTimeString and use your date formatter to write YYYYMMDD without separators. Do not change the code while leaving the date in a different format. 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
Value of '@format' is not allowed. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 BASIC WL | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC WL | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000449 still fails, and which other rules do.
Related rules
- 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
- FX-SCH-A-000455 A delivery address must contain exactly one country