What it means
For udt:DateString under ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:TaxPointDate, this rule requires the format attribute to exist. It applies to the EN 16931 and Extended profiles. It does not check the attribute's value or the date itself; even an empty attribute satisfies this presence test.
Why it matters
The attribute declares the notation used for the VAT point date. Requiring the attribute and checking its value are separate checks.
How to fix it
Correct the export so that udt:DateString under ram:TaxPointDate includes its format attribute. For a date written as YYYYMMDD, use format="102". Keep the date value and format code consistent. If you cannot control the XML output, give your software supplier the element path and rule ID. Regenerate and recheck your invoice.
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
Attribute '@format' is required in this context. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000590 still fails, and which other rules do.
Related rules
- FX-SCH-A-000591 Use format 102 for the VAT point date
- FX-SCH-A-000592 Use VAT as the tax type code
- FX-SCH-A-000593 Use format 102 for the invoicing period end
- FX-SCH-A-000594 Use format 102 for the invoicing period start
- FX-SCH-A-000595 Use a listed invoice currency code
- FX-SCH-A-000596 Use format 102 for the preceding invoice date