Skip to content

Warning

UBL-CR-665: Only an invoiced object reference may carry a scheme identifier

In short

Warning: worth checking.

UBL-CR-665 means a document reference has a scheme identifier (schemeID) although it is not an invoiced object reference with document type code 130. It is a warning; remove the schemeID from that reference.

On this page

What it means

A UBL file can hold several additional document references (cac:AdditionalDocumentReference). Only a reference with document type code 130 is an invoiced object identifier (BT-18), for example a subscription number or a meter point, and only that one may state the scheme of its identifier (BT-18-1). This rule checks that every other reference, including one with no document type code, has no schemeID on its cbc:ID. A supporting document reference (BG-24, BT-122) is a plain identifier with no scheme.

Why it matters

This is a warning. A scheme on a supporting document reference has no meaning in EN 16931. It is worth fixing when you control the export, or when a recipient asks for a file with no warnings.

How to fix it

Open the references and attached documents on the invoice in your software. If the reference is a normal supporting document, such as a delivery note or a contract, clear the scheme or type field next to its number. If it is really an invoiced object, such as a subscription or a meter, enter it as an invoiced object reference. If you build the XML yourself, delete the schemeID attribute from cbc:ID in cac:AdditionalDocumentReference unless cbc:DocumentTypeCode is 130.

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 AdditionalDocumentReference ID schemeID unless the DocumentTypeCode equals '130'

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

Updated 6 November 2026