What it means
The payment card details (ApplicableTradeSettlementFinancialCard) inside the payment means section contain a VerificationNumeric element. This is where the CII format can hold the short security code of a payment card. EN 16931 has no field for it.
Why it matters
This is a warning, so the file is still accepted. The buyer's software does not read the field. It is worth fixing soon all the same, because an invoice is passed on to several people and systems, and a card security code should not travel with it.
How to fix it
Delete the VerificationNumeric element from the card details. If your invoicing software exports a card security code, switch that off and check where it takes the value from. If the invoice is paid by card, give only the card number (BT-87), kept to its last digits, and the cardholder name (BT-88).
The rule as published
VerificationNumeric 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-376 still fails, and which other rules do.
Related rules
- CII-SR-377 Do not include a card valid-from date
- CII-SR-378 Do not include a card spending limit
- CII-SR-379 Do not include the amount still available on a card
- CII-SR-380 Do not include a card interest rate
- CII-SR-381 Do not include a payment card description
- CII-SR-382 Do not include the name of the account to be debited