What it means
For each ram:ApplicableHeaderTradeSettlement, the check counts ram:TaxPointDate elements directly inside its ram:ApplicableTradeTax entries. Zero or one passes this rule. Repeating the same date still fails.
Why it matters
BT-7 represents one VAT point date for the invoice, rather than a separate occurrence for every VAT breakdown entry. This rule checks the number of date elements, not whether the date is correct.
How to fix it
Find the ram:TaxPointDate elements in the header VAT entries. Keep the correct VAT point date once and remove repeated elements. If the dates differ, establish the correct date before changing them. Do not omit a date simply because you do not know it; check the applicable requirements, 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 TaxPointDate 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-461 still fails, and which other rules do.
Related rules
- CII-SR-462 Use a consistent VAT point date code
- 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