When the Premium Starts
The thresholds a premium attaches to, why the period it is measured over matters more than the number, and hours that count without being worked.
A premium attaches to a threshold, and the threshold has two parts that get confused: the number of hours and the period they are measured over. Getting the number right and the period wrong produces an answer that is plausible, consistent and incorrect — which is the hardest kind of error to find.
The pay calculation in “When the Premium Starts” depends on a complete record before any rate is applied. For organisations researching how to detect mouse jigglers, learn more on this page can connect hours with projects and review steps, provided payroll keeps the governing formula, contract terms and disputed-entry process outside any single dashboard.
The common failure is applying a weekly threshold to a pay period. In a fortnightly cycle, a week of forty-six hours followed by a week of thirty-four produces premium hours under a weekly measure and none at all under a fortnightly one.
For an independent reference relevant to “When the Premium Starts”, consult the Canada Revenue Agency payroll guidance. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.
The thresholds that exist
| Threshold | Measured over | Typical effect |
|---|---|---|
| Hours in a week | One workweek | The most common |
| Hours in a day | A single day | Sits alongside a weekly one, not instead |
| Consecutive days worked | A run of days | Attaches to the day, not the hours |
| Hours at particular times | Nights, weekends | Usually a differential, not a premium |
| Contractual thresholds | Whatever the agreement says | Can be lower than any statutory one |
Which of these apply where you operate, and how they interact when more than one is triggered, differs by jurisdiction and by agreement. It is a question for somebody qualified in the place concerned, and the answer is worth getting as a written statement rather than as a conversation.
The contractual threshold nobody told payroll about
A collective agreement or a contract may set a lower threshold than any general rule — a premium after thirty-seven and a half hours, say, rather than forty.
These are agreed by people who do not configure payroll, and the system continues to apply its default. The resulting shortfall is systematic, applies to everybody covered by the agreement, and is invisible because every payslip is internally consistent.
Hours that count without being worked
Some systems count certain non-working hours towards the threshold — paid leave, public holidays, sick pay, standby — and others do not. Whether yours does is a configuration setting and a question of rule.
The practical risk is the mismatch: an agreement that says holiday counts towards the threshold, and a system configured so that it does not. That mismatch produces a shortfall in exactly the weeks people are most likely to look at their payslips.
Testing the threshold
- Build a week of exactly the threshold number of hours and confirm no premium.
- Build a week one hour over and confirm a premium on one hour only.
- Build a fortnight of a heavy week and a light week, and confirm the premium survives.
- Build a week containing a day of paid leave and see whether it counts.
- Build a week that crosses a month end and confirm nothing changes.
- Record all five results with the date and the system version.
Step three is the one that fails. It takes ten minutes and it is the single most valuable test in this whole area, because it catches the error that is most common and least visible.
Daily and weekly together
Where both a daily and a weekly threshold apply, hours can qualify under both, and the rule for what happens then — usually that an hour is not counted twice — has to be configured rather than assumed.
Systems handle this with varying competence. The test is a week containing one very long day and a modest total: the daily premium should appear and the weekly one should not, and those hours should not be double-counted into anything else.
Announcing a threshold change
Where a threshold changes, by agreement or by rule, the change has a date and the date matters. Applying it from the start of the pay period rather than from the start of the workweek creates a short window where the wrong threshold applied.
When a threshold changes, apply it from the start of a workweek, not from the start of a pay period, and say in writing which week is the first. A change applied mid-week produces a week that was measured two ways.
The threshold on one page
The threshold, the period, what counts towards it, where the rule comes from, and the date of the last review. Five lines, alongside the week definition.
Organisations that keep this page find the questions in this section easy and the ones that do not find them impossible, because the information exists only as a configuration setting that nobody can interpret without the context the page would have held.