What it means
The check considers these code elements throughout the document, not just in the header VAT breakdown. It passes if there are no code elements or if all their values are identical. Whitespace is not normalised. The rule does not require a code in every VAT entry or check which code values are valid.
Why it matters
BT-8 identifies the basis used for the invoice's VAT point date. Wherever this code is repeated, its values need to agree.
How to fix it
Check every ram:DueDateTypeCode under ram:ApplicableTradeTax in your XML. Establish which code applies and correct inconsistent values, including unwanted whitespace. You do not need to add a code to every VAT entry to satisfy this rule. Only omit codes if the invoice's other requirements allow it, then export and recheck your file.
Once the file is corrected, check it again for free: Validate an invoice against EN 16931
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice
The rule as published
Only one DueDateTypeCode shall be present Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (CII) | 1.3.17 |
| XRechnung 3.0 (CII) | 3.0.2 |
| NLCIUS (CII) | 1.0.3.13 |
| France CTC (CII) | 1.4.0-04 |
Check your file
Drop your e-invoice to see whether CII-SR-462 still fails, and which other rules do.
Related rules
- CII-SR-463 Each discount or charge must say which it is
- CII-SR-464 Remove the payer's bank block
- CII-SR-465 Choose a person or department for the seller contact
- CII-SR-466 Choose a person or department for the buyer contact
- CII-SR-467 Use the same payment type code throughout
- CII-SR-468 Use consistent payment means text