Skip to content

Warning

UBL-CR-264: The buyer contact must sit in the party's contact element

In short

Warning: worth checking.

UBL-CR-264 means the file has a cac:BuyerContact directly inside the buyer's details, which EN 16931 does not read. Remove it, and give the buyer's contact person in the normal buyer contact fields instead. It is only a warning, so the file is still accepted.

On this page

What it means

Checks that the buyer's details (cac:AccountingCustomerParty) in a UBL invoice or credit note do not contain a cac:BuyerContact element. The name is misleading: EN 16931 takes the buyer contact (BG-9, with name BT-56, telephone BT-57 and email BT-58) from cac:Party/cac:Contact, one level lower, and ignores cac:BuyerContact.

Why it matters

This is a warning, so the file is still accepted. The contact details in the wrong element are not part of the standard, so the recipient's software normally does not see them and your contact person may not appear on their side. It is worth fixing when the recipient needs to reach that person, because only the right element is read.

How to fix it

In your invoicing software, fill in the buyer contact name, telephone and email on the customer record and export again. If the software writes the contact in two places, look for an export setting that stops the extra copy. If you build the XML yourself, move the details into cac:AccountingCustomerParty/cac:Party/cac:Contact and delete cac:BuyerContact.

The rule as published

A UBL invoice should not include the AccountingCustomerParty BuyerContact

Where this rule applies

Rule set Version
EN 16931 (UBL) 1.3.17
EN 16931 (UBL credit note) 1.3.17
XRechnung 3.0 (UBL) 3.0.2
XRechnung 3.0 (UBL credit note) 3.0.2
Peppol BIS Billing 3.0 (invoice) 2026.5
Peppol BIS Billing 3.0 (credit note) 2026.5
SI-UBL 2.0 / NLCIUS (invoice) 2.0.3.13
SI-UBL 2.0 / NLCIUS (credit note) 2.0.3.13
France CTC (UBL invoice) 1.4.0-04
France CTC (UBL credit note) 1.4.0-04
CIUS-RO UBL Invoice 1.0.9 1.0.9
CIUS-RO UBL Credit Note 1.0.9 1.0.9
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether UBL-CR-264 still fails, and which other rules do.

Updated 6 November 2026