Peppol BIS Billing 3.0 · rule

UBL-CR-150

Layer en16931·Checked against Peppol BIS Billing 3.0 2026.5

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

Why did my invoice fail UBL-CR-150?

The invoice should not contain the element cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:Postbox, i.e. a post box 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 post box term; PO box information should be carried in the address lines (BT-35/BT-36/BT-162) instead. 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 Postbox

Common causes

Your invoice generator emits the full UBL 2.1 structure and populates cbc:Postbox even though EN 16931 does not use it
Mapping from an internal/ERP data model copies every available field into the UBL output instead of only the EN 16931 business terms
A template or example invoice from a non-EN 16931 UBL context (e.g. generic UBL samples) was reused without stripping unsupported elements

How do I fix it?

<cac:PostalAddress>
  <cbc:StreetName>P.O. Box 123</cbc:StreetName>
  <cbc:CityName>Maribor</cbc:CityName>
  <cbc:PostalZone>2000</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.