tax-rounding receipt · till receipt with a tear-off foot

Expose Line-versus-Document Tax Rounding with Exact Decimal Workings

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.

1 · Invoice line | whole quantity | pre-tax unit price

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.

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.

Perspective: Before: a cent difference looked like an unexplained rate error. After: two explicit rounding locations and a signed reconciliation difference are visible.

2 · Read the tax-rounding receipt

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.

Paid layer: tax-rounding receipt filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked tax-rounding receipt run in the app
three labeled samples and unlimited article-demo calculations
complete result text and a user-triggered input-state link

What $4 one-time adds

unlimited subsequent tax-rounding receipt app calculations after a local convenience signal
print the tax-rounding receipt with visible assumptions and its safety boundary
CSV of the displayed currency units difference and row workings; conditional estimate uses your manual-retyping minutes
five local reading summaries (headline/count/time), not saved full inputs or cross-device backups

HYPOTHESIS / PROTOTYPE: $4 is a proposed one-time price for filing the tax-rounding receipt, not a current sales offer. No measured time saving or buyer demand is claimed. The optional manual-retyping baseline above estimates one export’s retyping budget only; it does not change the calculation or guarantee savings.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

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.

Boundary and sources

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.

Mechanism: competence-autonomy-loop

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.