Payroll integration
Dayforce to IRIS Payroll integration: UK new hires and basic pay from Dayforce in Staffology Payroll
An integration between Dayforce and IRIS Payroll (Staffology) creates a new employee of the UK org unit in Dayforce as an employee in Staffology, with payroll code, start date and their own PayOptions, and adjusts basic pay when compensation changes in Dayforce. Leavers are put on payroll's list well before the last pay run, and payroll handles the leaver and P45 in Staffology.
What the integration does
Organisations that use Dayforce for HR and run UK payroll in IRIS Staffology, in-house or through a bureau, email starters and pay rises to payroll. If a rise arrives after the cut-off day, a correction follows the next month.
- KoppelHet requests new employees of the UK units in Dayforce and reads them on their start date.
- KoppelHet looks up in Staffology by payroll code whether the person already exists.
- A new person becomes an employee with starter details and PayOptions from the Dayforce compensation.
- A changed compensation adjusts payAmount and basis.
- Leavers and missing starter declarations go on payroll's list.
What to watch for with Dayforce and IRIS Payroll
- Dayforce filters employees by org unit and hire date. KoppelHet only uses the UK units, so no employees from other countries end up in the Staffology employer of the UK entity.
- Staffology uses the employer's DefaultPayOptions when a new employee has none of its own. KoppelHet therefore reads the compensation in Dayforce with the start date as context date and always sends it along, so the first pay run uses the agreed pay rather than the default amount.
- A monthly salary from Dayforce becomes a fixed amount with basis Monthly in Staffology. An hourly rate becomes basis Hourly with the contracted hours as payAmountMultiplier. If the Dayforce employee is on weekly pay, period gets the value Weekly.
- With NationalMinimumWage on, Staffology calculates the minimum wage by age and ignores the hourly rate; the flag only works with basis Hourly. KoppelHet never sets it, so an hourly rate from Dayforce above the minimum is not replaced.
- KoppelHet finds compensation changes with Dayforce's update filter, limited to the compensation entities. Dayforce only applies that limit when both start and end date are passed; otherwise every changed employee comes back and KoppelHet compares far too many records.
- A starter in Staffology needs a starter declaration A, B or C. If it is not recorded in Dayforce, KoppelHet still creates the employee but puts the starter on the list with name and start date, so payroll fills in the declaration before the first pay run.
- With the termination date filter KoppelHet also sees leavers with a date after the next pay run. They already go on payroll's list, and payroll records the leaver in Staffology and produces the P45.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Why not Dayforce's own UK payroll?
That can be a good choice. This integration is for organisations that deliberately keep UK payroll in Staffology, for example with a bureau.
Do payslips go back to Dayforce?
Not in the first version. Staffology supplies payslips through the API; a flow back can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the REST API on /api/{clientName}/v1/Employees with OrgUnitXRefCode, FilterHireStartDate/EndDate, FilterTerminationStartDate/EndDate and FilterUpdatedStartDate/EndDate with filterUpdatedEntities, and expand for Addresses, WorkAssignments and CompensationSummary with contextDate.
- Staffology Payroll REST API with an API key per user. Create employee with personalDetails, employmentDetails (payrollCode, starterDetails) and payOptions; look up with Get Employee by Payroll Code; update PayOptions on the employee.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in IRIS Payroll | Notes |
|---|---|---|
EmployeeNumber | employmentDetails.payrollCode | Key for lookups |
FirstName, LastName | personalDetails (firstName, lastName) | |
Addresses (primair) | personalDetails.address | |
HireDate | starterDetails.startDate | |
CompensationSummary (salaris of uurloon) | payOptions (period, basis, payAmount, payAmountMultiplier) | |
Pay frequency | payOptions.period | Monthly or Weekly |
Related
Ashby → Dayforce
Ashby to Dayforce integration: have Dayforce validate the hire first, then save it
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce
Dayforce → 4PS Construct
Dayforce to 4PS Construct integration: technicians and site managers from Dayforce in 4PS, with cost centre and end date