HR to scheduling

Employees and contract hours from HR to scheduling automatically, including future changes

Employees, contract hours and departure dates reach scheduling automatically when the integration reads them from the HR system, including changes that take effect later. KoppelHet connects Visma Raet YouForce, AFAS, Nmbrs, HiBob, Personio, SAP SuccessFactors and Workday with Dyflexis, Shiftbase, Planday and vPlan, so planners roster ahead with HR's data.

Last updated: 9 November 2026

Discuss your integration All about Leave, absence and time

What it is

Planners roster weeks ahead. A new employee, an increase in hours next month or a transfer is already in HR but not yet in scheduling. Without an integration someone retypes it, or the planner only hears about it on the effective date.

Someone rostered on old contract hours gets incorrect plus or minus hours. Someone who has already left is still on the roster.

How the integration handles it

Planned changes come along with their effective date. YouForce and SAP SuccessFactors record them in advance; the integration also requests those future records.
If scheduling has no effective date for contract hours, as in Planday, the integration stores the change and applies it on the effective date itself.
A transfer becomes a new contract in the new team that starts on the effective date. The old contract closes a day earlier, so the current team keeps rostering until then.
Personio only reports the start of an employment on the start date itself. The integration reacts to the creation of the employment, so the new colleague is in scheduling weeks ahead.
Schedule types are converted. AFAS has hours per day, hours per week and fixed times; Nmbrs a two-week schedule; vPlan working hours per weekday. The integration spreads the hours according to a rule you choose beforehand.
If someone has two employments, for example a permanent and an on-call contract, they get two contracts under one employee in Dyflexis.
Only what scheduling needs goes across: name, contact details, employment and hours. Not salary or BSN.

Edge cases we handle

Shiftbase calculates plus and minus hours from contract hours. If HR changes hours retroactively, the integration puts the new contract into Shiftbase with that date, so the balance is recalculated from the right week.
Dyflexis first places an employee arriving through the integration as an external employee. An administrator links it once; after that Dyflexis updates it automatically.
In Bob organisations add their own employment types. Per type we record whether someone goes into scheduling: an external specialist not, a holiday worker yes.
Setting an employee in Shiftbase to export hours only stops changes from Nmbrs. The integration reports employees who fall outside the import this way.

What KoppelHet does

In the smallest setup employees, contracts and departures go from HR to scheduling. Worked hours back to payroll and leave can follow later as an extension. The translation of departments and contract types to sites and contract types in scheduling sits in a table that scheduling can maintain itself.

Common integrations

Personio → Dyflexis

Personio to Dyflexis integration: new employees and contract hours straight into scheduling

HiBob → Dyflexis

HiBob to Dyflexis integration: employees and working patterns from Bob automatically in scheduling

SAP SuccessFactors → Dyflexis

SAP SuccessFactors to Dyflexis integration: Employee Central employments as contracts in scheduling

Workday → Shiftbase

Workday to Shiftbase integration: workers, contract hours and approved leave in the schedule

AFAS Profit → vPlan

AFAS to vPlan integration: employees as resources, schedule hours and leave in work planning

Nmbrs → vPlan

Nmbrs to vPlan integration: employees, alternating work weeks and approved leave in production planning

Planday → Visma Raet YouForce

Planday to YouForce integration: worked hours per employment to payroll

SAP SuccessFactors → Protime

SAP SuccessFactors to Protime integration: employees and contract hours from Employee Central in time registration

HiBob → Protime

HiBob to Protime integration: employees and working pattern from Bob in Protime, approved absence back as time off

Workday → vPlan

Workday to vPlan integration: Dutch workers as vPlan resources, with hours, time off and leave of absence per day

Customer case

ROVA

Public services

Employee data flows from Visma Raet YouForce to Dyflexis for scheduling.

Frequently asked questions

Does salary go to scheduling?

No. Scheduling needs name, employment and contract hours, not salary or BSN.

Does scheduling see an hours change that takes effect next month?

Yes. The integration takes planned changes along with their effective date, so the planner already sees the new contract when making that month's roster.

Can worked hours also go back to the HR system?

Yes, as an extension. Scheduling systems such as Dyflexis prepare closed periods, and payroll systems such as YouForce accept hours and pay components.