Peppol BIS Billing 3.0 · rule
UBL-CR-075
What does UBL-CR-075 mean? A UBL invoice should not include the ReceiptDocumentReference IssuerParty
Why did my invoice fail UBL-CR-075?
EN 16931 states that a UBL invoice should not include the cac:IssuerParty child of cac:ReceiptDocumentReference. In the core invoice model this element carries the receiving advice reference (BT-15), for which the core model only uses the document identifier (cac:ReceiptDocumentReference/cbc:ID), so cac:IssuerParty lies outside the standard's subset of UBL and validators flag its presence. It is a warning-level cardinality rule: the extra data is ignored by receivers that implement only the core model.
Official rule text
A UBL invoice should not include the ReceiptDocumentReference IssuerParty
Common causes
- The party that issued the referenced document is exported as cac:IssuerParty, which the core model does not support.
- A full UBL 2.1 document model is serialised without pruning it to the EN 16931 subset.
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.