Tables - Overtime Methods

Updated 1 month ago by Oscar Combes

Quinyx offers various calculation methods for overtime and additional time. These are configured under Settings - Tables - Overtime types, and can be customized entirely according to your needs. The overtime types are then added to the agreement template via the Select overtime method drop-down list. This means that different agreement templates may have completely different additional hours and overtime calculations. 

Check which calculation methods  are used in your workplace.

Field

Description

Comment

Name

Optional name for the rule


Salary type

The type of salary to be calculated: overtime, additional hours or minus time


Working time quota

Basis for calculation of salary type: schedule*, nominal hours, fixed schedule hours, base schedule hours**, worked hours, working day model, nominal hours part-time, scheduled hours, overtime hours*

This means when the salary type is to be specified. For example, 1) if the salary type is overtime and time will exceed scheduled hours: 8h as all hours punched on will be paid as overtime 2) If salary type is overtime and time will exceed nominal hours, all punched time over nominal hours will be paid as overtime

Reduce for public holidays

Reduction of working time quota according to the settings in public holidays

For example, if nominal hours for a month amounts to 168 and there is a public holiday during this period, the number of hours is reduced by 8. The result is that nominal hours equals 160 and the employee receives overtime beyond this.

Period

Calculation period, day, week, days, months

Scheduled period is set up in an employment agreement / agreement template. May be 1 month, 1 week, 2 weeks, 1 day, 369 days, etc.

Limit period/limit

The specified salary type is paid only if a specified limit is exceeded.

For example, overtime rule "Time exceeds hours worked per day: 8h" and the limit is 10h. This means that if the employee works 9h, he/she will not receive 1h of overtime; but if the employee works 10h, he/she will receive 2h overtime.

Include in subsequent

An indicator of overtime hours generated from the selected method must be included in subsequent methods. Essentially, this determines whether the employee should be paid several times for the same overtime.

For example, overtime rules: Time exceeds hours worked per day: 8 hours, Time exceeds hours worked per week: 40 hours. If an employee worked over a day (9 hours) and over an entire week 42 hours, and if this setting is unchecked, he/she will receive 1 h per day and 1 h of weekly overtime. If this setting is checked, he/she will receive 1 h per day and 2 h of weekly overtime.

Overtime levels

Value types to be used for various overtime levels: Overtime schedule, Hours worked, Overtime hours

The overtime schedule is the overtime map compiled in the agreement template or Settings → Overtime. Hours worked and overtime hours can be set directly here and can be defined according to the number of hours and type of overtime to be given.

*  Difference between overtime methods besides Schedule and Scheduled hours per day under the Working time quota option. 

Schedule is if you work outside your scheduled times. If overtime generates time off in lieu, Webpunch can log leave if the employee arrives late, minus time off in lieu, and then plus time off in lieu if the employee stays for longer.

Scheduled hours is that you have to work more than the number of scheduled hours in the day in total. Beyond scheduled hours may be viewed a little more along the lines of flexible working hours. It is fine to arrive late, does not need to be tracked, plus time off in lieu is only triggered after all hours in my scheduled shift have been logged.

** If the scheduled hours in Schedule aren’t matching the number of scheduled hours there were in the base schedule at the very moment the last rollout took place, then overtime will be generated. This is reflected in the worked-rollout metric. This means that:

  • If you change the base schedule and you want that to be used for the basis of overtime calculation, then you need to re-rollout the base schedule across the same period in Schedule. See https://quinyx.helpdocs.io/l/en/article/mwraoqxbyp-re-rollout-logic for more details on re-rolling out base schedules.
  • If you add a shift to a date in Schedule over which a base schedule has been rolled out, this will generate overtime.
  • If you want to replace a shift originating from Base schedule with an ad-hoc shift in Schedule and you want that new ad-hoc shift to generate overtime, then you need to 1) delete the shift in question in base schedule, 2) re-rollout the base schedule, which will in turn null the rolled out hours metric for that day and employee and 3) proceed to adding the ad-hoc shift in Schedule.


How Did We Do?