Skip to content
Change language: English

Warning

UBL-CR-651: A top-level SalesOrderID should have no scheme attribute

In short

Warning: worth checking.

UBL-CR-651 means a cbc:SalesOrderID directly under the invoice or credit note has a schemeID attribute. Remove that attribute and keep the reference text. This test does not check the sales order reference (BT-14) inside cac:OrderReference.

On this page

What it means

This rule checks only cbc:SalesOrderID elements directly under the invoice or credit note and flags a schemeID attribute on them. It does not check cac:OrderReference/cbc:SalesOrderID, which carries the sales order reference (BT-14).

Why it matters

This warning concerns an extra attribute on a top-level cbc:SalesOrderID. Its XPath does not cover the sales order reference inside cac:OrderReference.

How to fix it

If cbc:SalesOrderID directly under the invoice or credit note has schemeID, remove that attribute and keep the text unchanged. Do not change the BT-14 reference inside cac:OrderReference to address this warning. 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 SalesOrderID scheme identifier

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

Updated 6 November 2026