Attestwire

Rule reference

BR-DEC-09 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 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.

This rule is implemented and its error payload below is real, but the long-form write-up — normative text, worked example, divergence note — is not written yet. Everything the library knows about this rule is on this page. Ask and we will prioritise it.

Business term
BT-106
Severity
fatal

What the library returns

The exact object in result.errors when this rule fires. Generated by running @attestwire/en16931, not transcribed:

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 locates the element in the generated UBL document, which is where a KoSIT or Peppol validator will report the same problem.

A passing value

the shape this field expects
"declaredTotals": { "lineExtensionAmount": 1500.00 }

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.

All 292 rules →

Nearby: BR-DEC-10 — The allowed maximum number of decimals for the Sum of allowances on document level (BT-107) is 2, but you declared 10.005, which has 3; BR-DEC-06 — 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; BR-DEC-11 — 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.

Check this rule against your invoice via the hosted API → https://api.attestwire.com/docs

Arrived from a stack trace? The docsUrl on every error links straight here. Something wrong on this page — tell us.