Officient users often wonder if it's possible to connect their time registration software to Officient. Some providers already have solutions in place, such as GeoDynamics, GPS, ... You can find them here: https://marketplace.officient.io/category/time-and-attendance. To add your time registration software to the list, send an email to support@officient.io.

For software that has not yet been connected, continue reading. 🚀

First, we should know your use case. For what reasons are you using time registration in your company?

  • Time registration software is being used only to check attendance. See 1
  • Time registration software is being used to check attendance and for internal reporting (eg. calculate costs and profit on projects). The time registration software is already linked to your payroll provider in some form. See 2
  • Time registration software is being used to do payroll, track and pay out overtime, work at special hours and tariffs. The time registration software is in no way linked to your payroll provider. See 3

1. Time registration software is being used only to check attendance

Time registration is only used to check attendance. In this case no existing connection from the time registration software to the payroll provider is in place. The time registration data is only used for internal purposes at the company.

In this case, we recommend the following type of integration:

Use case specifications:

  • Time registration software is only used to track attendance, not for payroll purposes.
  • Officient pushes new employee data to the time registration software
  • Users are planning and approving time off in Officient. At the end of the month, the calendar, enriched with one-off wage components, is pushed to the payroll provider through Officient.

2. Time registration software is being used to check attendance and for internal reporting (eg. calculate costs and profit on projects). The time registration software is already linked to your payroll provider in some form

Time registration software is used to calculate HR cost and project expenses. An example in this category is GeoDynamics (time tracking based on GPS systems in cars). The time registration data is used for internal reporting purposes and an integration with a payroll provider exists.

In this case, we recommend the following type of integration:

Use case specifications:

  • Users are planning and approving time off in Officient, the time registration software imports the time off from the Officient calendar to itself. The sync could be set up to work at set times (e.g.: nightly or 2 times a day). To sync instantly, webhooks can be used.
  • The time registration software is responsible for interpreting the registered time and pushing calendar data to the payroll provider at the end of the month to get payroll started. Usually, this is done via a structured file.
  • In some cases, Officient can still be used to signal one-off wage components for certain employees that month. An API for that is currently planned (message support@officient.io if you want to be the first to try this API).
  • The calendar that has been sent to the payroll provider will be sent back to the Officient calendar after the payroll for that month has been processed.

3. Time registration software is being used to do payroll, track and pay out overtime, work at special hours and tariffs. The time registration software is in no way linked to your payroll provider

This situation sometimes occurs with custom time registration software (e.g.: in a call center or other businesses that have an ERP to do planning and time registration).

In this case, we recommend the following type of integration:

  • Push the calendar to your payroll provider at the end of the month
    Because your time registration software isn't linked to your payroll provider in this scenario, you pass the time registration data from your time registration software through Officient to your payroll provider. You can find a list of supported payroll providers at https://marketplace.officient.io/category/payroll

Use case specifications:

  • Users are planning and approving time off in your ERP system
  • The time registration software is responsible for interpreting the registered time and pushes the interpreted calendar data to Officient.
  • Officient is responsible for pushing the calendar data to your payroll provider.
Did this answer your question?