Skip to content
Change language: English

Warning

UBL-CR-649: The business process identifier should have no scheme attribute

In short

Warning: worth checking.

UBL-CR-649 means the business process identifier (BT-23) has a schemeID attribute, which EN 16931 does not use. Remove the attribute and keep the identifier text.

On this page

What it means

This rule checks the business process identifier (BT-23), the cbc:ProfileID element, and flags it if it has a schemeID attribute. The element holds a plain text code that says which business process the invoice belongs to. In Peppol BIS Billing 3.0 the value is urn:fdc:peppol.eu:2017:poacc:billing:01:1.0. EN 16931 defines no scheme for it.

Why it matters

EN 16931 uses the business process identifier without a schemeID attribute. The check concerns the attribute rather than the identifier value.

How to fix it

Remove schemeID from cbc:ProfileID and leave the business process identifier (BT-23) text as it is. If your software adds the attribute, ask its supplier to correct the export, then check the new 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 ProfileID 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-649 still fails, and which other rules do.

Updated 6 November 2026