How do I fix UBL-CR-130?

DOC-1 Timesheet for June https://example.com/docs/timesheet-june.pdf

Peppol BIS Billing 3.0 · rule

UBL-CR-130

Layer en16931·Checked against Peppol BIS Billing 3.0 2026.5

What does UBL-CR-130 mean? A UBL invoice should not include the AdditionalDocumentReference Attachment External Descriprion

Why did my invoice fail UBL-CR-130?

The invoice should not contain the element cac:AdditionalDocumentReference/cac:Attachment/cac:ExternalReference/cbc:Description, i.e. a description on an externally referenced attachment. 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. The supporting document description belongs at BT-123 (cbc:DocumentDescription on the document reference itself), not inside the external reference, which carries only the URI (BT-124). 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 Attachment External Descriprion

Common causes

The attachment description is placed inside cac:ExternalReference instead of cbc:DocumentDescription (BT-123) on the AdditionalDocumentReference
A generic UBL 2.1 attachment template with all external-reference fields was reused
A mapper copies file metadata (description, name, hash) from the DMS into the external reference block

How do I fix it?

<cac:AdditionalDocumentReference>
  <cbc:ID>DOC-1</cbc:ID>
  <cbc:DocumentDescription>Timesheet for June</cbc:DocumentDescription>
  <cac:Attachment>
    <cac:ExternalReference>
      <cbc:URI>https://example.com/docs/timesheet-june.pdf</cbc:URI>
    </cac:ExternalReference>
  </cac:Attachment>
</cac:AdditionalDocumentReference>

Check your invoice against this rule

Paste it into the live demo, or call POST /v1/validate. See the quickstart.