Organisation and access
HR reporting across several employers and countries in Power BI
Reporting across several employers or countries in Power BI needs a key of employer plus employee number and payroll costs fixed in one currency. KoppelHet builds this for example for several companies in Nmbrs or AFAS, and for international organisations in Deel, Personio or BambooHR.
What it is
With several employers someone exports a list per employer every month and pastes them together in Excel. Figures on absence and turnover then never quite match.
In one model it goes wrong on the key and on money. Employee number 1001 exists at two employers, and payroll costs in dollars and euros do not simply add up.
How the integration handles it
- In Nmbrs and AFAS employee numbers are unique per company or employer. The key in the model is therefore employer plus number, so figures per employer and for the group are both right.
- In YouForce and Personio the employer or legal entity goes along as a dimension, next to cost centre and department.
- BambooHR only provides the latest exchange rate. KoppelHet stores the rate per load day, so last month's payroll costs do not change when the rate rises tomorrow.
- Deel can convert the gross-to-net report to a chosen currency. KoppelHet fetches each payroll run in euros and stores that amount.
- The columns of the Deel report differ per country. KoppelHet maps them to fixed cost types, such as gross pay, employer costs and allowances, so countries add up.
- Personio counts absence per type in days or hours. KoppelHet uses the per-day breakdown, so absence from the Netherlands and Germany counts the same way.
Edge cases we handle
- In Workday supervisory organisations, cost centres and companies sit side by side. They become three dimensions, so finance reports by cost centre and HR by organisation.
- Personio returns compensation for at most one month per request, and the base salary without pro-rating for a mid-month start or exit. KoppelHet builds the history month by month and flags those months.
- Deel allows five requests per second for the whole organisation. If other integrations run on Deel, KoppelHet spreads the run.
- If an international HR system does not run Dutch payroll, payroll costs from the Dutch payroll package can go into the same model.
What KoppelHet does
KoppelHet agrees the key, the dimensions and the currency rule with HR and finance before the first report is built. When employers come from different systems, for example an international HR system and a Dutch payroll package, they go into the same model.
Common integrations
Nmbrs → Power BI
Nmbrs to Power BI integration: HR and payroll data ready for reporting per company
AFAS Profit → Power BI
AFAS to Power BI integration: HR data from Profit in Power BI, with history and its own security
Visma Raet YouForce → Power BI
YouForce to Power BI integration: HR and payroll data from Visma Raet in one reporting model
Personio → Power BI
Personio to Power BI integration: employees, absence and pay costs from Personio 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
Customer case
Spinners
HR and payroll data from Nmbrs is ready for reporting in Power BI, with contracts, job history, absence, leave balances, schedules and the average length of employment per company.
Frequently asked questions
Which exchange rate do you use?
By default the rate the HR or payroll system provides, fixed per load day or per payroll run. If finance wants the rate from its own finance package, we use that.
Can we report per employer and for the whole group?
Yes. The employer is a dimension in the model, so both come from the same model.
How long does it take to go live?
As an indication, two to four weeks.
More on HR data to BI
History and counting
Organisation and access
- Multiple employers and countriesOne report across employers, countries and currencies.
- Security and privacyManagers only see their own department; social security number and diagnosis stay out of the model.