Peppol BIS Billing 3.0 · rule
UBL-CR-098
What does UBL-CR-098 mean? A UBL invoice should not include the ContractDocumentReference DocumentTypeCode
Why did my invoice fail UBL-CR-098?
EN 16931 states that a UBL invoice should not include the cbc:DocumentTypeCode child of cac:ContractDocumentReference. In the core invoice model this element carries the contract reference (BT-12), for which the core model only uses the document identifier (cac:ContractDocumentReference/cbc:ID), so cbc:DocumentTypeCode lies outside the standard's subset of UBL and validators flag its presence. It is a warning-level cardinality rule: the extra data is ignored by receivers that implement only the core model.
Official rule text
A UBL invoice should not include the ContractDocumentReference DocumentTypeCode
Common causes
- A UNCL1001 document type code is exported as cbc:DocumentTypeCode, although the core model does not use it on the contract reference.
- A mapping copied from AdditionalDocumentReference (where a type code is used) is reused for the contract reference.
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.