attestwireAttestwire › Rule reference › BR-DEC-05
BR-DEC-05 A document-level charge amount may have at most two decimals
noun · EN 16931 · fatal · BT-99
For a sample invoice, the library reports: The allowed maximum number of decimals for the document level charge amount (BT-99) is 2, but charges[0].amount is 10.005, which has 3.
- Business term
BT-99- Severity
fatal
The fix
Round charges[0].amount to two decimals before you hand it over — 10.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
"amount": 10.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-05",
"field": "BT-99",
"severity": "fatal",
"message": "The allowed maximum number of decimals for the document level charge amount (BT-99) is 2, but charges[0].amount is 10.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. An allowance amount usually arrives as a percentage of something — 3% settlement discount, 1.5% surcharge — and a percentage of a two-decimal figure is almost never a two-decimal figure. EN 16931 wants the *result* rounded, once, before it is written.",
"fix": "Round charges[0].amount to two decimals before you hand it over — 10.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": "\"amount\": 10.01",
"xpath": "/ubl:Invoice/cac:AllowanceCharge[1]/cbc:Amount",
"docsUrl": "https://attestwire.com/rules/BR-DEC-05"
}
xpath is always a UBL path. On a CII invoice, look for the
matching CII field instead.