attestwireAttestwire › Rule reference › BR-DEC-13
BR-DEC-13 The total VAT amount may have at most two decimals
noun · EN 16931 · fatal · BT-110
For a sample invoice, the library reports: The allowed maximum number of decimals for the Invoice total VAT amount (BT-110) is 2, but you declared 285.0004, which has 4.
- Business term
BT-110- Severity
fatal
The fix
Round declaredTotals.taxAmount to two decimals before assigning it (285.00 here), using half-up rounding away from zero. This package exports round2() for exactly this, and it avoids the two JavaScript traps: Math.round(1.005 * 100) / 100 gives 1.00, and (2.675).toFixed(2) gives "2.67". Alternatively drop declaredTotals and let the library compute the totals, which it always rounds correctly.
A passing value
"declaredTotals": { "taxAmount": 285.00 }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-DEC-13",
"field": "BT-110",
"severity": "fatal",
"message": "The allowed maximum number of decimals for the Invoice total VAT amount (BT-110) is 2, but you declared 285.0004, which has 4. The rule is written against the serialised value — the schematron measures the digits after the decimal point in the XML — so a value that merely *displays* as two decimals still fails if the underlying number carries more. Applying a percentage produces a long decimal almost every time — 1 234.56 x 19% is 234.5664. VAT is rounded per VAT breakdown group (BR-CO-17) and the rounded group amounts are then summed, so the total should never carry more than two decimals.",
"fix": "Round declaredTotals.taxAmount to two decimals before assigning it (285.00 here), using half-up rounding away from zero. This package exports round2() for exactly this, and it avoids the two JavaScript traps: Math.round(1.005 * 100) / 100 gives 1.00, and (2.675).toFixed(2) gives \"2.67\". Alternatively drop declaredTotals and let the library compute the totals, which it always rounds correctly.",
"example": "\"declaredTotals\": { \"taxAmount\": 285.00 }",
"xpath": "/ubl:Invoice/cac:TaxTotal/cbc:TaxAmount",
"docsUrl": "https://attestwire.com/rules/BR-DEC-13"
}
xpath is always a UBL path. On a CII invoice, look for the
matching CII field instead.