Peppol BIS Billing 3.0 · rule
UBL-CR-392
What does UBL-CR-392 mean? A UBL invoice should not include the DeliveryParty PartyIdentification
Why did my invoice fail UBL-CR-392?
The UBL element cac:Delivery/cac:DeliveryParty/cac:PartyIdentification should not be used in an EN 16931 invoice. In the core model the deliver-to location identifier is BT-71, carried on cac:DeliveryLocation/cbc:ID, not as a party identification of the delivery party.
Official rule text
A UBL invoice should not include the DeliveryParty PartyIdentification
Common causes
- Mapping the location ID (e.g. a GLN) onto the party instead of DeliveryLocation/cbc:ID
- Reusing buyer/seller party mapping code, where PartyIdentification is valid, for the delivery party
How do I fix it?
<cac:Delivery>
<cac:DeliveryLocation>
<cbc:ID schemeID="0088">7300010000001</cbc:ID>
</cac:DeliveryLocation>
<cac:DeliveryParty>
<cac:PartyName><cbc:Name>Warehouse Ljubljana</cbc:Name></cac:PartyName>
</cac:DeliveryParty>
</cac:Delivery>
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
Check your invoice against this rule
Paste it into the live demo, or call POST /v1/validate. See the quickstart.