Peppol BIS Billing 3.0 · rule
UBL-CR-198
What does UBL-CR-198 mean? A UBL invoice should not include the AccountingSupplierParty DespatchContact
Why did my invoice fail UBL-CR-198?
This EN 16931 rule warns when the UBL element cac:AccountingSupplierParty/cac:DespatchContact is present: the invoice should not include a despatch contact on the supplier party wrapper. EN 16931 defines a single seller contact (BG-6), carried under cac:Party/cac:Contact; separate role-specific contacts such as a despatch contact are outside the core model. The element is not forbidden by UBL itself, but it lies outside the EN 16931 core invoice model, so remove it to keep the invoice fully conformant and interoperable.
Official rule text
A UBL invoice should not include the AccountingSupplierParty DespatchContact
Common causes
- Logistics contact data exported from the ERP into the invoice
- Mapping from an order/despatch document reused for invoicing
- Schema-driven generator populating all SupplierParty children
Related rules
UBL-CR-001 · UBL-CR-002 · UBL-CR-003 · UBL-CR-004 · UBL-CR-005 · UBL-CR-006 · UBL-CR-007 · UBL-CR-008
Paste it into the live demo, or call POST /v1/validate. See the quickstart.