Skip to content

Fatal

UBL-SR-10: An invoice can have only one seller trading name

In short

Fatal: fails the selected checks.

UBL-SR-10 means the invoice gives the seller more than one trading name (BT-28). Keep the one name your customers know you by, or leave the trading name out.

On this page

What it means

The seller trading name (BT-28) is the name you trade under when it differs from your legal name. In UBL it is cbc:Name inside the seller's cac:PartyName. The rule allows at most one. The field itself is optional.

Why it matters

The standard has one place for it.

How to fix it

In your invoicing software, look at the company name, trading name or brand fields in the seller details and keep the one name customers know you by. If the software fills the trading name from more than one place, clear all but one. The trading name is optional, so you can also leave it empty. In the XML, keep one cac:PartyName with one cbc:Name under cac:AccountingSupplierParty/cac:Party.

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

Seller trader name shall occur maximum once

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

Updated 6 November 2026