History and counting
Counting turnover and headcount correctly in Power BI
Turnover and headcount are only right in Power BI when leavers come along, people and contracts are counted separately and contractors have their own dimension. HiBob, BuddeeHR and Workday leave out leavers by default or can exclude them, and Visma Raet YouForce, SAP SuccessFactors and Oracle HCM allow several contracts per person.
What it is
Turnover is the figure management asks for first, and the figure that is most often wrong. Leavers drop out of an ordinary request, and then turnover looks like zero.
Headcount goes wrong the other way: someone with two appointments counts twice, an internal move counts as a departure, or contractors appear in headcount.
How the integration handles it
- Bob returns only active employees by default. KoppelHet also requests inactive employees, and the service user gets access to that group.
- Leavers are archived in BuddeeHR. KoppelHet also fetches archived employees with their end date.
- Workday can exclude terminated workers and ended contingent workers. KoppelHet includes them with the termination reason, so voluntary and involuntary turnover can be shown per country.
- With YouForce, SuccessFactors and Oracle HCM KoppelHet keeps person and contract apart, so someone with two appointments counts once for headcount and twice for positions.
- In Deel the employment type, such as own entity, employer of record or contractor, becomes a fixed dimension, so headcount with and without contractors sits side by side.
Edge cases we handle
- In Oracle HCM a departure is the end of the work relationship. Changing assignment within the same employer is not a departure.
- BuddeeHR numbers contracts within an employment. In Power BI HR thus sees who is on their third temporary contract and when it ends.
- The employee number in BambooHR is editable. KoppelHet links on the internal ID, so a changed number does not become a new employee.
- BambooHR sends all table rows of an employee on every change. KoppelHet replaces the whole history per employee, so Power BI does not count duplicate job rows.
What KoppelHet does
At the start KoppelHet agrees with HR what a departure is, what a person and what a contract, and whether contractors count. Those choices are then fixed in the model, so every report on it counts the same way. Derived measures, such as the average length of employment, become a fixed measure in the model.
Common integrations
HiBob → Power BI
HiBob to Power BI integration: people data and work history from Bob in Power BI
BuddeeHR → Power BI
Buddee to Power BI integration: headcount, contracts, absence and turnover from Buddee in one model
Workday → Power BI
Workday to Power BI integration: global HR data in Power BI, with retroactive changes handled correctly
Visma Raet YouForce → Power BI
YouForce to Power BI integration: HR and payroll data from Visma Raet in one reporting model
Oracle HCM Cloud → Power BI
Oracle HCM to Power BI integration: workers, assignments and history from Oracle Fusion in Power BI
Deel → Power BI
Deel to Power BI integration: global headcount and pay costs per country and type of employer
BambooHR → Power BI
BambooHR to Power BI integration: employees, job history and pay costs in one currency
Frequently asked questions
Do contractors count in headcount?
You choose. Employment type is a filter in the model, so both figures sit side by side.
Can Power BI show voluntary and involuntary turnover?
Yes, if the HR system records the reason. Workday and Deel do; KoppelHet takes the reason into the model.
Does an internal move count as a departure?
Not if that is agreed at the start. With Oracle HCM KoppelHet counts turnover on the end of the work relationship, not on a change of assignment.
More on HR data to BI
History and counting
- History by reference dateWho held which job in which department on a date, also after a reorganisation.
- Turnover and headcountCounting leavers, people and contracts separately, contractors apart.