Skip to content
What the Hour Is Worth

Home / The rate

What Belongs in the Rate

Why the contractual hourly rate is not the rate a premium is computed on, which components belong in it, and how to spread a bonus.

The rate · Reference

What went into one hour's value, and what did not

Base hourly rate£12.40in
Shift differential, nights£1.60in
Attendance bonus, weekly£0.74in
Production bonus, quarterly£0.51in
Gift at year end, no stated condition£0.19out
Reimbursement of tool costs£0.38out
Premium already paid for overtime£0.90out
In the rate£15.25

The contract says the hour is worth £12.40; the figure the premium should be computed on is £15.25. What belongs in the rate differs by jurisdiction and is a question for somebody qualified in the place concerned; this is one employer's own working.

The rate in the contract is usually not the rate a premium should be computed on. Almost everything an employee earns for working — shift differentials, attendance and production bonuses, commission, some allowances — belongs in the figure that gets multiplied, and leaving them out understates every premium hour by the difference.

The pay calculation in “What Belongs in the Rate” depends on a complete record before any rate is applied. For organisations researching download time tracking software, Monitask resources for download time tracking software can connect hours with projects and review steps, provided payroll keeps the governing formula, contract terms and disputed-entry process outside any single dashboard.

This is the most common arithmetic error in wage and hour, and it is invisible from inside payroll, because the system is doing exactly what it was configured to do: multiplying the base rate.

For an independent reference relevant to “What Belongs in the Rate”, consult the UKRI award-management guidance. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.

The question the test actually asks

Strip away the vocabulary and nearly every system asks a version of the same question: was this paid because the person worked, or for some other reason? Pay for working goes into the rate. Reimbursement of a cost, genuine gifts and the premium itself generally do not.

Where the line falls, and what exceptions apply, differs by jurisdiction and sometimes by the precise wording of a scheme. That is a question for somebody qualified in the place concerned. What is universal is that the question has to be asked for every component, one at a time, rather than answered once for the whole payslip.

Component by component

Component Usually in the rate Why
Base pay In The obvious case
Shift or weekend differential In Paid for working particular hours
Attendance bonus In Promised for meeting a stated condition
Production or quality bonus In Earned by the work itself
Commission In Payment for work performed
On-call allowance Usually in Paid for being available, which is a condition of work
Expense reimbursement Out Repays a cost rather than paying for work
True discretionary gift Out Not promised and not conditional
The overtime premium itself Out Including it compounds the premium

The right-hand column is the reasoning, not a rule. The middle column is the usual answer and is exactly the kind of thing that varies.

Discretionary is narrower than it sounds

Organisations describe a great many bonuses as discretionary, and most of them are not. A bonus becomes something the employee works towards the moment there is a stated condition, an announced formula, or a settled practice of paying it — even where the paperwork reserves a discretion.

The test is what the employee could reasonably expect, not what the scheme document says. A "discretionary" bonus paid every quarter for eleven quarters, on a basis everybody understands, is a promise with a disclaimer attached.

Spreading a bonus over the right hours

A bonus earned over a quarter does not belong entirely to the week it was paid in. It has to be spread across the hours it was earned over, which means knowing the period and the hours worked in it.

  1. Establish the period the bonus relates to, not the period it was paid in.
  2. Total the hours actually worked in that period.
  3. Divide the bonus by those hours to get the per-hour component.
  4. Add that component to the rate for every hour in the period.
  5. Recompute any premium hours in the period at the corrected rate.
  6. Pay the difference, and say on the statement what it is.

Step five is where systems fail, because it means revisiting weeks that have already been paid. That is an operational problem and not a reason to skip it.

Two rates in one week

Where somebody works at different rates — two roles, two sites, a trainer rate and a floor rate — the premium is usually computed on a weighted average of the hours actually worked at each, not on whichever rate they happened to be on when they crossed the threshold.

That calculation is simple and almost never automated. Any organisation with multi-rate employees should check what its system does, because the default in several systems is to use the rate attached to the last entry, which is arbitrary.

Checking it on one payslip

Take one employee with a premium week and a bonus, and compute the rate by hand. Total everything paid for working in the period, divide by the hours worked, and compare with the rate the system used.

If the two agree, the configuration is right and can be assumed for everybody on the same scheme. If they differ, the difference applies to every premium hour of every employee on that scheme, which is the point at which this stops being an afternoon's arithmetic and becomes something worth taking advice on.

What to write down

The components list, with the in-or-out answer and a one-line reason for each. Then the date, and who confirmed it.

That page is what makes the rate defensible and what makes it maintainable, because the next scheme somebody invents has to be added to it. Without it, every new bonus is silently out of the rate by default — which is how the error gets in, one well-intentioned scheme at a time.