Review fractional-quantity totals by preserving the exact supported quantity and checking each calculation stage. A short displayed money amount can hide a quantity copied with lost precision, a unit mismatch or a different rounding sequence. Compare the source measurement with the input before investigating the document total.
This review extends the invoice calculation workflow to invoices with measured goods or time-based services. The current creator supports positive quantities with up to four decimal places and unit prices with up to two. It rounds the initial line amount, the supported percentage discount and line tax in separate stages.
Gather the unrounded source quantities
Use the original measurement, approved duration or delivery record. Do not reconstruct quantity by dividing an already rounded line amount by the unit price, because several nearby quantities can produce the same cent result. Keep the original quantity as the starting evidence.
Confirm the measurement unit at the same time. A source record of 0.75 tonnes and an invoice quantity of 0.75 kilograms preserve the digits but not the meaning. Review any conversion and the corresponding price basis together before checking money totals.
For time-based work, convert minutes correctly to decimal hours. One hour and thirty minutes is 1.5 hours, not 1.30. An arithmetic review cannot repair a duration that was translated incorrectly before it reached the quantity field.
Check the initial amount per row
A quantity of 1.375 at 20.00 produces 27.50 before discount and tax. A quantity rounded prematurely to 1.38 produces 27.60. The ten-cent difference is caused by changed input, not by two systems rounding the same initial product differently.
For another fictional row, 0.125 at 1.00 produces an exact initial product of 0.125 and a supported rounded amount of 0.13. Record that rounded value before applying later percentages. This is the amount the current creator uses for its supported discount step.
If a source quantity needs more than four decimal places, identify that as a model limitation. Do not silently truncate it and then describe a later mismatch as ordinary rounding. Use an agreed representable basis or an invoicing system that supports the required precision.
Reconcile discounts and tax separately
Check the supported discount percentage against the agreement and calculate it from the rounded initial amount. Round the discount to cents, subtract it and then check the manually entered tax information. Keep the rounded tax contribution visible for every line.
For a simple example, 2.5 units at 12.00 give 30.00. A ten-percent discount is 3.00, leaving 27.00 net. At an illustrative twenty-percent rate, tax is 5.40. The line contributes 32.40 including tax. The rate is an arithmetic illustration, not a recommendation for a particular supply.
Where the other system calculates from unrounded intermediate values, note the policy difference explicitly. Do not assume the fractional quantity itself is wrong merely because the final totals differ. Identify the first stage at which equal inputs produce different intermediate results.
Sum money, not unlike quantities
An invoice can contain 1.5 hours, 2.75 metres and three individual products. Their combined quantity is not a meaningful measure. Reconcile the rounded monetary net amounts and tax contributions instead, while checking each quantity against its own evidence.
If two rows use the same unit, a combined quantity can sometimes provide an additional review check, but it does not replace the individual line calculation. Different unit prices, discounts or tax treatments can make apparently similar rows financially distinct.
The guide to decimal quantity-times-price calculations explains the first calculation stage in detail. Use it to reproduce a particular line, then return to the full set of rows to check missing supplies, duplicated quantities and the document-level sums.
Document the result and its limits
Keep a short reconciliation record with exact supported quantities, rates, rounded net amounts and tax. Mark any source precision or adjustment the current model cannot represent. That makes the final decision about tool suitability visible instead of hiding it behind a matching total.
After correcting an input, reread the description for a stale written measurement. The preview recalculates numeric fields, but text such as “1.38 metres” will not update when quantity becomes 1.375. Conflicting values can confuse the recipient even when the arithmetic is correct.
Finally, download a fresh export after review and compare it with the intended final workspace state. The application’s JSON and line-item CSV do not guarantee that another system accepts the same precision or uses the same rounding sequence. Formal destination rules, tax correctness and delivery validation need separate checks in a workflow that genuinely implements them.
On a long measured-goods invoice, review the quantity column against the measurement record before comparing monetary totals. Transposed digits may still produce a plausible amount. A second pass over the unit column can reveal a copied unit label that the numeric calculation cannot detect. These checks address data quality before a later rounding comparison is asked to explain the wrong problem.