AttestwireRule referenceBR-DEC-09

BR-DEC-09 The sum of line net amounts may have at most two decimals

noun · EN 16931 · fatal · BT-106

For a sample invoice, the library reports: The allowed maximum number of decimals for the Sum of Invoice line net amounts (BT-106) is 2, but you declared 1500.001, which has 3.

Business term
BT-106
Severity
fatal

The fix

Round declaredTotals.lineExtensionAmount to two decimals before assigning it (1500.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": { "lineExtensionAmount": 1500.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-09",
  "field": "BT-106",
  "severity": "fatal",
  "message": "The allowed maximum number of decimals for the Sum of Invoice line net amounts (BT-106) is 2, but you declared 1500.001, which has 3. 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. A sum of line amounts only carries extra decimals if the lines were summed before they were rounded. EN 16931 requires the opposite order: round each line net amount (BT-131) to two decimals first, then add.",
  "fix": "Round declaredTotals.lineExtensionAmount to two decimals before assigning it (1500.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\": { \"lineExtensionAmount\": 1500.00 }",
  "xpath": "/ubl:Invoice/cac:LegalMonetaryTotal/cbc:LineExtensionAmount",
  "docsUrl": "https://attestwire.com/rules/BR-DEC-09"
}

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