What it means
When a line's contract reference contains ram:ContractReferencedDocument/ram:FormattedIssueDateTime/qdt:DateTimeString, that date element must have a format attribute. This rule checks only that the attribute exists, not whether it is empty, contains an allowed code or matches the date text.
Why it matters
The attribute identifies how the contract date is written. Its presence is a structural requirement for this date element in the Extended profile.
How to fix it
Add the format attribute to qdt:DateTimeString under the affected line's ram:ContractReferencedDocument/ram:FormattedIssueDateTime. For an eight-digit date written as YYYYMMDD, use format="102" and make the date text match. 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 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-001031 still fails, and which other rules do.
Related rules
- FX-SCH-A-001032 The date format code on the line contract is not allowed
- FX-SCH-A-001033 The unit price discount has a reason code that is not allowed
- FX-SCH-A-001034 The unit price charge has duplicate charge indicators
- FX-SCH-A-001035 The unit price charge needs exactly one amount
- FX-SCH-A-001036 The unit price charge has a reason code that is not allowed
- FX-SCH-A-001037 The unit price basis quantity has a unit code that is not allowed