TimePunch Calendar v3.0.830.0

The following issues have been fixed:

  • Authorization to view booking types
    During the permission check, an error occurred that made it possible for employees without authorization to see the posting reason (for example, leave). This problem has been fixed in the current patch.
Read More

TimePunch Patch v3.0.824/825.0



This patch for TimePunch 3.0 eliminates minor issues that have occurred in different installations.

The following issues have been fixed:

  • FS#793 – Book time entries on expired project
    In TimePunch, past completed projects (i. e. projects with defined start and end times) were also displayed for booking. This problem has been fixed in the current patch.
  • Import of Project data
    When importing project data, the maximum working time of the project pool was not imported correctly. With the current patch, the project data import works correctly again.
Read More

TimePunch Studio v3.0.822.1

This patch for TimePunch Studio Module 3.0 eliminates minor issues that have occurred in different installations.

The following issues have been fixed:

  • FS#795 – TimePunch Studio in Tablet Mode
    In version 3.0, TimePunch Studio could not be started in the tablet mode of a Windows 10 PC. This problem has been fixed.
  • Read More

    TimePunch Patch v3.0.821.0



    This patch for TimePunch 3.0 eliminates minor issues that have occurred in different installations.

    New features:

    • Filtering option for tasks
      In the report filter, the tasks can now also be filtered using an input field. This simplifies the search if many tasks have been created.

    The following issues have been fixed:

    • Possibility to charge travel time in TimePunch ONE
      With TimePunch ONE it is now also possible to have travel charges included in the current patch. This means that the travel costs can also be charged to the customer.
    • Missing cost factor for pure project bookings
      If working times were booked directly to a project, the cost factor for invoicing work at the customer’s premises was missing. The patch fixes this problem.
    • Crash when sorting by column “Updated by”
      When sorting the data after “Changed by” an error occurred and TimePunch was terminated. This problem is now fixed.
    • Missing update after abort of time entry edit dialog
      If the Edit Time Entry dialog was closed with the Close button of Windows, the data in TimePunch’s main window was not updated. This problem is also fixed now.
    Read More

    TimePunch Patch v3.0.817.0



    This patch for TimePunch 3.0 eliminates minor issues that have occurred in different installations.

    The following issues have been fixed:

    • FS#438 – TpWatcher memory usage very high
      The reason for the sometimes very high memory consumption could be adjusted and fixed in the test.
    • FS#792 – DATEV Export mit Gehalt 0€
      If no salary has been defined for employees, this value is no longer exported to DATEV Lodas.
    • FS#791 – PZE Online Lizenz wurde nicht im Profil angezeigt
      The PZE Online license could be assigned to the employee in license management, but it was not displayed in the employee profile.
    Read More

    TimePunch Patch v3.0.812.1



    The first patch for TimePunch 3.0 eliminates minor issues that have occurred in different installations.

    The following issues have been fixed:

    • Report Generation Performance
      Performance had deteriorated extremely during the reporting process when using local MDB databases. This issue is resolved with the current patch.
    • Import of project Data
      When you import projects. CSV files, the start and end dates have not been correctly taken into account. The import has been corrected with the current patch.
    • Crash on New Installation
      If TimePunch v 3.0 was installed on a completely new PC, then there was an error message if the watcher was started before the client. This problem has been resolved.
    • Problem when exporting to DATEV Lodas
      If the fiscal year in TimePunch does not start at the beginning of January but, for example, already in December, the working hours during export to DATEV Lodas were not posted to the correct cost points. This issue is resolved with the current patch.
    Read More

    TimePunch v3.0



    TimePunch 3.0 is finally online!

    The following Features have been implemented:

    • For the modules TimePunch Watcher“, “TimePunch Studio” and “TimePunch Management” you no longer need a separate installation – with TimePunch 3.0 you can use the individual modules anytime and anywhere over the TimePunch Application Server.
    • To make staff management even easier for you, team and department managers are now allowed to directly access the employees working hours. They don’t have to use the reports anymore.
    • With TimePunch 3.0, holidays can also be represented as a regular working day. This makes it possible to record the hours normally, even on public holidays.
    • In order to better reflect the reality for the project management, with TimePunch 3.0 project managers no longer have the right to change all projects. They are assigned to their projects and can only edit them.
    • Reports no longer need to be reinstalled after a patch update.


    Read More

    TimePunch Management v2.95.1229.0



    TimePunch 3.0 is in the starting blocks! But before the new version goes online on 08.01.2018, we have fixed a few bugs of the current version with our latest patch 2.95.

    The patch fixes the following problems:

    • FS#767 – Report holiday overview does show half days of vacation incorrectly

      In the holiday overview report, half holidays were sometimes incorrectly reported. This bug has been fixed – in the latest patch, even half-days are listed without errors.

    • FS#768 – Export to Excel with annual leave and sick leave report.

      Die The annual leave and sick leave reports have been revised to export only the data (without headers and footers). This will allow you to filter and postprocess the cells in Excel in the future.

    • FS#774 – Grouping and summation DATEV Lodas

      The export to DATEV Lodas has been simplified. In the future, you can group time entries by wage type and add up the times. This makes it easier for you to check the working hours which are imported in DATEV.

    Read More

    TimePunch Management v2.95.1115.0



    Following features have been added:

    • FS#765 – Employees should be able to reassign break entries

      With the option “Employees can allocate new breaks” in the “Internals” tab of the Extras/Options dialog, employees with standard rights can now also be authorized to allocate registered breaks and to book them for a project.

    • FS#764 – Print sequence for flextime account daily report

      The print order has been adjusted to match the flexitime reports. The personnel number and the name of the employee are used as sort criteria.

    The following issues have been fixed in the patch:

    • FS#766 – Daily working time report

      The report now also shows sick leave and vacation as working hours for permanent employees. The number of working hours displayed in the TimePunch analysis therefore corresponds to the number of working hours displayed.

    • FS#763 – Missing time compensation with automatic overtime payout

      The automatic calculation of paid hours now takes into account the special case that absenteeism compensation can exceed the defined overtime limit.

    • FS#751 – Synchronization with new booking types

      With the previous synchronization, new booking types such as unpaid sickness or absence could not yet be transmitted. With the new version, these booking types can also be synced.

    • FS#748 – Display of common tasks in the Watcher

      Common tasks are now hidden in the watcher, if this has been defined in the project. This setting has been ignored by the watcher so far.

    • FS#744 – Job termination

      If an employee is dismissed, the working time model is first set to 0 hours one day after the dismissal. Previously, the time was identical to that of the termination – one day too early.

    • FS#699 – Watcher starts after a holiday with vacation

      After an employee’s vacation, the Watcher now starts the last working time project. This distinction is new. Before that, the Watcher started with a holiday booking after the vacation.

    Read More

    TimePunch Cutter v1.95.1019.0

    TimePunch Cutter 1.95 – Fixed

    The following issues have been fixed:

    • Fixed, FS#759 – Take into account break after 6 hours in the 9 hour break.

      The second break booking did not take into account the break time of the first break. I. e. the second pause might have been booked too early.

    Read More
    Page 4 of 30« First...«23456»102030...Last »