What it means
The payment terms contain a TypeCode element, a code for the kind of payment terms. EN 16931 does not use it. It gives the payment terms as text (BT-20) and the due date (BT-9) as a date.
Why it matters
This is a warning, so the invoice is still accepted. The buyer's software does not read the code, so the classification is lost. It is worth fixing if the terms are only explained through that code, or if the buyer's system is strict about extra elements.
How to fix it
Remove the TypeCode element from the payment terms. Write what the terms mean in the payment terms text (BT-20) and fill in the due date (BT-9). If your invoicing software offers a choice of profile or format, pick EN 16931 (or XRechnung, if your buyer asked for it).
The rule as published
TypeCode should not 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-401 still fails, and which other rules do.
Related rules
- CII-SR-402 Leave the instruction type code out of the payment terms
- CII-SR-404 Leave the partial payment percentage out of the payment terms
- CII-SR-405 Leave the payment means reference out of the payment terms
- CII-SR-406 Leave the partial payment amount out of the payment terms
- CII-SR-407 Leave structured late-payment penalty terms out of the invoice
- CII-SR-408 Leave structured early-payment discount terms out of the invoice