Statutory Bonus

How is it different from a performance bonus?

In almost every respect except the word. A performance bonus is something the employer designs: who qualifies, how much, on what measure, and whether to pay it at all in a difficult year. A statutory bonus is none of those things. Eligibility, the basis of computation and the limits are set externally, the employer's discretion is largely confined to how it administers the payment, and a poor year does not remove the obligation in the way it can close a discretionary scheme. Naming both bonus in internal documents is the source of a great deal of confusion in offer conversations and in exit disputes.

Why does it behave like a liability rather than a payroll line?

Because it accrues through a period and settles afterwards. Between those two moments the organisation owes something it has not yet paid, and unless somebody carries that forward deliberately it appears nowhere: not in the monthly payroll cost, not in the manager's view of team cost, and not in the plan for the year. Finance teams that build headcount budgets from payroll registers alone therefore understate the position, and discover the shortfall when the payment falls due rather than when the obligation was being incurred. Carrying the accrual explicitly is unglamorous and removes an entire category of surprise.

What makes eligibility harder than it looks?

The edges. A full-year employee at a modest salary is straightforward; the difficulty is everybody else. Joiners and leavers part-way through the period, people who crossed a threshold mid-year, employees on extended leave, those who moved between entities in a group, and workers engaged through a contractor all raise questions the payroll configuration was never asked. Each has an answer, but the answer depends on facts and on current rules rather than on precedent inside the company, and the habit of resolving them from what was done last time is how a defensible position quietly becomes an inherited assumption.

Why does the accounting year, not the pay cycle, drive it?

Because the entitlement is measured over a period of employment and the employer's position, not over a month of work. That makes the calculation retrospective: you cannot finalise it until the period has closed and the underlying records are settled. Anything that changes during the period, such as a revision to salary, a promotion or a spell of unpaid leave, feeds into a figure that only becomes computable at the end.

The consequence for planning is that the work arrives in a lump alongside the year-end close, when the same people are busiest. Organisations that treat it as a payroll task in that window tend to compress the review and accept whatever the system produces. Sequencing it as its own exercise, with the eligibility list produced and challenged before the computation is run, is the difference between a checked number and a plausible one.

What goes wrong when it is folded into cost to company?

Presenting the payment as a component of a candidate's package makes an externally-fixed entitlement look like a negotiated element of pay, and candidates read it as one. The immediate effect is a conversation at offer stage about whether it can be traded for something else, which it generally cannot be in the way the candidate is imagining. The later effect is a dispute at exit about what was owed and on what basis.

The cleaner practice is to describe the fixed and variable elements the employer actually controls in the package, and to describe the statutory entitlement separately as what it is. That costs nothing and removes an ambiguity that surfaces at exactly the two moments where trust matters most. See cost to company for why bundling everything into a single headline figure creates this class of problem generally.

Who is left out of the calculation, and how?

People who are not in the payroll register the calculation is run from. Workers engaged through a contractor, employees of a group company sitting on someone else's payroll, and staff added mid-period through an acquisition are the recurring examples. In each case the omission is structural rather than careless: the run was drawn from a source that never contained them, so no reconciliation inside payroll can reveal the gap.

The check that catches it is external to payroll. Compare the eligibility list against headcount from a different source, such as the access system, the attendance record or the finance ledger, and investigate every name that appears in one and not the other. Differences are usually explainable, and the point of the exercise is to explain them deliberately rather than to discover at a later date that nobody ever looked.

Where should the eligibility limits and the rate come from?

From a qualified advisor or the relevant authority. The wage limit that determines who is eligible, the ceiling used in the computation, the minimum and maximum proportions payable, the qualifying period of service and the window for payment are all prescribed, are revised from time to time, and interact with the type of establishment. This entry states none of them, because the failure mode here is not ignorance but a confidently wrong inherited figure.

The operational form of that advice is a dated note: what was confirmed, by whom, and when. Re-confirm before each computation rather than assuming last period's parameters carried forward, and re-confirm immediately after any change in the establishment's structure or workforce composition. A parameter that was right once and is wrong now produces an underpayment that is discovered by an employee, which is the most expensive way to find out.