Attestwire › Rule reference › BR-CL-06

BR-CL-06 The VAT point date code must be one of the three codes EN 16931 allows

noun · EN 16931 · fatal · BT-8

For a sample invoice, the library reports: The VAT point date code (BT-8) is "99", which is not one of the 3 codes EN 16931 admits. UNTDID 2005 is a large list of date qualifiers and the standard restricts it to exactly three: "3" the invoice date, "35" the actual delivery date, and "432" paid to date.

Business term

BT-8

Severity

fatal

The fix

Set invoicingPeriod.descriptionCode to "3" (tax point is the invoice issue date), "35" (the actual delivery date) or "432" (paid to date). If you know the tax point as a date rather than as a rule, use taxPointDate (BT-7) instead — but not both, which BR-CO-03 forbids.

A passing value

"invoicingPeriod": { "descriptionCode": "35" }

What the library returns

The full error returned by @attestwire/en16931. It includes the rule ID, affected field and suggested correction. Developers can use this object in their application:

{
  "rule": "BR-CL-06",
  "field": "BT-8",
  "severity": "fatal",
  "message": "The VAT point date code (BT-8) is \"99\", which is not one of the 3 codes EN 16931 admits. UNTDID 2005 is a large list of date qualifiers and the standard restricts it to exactly three: \"3\" the invoice date, \"35\" the actual delivery date, and \"432\" paid to date. The code is not a label for the period — it says which event determines the tax point, and therefore which VAT period and which rate the supply falls under. Anything outside the three leaves that undetermined.",
  "fix": "Set invoicingPeriod.descriptionCode to \"3\" (tax point is the invoice issue date), \"35\" (the actual delivery date) or \"432\" (paid to date). If you know the tax point as a date rather than as a rule, use taxPointDate (BT-7) instead — but not both, which BR-CO-03 forbids.",
  "example": "\"invoicingPeriod\": { \"descriptionCode\": \"35\" }",
  "xpath": "/ubl:Invoice/cac:InvoicePeriod/cbc:DescriptionCode",
  "docsUrl": "https://attestwire.com/rules/BR-CL-06"
}

xpath is always a UBL path. On a CII invoice, look for the matching CII field instead.