Expose Line-versus-Document Tax Rounding with Exact Decimal Workings — Free
A one-cent invoice difference may come from where tax is rounded, not a wrong rate. Compare line-level and document-level rounding explicitly before escalating a reconciliation question to the billing team.
The proof surface
Time-increment tools expose billed-minute rounding. This receipt uses exact decimal cents and a supplied percentage to compare two monetary rounding locations. It preserves fractional-cent workings without declaring either convention legally correct.
InputInvoice line | whole quantity | pre-tax unit price; illustrative common tax rate (%)
Rare deviceTime-increment tools expose billed-minute rounding. This receipt uses exact decimal cents and a supplied percentage to compare two monetary rounding locations. It preserves fractional-cent workings without declaring either convention legally correct.
Output artifactLine-rounded tax minus document-rounded tax with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Blue rivet | 1 | 0.06; Red rivet | 1 | 0.06. Illustrative common tax rate (%) = 8.25. Line-rounded tax minus document-rounded tax: -0.01 currency units difference. All records are invented.
Before using the tax-rounding receipt
This restricted model uses one currency with two decimal minor units, whole quantities, unit prices with at most two decimal places, one common non-negative rate and round-half-up to cents. It has no mixed tax rates, exemptions, inclusive-tax extraction, discounts or shipping adjustments. Copy pre-tax unit prices from the source and isolate a compatible group of invoice lines. Exact scaled integers prevent binary floating-point representations of values such as 0.07 from deciding a cent boundary. The sign convention is line-rounded tax sum minus tax rounded once on the full subtotal. A positive difference means the first convention produces more tax; it does not prove the invoice overcharged anyone or identify the applicable legal method.
Why the flat version breaks
Using ordinary binary arithmetic at the cent boundary
Fractional binary approximations can change a naive rounding result for a value that should lie exactly at half a cent. This calculator represents prices as integer cents and rates as scaled decimal integers, then applies an explicit half-up rule. It does not leave the convention to a browser's incidental floating-point result.
Mixing rates or inclusive prices
An invoice can contain several rates, exempt lines and tax-inclusive prices. One rate on pre-tax prices cannot reproduce that structure. Restrict the run to compatible lines and get adjusted source amounts; otherwise a calculated difference may be entirely unrelated to rounding location.
Calling any positive difference an unlawful charge
Both conventions can differ by a cent without establishing which one is required. The source law, contract and billing policy are not inputs here. Treat the result as a precise reconciliation question with a declared model, not as evidence of fraud, a tax filing answer or an automatic refund amount.
How to work the tax-rounding receipt
Identify the invoice's actual convention
Ask whether the billing system rounds tax per line, per tax group or once per document. Confirm currency precision and whether prices are genuinely pre-tax. If a discount is applied before tax, obtain the adjusted taxable amount from the source; do not drop the discount and expect this restricted calculation to reproduce the invoice.
Enter a compatible line group
Use whole quantities and plain unit prices with zero, one or two decimal places. Separate groups with different tax rates into different runs. A single anonymous line label is sufficient; customer data and invoice account numbers need not appear. Negative credit lines are outside this non-negative model and require a separate reviewed reconciliation.
Round exact tax at both locations
Multiply quantity by exact price cents for each line. Multiply the subtotal by the supplied rate, retaining the fractional-cent numerator; round half-up to whole cents for line tax. Add those rounded amounts. Independently add pre-tax subtotals first and round their combined tax once. Subtract the second total from the first and retain both totals in the receipt.
Explain the difference before disputing it
Give the invoice team the rate, compatible line set, sign convention and two totals. Ask which rounding rule the invoice actually uses and whether other adjustments were omitted. A qualified accountant or tax professional can confirm the jurisdiction-specific rule. Do not replace the source tax calculation with this model without that confirmation.
What the tax-rounding receipt separates
Question
Before
Inspect this instead
Using ordinary binary arithmetic at the cent boundary
Fractional binary approximations can change a naive rounding result for a value that should lie exactly at half a cent. This calculator represents prices as integer cents and rates as scaled decimal integers, then applies an explicit half-up rule. It does not leave the convention to a browser's incidental floating-point result.
Enter a compatible line group
Mixing rates or inclusive prices
An invoice can contain several rates, exempt lines and tax-inclusive prices. One rate on pre-tax prices cannot reproduce that structure. Restrict the run to compatible lines and get adjusted source amounts; otherwise a calculated difference may be entirely unrelated to rounding location.
Round exact tax at both locations
Calling any positive difference an unlawful charge
Both conventions can differ by a cent without establishing which one is required. The source law, contract and billing policy are not inputs here. Treat the result as a precise reconciliation question with a declared model, not as evidence of fraud, a tax filing answer or an automatic refund amount.
Explain the difference before disputing it
This tax-rounding receipt replaces a manual count or calculation, not source verification or the responsible person’s review.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Restricted invoice arithmetic only, not tax or legal advice. Ask the billing team and a qualified accountant or tax professional to confirm taxability, adjustments and the required rounding convention before changing an invoice or filing a claim.
Data note: The tax-rounding receipt processes Invoice line | whole quantity | pre-tax unit price locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.
Go deeper: the companion app files the same reading as a till receipt with a tear-off foot
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the tax-rounding receipt reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
The tax-rounding receipt answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.
Restricted invoice arithmetic only, not tax or legal advice. Ask the billing team and a qualified accountant or tax professional to confirm taxability, adjustments and the required rounding convention before changing an invoice or filing a claim.
What this is built on
Method: Multiply quantity by exact price cents for each line. Multiply the subtotal by the supplied rate, retaining the fractional-cent numerator; round half-up to whole cents for line tax. Add those rounded amounts. Independently add pre-tax subtotals first and round their combined tax once. Subtract the second total from the first and retain both totals in the receipt.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.
Before: a cent difference looked like an unexplained rate error. After: two explicit rounding locations and a signed reconciliation difference are visible.
Three worked readings, with different inputs
Sample A — typical inputs
Blue rivet | 1 | 0.06
Red rivet | 1 | 0.06
Setting: Illustrative common tax rate (%) = 8.25. Expected summary: -0.01 currency units difference.
Each six-cent line has unrounded tax of 0.00495 at the supplied 8.25%. Half-up rounding to cents produces zero on each line, while tax on the combined twelve-cent subtotal is 0.0099, rounded to 0.01. Line-tax sum minus document-rounded tax is therefore -0.01. These small prices deliberately expose a rounding boundary; they are invented purchases, not a claim about an actual tax schedule.
Sample B — changed plan
Green rivet | 1 | 0.07
Amber rivet | 1 | 0.07
White rivet | 1 | 0.07
Setting: Illustrative common tax rate (%) = 8.25. Expected summary: 0.01 currency units difference.
Tax on each seven-cent line is 0.005775, rounded half-up to one cent. Three lines produce 0.03 total line tax. The twenty-one-cent subtotal yields 0.017325 tax, rounded to 0.02. The difference is +0.01. Opposite signs are possible under the same rate because fractional-cent remainders, not a blanket overcharge rule, determine the result.
Sample C — boundary convention
Gate batch | 2 | 5.00
Setting: Illustrative common tax rate (%) = 8.25. Expected summary: 0 currency units difference.
Two units at 5.00 create a 10.00 line subtotal. At 8.25%, tax is 0.825 and the declared half-up convention produces 0.83. There is only one line, so line and document rounding agree and the difference is zero. This does not verify taxability, discount handling or the legally required rounding convention; it checks only the explicitly modeled arithmetic.
Optional AI formatting, never the calculation
Manual entry completes this tax-rounding receipt for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a tax-rounding receipt. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Invoice line | whole quantity | pre-tax unit price; the setting is Illustrative common tax rate (%). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.