What it means
For the Minimum profile, the test checks a non-empty format value on udt:DateTimeString inside rsm:ExchangedDocument/ram:IssueDateTime against the profile's date-format code list. An empty value does not fail this test. A missing attribute is checked separately by FX-SCH-A-000021.
Why it matters
An agreed format code gives the date text a defined interpretation. The code and the date representation need to match.
How to fix it
Correct the format attribute on the invoice date's udt:DateTimeString. For a date written as YYYYMMDD, use format="102" and ensure the date text follows that pattern. Correct the export in your invoicing software or ask its supplier to do so, then export 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 MINIMUM | 1.0.9-2 |
| ZUGFeRD 2.5 MINIMUM | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000022 still fails, and which other rules do.
Related rules
- 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
- FX-SCH-A-000028 The invoice must contain exactly one buyer