Check a mixed-rate invoice by reviewing each line’s determined tax category and rate, calculating its tax on the supported discounted net amount and summing the rounded contributions. Do not average the rates and apply that average to the whole subtotal. A blended percentage can conceal which amounts belong to which treatment.
The invoice amount workflow separates tax determination from arithmetic. The current creator lets you enter tax information manually per line and sums rounded line tax. It does not decide the treatment, calculate a formal profile’s tax-category breakdown or guarantee that the resulting representation meets a recipient’s requirements.
Confirm the treatment before calculating
Start with the transaction facts and the appropriate current requirements. Similar products can have different circumstances, and different products can sometimes share a treatment. Do not derive a tax decision merely from the wording of the description or the country selected in the app.
Keep the basis for the category and rate with your business records. If qualified advice or an official determination is necessary, obtain it outside the creator. A supported percentage and a completed reason field are not evidence that the treatment is legally correct.
Ensure the line structure can express the distinctions. One current row has one category and rate. If a combined line contains amounts requiring different treatments, resolve the commercial allocation and structure in a suitable way before calculating tax.
Build a worked arithmetic comparison
For illustration only, suppose one line has net 80.00 and a manually determined rate of twenty percent. Its tax is 16.00. Another has net 50.00 and an illustrative ten-percent rate, producing 5.00. The net subtotal is 130.00, summed tax is 21.00 and the supported total is 151.00.
Those rates are fictional arithmetic inputs, not a recommendation for any product or country. The useful point is that each rate applies to its own net amount. A simple average of fifteen percent on 130.00 would produce 19.50, which does not reproduce the line calculations.
If a further line has zero tax, keep its category and basis visible in the review. A zero-rated, exempt or outside-scope line is not interchangeable simply because its tax contribution is zero. The app’s manual categories and reasons do not determine the underlying legal distinction.
Check discounts before tax
The creator calculates supported line tax after the rounded percentage discount has reduced that line’s net amount. If a discount is omitted or copied onto an ineligible row, the tax sum may differ even when the entered rates match another calculation.
Review each row’s initial amount, rounded discount and net value before comparing tax. A final-tax discrepancy can originate in a commercial adjustment rather than in the rate itself. Keep those stages separate in the reconciliation record.
The app does not implement document-level allowance allocation across different tax categories. If the transaction requires that structure, do not assign the adjustment arbitrarily to one row. Use a model that supports the appropriate calculation and required destination fields.
Compare rounding methods explicitly
The current calculation rounds tax per line and sums those rounded values. Another system may calculate grouped tax amounts under its own applicable rules. Even if the visible net subtotal and rates match, the stage of rounding can create a small difference.
The guide to per-line rounding gives reproducible small examples. When comparing a real invoice, use the exact rows and inputs rather than assuming every discrepancy follows the example. Identify the first intermediate amount that differs.
Do not change a rate to remove a cent difference. That changes the stated treatment instead of resolving the calculation policy. Likewise, a free-text rounding note does not create a supported rounding adjustment or formal tax-breakdown structure in the current model.
Review the final representation
Compare the preview with your line-level review record. Check that every row’s category, rate and reason corresponds to its actual supply, and that the summed tax equals the sum of the supported rounded line contributions. Then confirm the combined net-plus-tax amount.
If the destination requires tax subtotals, exemption codes, accounting-currency tax amounts or other structured fields, verify them in a system that implements those requirements. The current application’s field checks and exports do not establish that formal model.
After any edit, recalculate and create a fresh export. Keep the final version distinguishable from earlier drafts and preserve the evidence for both treatment and arithmetic. A balanced mixed-rate preview is useful for preparation, but it does not guarantee tax compliance, recipient acceptance, authority submission or delivery through a structured-invoice network. Complete any required formal validation and transmission in the appropriate verified workflow.
For the worked example, a quick independent check is 16.00 plus 5.00 equals 21.00, followed by 130.00 plus 21.00 equals 151.00. Keep these two additions separate from the rate calculation. If the additions reconcile but the expected tax differs, investigate the treatment, taxable bases and rounding rather than repeatedly adjusting the final total without identifying its source.