Understanding When New Employment Records Are Created from HiBob Updates
Last updated: November 12, 2025
Overview
When integrating HiBob with TeamOhana, it’s important to understand how changes in employee data are processed and when new employment records are created in TeamOhana. This article explains why some updates may not immediately appear and provides guidance on expected behavior.
Key Points
Effective Date vs. Changes to Title or Salary
A change in the effective date alone does not trigger the creation of a new employment record in TeamOhana.
For a new employment record to be created, either the employee’s job title or base salary must change.
HiBob API Behavior
HiBob will only start sending a new job title once it is active.
If a future job title is set in HiBob, TeamOhana will continue to see the current title until the effective date arrives.
Similarly, salary changes must reflect an actual difference in amount. Updating only pay frequency or effective date will not trigger a new employment record.
Common Scenarios
Employee | HiBob Update | TeamOhana Result | Notes |
#1 | Pay frequency changed effective 11/01 but same salary amount | No new employment created | Salary unchanged → no new record |
#2 | New title effective 11/01, salary unchanged | No new employment created yet | HiBob API sends new title only on effective date |
#3 | Salary updated effective 11/01 | New employment record created | Change in base salary triggered creation |
Expected Behavior
Salary or title changes: Will create a new employment record in TeamOhana.
Effective date changes only: Will not create a new record.
Pay frequency changes only: Will not create a new record.
Summary
TeamOhana’s API integration depends on actual changes in job title or salary to trigger new employment records.
Simply changing the effective date or pay frequency will not trigger a new employment record.
This behavior is consistent with HiBob’s API limitations.