Attestwire › Rule reference › BR-DEC-11
BR-DEC-11 The sum of document-level charges may have at most two decimals
noun · EN 16931 · fatal · BT-108
For a sample invoice, the library reports: The allowed maximum number of decimals for the Sum of charges on document level (BT-108) is 2, but you declared 5.005, which has 3.
- Business term
BT-108- Severity
fatal
The fix
Round declaredTotals.chargeTotalAmount to two decimals (5.01 here) using half-up rounding away from zero, for which this package exports round2(). Alternatively drop declaredTotals and let the library compute the totals, which it always rounds correctly.
A passing value
"declaredTotals": { "chargeTotalAmount": 5.01 }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-11",
"field": "BT-108",
"severity": "fatal",
"message": "The allowed maximum number of decimals for the Sum of charges on document level (BT-108) is 2, but you declared 5.005, which has 3. The rule is written against the serialised value — the schematron counts the characters after the decimal point in the XML — so the check is about what gets written, not about what the number \"really\" is. Charges are the usual home of per-unit and percentage-based figures — freight per kilo, a 1.5% handling fee — so this is the total most likely to inherit a long decimal from the arithmetic that produced it.",
"fix": "Round declaredTotals.chargeTotalAmount to two decimals (5.01 here) using half-up rounding away from zero, for which this package exports round2(). Alternatively drop declaredTotals and let the library compute the totals, which it always rounds correctly.",
"example": "\"declaredTotals\": { \"chargeTotalAmount\": 5.01 }",
"xpath": "/ubl:Invoice/cac:LegalMonetaryTotal/cbc:ChargeTotalAmount",
"docsUrl": "https://attestwire.com/rules/BR-DEC-11"
}
xpath is always a UBL path. On a CII invoice, look for the
matching CII field instead.