Peppol BIS Billing 3.0 · rule
UBL-CR-262
What does UBL-CR-262 mean? A UBL invoice should not include the AccountingCustomerParty DeliveryContact
Why did my invoice fail UBL-CR-262?
EN 16931 defines a fixed set of business terms, and the UBL syntax binding marks every UBL element outside that set as not to be used. This rule (a warning) fires when the DeliveryContact group under AccountingCustomerParty (delivery information belongs in the cac:Delivery structure) is present: DeliveryContact at cac:AccountingCustomerParty/cac:DeliveryContact has no corresponding business term in the core invoice model. Remove the element — receivers are not required to process it, so any data placed there may be silently ignored.
Official rule text
A UBL invoice should not include the AccountingCustomerParty DeliveryContact
Common causes
- Your UBL generator or ERP export populates the full UBL 2.1 schema, including DeliveryContact, instead of restricting output to the EN 16931 subset
- An invoice template copied from a generic (non-EN 16931) UBL sample carries the element along
- Mapping software transfers every available master-data field of the customer/payee into the XML rather than only the fields the standard supports
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.