Peppol BIS Billing 3.0 · rule
UBL-CR-119
What does UBL-CR-119 mean? A UBL invoice should not include the AdditionalDocumentReference DocumentStatusCode
Why did my invoice fail UBL-CR-119?
The invoice should not contain the element cac:AdditionalDocumentReference/cbc:DocumentStatusCode, i.e. the status code of a referenced additional document. This is one of the EN 16931 "cardinality restriction" (UBL-CR) warnings: the UBL 2.1 schema allows the element, but it maps to no business term in the EN 16931 core invoice model, so a compliant core invoice must leave it out. Supporting document references (BG-24) in EN 16931 carry only an identifier, description, and optional attachment; a document status code is not part of the semantic model. Receivers may ignore or reject data carried in such elements, so remove it or move the information to the supported business term.
Official rule text
A UBL invoice should not include the AdditionalDocumentReference DocumentStatusCode
Common causes
- Your invoice generator emits the full UBL 2.1 structure and populates cbc:DocumentStatusCode even though EN 16931 does not use it
- Mapping from an internal/ERP data model copies every available field into the UBL output instead of only the EN 16931 business terms
- A template or example invoice from a non-EN 16931 UBL context (e.g. generic UBL samples) was reused without stripping unsupported elements
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.