What it means
In the Extended profile, this rule checks that format exists on qdt:DateTimeString inside ram:ReceivingAdviceReferencedDocument/ram:FormattedIssueDateTime under the line's ram:SpecifiedLineTradeDelivery. It checks attribute presence, not the format code or the date value.
Why it matters
The format code tells software how to interpret the date's characters.
How to fix it
In XML, add the format attribute to qdt:DateTimeString inside the line's ram:ReceivingAdviceReferencedDocument/ram:FormattedIssueDateTime. Use format="102" if you write the date as YYYYMMDD. Otherwise, use an allowed code matching the actual representation. If your invoicing software omits the attribute, ask its supplier to correct the export. Export and recheck your 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-001087 still fails, and which other rules do.
Related rules
- FX-SCH-A-001088 Receiving advice date on a line must use an allowed format code
- FX-SCH-A-001089 Line delivery party may have only one identifier
- FX-SCH-A-001090 Line delivery party may have only one role code
- FX-SCH-A-001091 Line delivery party may have only one electronic address block
- FX-SCH-A-001092 Line delivery party may have only one tax registration
- FX-SCH-A-001093 Line delivery contact email needs one address element