Bonuses That Are Not Discretionary
Why most bonuses called discretionary are not, the three things that make one count towards the rate, and how a settled practice outlives the wording.
Six payments one employer called discretionary, read against what it actually did
Four of the six went into the rate once the question was asked properly; the scheme documents call all six discretionary. What makes a payment discretionary differs by jurisdiction and is a question for somebody qualified in the place concerned.
Most bonuses described as discretionary are not, and the word in the scheme document does not decide it. What decides it is whether the employee could expect the payment: whether there was a condition, a formula, an announcement, or simply a long enough run of paying it the same way.
The pay calculation in “Bonuses That Are Not Discretionary” depends on a complete record before any rate is applied. For organisations researching self report bias, this product overview 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 matters because a bonus that counts raises the rate used for every premium hour in the period it was earned over. Getting the classification wrong is not an error about one payment; it is an error about every premium hour of everybody on that scheme.
For an independent reference relevant to “Bonuses That Are Not Discretionary”, consult the ICAEW audit resources. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.
The three things that make a bonus count
A stated condition. "Paid if attendance exceeds a threshold" is a promise with a test attached, whatever else the document says.
A known formula. If the employee can compute the payment, or could if they had the numbers, there is nothing discretionary about the amount.
A settled practice. Paying the same bonus, on the same basis, for long enough that everybody expects it, creates the expectation regardless of what was reserved in writing.
What genuinely discretionary looks like
Narrow. No announcement in advance, no condition, no formula, no pattern, and a real decision each time about both whether to pay and how much.
- Nobody was told it might be paid.
- The amount was decided after the period, on no stated basis.
- It is not the same each time, and the variation is not explained by anything measurable.
- Not paying it would surprise nobody.
The last is the practical test. If skipping the payment would produce a wave of questions, it was expected, and something that is expected is not discretionary in substance.
The reserved-discretion clause
Scheme documents routinely say the bonus is discretionary, that the employer may withdraw it at any time, and that past payment creates no entitlement. Those clauses are not worthless and they are not decisive.
An employer that has paid the same bonus on the same basis for three years has behaved in a way the clause denies, and behaviour is what gets looked at. Whether the clause survives that differs by jurisdiction and is a question for somebody qualified in the place concerned.
Spreading it correctly
Once a bonus counts, it belongs to the period it was earned over, not the week it was paid in.
- Identify the period the bonus relates to.
- Total the hours actually worked in that period.
- Divide to get the per-hour component.
- Add it to the rate for each week in the period.
- Recompute premium hours in those weeks.
- Pay the difference, and label it on the statement.
Step five is the one that gets skipped, because it means reopening weeks that are closed. That is an operational objection to a correct calculation, not a reason to do a different one.
Where the error enters
Almost always at the point a new scheme is invented. Somebody in operations designs an incentive, it is announced, it starts paying — and nobody tells payroll it needs to go into the rate, because nobody in the conversation knew that was a thing.
The fix is procedural and cheap: any new payment to employees gets one question asked of it before the first payment, by somebody who knows to ask. Is this paid for working, and does it belong in the rate?
Reviewing what you already have
List every payment made to employees in the last year, by type. For each one, answer the question above and record the answer with a reason.
Most organisations find between one and four payments that should have been in the rate and were not. That is a finding with a quantity attached, and what to do about the past is the subject of its own section on this site.
Bonuses paid after somebody leaves
A bonus relating to a period somebody worked, paid after they have gone, raises the same questions and one more: the premium correction has to reach a final payment that has already been made.
That is awkward and it is not a reason to skip it. The practical answer is to compute the correction at the point the bonus is decided rather than at the point it is paid, so it goes out with the payment rather than as a second afterthought that nobody initiates.
Writing it down
A single table: payment type, in or out, reason, date decided, who decided. It goes stale the moment somebody invents a new scheme, which is why the procedural step above matters more than the table.
But the table is what makes the next person's job possible. Without it, every payroll manager rediscovers the whole question from scratch, and the ones who do not rediscover it carry on getting it wrong.