What it means
The rule checks the seller block (cac:AccountingSupplierParty) and fails when it holds a cac:DespatchContact, a contact for questions about shipping. EN 16931 has one contact for the seller (BG-6), placed in cac:Party/cac:Contact, and nothing more specific.
Why it matters
This is only a warning, so the invoice is still accepted. The recipient reads the one seller contact from the party. A despatch contact next to the party is not part of the standard and is ignored.
How to fix it
Remove cac:DespatchContact from cac:AccountingSupplierParty and export again. If the person to call about deliveries is not the person in the normal seller contact, decide which one should appear on the invoice, since only one can be shown. The contact name, telephone number and email address belong in cac:Party/cac:Contact. It is worth fixing when you build the XML yourself or want a file with no warnings.
The rule as published
A UBL invoice should not include the AccountingSupplierParty DespatchContact 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-CR-198 still fails, and which other rules do.