Overtime Calculator

How the pay adds up

Total = regular hours × base rate + overtime hours × (base rate × multiplier), plus the second tier's hours × (base rate × its multiplier) when used. The reference week — 40 hours at 20 with 10 overtime hours at 1.5× — splits into 800 regular pay and 300 overtime pay for a 1,100 total across 50 hours, every figure computed at build time by the same engine behind the form.

Nothing on this page is a stored result: each number is produced when the page is built by calling that engine on labelled example inputs, so the copy cannot drift from the code. A companion guide, salary conversions and overtime pay, runs the same engine beside the salary converter and works through how a per-period total behaves once annualized; the rest of this page stays with the overtime arithmetic itself.

What the result shows, line by line

The form returns the pieces, not only the final figure, because the pieces are where a pay question is usually settled. Regular pay is regular hours × base rate — 800 for the reference week. The overtime rate is the base rate scaled by the multiplier: 20 × 1.5 = 30 an hour. Overtime pay is the overtime hours at that rate, 300. Total hours is the plain sum of every hour entered, 50, and total pay is the sum of the money blocks, 1,100. When a second tier is used, two further lines appear — the second-tier rate and its pay — and both fold into the same totals. Reading the breakdown rather than the single total is what lets you check a figure: if the overtime rate shown is not your base rate times your multiplier, the inputs are wrong, not the arithmetic.

The multiplier is a rate on hours, not a surcharge on the bill

The most common misreading is to treat the multiplier as something applied to the whole period — as if a 1.5× week meant half again as much pay overall. It does not. The multiplier reaches only the overtime hours, and only through the rate they are paid at. Hold the reference week's hours fixed and pay those same 10 overtime hours at the plain base rate — a multiplier of 1 — and they are worth 200; at 1.5× they are worth 300. The gap between those two figures is the entire effect of the premium, and it falls on the overtime hours alone. Across the whole week the straight-time run totals 1,000 and the 1.5× run 1,100; the one line that moved is the overtime pay, not the week. The 800 of regular pay is identical in both cases, because the multiplier never touches the regular hours. Read overtime as a higher price on particular hours, not as a bonus layered over the total.

The same logic answers a question that trips people up when a multiplier looks unusual: nothing special happens at 1.5 or 2. The engine multiplies, and a 1.25× premium or a 3× premium runs through exactly the arithmetic above with a different factor. The conventional values are common because people choose them, not because the calculator privileges them.

Fractional hours, and the figures that carry extra decimals

Hours and rates need not be whole. A part-time reference — 37.5 regular hours at 18.5 an hour with 6.25 overtime hours at 1.5× — gives an overtime rate of 27.75 an hour and a 867.19 gross total. Fractional inputs often produce a result with more decimal places than money uses, and the engine does not hide them: it keeps full precision while computing and rounds only for display, to at most six decimal places. The overtime pay in that part-time week is 173.4375 to six places — which you would round to 173.44 as a money figure yourself. Doing the rounding last, on the final number rather than between steps, is the discipline the methodology page documents for every Sumvia tool. The displayed value is a clean presentation of a more precise figure held underneath.

No overtime, and more than one premium

Overtime hours of zero are allowed, and the result is simply the regular pay: 40 hours at 20 with no overtime returns 800 across 40 hours, the overtime line sitting at 0. That makes the tool usable as a plain regular-pay check as readily as an overtime one.

At the other end, some arrangements pay more than one premium — a standard overtime rate, then a higher one past a further point, such as double time. The optional second tier handles this as an independent block: its hours at the base rate scaled by its own multiplier. Adding 4 hours at 2× to the reference week introduces a second-tier rate of 40 an hour — exactly twice the 20 base, not twice the 30 overtime rate — contributing 160 and lifting the total to 1,260 across 54 hours. The tiers do not compound on one another; each is computed from the base rate and then summed. Leave the tier blank and a single overtime rate covers the whole overtime block.

Two weeks, worked end to end

It helps to see both examples carried all the way through. A standard week: 40 regular hours at 20 an hour is 800; 10 overtime hours at the 1.5× rate of 30 an hour is 300; the two add to 1,100 gross across 50 hours. A heavier week keeps those same first two blocks and adds a third: 4 hours at a 2× rate of 40 an hour, worth 160, so the gross rises to 1,260 across 54 hours. Every figure in both runs comes from the engine at build time; if a future change to the engine made any of them wrong, the page would fail to build rather than publish a number the code no longer produces. That is the point of computing the examples instead of typing them — the worked copy and the live calculator can never quietly disagree.

When the engine returns an error instead of a number

The same engine that produces these figures also refuses the ones it cannot answer honestly, and it says so in words rather than showing a stray NaN or a silent zero. Each input is validated before any arithmetic runs: the base rate has to be a real, positive number — a shift of hours at nothing per hour is not a calculation the tool will pretend to make — and hours and multipliers must be finite and non-negative, inside the documented working range that the methodology page sets out. A second tier is checked as a unit: give it hours and it will insist on a multiplier to go with them, because half a definition cannot produce a rate. When any check fails, the result area shows the specific reason, and no number is published. This matters more than it sounds. A calculator that answers every input, including the meaningless ones, teaches you to trust whatever it prints; one that declines the impossible cases is telling you where the edges of the method are. The breakdown and the refusal are two halves of the same contract — show the working when there is a sound answer, and name the problem when there is not.

That contract is also why the worked examples above can be trusted as a demonstration rather than decoration. Each example is one of these validated calls, run at build time; an input that the live form would reject would equally fail the build, so the figures on the page are only ever ones the engine genuinely produces. There is no separate, hand-written set of numbers that could quietly fall out of step with what the tool does when you use it.

Convention, not counsel

The 1.5× prefill is a convention, not a verdict. The engine treats the multiplier as ordinary arithmetic, so the field is editable precisely because overtime premiums are set by contract, agreement, or local rule, and those differ. Which hours count as overtime in the first place is a classification this page does not make: count the regular and overtime hours under the rules that govern your work, and the tool does the multiplication on the hours you give it. For the hours themselves, the time card calculator totals a week of in-and-out times; to see what an hourly figure comes to across pay periods, the salary calculator converts it, and the salary-and-overtime guide connects the two. The full set of business-math tools and guides is listed on the guides hub.

Frequently asked questions

Hours and rates are processed in your browser and go nowhere else. Figures are gross pay under the multipliers you chose — not a determination of overtime eligibility, which depends on law and contract. See the methodology page for engine details.