Skip to content

Fatal

CII-SR-467: All payment means must use the same payment type code

In short

Fatal: fails the selected checks.

CII-SR-467 means the invoice lists more than one payment means and they do not all have the same payment means type code. Fix it by using one code throughout, for example 30 for a bank transfer or 58 for a SEPA bank transfer.

On this page

What it means

Each payment means in the invoice has a type code (BT-81) that says how the buyer should pay. The check compares every code with the first one and fails when any of them is different. You can list several bank accounts, but they must all be the same type of payment.

Why it matters

The standard gives one payment means type for the whole invoice. If the codes differ, the buyer's system cannot tell how it is meant to pay, so the invoice is rejected.

How to fix it

Check the payment section of the invoice in your invoicing software. If the difference is a slip, such as 30 on one account and 58 on another, set both to the same code. If you really offer two ways to pay, choose one for the structured data and describe the other in the payment terms.

The rule as published

All Payment means type codes (BT-81) shall have the same value across all SpecifiedTradeSettlementPaymentMeans.

Business terms: BT-81

Where this rule applies

Rule set Version
EN 16931 (CII) 1.3.17
XRechnung 3.0 (CII) 3.0.2
Factur-X 1.09 BASIC WL 1.0.9-2
Factur-X 1.09 BASIC 1.0.9-2
Factur-X 1.09 EN 16931 1.0.9-2
Factur-X 1.09 EXTENDED 1.0.9-2
ZUGFeRD 2.5 BASIC WL 2.5.2
ZUGFeRD 2.5 BASIC 2.5.2
ZUGFeRD 2.5 EN 16931 2.5.2
ZUGFeRD 2.5 EXTENDED 2.5.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-467 still fails, and which other rules do.

Updated 6 November 2026