How do I fix UBL-CR-155?

Main Street 42 Ljubljana 1000 SI

Peppol BIS Billing 3.0 · rule

UBL-CR-155

Layer en16931·Checked against Peppol BIS Billing 3.0 2026.5

What does UBL-CR-155 mean? A UBL invoice should not include the AccountingSupplierParty Party PostalAddress BuildingNumber

Why did my invoice fail UBL-CR-155?

The invoice should not contain the element cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:BuildingNumber, i.e. a building number on the seller postal address. This is one of the EN 16931 "cardinality restriction" (UBL-CR) warnings: the UBL 2.1 schema allows the element, but it maps to no business term in the EN 16931 core invoice model, so a compliant core invoice must leave it out. The seller postal address (BG-5) has no dedicated building number term; house numbers belong in the street name line (BT-35). Receivers may ignore or reject data carried in such elements, so remove it or move the information to the supported business term.

Official rule text

A UBL invoice should not include the AccountingSupplierParty Party PostalAddress BuildingNumber

Common causes

The ERP stores street name and house number in separate fields and the mapper emits cbc:BuildingNumber instead of concatenating the number into cbc:StreetName (BT-35)
A generic UBL 2.1 address template with all address fields was reused
Address data imported from a structured national address register keeps its fine-grained fields in the UBL output

How do I fix it?

<cac:PostalAddress>
  <cbc:StreetName>Main Street 42</cbc:StreetName>
  <cbc:CityName>Ljubljana</cbc:CityName>
  <cbc:PostalZone>1000</cbc:PostalZone>
  <cac:Country><cbc:IdentificationCode>SI</cbc:IdentificationCode></cac:Country>
</cac:PostalAddress>

Check your invoice against this rule

Paste it into the live demo, or call POST /v1/validate. See the quickstart.