InvoiceKit

EN 16931 rules › BR-CL-06

BR-CL-06 — Value added tax point date code MUST be coded using a restriction of UNTDID 2475

Rule idBR-CL-06
Rule setEN 16931 itself, not a national or network addition
Severityfatal in CII and UBL — a validator enforcing this rule set rejects the invoice
Applies tothe CII and UBL syntaxes
Checked bythe validator on this site and invoicekit.go v0.2.11, the library behind it

The rule as published

Value added tax point date code MUST be coded using a restriction of UNTDID 2475.

fatal in CII — a validator enforcing this rule set rejects the invoice.

Value added tax point date code MUST be coded using a restriction of UNTDID 2005.

fatal in UBL — a validator enforcing this rule set rejects the invoice.

What runs for it

Straight from the artefacts the engine embeds: the node the assertion selects and the test it applies there. A failing invoice is reported with the message above.

SyntaxSeverityArtefact phaseApplied toFails when
CIIfatalcodelist_phaseram:DueDateTypeCode((not(contains(normalize-space(.), ' ')) and contains(' 5 29 72 ', concat(' ', normalize-space(.), ' '))))
UBLfatalcodelist_phasecac:InvoicePeriod/cbc:DescriptionCode((not(contains(normalize-space(.), ' ')) and contains(' 3 35 432 ', concat(' ', normalize-space(.), ' '))))

Data elements it names

Its message names no business term or business group; the node it applies to is in the table above.

See also

· All EN 16931 rules ·