Peppol BIS Billing 3.0 · rule

UBL-CR-063

Layer en16931·Checked against Peppol BIS Billing 3.0 2026.5

What does UBL-CR-063 mean? A UBL invoice should not include the ReceiptDocumentReference IssueDate

Why did my invoice fail UBL-CR-063?

The UBL 2.1 schema allows a IssueDate child inside cac:ReceiptDocumentReference, but this element is not part of the EN 16931 core invoice model, so a compliant invoice should not include it. UBL-CR rules exist because EN 16931 uses only a subset of full UBL: any element outside that subset carries data the receiver is not required to process. In the core model, cac:ReceiptDocumentReference conveys the receiving advice reference (BT-15) and should be limited to cbc:ID (the receiving advice reference, BT-15).

Official rule text

A UBL invoice should not include the ReceiptDocumentReference IssueDate

Common causes

Your ERP or invoicing software exports the full UBL 2.1 ReceiptDocumentReference structure, including IssueDate, instead of the EN 16931 subset
A generic UBL template or mapping copies every available source field into the XML rather than only the core-model elements
Data intended for another business term was mapped into cac:ReceiptDocumentReference/IssueDate because no obvious core element existed for it

How do I fix it?

<cac:ReceiptDocumentReference>
  <cbc:ID>REC-2024-007</cbc:ID>
</cac:ReceiptDocumentReference>

Check your invoice against this rule

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