HiBob has recently updated its leave request handling process, and it's important to understand how these changes affect integrations and manual workflows—especially when it comes to syncing with the EH system.
When an employee modifies a leave request in HiBob, the behavior of the system now depends on whether any of the original leave dates are included in the modified request:
Modified Request Contains None of the Original Dates
HiBob generates a new leave request ID.
The EH system treats this as a new leave request, which it can successfully accept and process.
Action Required: You must manually remove the previously applied leave hours to ensure records are accurate.
Modified Request Includes Any of the Original Dates
HiBob generates a new leave request ID.
Synchronization will only proceed if the original leave request is not locked in the payrun.
If locked in payrun then No synchronization occurs. You will need to make leave adjustment manually in EH. ("The request is invalid" error will be generated)
Previously, modifying a leave request—for example, adjusting the number of hours—required manually removing the old hours from EH because the system was unable to sync changes due to leave hour locks. The new process offers partial automation but still requires manual intervention for accurate tracking and reconciliation.
Always check if modified leave requests contain any original dates.
Remove old leave hours manually if a new request is created with different dates.
Make manual adjustments in cases where synchronization fails due to original dates being retained.
By staying informed of these updates, you can ensure a smoother leave management experience and avoid potential errors in leave balances and approvals.