What it means
The test counts SpecifiedTradePaymentTerms children directly under ApplicableHeaderTradeSettlement and allows zero or one. It counts blocks, not the text or date elements within them.
Why it matters
The EN 16931 CII mapping uses a single invoice-level payment terms block rather than a separate block for each instalment.
How to fix it
Compare the blocks and retain the agreed payment terms (BT-20), any applicable due date (BT-9) and other relevant payment information in one block. Describe any instalment schedule in the payment terms text. Resolve conflicting dates against the agreed terms rather than inventing a date. Remove the surplus blocks 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 SpecifiedTradePaymentTerms should 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-452 still fails, and which other rules do.
Related rules
- CII-SR-453 Give the payment terms text at most once
- CII-SR-454 Use exactly one VAT entry per line settlement
- CII-SR-455 Give the seller contact only once
- CII-SR-456 Give the buyer contact only once
- CII-SR-457 Give the tender or lot reference only once
- CII-SR-458 Give the invoiced object identifier only once