Peppol BIS Billing 3.0 · rule
UBL-CR-395
What does UBL-CR-395 mean? A UBL invoice should not include the DeliveryParty PhysicalLocation
Why did my invoice fail UBL-CR-395?
The UBL element cac:Delivery/cac:DeliveryParty/cac:PhysicalLocation should not be used in an EN 16931 invoice. The delivery place is expressed through cac:Delivery/cac:DeliveryLocation; a physical location nested under the party is outside the core model.
Official rule text
A UBL invoice should not include the DeliveryParty PhysicalLocation
Common causes
- Mapping location data onto the party instead of cac:DeliveryLocation
- Full party object serialization including physical location
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.