Skip to content

Warning

CII-SR-371: Do not use a separate payment method code

In short

Warning: worth checking.

CII-SR-371 means the payment means section of the file has a PaymentMethodCode element, which EN 16931 does not use. Fix it by deleting that element and keeping the payment means code (BT-81) in the TypeCode element. The file is still accepted.

On this page

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
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether CII-SR-371 still fails, and which other rules do.

Updated 6 November 2026