The premiums you forget: night, Sunday, public holidays

An employee covers a Sunday because someone is missing. Another finishes a shift at two in the morning three times in a month. On the timesheet, those hours look exactly like any other. Yet they carry a premium, set by your collective agreement, and that premium does not calculate itself from a simple sum of hours.

Why these hours slip through#

A timesheet, whether on paper, in a spreadsheet or on a basic clock-in system, records an arrival time and a departure time. It has no way of knowing, by itself, that a quarter hour worked after ten at night should be treated differently from a quarter hour worked at two in the afternoon.

Catching these hours takes an extra step, done by hand, at payroll time: re-reading every line, remembering the public holiday calendar, checking whether someone really worked a Sunday or whether a Saturday was misread. That step is easy to skip in a busy month, and even easier to skip for an employee who only works nights occasionally.

Catching the hours before running payroll#

Three checks, done before payroll is validated, are enough to stop missing them:

1. Compare every shift against the night window set by your collective agreement. It varies between sectors: read it, don't guess it.
2. Match every worked date against this year's calendar of Sundays and public holidays. A public holiday that falls on a Tuesday moves every year.
3. Note the exact reason for each qualifying hour: night, Sunday, or public holiday. One employee can stack all three in the same month.

A worked example#

Take a hypothesis: a team of fifteen shift workers, three of whom regularly work nights or Sundays. If five hours a month per employee slip past the check, that is fifteen monthly hours left without a premium across the team. At an average premium of 25% on a €13 hourly rate, that is just under €50 missing from payslips every month, unnoticed until the employee counts their own hours.

It is never a deliberate shortcut. It is a manual check that cannot keep up with the number of lines to re-read every month, as explained in calculating overtime from the timesheet.

What changes with an application built for the business#

The schedule already knows who is working a Sunday or a night shift: it planned that team on that post, that day. An application built for the business links that schedule to the timesheet, and calculates the premium the moment the hour is worked, not the moment someone re-reads the whole month.

The manager sees the month's premium hours, with their reason, before validating payroll, instead of reconstructing them by cross-checking three documents. Recording hours on site without a spreadsheet solves the same problem one step earlier, on the data entry side.

Night and Sunday pay premiums: the key takeaways#

A night or Sunday hour is not visible to the eye on a raw timesheet: it takes cross-checking a time, a date and a collective agreement, three times a month per employee concerned. As long as that check stays manual, it will always depend on how busy the month is and on the memory of whoever runs payroll.

The warning sign is not the error itself, rare and quickly fixed once found, but the moment it is found: before payroll, or after, by the employee who counts their own hours better than anyone.