UBL-CR-093: cac:OriginatorDocumentReference/cac:ResultOfVerification not used by EN 16931

The UBL schema allows cac:OriginatorDocumentReference/cac:ResultOfVerification at this place, but EN 16931 does not map it to any business term, so the CEN rules flag it. Below: the message, the cause and the fix.

The message validators print

UBL-CR-093 is a rule of the UBL syntax rules (UBL-CR, UBL-SR, UBL-DT) (CEN validation artefacts 1.3.16) for UBL. It is a warning: the invoice stays valid, but should be corrected.

UBL
[UBL-CR-093]-A UBL invoice should not include the OriginatorDocumentReference ResultOfVerification

What it checks

The UBL schema allows cac:OriginatorDocumentReference/cac:ResultOfVerification at this place, but EN 16931 does not map it to any business term, so the CEN rules flag it. The rule is a warning: the invoice stays valid, but a receiver may ignore whatever the element holds.

Why invoices fail it

The generator writes the full syntax (a library that serialises every field it knows), or information that EN 16931 does not model is put into a free element of the syntax.

How to fix it

Remove cac:OriginatorDocumentReference/cac:ResultOfVerification; if its content matters to the buyer, put it in the business term that carries that information (a note, BT-22, or an item attribute, BG-32).

This explanation covers the whole UBL-CR family (678 rules, overview), so this page is not indexed.

The rule as published

Where the rule applies (context) and what must hold (test), unmodified from CEN EN 16931 validation artefacts 1.3.16. An assert fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

UBL · CEN EN 16931 validation artefacts (UBL) 1.3.16 · assert · warning
context: /ubl:Invoice | /cn:CreditNote
test:    not(cac:OriginatorDocumentReference/cac:ResultOfVerification)

Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator (Peppol BIS, XRechnung, Factur-X): each runs the same rule files and links every finding to its rule page. From your own code, POST /einvoice/validate (reference) returns the same check as JSON, each finding with an explanation field pointing here (5 calls a check, anonymous within the daily allowance).

Sources