Expose the Minutes Added by Per-Entry Billing Increments — Free
A short task rounded separately several times can add more billed minutes than the same work grouped once. Enter recorded durations, occurrence counts and the increment from your terms to see raw minutes, rounded minutes and the difference.
The proof surface
A realised-rate audit divides money by hours after a project. This register checks the duration layer before rates are applied: per-occurrence ceiling rounding, not pay entitlement, pricing fairness or a revenue target.
Inputentry type | recorded minutes per occurrence | occurrences; billing increment in whole minutes
Rare deviceA realised-rate audit divides money by hours after a project. This register checks the duration layer before rates are applied: per-occurrence ceiling rounding, not pay entitlement, pricing fairness or a revenue target.
Output artifactTotal increment uplift 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: Sprint support | 37 | 2; Proof check | 16 | 3. Billing increment in whole minutes = 15. Total increment uplift: 58 additional billed minutes. All records are invented.
Before using the increment-rounding register
Read the time-entry clause before choosing the increment. “Nearest quarter-hour,” “each commenced quarter-hour” and “round once at the daily total” are different rules. This register models only the second shape: round every entered occurrence upward to a whole increment, then multiply by its count. If your terms use another convention, the result is not a substitute for that convention. Use generic descriptions such as proof check rather than client names or confidential case references. Keeping the raw time next to the uplift helps a provider explain a bill and helps a customer ask a precise question. Neither party needs to accuse the other of an error merely because rounding changed a total; the first question is whether the agreed method matches the calculation.
Why the flat version breaks
Rounding a total when terms round each entry
Ceiling each short occurrence and then adding can differ from ceiling the final total. State the level of rounding explicitly before interpreting the number.
Treating all entries in a category as identical
A count multiplier assumes equal durations. Use separate rows for a 16-minute check and a 23-minute check rather than an average that changes rounding boundaries.
Calling every uplift an overcharge
A difference is arithmetic, not a legal conclusion. The contract, accurate records and applicable rules still determine what may be billed.
How to work the increment-rounding register
Confirm the rounding unit and level
Enter a positive whole-minute increment from the actual agreement. This model rounds each occurrence upward; it does not round to nearest, use banker’s rounding or apply a single rounding step to a whole invoice.
Keep recorded durations separate
Enter the minutes actually recorded for one occurrence and a whole-number count of equivalent occurrences. If durations differ, use separate rows. The tool does not invent timesheets or accept negative credits as recorded work.
Compare raw and billed minutes
Rounded minutes per occurrence equal ceiling of recorded minutes divided by the increment, multiplied by the increment. Uplift is rounded minus recorded, multiplied by occurrences. Row notes retain both totals so grouping effects can be checked.
Resolve terms before applying a rate
A positive uplift receives a review mark, not a fraud label. Confirm entry grouping, any minimum charge and tax treatment with the provider or a qualified accountant. Do not change factual time records to engineer a preferred result.
What the increment-rounding register separates
Question
Before
Inspect this instead
Rounding a total when terms round each entry
Ceiling each short occurrence and then adding can differ from ceiling the final total. State the level of rounding explicitly before interpreting the number.
Keep recorded durations separate
Treating all entries in a category as identical
A count multiplier assumes equal durations. Use separate rows for a 16-minute check and a 23-minute check rather than an average that changes rounding boundaries.
Compare raw and billed minutes
Calling every uplift an overcharge
A difference is arithmetic, not a legal conclusion. The contract, accurate records and applicable rules still determine what may be billed.
Resolve terms before applying a rate
This increment-rounding register 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.
Billing-duration arithmetic only, not legal, accounting, tax or wage-entitlement advice. It models per-occurrence upward rounding and no separate minimum charge; it does not verify a contract or declare an overcharge. Check the signed terms and factual time records with the provider or a qualified accountant before disputing or issuing an invoice.
Data note: The increment-rounding register processes entry type | recorded minutes per occurrence | occurrences 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 bound register page
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the increment-rounding register 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 increment-rounding register 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.
Billing-duration arithmetic only, not legal, accounting, tax or wage-entitlement advice. It models per-occurrence upward rounding and no separate minimum charge; it does not verify a contract or declare an overcharge. Check the signed terms and factual time records with the provider or a qualified accountant before disputing or issuing an invoice.
What this is built on
Method: Rounded minutes per occurrence equal ceiling of recorded minutes divided by the increment, multiplied by the increment. Uplift is rounded minus recorded, multiplied by occurrences. Row notes retain both totals so grouping effects can be checked.
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-09-30, 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: rounded invoice minutes obscured recorded time. After: every occurrence’s raw, rounded and added minutes are shown without deciding what the contract authorizes.
Two 37-minute entries round to 45 minutes each, adding sixteen minutes together. Three 16-minute entries round to thirty minutes each, adding forty-two. The raw total is 122 minutes and the per-entry rounded total is 180, so the increment adds fifty-eight minutes. These sample terms are invented. The register is a way to expose how a specified rounding rule behaves; it does not decide whether rounding each occurrence is what a particular contract allows.
Consolidating the two support occurrences into one 74-minute entry produces seventy-five billed minutes, a one-minute uplift. Consolidating the proof work into forty-eight minutes produces sixty, a twelve-minute uplift. Total uplift becomes thirteen rather than fifty-eight. The comparison illustrates that grouping can change a rounded invoice. It is not permission to combine or split entries opportunistically: the signed terms and honest record of the actual work determine the appropriate grouping.
Entries already at exact fifteen-minute boundaries add no rounding minutes. Two thirty-minute occurrences and three fifteen-minute occurrences total 105 recorded and billed minutes. Zero uplift does not establish that the invoice is otherwise correct; rates, tax, expenses and authorization are not checked. A zero-duration entry is modeled as zero too, because this instrument has no minimum-charge rule. If a provider uses a separate minimum charge, it needs a separate calculation.
Optional AI formatting, never the calculation
Manual entry completes this increment-rounding register 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 increment-rounding register. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are entry type | recorded minutes per occurrence | occurrences; the setting is Billing increment in whole minutes. 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.