What it means
In the Extended profiles of Factur-X and ZUGFeRD, this checks udt:DateTimeString at rsm:ExchangedDocument/ram:EffectiveSpecifiedPeriod/ram:CompleteDateTime. The test only checks that the format attribute exists. An empty attribute also satisfies this test; its value and the date text need separate checks.
Why it matters
The attribute declares how the date is written. Its presence is part of the required XML structure for this date element.
How to fix it
Add format="102" if the date text is a full calendar date written as YYYYMMDD, without separators. If you use another permitted representation, supply its matching format code. Do not add an empty attribute just to satisfy this test. Have the export corrected, then export 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 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-000631 still fails, and which other rules do.
Related rules
- FX-SCH-A-000632 Check the effective period date format code
- 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