Skip to content

Warning

CII-SR-272: Do not add a separate contact person block to the buyer contact

In short

Warning: worth checking.

CII-SR-272 means the buyer's contact details contain a nested SpecifiedContactPerson block, which the invoice standard does not use. Put the contact's name in the normal contact name field and remove the extra block.

On this page

What it means

The buyer's contact details contain a SpecifiedContactPerson element, an extra block that describes a person. EN 16931 gives the buyer contact one name (BT-56), written directly in the contact itself, together with the telephone number (BT-57) and the email address (BT-58).

Why it matters

This is only a warning, so the file is still accepted. Software that follows EN 16931 reads the contact name from the contact itself, so a name that sits only in the extra block will probably not be found.

How to fix it

Open the buyer's contact on the customer record in your invoicing software and make sure the contact name is in the normal contact name field. Remove any second person or role block under it, or stop your software exporting it. If you build the XML yourself, put the name in the PersonName element of the buyer's contact and delete SpecifiedContactPerson.

The rule as published

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

Updated 6 November 2026