Remote now syncs approved future time-off data from HiBob to Remote. This allows Customers to make HiBob the source of truth for worker time-off reporting when using Remote and to automatically sync time-off info from HiBob over to Remote. Customers can also map different time-off types between HiBob and Remote and set their preferences for data synchronization across platforms. In this article, we will explain:
- Prerequisites
- How to configure the time-off integration
- How to fix errors in time-off syncs
- Disable the time-off integration
- Integration Recommendations
- Guidance for employees
Is the HiBob integration right for me?
Before you enable the integration, it's important to understand who the integration is available for and how the data is synced to make sure it's a good fit. Below are key things to know about the time off integration, to help you decide if it is the right choice for you:
-
Data synced: Approved time-off requests with time-off start dates in the future, as well as updates and cancellations of future time off requests
- The integration does not sync past time-off that has already occurred, as there could be too many differences between the two systems and Remote can't verify which was used as the source of truth for requests. For past time off (new approved requests, changes, cancellations), employees must manually update both Hibob and Remote to ensure payroll accuracy.
-
We do not sync time-off requests that have not been approved in Hibob.
- We only sync time-off requests for employees that have been synced through our integration, and that are active (fully onboarded in Remote).
-
Direction of sync: One-way from HiBob to Remote
-
Customer types covered: EOR and GP customers
- Time off for contractors is currently excluded from the integration.
-
As part of the integration setup, you will complete a mapping of time-off types between the two systems.
-
For some of the time off types, HiBob only sends us the number of days taken, without a breakdown by hours. For those time off types, we will assume 8 hours a day. Half days will be 4 hours and percentage of a day type time off will be percentage * 8 hours.
- Note that HiBob seems to default to 9 hours a day, while the maximum possible in Remote is 8 hours. This may be a reason for some of your balance discrepancies in the two systems.
How to achieve aligned balances for time off in HiBob and Remote
Please note that in addition to approved time off requests synced through the integration, the following things are taken into account for the calculation of balances in Remote and in HiBob:
- public holiday calendars
- history of time off requests since the start of employment
- yearly allowances per leave type
- carryover rules for unused time off
If having aligned balances in two systems is important for you, please consider aligning the time off policies in both systems before enabling the integration or soon after.
For EOR employees, Remote should be the source of truth about public holidays per country, statutory regulations about carryover rules and minimum entitlements for paid time off, sick leave, etc. Remote's data will be used for payroll calculations. Feel free to use Remote's information about public holidays, carryover rules and yearly entitlements and copy them into HiBob. This cannot be achieved through API integration and would need to be done manually.
If you do not resolve differences in time off data right now, a more thorough check and alignment will be required at the time of offboarding to ensure correct payment for any unused paid time off.
If it is not important for you to have the same balances in HiBob as in Remote, you can skip this alignment.
By default HiBob uses 9 hours of working per day, while Remote allows maximum 8 hours a day. Therefore, we recommend updating those setting in HiBob. You can find them here:
How to configure the time-off integration
If you have not set up the HiBob integration, first follow the setup steps and then continue to the following section.
If you have already added the HiBob integration in Remote and would like to include the time-off integration feature, follow the below steps:
Add more permissions to your service user:
The service user needs an additional set of permissions to access time off data, on top of the permissions given to enable employee data syncs. In the permission group configuration in HiBob (Account → Permission groups), the following options need to be checked for a group that contains the related service user:
-
To access time off policy names:
- Features > Time off > See company’s time off settings
-
To access time off requests for users:
- People’s data > Time off > See selected people’s time off and sick leave balances
- People’s data > Time off > View, approve or decline requests that are pending approval of others
- People’s data > Time off > See who's out because of a private policy
- People’s data > Time off > See who's out today
Once all the permissions have been selected and assigned to the Service user click Save.
Map time off between HiBob and Remote:
Your company may have different types of times-off between Hibob and Remote, so it’s important to map the types so that data will sync correctly from HiBob to Remote. For example, maternity leave may be called “FMLA” in HiBob and “Maternity Leave” in Remote, so it is important to map the two types in Remote.
- Go to the Company Settings, click Integrations and select the HiBob integration card. To set up the correct mapping, go to Settings tab in the HiBob integrations page
- Click Configure mapping.
-
Select the time-off type from HiBob and map it to the corresponding type in Remote.
As part of this mapping, you can also map to custom leave types in Remote (e.g. if you offer your employees extra leave days such as self-care days or day off for their birthday).
- Once your desired time-off types have been mapped, click Save.
Enable auto syncs for approved time-off requests
- Use the toggle in the Enable auto-sync Time off for EOR Employees to enable the integration.
- Perform an instant sync by going back to the Overview tab and clicking the Sync button.
3. Review any errors that need to be corrected in the Time off tab.
How to fix errors in time-off syncs
My balances in HiBob and Remote do not match. What should I do?
Please check the following in both systems:
- public holiday calendars
- history of time off requests since the start of employment
- yearly allowances per leave type
- carryover rules for unused time off
We sync approved time off requests with time-off dates in the future. In addition to the approved time off requests, all of the above components go into the calculation of balances in each system. Mismatch in any of them may lead to a difference in balances in the two systems.
Make sure employees are active and are synced through the integration
We only sync time-off requests for employees that have been synced through our integration, and that are active (fully onboarded in Remote). You can check which employees are synced through the integration by going to the People tab. If some employees you think should be synced are missing, please follow these troubleshooting steps.
Errors in time off syncs
In some cases we can automatically process incoming data from HiBob, e.g. due to contradicting data. You can review any skipped time-off requests due to an error in the Time off and Events section. Employees will need to fix the time-off request in the system (Hibob or Remote) where they made the error.
You can review typical error messages below and how to resolve them:
1. Timeoff with type [TYPE] was not synced due to unexisting mapping for this timeoff type
- Description: This error shows when we try to sync a time-off request with a HiBob type that is not mapped to a Remote type.
- Solution: Make sure to go through the time-off type mapping process when setting up the HiBob integration, and link the HiBob time-off type to an existing Remote type.
2. Error when timeoff_type is not allowed for a given country
- Description: This error will show when a mapped timeoff type is not allowed on the EE’s country.
- Solution: Map the timeoff type to an allowed type for the EE’s country and do a manual sync to fix the problem.
3. Error when time off overlaps a single Remote time off
-
Error message: All errors will start with:
Timeoff couldn't sync because timeoff [EXISTING REMOTE TIMEOFF SLUG] already exists with different
and can contains those different indicators:end_date: [EXISTING REMOTE TIMEOFF END DATE]
number of taken hours: [EXISTING REMOTE TIMEOFF NUMBER OF HOURS]
start_date: [EXISTING REMOTE TIMEOFF START DATE]
status: [EXISTING REMOTE TIMEOFF STATUS]
timeoff_type: [EXISTING REMOTE TIMEOFF TYPE]
- Description: This error will show when an overlap is found and there’s some conflicts we couldn’t fix ourselves.
-
Possible solutions:
- If possible, update either Remote or HiBob time off so fields can match and sync again
- If not possible: cancel the overlapping time off and sync again
4. Multiple existing time off were found, so we couldn't sync this time off, their identifiers are the following: [REMOTE TIMEOFF SLUG, REMOTE TIMEOFF SLUG…]
- Description: This error will show when multiple Remote time off were found when syncing the time off
-
Solution:
- If possible, update either Remote time offs or HiBob time off so there’s only one perfect overlap
- If not possible: cancel the overlapping time off and sync again
5. Time off with more than 8 hours a day requested: %{timeoff_days: [\"maximum hours requested for a day reached\"]}
- Description: This error will show when a user requests more than 8 hours of time off in one day. In Remote, 8 hours is the maximum duration of time off possible in one working day.
-
Solution:
- Ask the employee to update their time off request and specify the correct number of hours
- If you get this error, we recommend checking your settings for number of working hours per day. By default HiBob uses 9 hours of working per day, while Remote allows maximum 8 hours a day. Therefore, we recommend updating those setting in HiBob. You can find them here:
If after following the steps above, you could not resolve the issue, please reach out to our support team at help@remote.com and provide the following:
- Screenshot of the Time off tab with the syncing error you want to investigate. Hover over ‘Failed’ tag to see the error explanation
- Screenshot for this time off request in HiBob
Disable the time off integration
If for some reason you want to disable time-off integration, you can do it without disabling the employee data integration for Hibob. Simply turn off the toggle in the Enable auto-sync Time off for EOR and Global Payroll Employees section. We will not delete any previously synced time off in Remote.
Integration Recommendations
- We recommend periodically checking the People, Time off and Events tabs to review any time off requests that could not be processed automatically. It is a good practice to do that once a month before payroll cutoff date. Ideally, those errors would need to be fixed before the payroll cutoff date.
- At this time, the time-off sync only applies to full-time EOR and Global Payroll employees, not contractors.
- When employees attempt to request time-off in Remote, a product notification will direct them to use HiBob for such requests. Approved time-off will then automatically sync to Remote. We will not disable the function to add time-off in Remote since it might be necessary for correcting past time-off instances.
- Time-off should not be added directly to Remote to avoid future discrepancies.
Guidance for employees
If your company is using time-off integration from HiBob to Remote, it means that any of your future Hibob time-off requests will be synced to Remote.
You may still need to use Remote to log time off in the following cases:
-
To fix the history of your time off (as Remote only syncs future time off through the integration)
- Example: As of May 1, 2024 your company enabled the HiBob time-off integration. On May 9 you realized that you forgot to add your time off for April 5. You should add this time-off request in both platforms, but going forward you will only need to make the time-off requests in HiBob.
-
To update or cancel time-off requests, especially if you want to make updates or to cancel time off in the past. Please submit such request in Remote, as it has high impact on payroll.
- Example: As of May 1, 2024 your company enabled the HiBob time-off integration and you had added time-off for April 1-9 2024 in Remote and HiBob and it was approved. However, you only ended up taking off April 1-5 so you need to correct the dates for accurate payroll processing. You need to make that update in both HiBob and Remote so that your payroll is processed accurately.
-
To fix contradicting future time-off requests
- Example: You have future time-off request in Remote that partially overlaps with dates of the time-off request in HiBob. In Remote you already have a request for June 1-3 while Hibob has a request for June 1-5 . You will need to manually correct one of the requests.
- You have future time-off request in Remote and HiBob for the same dates but with different time-off type. You will need to manually correct one of the requests.
-
When you submit your requests in HiBob, please avoid requests for partial hours (e.g. requests for 3 hours and 20 minutes of time-off). Remote only allows to take time-off for round number of hours. All other requests will be rounded the following way, leading to discrepancies in your time-off balance in Hibob vs Remote:
- If time-off requests is < .5 hour, round to 0. e.g. 4 hours 20 minutes → 4 hours
- If time-off request is >= 0.5 hour, round to the higher full number. e.g. 4 hours 50 minutes → 5 hours
- For time-off requests that come with a percentage of each workday, the daily time-off will be calculated as 8 hours * percentage in day and then rounded up or down like mentioned above.
Comments
0 comments
Please sign in to leave a comment.