What it means
The rule checks ram:DueDateTypeCode under the line's ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax against code list 27. An empty value passes. CII examples used for VAT are 5 for the invoice date, 29 for the delivery date and 72 for the payment date.
Why it matters
The code identifies the event used to determine the tax point. It is distinct from the date by which the buyer must pay.
How to fix it
Check the intended tax point and correct ram:DueDateTypeCode in the line's ram:ApplicableTradeTax. Use the corresponding permitted CII code, such as 5, 29 or 72 where applicable. Do not assume that codes from another invoice syntax have the same meaning. Export again 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 'ram:DueDateTypeCode' 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-001129 still fails, and which other rules do.
Related rules
- FX-SCH-A-001130 Exemption reason code on a line must be allowed
- FX-SCH-A-001131 The tax type code on a line must be a valid code
- FX-SCH-A-001132 Date format of a line's period end date must be valid
- FX-SCH-A-001133 Date format of a line's period start date must be valid
- FX-SCH-A-001134 A referenced invoice date on a line needs a format attribute
- FX-SCH-A-001135 Date format code of a referenced invoice on a line must be valid