The service uses several different types of events. Below is a list of the most commonly used event types.
The types of events that are appropriate for your business model have been selected for your community. Remember to use different types of events according to the principles agreed in your community. The functionalities of the event types may vary from community to community because the functionalities are customizable.
Types of work events
Work (1)
The Work event type increases the number of working hours between the start time and the end time of the entry.
Regular working time is earned up to the daily work obligation, if the daily work obligation is defined. The excess part accumulates either balance or overtime. Days shorter than the obligation automatically reduce the working time balance if balance calculation is used.
Accumulated working hours can be limited by working time limits. The automatically reduced unpaid food hour reduces the working hours in accordance with the set.
Remote work (84)
Behaves like the Work event type except for the fach thet the only overtime option for Remote work event type is hour to hour work. It is possible to change overtime target default for Remote work by defining exceptional overtime pay target default on work community / setting group level. This value will be then used as a default when creating new Remote work event.
If Remote work event type with multiple overtime options is needed, it can be created on working community level by adding custom event type with behaviour of Work and by defining overtime options for it.
Emergency work (239)
The Emergency work event type is always overtime and follows the set overtime settings, eg the daily 50% overtime limit. Alarm work is always earned for at least one hour. Alarm work does not accumulate hours of regular working hours.
Meeting (31)
The Meeting event type works like the Work event type. This type of event is used to separate working time spent on meetings from other work done.
Correction (228)
The Correction event type is used with correction supplements. This allows manual change of event's interpretation and corrections from salary integration to payroll.
Training (25)
The Training event type can be used to distinguish working time spent on training from other working time. The transaction type accumulates working hours for the entire duration of the stamp. Upon implementation of the service this event type is set not to contribute to work week. This can be changed with setting Work hours -> TES -> Event types that contribute to work week.
Camp work (271)
Read more about camp work here.
Union steward work (5)
Upon implementation of the service this event type is set not to contribute to work week. This can be changed with setting Work hours -> TES -> Event types that contribute to work week.
Notes logged with a Union steward work event are not displayed in workshift planning.
Travel time (26)
By default, the Travel time event type does not earn overtime or balances. The time between the start and end time of the entry is calculated on its own line in the calendar view. Travel time hours supplement the daily working hours up to the work obligation, if the obligation falls short with other entries that increase working hours. Upon implementation of the service this event type is set not to contribute to work week. This can be changed with setting Work hours -> TES -> Event types that contribute to work week.
Travel invoice (27)
The Travel invoice event type can indicate the start and end times of the trip, mileage allowances, daily allowances and other possible expenses. In the case of a foreign daily allowance, the destination country can be marked in the comment. A travel invoice can also be assigned to a project. With a Travel invoice, you can create a Travel time event that corresponds to your travel time. If the trip accumulates normal working hours, a stamp will be made on the calendar accordingly.
Dining (15)
The Dining event type is only available in a terminal in cafeteria mode. The event is recorded with supplements added to it.
Lunch break (6)
A Lunch Break event type can be unpaid or paid. A paid lunch break accumulates working hours and an unpaid one does not. A paid lunch break can be set for a period beyond which the time is unpaid. The Lunch Break settings have their own article in our guide.
Break (28)
The Break event type can be used to mark paid refreshment breaks and the like. Marked breaks accumulate working hours for the entire duration of the stamp.
Health care (17)
The Health care event type works like the Work event type. The Health care event type is used when it comes to a health issue that is part of working hours, such as an occupational health check. Upon implementation of the service this event type is set not to contribute to work week. This can be changed with setting Work hours -> TES -> Event types that contribute to work week.
Notes logged with a Health care event are not displayed in workshift planning.
Work Elsewhere (18)
The Work Elsewhere event type works like the Work event type. This type of event can be used to distinguish work done at the workplace from work done elsewhere.
Supplement (165)
The Supplement event type does not affect the calculation and does not accumulate man-hours. It can be used to add, for example, working condition related supplements such as supplement for working in low-hygiene and unclean environment.
Workplace health and safety work (14)
Upon implementation of the service this event type is set not to contribute to work week. This can be changed with setting Work hours -> TES -> Event types that contribute to work week.
Notes logged with a Workplace health and safety work event are not displayed in workshift planning.
On call (33)
The On call event type indicates the time used for standby. On call does not accumulate working hours.
Overtime event types
Overtime event types are visible in Behaviour dropdown when adding custom event types.
Agreed additional work / overtime
A type of event that is used when an agreed additional time / overtime does not constitute regular working time. Work time is interpreted as daily overtime if the work done by the person exceeds the set maximum daily work time. If the work done by the person falls below the set maximum daily work time, then overtime is formed first as additional work, then as weekly overtime. When the daily maximum work time has been reached, overtime is created as daily overtime.
This event type is rounded with other overtime events according to the overtime rounding rules.
Agreed overtime
The type of event that is used when the agreed overtime does not constitute regular working time. Working time is interpreted as daily overtime if the work done by the person exceeds the set maximum daily working time. If the work done by the person falls below the set maximum daily working time, then overtime is formed as weekly overtime.
This event type is rounded with other overtime events according to the overtime rounding rules.
Agreed 100% overtime
The type of event that is used when the agreed 100% overtime does not constitute regular working time. Working time is interpreted always as daily 100% overtime. It does not affect calculations of other daily overtimes.
This event type is rounded independently, regardless of other overtime events, according to the overtime rounding rules.
Absence event types
All events for absence types are shown in workshift planning as "Absence" without possible notes.
Flexible work hours balance leave (2291)
The Flexible work hours balance leave event type is used when you want to take leave by using Flexible work hours balances. The event type gives a maximum of one working day of regular working time and the Flexible work hours balance is reduced by the same amount.
Flexible bank leave (1049)
The Flexible bank leave event type is used when you want to take leave by using Flexible bank balances. The event type gives a maximum of one working day of regular working time and the Flexible bank balance is reduced by the same amount.
Public holiday (7)
The most common public holidays are automatically added to the calendar. The visibility and calculation method of public holidays are managed in the settings of either the work community or the setting groups, as required. The type of public holiday event means a paid holiday. It does not accrue or subtract balance hours. The type of event can be used to control promotions and bonuses earned on public holidays.
Holiday pay leave (164)
The Holiday pay leave event type is used when you want to change holiday pay to leave. The event type gives a maximum of one working day of regular working time. If you want it to behave like annual holiday, you need to set up a new event type, e.g. Holiday pay leave (AH), which behaves like annual holiday.
Temporary lay-off (23)
The default for the Temporary lay-off event type compensation is "Unpaid". Examples of using different types of Temporary lay-offs.
Bank leave (102)
The Bank leave event type type is used when you want to keep the earned hours accumulated in the working time bank free. The transaction type gives a maximum of one working day of regular working time and the working time bank balance decreases by the same amount.
Absence (4)
An Absence event type can be marked as paid or unpaid or partially reimbursable. The entry type does not increase or decrease the balance. Different types of absence can be selected on the label. You can also choose on the label whether the absence accrues annual holidays. It is separate from the management of absence types guide.
Sick leave (2)
Sick leave event type indicates sick leave. Sick leave may indicate whether a medical certificate has been received and whether the absence is paid, unpaid or partially reimbursable. You can also choose from sick leave to accrue annual leave or not. Sick leave accrues working hours and regular working time up to the length of the working day and does not accumulate working hours balance.
Balance leave (16)
The Balance leave event type is used when you want to keep earned hourly balances or balances withdrawn from the working time bank. The transaction type gives a maximum of one working day of regular working time and the working hours balance is reduced by the same amount.
Levelling period hours leave (2294)
The Levelling period hours leave event type is used when you want to take leave by using Levelling period hours balances. The event type gives a maximum of one working day of regular working time and the Levelling period hours balance is reduced by the same amount.
Work time shortening leave (29)
Work time shortening leave event type indicates Work time shortening leave, which equalizes the 40 h working week to 37.5 h working week on an annual basis.
Weekly leave (287)
The Weekly leave event type records the planned holidays. Weekly leave event type does not constitute a payroll interpretation and prevents the balance from decreasing on that day.
Annual leave (3)
Annual leave event type marks the days of annual leave. The entry is made uniformly for the entire annual holiday period. The entry begins on the first day of the annual holiday and ends on the last Sunday of the annual holiday. In this case, the program takes Saturdays into account in the calculation (excluding Easter Saturday, Section 4 of the Annual Leave Act) and ignores Sundays. If work is entered for an annual holiday day, that day is ignored in the annual holiday calculation.
Annual absence (290)
The Annual absence event type is used when you want to take annual absence leave. The event type gives a maximum of one working day of regular working time and the Annual absence balance is reduced by the same amount.
Overtime leave (278)
The Overtime leave event type is used when you want to take leave by using Overtime balances. The event type gives a maximum of one working day of regular working time and the Overtime balance is reduced by the same amount.
Administrative event types
Accruals can be set and modified in any date view.
When accruals are set, all the previous accruals are erased and the new base value is used from specific date onwards. For example, 31.3.2021 Balance reset 10 h 33 min. Balance reset is typically used when the service is implemented for the first time.
Change affects accruals on a specific day. For example, 31.3.2021 Balance change +3 h 27 min adds balance for that day. Balance change be used for manual adjustments.
When using Annual leave earning change / reset it is important to pay attention on which annual leave accrual calculation it affects. For example, changes on 15.5.2021 affects on annual leave accruals on time period 1.4.2021 - 31.3.2022.
Annual leave earning reset can be done only on the first day of the month.
Annual leave earning change can be done on any day.
Annual leave balance locking is set on period start date - end date. Typically this period is march.
Flexible bank reset (1308)
Flexible bank change (1309)
Flexible work hours balance reset (2292)
Flexible work hours balance change (2293)
Bank reset (103)
Bank change (104)
Balance reset (12)
Balance change (13)
Levelling period hours reset (2295)
Levelling period hours change (2296)
Work time shortening leave reset (1435)
Work time shortening leave change (30)
Annual leave earning reset (9)
Annual leave balance locking (19)
Annual leave earning change (10)
Annual absence reset (1437)
Annual absence change (1438)
Overtime balance reset (279)
Overtime balance change (280)
When adding your customized accrual, these Administravite event types appear automatically.
Other event types
Notes (8)
The Notes event type can be used to make a separate comment for which a start and end time can be set. The Notes event type does not affect the calculation and does not accumulate man-hours.
Planned shift (24)
Only used in Planning section.
Invalid event (32)
This event type is used to notify a user or a supervisor that the system did not accept an event from a terminal. This event type is displayed as an exceptional entry in calendar view and in the exceptional entries report. This event type cannot be added manually but it can be removed. The event type does not affect the work time amount. Event notes display the information received from the terminal e.g. the event type, the date/time and project. Usually these cases have been caused by a terminal that has been offline for a while and due to some issue its internal clock has reset or has been set in the wrong time causing the offline events to be set on the wrong date/time. The system normally accepts the past offline events sent by a terminal once it is back online and sends them but if the times are too far away from current time the system will add this type of an event instead.