What it means
This applies to qdt:DateTimeString inside ram:FormattedIssueDateTime of a header ram:AdditionalReferencedDocument whose ram:TypeCode is 130, under ram:ApplicableHeaderTradeAgreement. It checks only that format exists, so an empty attribute also passes. BT-18 identifies the invoiced object; this rule concerns the date attached to that reference.
Why it matters
The reference's date needs its own format declaration. The reference type code 130 does not describe how the date is written.
How to fix it
Find the affected reference's qdt:DateTimeString and add a matching format attribute. Use format="102" for a full calendar date written as YYYYMMDD without separators. Do not merely add an empty attribute or delete the invoiced object identifier. Correct the 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-000637 still fails, and which other rules do.
Related rules
- FX-SCH-A-000638 Check the invoiced object reference date format
- FX-SCH-A-000639 Check the invoiced object identifier scheme
- FX-SCH-A-000640 Check all type codes in the invoiced object reference
- FX-SCH-A-000641 Add the tender or lot reference date format
- FX-SCH-A-000642 Check the tender or lot reference date format
- FX-SCH-A-000643 Check the tender or lot reference type code