What it means
This rule checks the format code on udt:DateTimeString inside ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime for the due date (BT-9). A non-empty code must appear in the profile's date-format list. The test does not reject an empty code or check the date itself.
Why it matters
The format code tells software how to interpret the due date, so it needs a meaning defined by the profile.
How to fix it
Correct the format attribute on udt:DateTimeString inside ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime. Use 102 if the date is eight digits in year, month and day order. Otherwise, use an allowed code matching the date's representation. Export the corrected file and check it again.
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
Value of '@format' is not allowed. 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-000983 still fails, and which other rules do.
Related rules
- FX-SCH-A-000984 Payee identifier in payment terms is repeated
- FX-SCH-A-000985 Payee in payment terms needs exactly one name
- FX-SCH-A-000986 Payee role code in payment terms is repeated
- FX-SCH-A-000987 Payee electronic address block is repeated
- FX-SCH-A-000988 Payee tax registration in payment terms is repeated
- FX-SCH-A-000989 Payee contact email needs one address element