Hours to payroll

Hour corrections after the payroll period closes: without paying twice or too little

A correction to hours after a payroll period closes goes well when the integration knows whether the payroll system adds a new delivery or replaces the old one, and whether it may still book in an earlier period. KoppelHet therefore sends the full total of the period to Loket and Nmbrs, only the difference to Visma YouServe, and puts late hours in the current period with the original date when Nmbrs refuses an earlier one.

Last updated: 9 November 2026

Discuss your integration All about Leave, absence and time

What it is

Hours are still approved or changed after closing. A planner reopens a period, a team leader approves a shift late. Every payroll system handles that differently.

Loket overwrites a pay component if the same period and cost centre already exist. Nmbrs replaces a second delivery for the same period. AFAS gives no warning on a duplicate pay mutation that arrives through an integration. Anyone who does not know this pays hours twice or too little.

How the integration handles it

To Loket and Nmbrs the integration always sends the full period total on a correction, not just the difference, because a new delivery replaces the old one.
To Visma YouServe a correction goes as a new mutation with the difference, because YouServe processes an imported mutation file only once.
In AFAS the integration records per shift or per closed period whether it has been booked, so a period sent again is not paid twice.
Nmbrs refuses hours in an earlier period unless backdating is explicitly allowed. Late hours therefore land in the current period, with the original date and an alert for payroll.
If scheduling states the target period for the hours, as Dyflexis does, the integration books on that period, even if the planner only now sends last month's period.
A correction to YouForce goes as a new line with the original date. How YouForce settles it depends on how the pay component is set up; we agree that beforehand.

Edge cases we handle

If the planner reopens a locked period in Dyflexis and closes it again, the period gets a new identifier. Without the full total, Loket would double the hours.
AFAS can book hours in the shift's period or in the current payroll run. Shifts approved after closing are booked using your payroll department's method.
A delivery in YouForce can be blocked or rejected. The integration tracks the status and does not let a rejected line disappear silently.
Absence that changes in Protime after processing goes to YouForce as a correction with the original date.

What KoppelHet does

We agree how corrections run with payroll before the first payroll run: which period applies, what happens to hours after the delivery date and who gets an alert. The platform shows per payroll period how many lines were delivered, processed and rejected.

Common integrations

Dyflexis → Loket

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

Dyflexis → Nmbrs

Dyflexis to Nmbrs integration: locked payroll periods to Nmbrs, employees back to scheduling

Nmbrs → Shiftbase

Nmbrs to Shiftbase integration: staff and contracts to the schedule, hours back on the right hour code

AFAS Profit → Dyflexis

AFAS to Dyflexis integration: employees per employer to scheduling, paid hours back as payroll changes

Planday → Nmbrs

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

Protime → Nmbrs

Protime to Nmbrs integration: clocked hours per period to Nmbrs, employees and schedules back

Deputy → AFAS Profit

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

Nedap ONS → Visma YouServe

Nedap ONS to Visma YouServe integration: approved hours and irregular-hours pay to the payroll service, employees back into scheduling

Frequently asked questions

What if the planner closes a period again?

Then the integration sends the full total for that period again, or only the difference if the payroll system adds deliveries. That way hours are not paid twice.

Can hours still be booked in an earlier period?

That depends on the payroll system. Nmbrs refuses unless backdating is allowed; the hours then go to the current period with the original date.

How do we know all hours arrived?

The platform shows per payroll period how many lines were delivered, processed and rejected. Rejected lines get an alert with the reason.