What it means
This rule checks the format attribute on udt:DateTimeString inside the line's ram:BillingSpecifiedPeriod/ram:EndDateTime, which holds the end date (BT-135). It compares non-empty values with the Basic profile's date-format code list for Factur-X and ZUGFeRD. An empty value passes this particular test; the test does not require the attribute or check the date text.
Why it matters
The format code and date text need to agree so the line period end date has a consistent meaning.
How to fix it
Check the intended line period end date and its XML representation. For a full calendar date, write the date as YYYYMMDD and set format to 102 on the corresponding udt:DateTimeString. Correct the export configuration or XML output, then export and check the file 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 BASIC | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000540 still fails, and which other rules do.
Related rules
- FX-SCH-A-000541 Add the line period start date's format attribute
- FX-SCH-A-000542 Use a permitted line period start date format code
- FX-SCH-A-000543 Keep one indicator in each line discount
- FX-SCH-A-000544 Give each line discount one amount
- FX-SCH-A-000545 Use a permitted line discount reason code
- FX-SCH-A-000546 Keep one indicator in each line charge