TimePunch

TimePunch covers all functions of modern personnel time recording. This includes the recording of pure clock-in and clock-out time, including the possibility to book overnight entries, as well as the management of flexitime accounts with automatic calculation of overtime and absences.

In this way, target working time models can be stored for employees, from which the overtime balance is then automatically calculated. Of course, overtime can also be used to compensate for time off in lieu or to pay out to employees.

Also integrated is vacation management, including vacation carryover to the next year and direct display of remaining vacation for employees at the terminal or in the PC software. This also includes the possibility to manage special leaves or sabbaticals.

Sick days of employees can be stored and managed in TimePunch. This also applies to a possible Corona quarantine. For the wage data export, a distinction can be made between illness with continued payment by the employer and without continued payment for illness lasting more than 6 weeks.

Public holidays are already stored per state for Germany, Switzerland and Austria and do not have to be updated manually. Floating holidays are calculated automatically by the time recording.

Using the integrated wage and salary data export, the recorded working times can be transferred directly to the wage and salary program used. For this purpose, the wage data is saved from TimePunch in the respective target format in an export file.

TimePunch offers integrated export options to DATEV Lodas, DATEV Lohn und Gehalt, Lexware Lohn und Gehalt, SBS Lohn Plus and GFP-Impuls.

In addition to working hours, lost time such as sickness, vacation and holidays can also be transferred with the target time or the average calculation after 13 weeks or 6 months.

Night, weekend, holiday and overtime surcharges are taken into account. Of course also with prioritization possibilities.

If a payroll program other than the already integrated systems is used, the export can be adapted with manageable development effort.

TimePunch has a digital personnel file for each employee. This means that all employee-related master data can be stored in TimePunch. This includes general data, such as email address and team or department affiliation, but also personal data, such as postal address, salary information or account data. Everything centrally at one point - in TimePunch.

TimePunch can also be used as a document repository. For example, employment contracts, employee interviews or salary statements can be stored in TimePunch and made centrally accessible to employees. Within the document repository, access rights can be assigned to specific folders or documents. This prevents employees from viewing documents that are not intended for them.

The viewing of documents for employees is done via the self-disclosure module. There, employees can access the documents that have been released for them. If a new document is uploaded that can be viewed by employees, then an e-mail is automatically sent to the person concerned with the information that new documents are available.

Not to be forgotten are the time-controlled dismissals and settings. The date of termination or the date of hiring can be stored for employees in advance. If this date is exceeded, the employee's access rights are withdrawn or, in the case of a hiring, also given. This avoids surprises at the start or end of an employment relationship.

Transparency is always important, especially in a time tracking system. Therefore, many processes are logged in TimePunch and sent to different responsibilities on request.

In TimePunch, it is also possible to store core times per working time model. If employees are late or forget to book, the employees themselves or their supervisors can be informed.

The same applies when adjusting or changing time entries. Here, too, the employees themselves (if the change was made by the personnel office) or their superiors (if the employees themselves have the right to make changes) can be informed by e-mail.

This also applies to month-end closings or incorrect postings, which can occur if employees forget to stamp or stamp twice, for example. Here, too, the personnel office is automatically informed.

Last but not least, this also applies to violations of the framework time model. If, for example, employees do not clock in for their break or come to work too early, these points are logged and reported to the appropriate stored office.