Skip to content
Theme
English
Theme

Warning

UBL-CR-273: The payee should not include a physical location

In short

Warning: worth checking.

UBL-CR-273 means the payee has a physical location (cac:PhysicalLocation), which EN 16931 does not use. Remove it from the payee block. It is only a warning, so the invoice is still accepted.

On this page

What it means

Checks that the payee block (cac:PayeeParty) does not contain cac:PhysicalLocation, a place such as a site or branch that UBL lets you link to a party. For the payee (BG-10), the party that receives the payment when that is not the seller, EN 16931 only has the name (BT-59), the identifier (BT-60) and the legal registration identifier (BT-61).

Why it matters

This is a warning, so the file is still accepted. The standard has no field for a location on the payee, so the recipient's software normally ignores it. It is worth removing when you want a clean report. It does not affect the amounts or the payment.

How to fix it

Look for a branch, site or location entry on the payee in your invoicing software and clear it for e-invoice exports, then export again. If you build the XML yourself, delete cac:PhysicalLocation from cac:PayeeParty. If the delivery place matters, use the delivery details of the invoice, not the payee.

The rule as published

A UBL invoice should not include the PayeeParty PhysicalLocation

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

Updated 6 November 2026