Reconcile the creator’s document total by adding the rounded net amounts of its lines, adding their rounded tax amounts and combining those two sums. Review the inputs and intermediate values before investigating the final addition. A document can add up correctly while containing the wrong quantity, price, discount or tax decision.
This check sits at the centre of the invoice amount workflow. The current creator handles ordinary positive invoices with line percentage discounts and manually entered tax information. Its displayed total does not deduct prior payments or implement document-level allowances, withholding or other account adjustments.
Prepare a three-column check record
For each line, record the net amount after the supported discount, the calculated tax and their combined contribution. Use the same row descriptions as the invoice so you can trace each result back to the quantity and price. Avoid starting from only the final document total.
A simple spreadsheet or written review record can help, but ensure its calculation sequence matches the app. The creator rounds quantity times price to cents, rounds the percentage discount to cents, subtracts it and then rounds the supported line tax. A sheet that rounds only at document level can differ.
Keep the source evidence for the inputs. The review record explains the calculation, while the accepted order or approved service record explains why those inputs belong on the invoice. Neither should be mistaken for the other.
Work through a two-line example
Consider a fictional first line with quantity two at 35.00 and a ten-percent discount. The initial amount is 70.00, the reduction is 7.00 and the net is 63.00. At an illustrative twenty-percent rate, tax is 12.60 and the contribution including tax is 75.60.
A second line has quantity one at 25.00, no discount and the same illustrative rate. Its net is 25.00, tax is 5.00 and contribution is 30.00. The document net subtotal is therefore 88.00, tax is 17.60 and the supported total is 105.60.
These rates are arithmetic examples, not tax advice. Establish the correct treatment separately. You can check a fictional example in the creator and compare the live preview with a review record before entering a longer real invoice.
Diagnose a net-subtotal difference
If the net subtotal differs, compare the individual net values first. Check for missing rows, duplicate services, a quantity copied from the full order rather than a partial delivery, or a unit price entered as though it were already the full line amount.
Then inspect discounts. A percentage may have been copied onto an ineligible row, omitted from an eligible row or applied twice because the entered unit price was already reduced. Review the agreed basis rather than changing a value solely to make the subtotal match.
For decimal quantities, inspect the supported precision and initial rounding stage. A source price with more than two decimal places cannot be preserved unchanged in the current model. Record the limitation and use a suitable system if the required basis cannot be represented faithfully.
Diagnose a tax difference
Compare category and rate for every line before comparing only the summed tax. A zero result can come from different treatments, and the creator does not determine which one applies. Confirm the business and tax basis outside the arithmetic review.
Check whether the other calculation rounds tax per line or after grouping amounts. The current app sums rounded line tax. Another method can yield a small difference even with apparently identical rates and net values. Do not automatically label that difference an error in one system without checking the intended rules.
The guide to mixed-rate invoice totals explains how to review different manually determined rates without averaging them. Keep each line’s actual tax contribution visible, and distinguish an arithmetic discrepancy from an unsupported or incorrect tax classification.
Confirm what the total represents
In the current model, the total combines supported net amounts and tax. It is not a reconciled account balance after deposits, credits or payments. Writing “already paid 50.00” in notes does not make the numeric total subtract that amount.
If the agreement requires an unsupported adjustment, complete the invoice in a system that implements it rather than modifying a line price to hide the difference. The source transaction, displayed amounts and amount requested for payment need to agree within the final delivery workflow.
After edits, repeat the relevant line checks and create a fresh export. Earlier downloaded files retain the old values. Keep the final calculation record and source evidence with the invoice, and verify any required formal format rules separately. Application-level field validation, application JSON, line-item CSV and browser printing do not establish standards conformity, tax correctness, recipient acceptance or successful submission.
If the net subtotal matches but the tax does not, keep the net values fixed during investigation. Compare only the category, rate, taxable base and rounding stage first. Changing prices at the same time removes the useful evidence that the commercial amounts already reconciled. A staged comparison is faster to explain and less likely to introduce a second error while repairing the first.