Skip to content

Warning

CII-SR-257: Leave out the type code of the buyer's contact

In short

Warning: worth checking.

CII-SR-257 means the buyer's contact has a TypeCode element, which EN 16931 does not use. Remove the code and keep the contact point, phone number and email address. It is only a warning, so the file is still accepted.

On this page

What it means

The buyer's contact (BG-9) must not have a TypeCode, a code for the kind of contact. The standard carries only a contact point (BT-56), a telephone number (BT-57) and an email address (BT-58). The same restriction applies in the CII rules for XRechnung, NLCIUS and the French CTC rules.

Why it matters

This is a warning, so the file is still accepted. The recipient's software reads only the standard contact fields, so a contact type is ignored and changes nothing about how the invoice is handled. Fix it if you want a file with no warnings.

How to fix it

Look at the contact person on the customer record for a contact type or contact role field and clear it, or switch off the export option that writes it. If you edit the XML yourself, delete the TypeCode element inside the buyer's DefinedTradeContact.

The rule as published

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

Updated 6 November 2026