What it means
The format attribute on the date of the seller's order on a line (qdt:DateTimeString inside ram:SellerOrderReferencedDocument) must be one of the date format codes in the code list of the Extended profile (code list 17 in its code database). The usual code is 102, for a full date written as YYYYMMDD. An empty value is not tested by this rule.
Why it matters
The format code tells the recipient how to read the date. A code outside the agreed list cannot be interpreted, so the file fails the check and the recipient may reject it.
How to fix it
In your invoicing software, enter the date of the seller's order through the date field instead of as free text. If you build the XML yourself, set format to 102 and write the date as YYYYMMDD, matching the code you chose. If you do not need the date, remove it from the order reference.
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-001070 still fails, and which other rules do.
Related rules
- FX-SCH-A-001071 Add the end customer's order date format attribute
- FX-SCH-A-001072 The date format code of the end customer's order must be valid
- FX-SCH-A-001073 Give each line delivery event one date element
- FX-SCH-A-001074 Add the line delivery date format attribute
- FX-SCH-A-001075 Use an allowed format code for the line delivery date
- FX-SCH-A-001076 Use an allowed unit code for the invoiced quantity