Hours to payroll

Worked hours and allowances from scheduling to payroll automatically

Worked hours and allowances reach payroll automatically when the integration picks up only approved hours from scheduling and translates each hour type into a pay component of the payroll system. KoppelHet does this from Dyflexis, Quinyx, Planday, Shiftbase and Protime to AFAS, Visma Raet YouForce, Loket and Nmbrs, per employment and in the right payroll period.

Last updated: 9 November 2026

Discuss your integration All about Leave, absence and time

What it is

Planners work in the scheduling system, payroll in the HR system. Without an integration hours and irregular-hours allowances move over monthly by export, which someone has to import and check.

Scheduling and payroll speak different languages. Dyflexis gives each part of the hours its own name, Loket recognises a pay component by its number. Planday calculates an amount per shift, AFAS calculates pay itself with the collective agreement and its own rates.

How the integration handles it

Only hours approved or signed off in scheduling go to payroll.
We set the translation from hour type to pay component with payroll before the first run: a Dyflexis column to a Loket number, a Planday salary code to a YouForce element code, a Deputy export code to an AFAS pay component.
An hour type without a pay component is not silently skipped but reported, so no hours disappear unnoticed.
We send hours, not amounts. If scheduling calculates an amount per shift, we leave it out, so the payroll system stays leading for pay.
Allowances in time go as hours, allowances in money as a pay component, so Nmbrs, for example, pays each part the right way.
Hours are totalled the way the payroll system accepts them. YouForce takes a total per pay component, date and employment; Protime delivers minutes per day that we total per payroll period.
With several employers or entities the hours go to the right employer in AFAS or the right company in Nmbrs, based on the site or department in scheduling.

Edge cases we handle

AFAS only processes hour types per day for employees with a daily schedule. For part-timers with a weekly-hours schedule we book pay mutations per period.
A night shift across midnight falls on the day the shift belongs to in the schedule, so the allowance lands in the right period.
For an hourly worker an allowance hour can count as a worked hour, for a salaried employee it cannot. We check per contract type that an allowance hour is not also paid as a worked hour.
A pay component in YouForce carries only a code, a value and an effective date through this route. Hours on another cost centre are handled with a separate pay component or YouForce's cost allocation.

What KoppelHet does

KoppelHet builds the integration from scheduling to payroll per organisation. Several employers and checks on double bookings are part of the design. KoppelHet books approved hours without manual steps, shows before closing who still has unapproved hours and returns the status per period, so the planner sees what has been booked. As an indication, allow two to four weeks to go-live.

Common integrations

Dyflexis → Loket

Dyflexis to Loket integration: payroll hours and allowances per pay component, employees back

Quinyx → AFAS Profit

Quinyx to AFAS integration: worked hours and allowances to the payroll run, contracts and leave balance back

Planday → Visma Raet YouForce

Planday to YouForce integration: worked hours per employment to payroll

Planday → Nmbrs

Planday to Nmbrs integration: approved hours as variable hours in the right period, employees back

Protime → AFAS Profit

Protime to AFAS integration: calculated hours and absence to payroll, employees and contracts back

Shiftbase → Visma Raet YouForce

Shiftbase to YouForce integration: worked hours and surcharges to payroll, employees and contract hours to scheduling

Deputy → AFAS Profit

Deputy to AFAS integration: approved timesheets to the payroll run, employees and leave balance back

UKG Dimensions → Nmbrs

UKG Dimensions to Nmbrs integration: signed-off hours per pay code as variable hours in the right Nmbrs period

Frequently asked questions

How often are hours transferred?

We align this with the payroll run. Usually approved hours daily, with a final run just before closing.

Does the integration calculate the allowances?

No. Scheduling or payroll calculates; the integration transfers the hours per type. Where scheduling already calculates an amount, we leave it out if the payroll system calculates itself.

What happens to an hour type without a pay component?

The integration does not silently skip it. KoppelHet reports it, so no hours disappear unnoticed. We set the translation from hour type to pay component with payroll before the first run.