attestwire, n.Get an API key

Attestwire › Rule reference › BR-CO-18

BR-CO-18 An invoice must have at least one VAT breakdown group

noun · EN 16931 · fatal · BG-23

For a sample invoice, the library reports: An invoice shall have at least one VAT breakdown group (BG-23).

Business term
BG-23
Severity
fatal

The fix

Add the VAT breakdown to the document: one group per VAT category and rate, with its taxable amount (BT-116), VAT amount (BT-117) and category (BT-118).

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:

TeachingError
{
  "rule": "BR-CO-18",
  "field": "BG-23",
  "severity": "fatal",
  "message": "An invoice shall have at least one VAT breakdown group (BG-23). Even a document on which no VAT is due must say so explicitly and say why — with a category (BT-118), a taxable amount (BT-116) and a tax amount of zero (BT-117) — because \"no VAT breakdown\" and \"no VAT due\" are different claims, and only the second is something a tax authority can accept.",
  "fix": "Add the VAT breakdown to the document: one group per VAT category and rate, with its taxable amount (BT-116), VAT amount (BT-117) and category (BT-118).",
  "xpath": "/ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal",
  "docsUrl": "https://attestwire.com/rules/BR-CO-18"
}

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

All 307 rule pages

Nearby: BR-CO-19 — An invoicing period must give a start date, an end date or a VAT point code; BR-CO-17 — The VAT in each breakdown group must equal base × rate; BR-CO-20 — An invoice line period must have a start date, an end date or both.

Want a worked example for BR-CO-18? Ask, and it gets written.

Check your invoice in the browser, or over the API. Something wrong on this page?