What it means
The rule checks the format attribute on udt:DateTimeString under the line's ram:SpecifiedLineTradeSettlement/ram:BillingSpecifiedPeriod/ram:EndDateTime against code list 3. A missing or empty format value passes this test. It does not check the date text or whether the end date follows the start date (BT-134).
Why it matters
The format code tells software how to interpret the period end date text.
How to fix it
Correct the format attribute and matching date text in the affected ram:EndDateTime/udt:DateTimeString. If you use format="102", write eight digits as YYYYMMDD, including leading zeros for the month and day. If your software generates the attribute incorrectly, ask its supplier to correct the export. Export again and recheck.
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-001132 still fails, and which other rules do.
Related rules
- FX-SCH-A-001133 Date format of a line's period start date must be valid
- FX-SCH-A-001134 A referenced invoice date on a line needs a format attribute
- FX-SCH-A-001135 Date format code of a referenced invoice on a line must be valid
- FX-SCH-A-001136 Document type code of a referenced invoice on a line must be valid
- FX-SCH-A-001137 Reason code for a line discount must be a valid code
- FX-SCH-A-001138 A reason code from list 5153 on a line charge must be allowed