attestwireAttestwire › Rule reference › BR-DEC-06
BR-DEC-06 A document-level charge base amount may have at most two decimals
noun · EN 16931 · fatal · BT-100
For a sample invoice, the library reports: The allowed maximum number of decimals for the document level charge base amount (BT-100) is 2, but charges[0].baseAmount is 100.005, which has 3.
- Business term
BT-100- Severity
fatal
The fix
Round charges[0].baseAmount to two decimals before you hand it over — 100.01 here. This package exports round2() for it, which avoids the two JavaScript traps: Math.round(1.005 * 100) / 100 gives 1.00, and (2.675).toFixed(2) gives "2.67".
A passing value
"baseAmount": 100.01What 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-06",
"field": "BT-100",
"severity": "fatal",
"message": "The allowed maximum number of decimals for the document level charge base amount (BT-100) is 2, but charges[0].baseAmount is 100.005, which has 3. The schematron measures the digits after the decimal point in the serialised XML, so a value that merely *displays* as two decimals still fails when the underlying number carries more. A base amount is normally lifted straight out of a subtotal your own system computed, so it carries whatever precision that computation left behind. It is also the number the percentage is applied to, so an over-precise base tends to produce an over-precise amount alongside it.",
"fix": "Round charges[0].baseAmount to two decimals before you hand it over — 100.01 here. This package exports round2() for it, which avoids the two JavaScript traps: Math.round(1.005 * 100) / 100 gives 1.00, and (2.675).toFixed(2) gives \"2.67\".",
"example": "\"baseAmount\": 100.01",
"xpath": "/ubl:Invoice/cac:AllowanceCharge[1]/cbc:BaseAmount",
"docsUrl": "https://attestwire.com/rules/BR-DEC-06"
}
xpath is always a UBL path. On a CII invoice, look for the
matching CII field instead.