Skip to content
Change language: English

Warning

UBL-CR-017: The purchase order reference should not have a UUID

In short

Warning: worth checking.

UBL-CR-017 means the document-level purchase order reference contains a UUID (cbc:UUID), which EN 16931 does not use. Remove it and keep the purchase order number (BT-13).

On this page

What it means

The rule checks that the document-level cac:OrderReference has no cbc:UUID. A UUID is a generated technical identifier. The purchase order number (BT-13) is held in cac:OrderReference/cbc:ID.

Why it matters

This rule concerns the cbc:UUID element within the document-level order reference, not the format of the purchase order number (BT-13).

How to fix it

Delete cbc:UUID inside cac:OrderReference directly under the invoice or credit note root. Keep the purchase order number the buyer gave you in cbc:ID, even if that number looks like a UUID. Export again and recheck the file.

Once the file is corrected, check it again for free: Validate an invoice against EN 16931

Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice

The rule as published

A UBL invoice should not include the OrderReference UUID

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

Updated 6 November 2026