Skip to content

Warning

UBL-CR-077: Do not include a statement document reference

In short

Warning: worth checking.

UBL-CR-077 means the invoice has a statement document reference (cac:StatementDocumentReference), which EN 16931 does not use. It is only a warning, so the invoice is still accepted, but you should remove that element and export again.

On this page

What it means

This rule checks that a UBL invoice or credit note does not contain a statement document reference at all, meaning a reference to a statement document that goes with the invoice. EN 16931 has no field for it, so the whole element, with everything inside it, is outside the standard.

Why it matters

The recipient reads only the fields that EN 16931 defines, so their software ignores the reference or drops it. They will not see which statement you meant. The rule is a warning because no amount or VAT figure depends on it, so the invoice is still accepted.

How to fix it

Delete cac:StatementDocumentReference from the invoice and export again. If the recipient needs to know which statement the invoice belongs to, mention it in an invoice note (BT-22). You can also add the statement as a supporting document (BG-24). Check your invoicing software for a statement or account reference field and clear it.

The rule as published

A UBL invoice should not include the StatementDocumentReference

Where this rule applies

Rule set Version
EN 16931 (UBL) 1.3.17
EN 16931 (UBL credit note) 1.3.17
XRechnung 3.0 (UBL) 3.0.2
XRechnung 3.0 (UBL credit note) 3.0.2
Peppol BIS Billing 3.0 (invoice) 2026.5
Peppol BIS Billing 3.0 (credit note) 2026.5
SI-UBL 2.0 / NLCIUS (invoice) 2.0.3.13
SI-UBL 2.0 / NLCIUS (credit note) 2.0.3.13
France CTC (UBL invoice) 1.4.0-04
France CTC (UBL credit note) 1.4.0-04
CIUS-RO UBL Invoice 1.0.9 1.0.9
CIUS-RO UBL Credit Note 1.0.9 1.0.9
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether UBL-CR-077 still fails, and which other rules do.

Updated 6 November 2026