Peppol BIS Billing 3.0 · rule
UBL-CR-530
What does UBL-CR-530 mean? A UBL invoice should not include the InvoiceLine ReceiptLineReference
Why did my invoice fail UBL-CR-530?
EN 16931 defines a fixed set of information elements for a compliant invoice, and the UBL element InvoiceLine / ReceiptLineReference is not part of that core model. This rule flags the element as not allowed so that invoices stay interoperable: receivers implementing only the EN 16931 semantic model would ignore or reject data placed there. Remove the ReceiptLineReference element from the InvoiceLine structure rather than relying on it to convey information.
Official rule text
A UBL invoice should not include the InvoiceLine ReceiptLineReference
Common causes
- Your UBL generator or ERP export maps internal fields to the full UBL 2.1 schema, which allows ReceiptLineReference, but EN 16931 restricts the invoice to its core elements
- Reusing a UBL template from an order/despatch/receipt document flow where this element is normally populated
- Copying an example invoice from generic UBL documentation instead of an EN 16931 / Peppol BIS example
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.