What it means
If delivery information includes a party that receives the goods (cac:DeliveryParty), the delivery block must contain exactly one deliver to party name (BT-70) in total, counted at cac:DeliveryParty/cac:PartyName/cbc:Name; Peppol BIS and NLCIUS allow zero or one instead. If the delivery block has no cac:DeliveryParty, this rule passes.
Why it matters
EN 16931 requires exactly one delivery party name within a delivery block when a delivery party is included. The Peppol BIS and NLCIUS checks allow zero or one name instead.
How to fix it
Fill in the name of the party the goods were delivered to, once, or leave the name out for Peppol BIS and NLCIUS. If you have no delivery party to name, remove it; the delivery date and address do not depend on it. In the XML, each cac:Delivery that contains cac:DeliveryParty needs exactly one cac:DeliveryParty/cac:PartyName/cbc:Name in total, except in Peppol BIS and NLCIUS, which allow zero or one.
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
Deliver to party 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 |
Check your file
Drop your e-invoice to see whether UBL-SR-25 still fails, and which other rules do.
Related rules
- UBL-SR-26 A payment block can have only one payment reference
- UBL-SR-27 Only one payment means code per payment block
- UBL-SR-28 A payment block can have only one mandate reference
- UBL-SR-29 Only one SEPA creditor identifier is allowed in the invoice
- UBL-SR-30 A discount can have only one reason text
- UBL-SR-31 A charge can have only one reason text