What it means
This checks the format attribute of udt:DateTimeString at rsm:ExchangedDocument/ram:EffectiveSpecifiedPeriod/ram:CompleteDateTime. A non-empty value must appear in the Extended profile's date-format code list. An empty value passes this particular check. The test does not check the date text.
Why it matters
The format code declares how software should read the date. A recognised code still needs date text written in the corresponding format.
How to fix it
Correct the format attribute on this effective period date. For format="102", write the actual date as eight digits in YYYYMMDD order, without separators. Do not put YYYYMMDD itself in the attribute. If your software generates the file, have its export corrected, then export and recheck it.
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-000632 still fails, and which other rules do.
Related rules
- FX-SCH-A-000633 The subject code of a note must be an allowed code
- FX-SCH-A-000634 Check the invoice date format code
- FX-SCH-A-000635 Use an allowed Extended profile invoice type code
- FX-SCH-A-000636 Check the Extended profile specification identifier
- FX-SCH-A-000637 Add the invoiced object reference date format
- FX-SCH-A-000638 Check the invoiced object reference date format