BR-DEC-27 — E-Invoice Validation Rule & Fix

Fixture ID: lineAllowanceOverPrecise · XPath: /ubl:Invoice/cac:InvoiceLine[1]/cac:AllowanceCharge[2]/cbc:Amount

1. Why This Rule Triggers (Diagnostic Message)

The allowed maximum number of decimals for the invoice line charge amount (BT-141) is 2, but lines[0].charges[0].amount is 1.005, which has 3. The constraint is on the serialised value, so it is about what reaches the XML rather than about what your variable holds — and the line is where over-precision starts, since every document total downstream of it inherits the drift. A line charge is added into the line net amount (BT-131), which must land on two decimals. Per-unit surcharges multiplied by a fractional quantity are the usual source of the extra digits.

2. How to Fix BR-DEC-27

Round lines[0].charges[0].amount to two decimals before assigning it (1.00 here). Use half-up rounding away from zero — this package exports round2(), which handles the cases Math.round and toFixed get wrong.

3. Valid Code / Payload Example

"amount": 1.00