AttestwireRule referenceBR-DEC-14

BR-DEC-14 The total amount with VAT may have at most two decimals

noun · EN 16931 · fatal · BT-112

For a sample invoice, the library reports: The allowed maximum number of decimals for the Invoice total amount with VAT (BT-112) is 2, but you declared 1785.0011, which has 4.

Business term
BT-112
Severity
fatal

The fix

Round declaredTotals.taxInclusiveAmount to two decimals before assigning it (1785.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

the shape this field expects
"declaredTotals": { "taxInclusiveAmount": 1785.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:

TeachingError
{
  "rule": "BR-DEC-14",
  "field": "BT-112",
  "severity": "fatal",
  "message": "The allowed maximum number of decimals for the Invoice total amount with VAT (BT-112) is 2, but you declared 1785.0011, 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. BT-112 is BT-109 + BT-110; if either of those is over-precise this one will be too.",
  "fix": "Round declaredTotals.taxInclusiveAmount to two decimals before assigning it (1785.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\": { \"taxInclusiveAmount\": 1785.00 }",
  "xpath": "/ubl:Invoice/cac:LegalMonetaryTotal/cbc:TaxInclusiveAmount",
  "docsUrl": "https://attestwire.com/rules/BR-DEC-14"
}

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