What it means
This checks for format on ram:SpecifiedAdvancePayment/ram:InvoiceSpecifiedReferencedDocument/ram:FormattedIssueDateTime/qdt:DateTimeString. It checks only attribute presence, so an empty attribute passes this test. FX-SCH-A-000960 separately checks non-empty format codes.
Why it matters
The attribute identifies how the referenced invoice's date is written.
How to fix it
Add format to qdt:DateTimeString for the referenced invoice date, not the advance payment's received date. Use a code from the profile's date-format list. If you use 102, write the earlier invoice's actual invoice date as YYYYMMDD. 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
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-000959 still fails, and which other rules do.
Related rules
- FX-SCH-A-000960 Use an allowed format for the referenced invoice date
- FX-SCH-A-000961 Use an allowed type for the referenced invoice
- FX-SCH-A-000962 Each financial adjustment needs one amount element
- FX-SCH-A-000963 One description per logistics charge
- FX-SCH-A-000964 One tax type code per logistics charge tax block
- FX-SCH-A-000965 One VAT category per logistics charge tax block