What it means
This rule checks a non-empty format attribute on ram:TaxPointDate/udt:DateString within ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax. The EN 16931 profile uses 102 for YYYYMMDD. An absent or empty format value does not fail this code-list test. FX-SCH-A-000590 separately requires the attribute to exist.
Why it matters
The format code specifies how the VAT point date is written. This rule checks the code, not the date's accuracy or the resulting VAT period.
How to fix it
Correct the VAT point date output in your export. In CII XML, write the intended BT-7 date as YYYYMMDD in ram:TaxPointDate/udt:DateString and set format="102". If the attribute is generated incorrectly, ask your software supplier to correct that output rather than changing the intended date. 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
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-000591 still fails, and which other rules do.
Related rules
- 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
- FX-SCH-A-000597 Use a listed payee identifier scheme