Skip to content
Theme
English
Theme

Warning

UBL-CR-079: Do not add a UUID to the originator document reference

In short

Warning: worth checking.

UBL-CR-079 means the invoice has a UUID (cbc:UUID) inside its originator document reference, which EN 16931 does not use. It is only a warning, so the invoice is still accepted, but you should remove that element and export again.

On this page

What it means

This rule checks that the originator document reference in a UBL invoice or credit note (cac:OriginatorDocumentReference) does not contain a UUID, a long unique identifier that some systems give to a document. EN 16931 uses that block only for the tender or lot reference (BT-17, in cbc:ID).

Why it matters

The standard has no field for this identifier, so the recipient's software ignores it or drops it. If you meant the recipient to match the invoice to a tender by this code, they will only see the tender or lot reference. The rule is a warning, so the invoice is still accepted.

How to fix it

Delete cbc:UUID from cac:OriginatorDocumentReference and export again. If the recipient identifies the tender or lot by this code, put it in the tender or lot reference field (BT-17) instead. If your software copies an internal ID into that block automatically, switch that off.

The rule as published

A UBL invoice should not include the OriginatorDocumentReference 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-079 still fails, and which other rules do.

Updated 6 November 2026