UBL-CR-673: An invoiced object reference must not have a description

What it means

In a UBL file, cac:AdditionalDocumentReference is used for two different things. With document type code 130 it holds only the invoiced object identifier (BT-18) and its scheme (BT-18-1). A description (BT-123) belongs to a supporting document (BG-24), which is a reference without that code. This rule checks that a reference with code 130 has no cbc:DocumentDescription.

Why it matters

This rule is an error, not a warning. A reference with code 130 is read as an identifier only, so a description on it breaks the EN 16931 UBL rules.

How to fix it

In your invoicing software, check the references on the invoice and clear the description typed on the invoiced object reference, such as a subscription number or a meter point. If you want to describe a supporting document, add it as a separate document with its own description. If you build the XML yourself, remove cbc:DocumentDescription from the cac:AdditionalDocumentReference that has cbc:DocumentTypeCode 130.

The rule as published

A UBL invoice shall not include an AdditionalDocumentReference simultaneously referring an Invoice Object Identifier and an Document Description

Where this rule applies