What it means
The test checks for a format attribute on udt:DateTimeString inside rsm:ExchangedDocument/ram:IssueDateTime. It checks only that the attribute exists, not its value or the date text. Even an empty attribute passes this particular test.
Why it matters
The format attribute identifies the notation used for the invoice date, giving software an explicit way to interpret the date text.
How to fix it
Correct the invoice date export. If you build the XML yourself, set format="102" on udt:DateTimeString when the date is written as YYYYMMDD. If your software omits the attribute, ask its supplier to correct the export. Export again and recheck the file.
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
Attribute '@format' is required in this context. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 MINIMUM | 1.0.9-2 |
| Factur-X 1.09 BASIC WL | 1.0.9-2 |
| Factur-X 1.09 BASIC | 1.0.9-2 |
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 MINIMUM | 2.5.2 |
| ZUGFeRD 2.5 BASIC WL | 2.5.2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000021 still fails, and which other rules do.
Related rules
- FX-SCH-A-000022 The invoice date format must be one the Minimum profile allows
- FX-SCH-A-000023 The document type code must be allowed in the Minimum profile
- FX-SCH-A-000024 An invoice can name at most one business process
- FX-SCH-A-000025 The invoice must say which specification it follows
- FX-SCH-A-000026 The specification identifier must match the Minimum profile
- FX-SCH-A-000027 The invoice must contain exactly one seller