What it means
The payment means part of the settlement section (SpecifiedTradeSettlementPaymentMeans) contains a PaymentMethodCode element. EN 16931 states the type of payment once, in the payment means code (BT-81), which is written in the TypeCode element next to it. A second payment method code has no place in the format.
Why it matters
This is a warning, so the file is still accepted. The buyer's software reads the payment means code (BT-81) and is not expected to read the other code. If the two ever disagreed, the extra code would only cause confusion. It is worth fixing to keep the file clean.
How to fix it
Delete the PaymentMethodCode element from SpecifiedTradeSettlementPaymentMeans. Then check that the TypeCode next to it is present and right: 30 for a bank transfer, 58 for a SEPA bank transfer, 59 for a SEPA direct debit, 48 for a payment by card. In your invoicing software, this is usually the payment method on the invoice, and the software may be writing it into two places.
The rule as published
PaymentMethodCode 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-371 still fails, and which other rules do.
Related rules
- CII-SR-372 Do not include a card chip indicator
- CII-SR-373 Do not include a payment card type code
- CII-SR-375 Do not include a payment card expiry date
- CII-SR-376 Do not include a card verification number
- CII-SR-377 Do not include a card valid-from date
- CII-SR-378 Do not include a card spending limit