Skip to content

Warning

UBL-DT-08: Leave out the schemeName attribute

In short

Warning: worth checking.

UBL-DT-08 means the invoice contains a schemeName attribute, which the standard asks you to leave out. Remove the attribute from your export to clear the warning.

On this page

What it means

The check searches the whole file for a schemeName attribute. In UBL this attribute can sit on an identifier, such as an electronic address (BT-34, BT-49) or a company registration number (BT-30, BT-47), and give the name of its identification scheme in words. One occurrence anywhere in the file is enough to trigger the warning.

Why it matters

EN 16931 asks you to omit schemeName from UBL invoices and credit notes.

How to fix it

It is worth fixing when you control the export, or when the same warning appears on every invoice you send. Ask the supplier of your invoicing software to stop writing schemeName. If you build the XML yourself, remove the schemeName attribute from every element that has it and keep schemeID. Export again and recheck the file.

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

Scheme name attribute should not be present

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

Updated 6 November 2026