What it means
Checks a non-empty format attribute on ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:TaxPointDate/udt:DateString against date format list 44. An absent or empty attribute passes this value test. The date text itself is not checked here.
Why it matters
The format code identifies how the date text is written. An unsupported code does not match the profile's permitted date encoding.
How to fix it
For a VAT point date written as YYYYMMDD without separators, set format="102" on udt:DateString inside ram:TaxPointDate. Correct both the attribute and the date text if they do not match. If your software generates this XML, ask its supplier to correct this export field if necessary. Export the corrected invoice and check it again.
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-000856 still fails, and which other rules do.
Related rules
- FX-SCH-A-000857 Tax type code is not allowed
- FX-SCH-A-000858 Too many invoicing period descriptions
- FX-SCH-A-000859 Invoicing period end date format is not allowed
- FX-SCH-A-000860 Invoicing period start date format is not allowed
- FX-SCH-A-000861 Invoice currency code is not allowed
- FX-SCH-A-000862 The earlier invoice's date needs an allowed format