What it means
This checks for format on ram:SpecifiedAdvancePayment/ram:FormattedReceivedDateTime/qdt:DateTimeString. It checks only attribute presence, so an empty attribute passes this test. FX-SCH-A-000951 separately checks non-empty format codes.
Why it matters
The format attribute identifies how the received-date text is written.
How to fix it
Add format to qdt:DateTimeString inside the advance payment's ram:FormattedReceivedDateTime. Choose a code from the profile's date-format list. If you use 102, write the actual received date as YYYYMMDD. Correct the date format without removing a genuine advance payment, then 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-000950 still fails, and which other rules do.
Related rules
- FX-SCH-A-000951 Use an allowed format for the advance payment received date
- FX-SCH-A-000952 Each advance payment tax entry needs one amount element
- FX-SCH-A-000953 Each advance payment tax entry needs one tax type element
- FX-SCH-A-000954 Each advance payment tax entry needs one category element
- FX-SCH-A-000955 Use an allowed advance payment tax category
- FX-SCH-A-000956 Use an allowed advance payment exemption reason code