What it means
The format attribute on udt:DateTimeString under ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime is checked against code list 3 in FACTUR-X_EXTENDED_codedb.xml. An empty value passes this rule; the rule does not require the attribute to exist.
Why it matters
The format code identifies how the date text is written. The profile restricts which codes you can use.
How to fix it
Correct the format attribute for the affected line's delivery date. For a date written as YYYYMMDD, use format="102"; if you use another allowed format, keep its code and date text consistent. Do not put the pattern YYYYMMDD itself in the attribute. Export the corrected file and check it again.
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 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-001075 still fails, and which other rules do.
Related rules
- FX-SCH-A-001076 Use an allowed unit code for the invoiced quantity
- FX-SCH-A-001077 Add a unit code to the free-of-charge quantity
- FX-SCH-A-001078 Use an allowed unit code for the free-of-charge quantity
- FX-SCH-A-001079 Add the line delivery note date format attribute
- FX-SCH-A-001080 Use an allowed format code for the line delivery note date
- FX-SCH-A-001081 Add the line despatch advice date format attribute