Skip to content

Warning

UBL-CR-021: Do not send an order type code in the order reference

In short

Warning: worth checking.

UBL-CR-021 warns that your UBL invoice or credit note contains an order type code (cbc:OrderTypeCode) inside its order reference. Remove that element from cac:OrderReference.

On this page

What it means

A UBL file can hold an order reference (cac:OrderReference) with the buyer's purchase order number (BT-13) and the seller's sales order reference (BT-14). This rule checks that the order reference does not also hold cbc:OrderTypeCode, a code that says what kind of order it is. EN 16931 has no field for it.

Why it matters

The EN 16931 UBL rules do not use an order type code in the order reference.

How to fix it

Remove only cbc:OrderTypeCode from cac:OrderReference. Keep the purchase order number (BT-13) in cbc:ID and any sales order reference (BT-14). Check the corrected file again.

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 OrderTypeCode

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

Updated 6 November 2026