What it means
This rule checks a non-empty format value on ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime/udt:DateTimeString against the permitted date format codes. An empty value passes this particular test. The test does not check the date text or require the attribute to exist.
Why it matters
The format code identifies how your delivery date is written. The Extended profile restricts the non-empty codes you can use.
How to fix it
Correct format on ram:ApplicableHeaderTradeDelivery/ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime/udt:DateTimeString. For YYYYMMDD date text, use format="102", not the pattern YYYYMMDD as the attribute value. Export your invoice again 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 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-000786 still fails, and which other rules do.
Related rules
- FX-SCH-A-000787 A delivery note reference needs one number field
- FX-SCH-A-000788 The delivery note date needs a format attribute
- FX-SCH-A-000789 Use an allowed format code for the delivery note date
- FX-SCH-A-000790 The despatch advice date needs a format attribute
- FX-SCH-A-000791 Use an allowed format code for the despatch advice date
- FX-SCH-A-000792 The receiving advice date needs a format attribute