Skip to content

Warning

CII-SR-369: Do not include a payment channel code

In short

Warning: worth checking.

CII-SR-369 means the payment means section of the file has a PaymentChannelCode element, which EN 16931 does not use. Fix it by deleting that element. The file is still accepted, because this is only a warning.

On this page

What it means

The payment means part of the settlement section (SpecifiedTradeSettlementPaymentMeans) contains a PaymentChannelCode element, a code for the channel the payment goes through. EN 16931 has no field for it. The kind of payment, such as a bank transfer or direct debit, is already given by the payment means code (BT-81), which is a different element.

Why it matters

This is a warning, so the file is still accepted. Receiving software follows EN 16931 and does not read a channel code, so it has no effect on how the invoice is processed or paid. It is worth fixing to keep the file clean.

How to fix it

Look in your invoicing software for a payment channel detail that is exported into the file and switch it off. If you edit the XML yourself, delete the PaymentChannelCode element inside SpecifiedTradeSettlementPaymentMeans. Leave the payment means code (BT-81) in place, for example 30 for a bank transfer or 58 for a SEPA bank transfer.

The rule as published

PaymentChannelCode 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-369 still fails, and which other rules do.

Updated 6 November 2026