What it means
This checks the format attribute of udt:DateTimeString inside rsm:ExchangedDocument/ram:IssueDateTime. A non-empty value must appear in the Extended profile's date-format code list. An empty value passes this check. It does not check whether the date text matches the code.
Why it matters
The format code tells software how to interpret your invoice date. This is a check of its representation, not its tax treatment.
How to fix it
Correct the format attribute on the invoice date, not a delivery or payment date. For format="102", write the actual invoice date as YYYYMMDD without separators. Do not change the actual invoice date merely to resolve a format error. 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
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-000634 still fails, and which other rules do.
Related rules
- FX-SCH-A-000635 Use an allowed Extended profile invoice type code
- FX-SCH-A-000636 Check the Extended profile specification identifier
- FX-SCH-A-000637 Add the invoiced object reference date format
- 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