Skip to content
Theme
English

Warning

UBL-CR-288: Contact details for the payee should be left out

In short

Warning: worth checking.

UBL-CR-288 means the file includes contact details for the payee (cac:Contact), which EN 16931 does not use. It is only a warning, so the file is still accepted, but you should move the contact to the seller and export again.

On this page

What it means

The payee (BG-10) is the party that receives the payment when that is not the seller. This rule checks that cac:PayeeParty has no cac:Contact block, which would hold a contact name, phone number or email address. The standard has contact details for the seller (BG-6) and the buyer (BG-9), but not for the payee.

Why it matters

The recipient's software has no field for payee contacts, so the block is ignored and nobody sees it. The invoice or credit note is not rejected because this is a warning. If someone is meant to call or write to the payee, that information does not reach them.

How to fix it

Remove the contact from the payee settings in your invoicing software. If the recipient needs a contact for questions about the invoice, enter it as the seller contact (BG-6) instead. If you build the XML yourself, delete cac:Contact from cac:PayeeParty.

The rule as published

A UBL invoice should not include the PayeeParty Contact

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

Updated 6 November 2026