Peppol BIS Billing 3.0 · rule
UBL-CR-077
What does UBL-CR-077 mean? A UBL invoice should not include the StatementDocumentReference
Why did my invoice fail UBL-CR-077?
EN 16931 states that a UBL invoice should not include the cac:StatementDocumentReference element at all. The core invoice model (EN 16931-1) defines no business term for a reference to a statement, so this UBL element lies outside the standard's subset of UBL and validators flag its presence. It is a warning-level cardinality rule: the data is ignored by receivers that implement only the core model.
Official rule text
A UBL invoice should not include the StatementDocumentReference
Common causes
- The ERP links the invoice to an account statement and exports that link as cac:StatementDocumentReference.
- A full UBL 2.1 invoice model is serialised without pruning it to the EN 16931 subset.
- The reference actually belongs in cac:AdditionalDocumentReference (BG-24), the element the core model provides for extra supporting documents.
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
Check your invoice against this rule
Paste it into the live demo, or call POST /v1/validate. See the quickstart.