CII-SR-451: Element count restricted by EN 16931

The syntax allows the element more often (or not at all) at this place, but EN 16931 maps it to one business term, so the CEN rules restrict how often it occurs: « Only one payee identifier should be present (either the ID or the Global ID) » Below: the message, the cause and the fix.

The message validators print

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

CII
[CII-SR-451] - Only one payee identifier should be present (either the ID or the Global ID)

What it checks

The syntax allows the element more often (or not at all) at this place, but EN 16931 maps it to one business term, so the CEN rules restrict how often it occurs: « Only one payee identifier should be present (either the ID or the Global ID) »

Why invoices fail it

The generator writes one element per source value (two notes, two references) where EN 16931 expects one, or leaves out an element EN 16931 needs exactly once.

How to fix it

Write the element exactly as often as the message says; join several values into one, or move the extra ones to a business term that repeats.

This explanation covers the whole CII-SR family (482 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.

CII · CEN EN 16931 validation artefacts (CII) 1.3.16 · assert · warning
context: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement
test:    (not(ram:PayeeTradeParty/ram:ID) and ram:PayeeTradeParty/ram:GlobalID) or (ram:PayeeTradeParty/ram:ID and not(ram:PayeeTradeParty/ram:GlobalID)) or (not(ram:PayeeTradeParty/ram:ID) and not(ram:PayeeTradeParty/ram:GlobalID))

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