Skip to content
Theme
English

Warning

UBL-CR-093: Leave the verification result out of the tender or lot reference

In short

Warning: worth checking.

UBL-CR-093 means the tender or lot reference contains a result of verification, which EN 16931 does not use. Remove it and keep only the reference number. The file is still accepted, so this is a warning.

On this page

What it means

An invoice or credit note can refer to a tender or lot (BT-17) through cac:OriginatorDocumentReference, and EN 16931 uses only the identifier (cbc:ID) inside it. This rule checks that there is no cac:ResultOfVerification, which would record the outcome of a check made on the referenced document.

Why it matters

This is a warning, so the file is still accepted. A verification result of a tender document has no place in an invoice, so the recipient's software cannot map it and usually ignores it. It is worth removing so the file follows the standard exactly.

How to fix it

This block is normally written by software, not typed by you. Export the invoice again from your invoicing software, and if the block is still there, update the software or ask its supplier to stop writing it. If you build the XML yourself, delete cac:ResultOfVerification from cac:OriginatorDocumentReference.

The rule as published

A UBL invoice should not include the OriginatorDocumentReference ResultOfVerification

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

Updated 6 November 2026