What it means
In the Basic profiles of Factur-X and ZUGFeRD, this rule checks a non-empty format attribute on ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime/udt:DateTimeString against the permitted date format codes. Code 102 describes an eight-digit date in year, month and day order without separators. This rule checks the format code, not the date text or whether a due date is present.
Why it matters
The format code tells software how to interpret the due date text. The declared format and the date text need to describe the same representation.
How to fix it
Check the exported due date element. If the date uses YYYYMMDD, put format="102" on udt:DateTimeString within ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime. Ensure the date text follows that pattern. If your invoicing software generates the invalid attribute, report this rule id to its supplier. 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
Value of '@format' is not allowed. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 BASIC | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000524 still fails, and which other rules do.
Related rules
- FX-SCH-A-000525 Use a valid currency code on the invoice VAT total
- FX-SCH-A-000526 Use a valid currency code on the accounting VAT total
- FX-SCH-A-000527 Use an allowed payment means code
- FX-SCH-A-000528 Use a valid VAT accounting currency code
- FX-SCH-A-000529 A line note needs exactly one text element
- FX-SCH-A-000530 A price discount needs exactly one charge indicator