What it means
This rule checks the format attribute of ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime/udt:DateTimeString. A non-empty attribute value must belong to the profile's date-format code list. Code 102 represents YYYYMMDD. An empty value passes this code-list test; the test does not check the date text itself.
Why it matters
The format code explains how to read the date text. It must describe the date representation used in the XML.
How to fix it
Check how your export writes the due date. If you generate XML, set the format attribute on the due date's udt:DateTimeString to 102 and write its text as YYYYMMDD. Generate the file 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 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-000605 still fails, and which other rules do.
Related rules
- FX-SCH-A-000606 Check the currency code on the VAT total
- FX-SCH-A-000607 Check the VAT accounting currency on the VAT total
- FX-SCH-A-000608 Card details need one ID element
- FX-SCH-A-000609 Use a recognised payment method code
- FX-SCH-A-000610 Use a recognised VAT accounting currency code
- FX-SCH-A-000611 Check the unit for the price before discount