What it means
Checks a non-empty format attribute on ram:ApplicableHeaderTradeSettlement/ram:BillingSpecifiedPeriod/ram:EndDateTime/udt:DateTimeString against date format list 3. An absent or empty attribute passes this value test. It does not check the date text or compare the period's start and end dates.
Why it matters
The format code identifies how the end date text is written. It must use an encoding permitted for this date field.
How to fix it
Find the end date of your invoicing period (BG-14), not the payment due date. For a date written as YYYYMMDD without separators, set format="102" on ram:EndDateTime/udt:DateTimeString. Correct the date text if it uses a different format. 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-000859 still fails, and which other rules do.
Related rules
- 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
- FX-SCH-A-000863 Use an allowed type code for the earlier invoice
- FX-SCH-A-000864 Keep at most one invoicee identifier
- FX-SCH-A-000865 The invoicee must have exactly one name