Netvisor allows importing working hour entries from an external software via the API resource workday.nv. Using the same API resource, it is also possible to import, for example, absence data. Data imported with the workday.nv resource is allocated to Netvisor record types (Palkat - Payroll settings - Record types). Allocating is done with the record type number, which can be set in the record type settings by clicking the name of the record type. In order for the imported hour entries to be allocated to the correct record types in Netvisor, the numbering of record types must be identical both in Netvisor and in the source system.
Selecting the import method for working hour entries
Options are replace or increment.
The replace import handling overwrites previous hour entries made for the same day that are in status open/acknowledged. However, if there are already hour entries in Netvisor for the same day that are either in status approved or paid, then it is not possible to import hours/absences for the same day using the replace import handling.
The increment import handling imports the new hour entries in addition to any previous entries made for the same day as new entries, regardless of the status of the previous entries.
Shifts spanning overnight
{#h_79dcdd453b}
In time-based imports (workdaytime), the start and end times must be within the same day, meaning a single working hour entry cannot cross midnight. If the end time is earlier than the start time, the import returns the error “Alkamisaika tulee olla ennen loppumisaikaa” (“The start time must be before the end time”). A shift spanning overnight is imported by splitting it at midnight into two separate workday messages, for example saturday 22:00–24:00 and sunday 00:00–06:00. The value 24:00 can be used as the end time. Working hours are always recorded in Netvisor for the day specified in the date element of the message.
It is not possible to import entries with overlapping times for the same day even with the increment import handling. In that case, the import returns the error “Annetulla kellonajalla on jo tallennettu päivälle tuntikirjaus” (“There is already an hour entry saved for the day with the given time”).
Recommended to import data on a daily basis
It is recommended that hours are imported on a daily basis. If hours are imported as a lump sum, for example, on the first or last day of the pay period, Netvisor loses the ability to use certain tracking features – for example, the 14-day rule for vacation accrual. Likewise, the voluntary absence data of the Incomes Register could in practice not be utilized without manually editing the data on the report.
Allocating hour entries to the employee
Allocation to the employee is done in the employeeidentifier element. The allocation can be made either with the employee number (recommended), the employee’s netvisorkey, or the personal identity code. When using the employee number, employees must be numbered in the same way as in the source system. This can be done in Netvisor via the employee list by selecting the employee and entering the Employee number in the employee settings.
//
*This article has been translated using an AI-based translation tool. The contents or wording of these instructions may differ from those in other instructions or in the software.
*