Peppol BIS Billing 3.0 · rule
UBL-CR-666
What does UBL-CR-666 mean? A UBL invoice shall not include an AdditionalDocumentReference simultaneously referring an Invoice Object Identifier and an Attachment
Why did my invoice fail UBL-CR-666?
A single cac:AdditionalDocumentReference must not act as both an invoiced object identifier (DocumentTypeCode 130) and an attachment carrier at the same time. EN 16931 treats the invoiced object identifier (BT-18) and supporting documents (BG-24) as separate things, so put the attachment in its own AdditionalDocumentReference without DocumentTypeCode 130.
Official rule text
A UBL invoice shall not include an AdditionalDocumentReference simultaneously referring an Invoice Object Identifier and an Attachment
Common causes
- One AdditionalDocumentReference reused for both the object identifier and an embedded attachment
- DocumentTypeCode 130 set on a reference that carries cac:Attachment
- Mapper merges all document references into a single element
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.