Payroll integration
SAP SuccessFactors to IRIS Payroll integration: UK starters, pay and leavers from Employee Central in Staffology
An integration between SAP SuccessFactors and IRIS Staffology Payroll creates UK workers from Employee Central as an employee with starter details and PayOptions, updates their pay and marks leavers with the leave date. Staffology has an open REST API, so the integration writes straight into the UK employer without a CSV import.
What the integration does
Organisations that use Employee Central worldwide and run UK pay in IRIS Staffology Payroll send UK joiners and leavers to payroll by email. There, name, NI number and salary are entered again in Staffology, and a leaver already confirmed in SuccessFactors only gets a P45 when someone notices.
- HR records a hire at the UK legal entity in Employee Central.
- KoppelHet reads person, address, NI number and compensation through OData, including entries with a future effective date.
- KoppelHet creates the employee in the UK employer with the personIdExternal as payrollCode and the PayOptions from SuccessFactors.
- On a pay change KoppelHet reads the employee and writes the complete record back with the new amount.
- On a termination KoppelHet sets the leaver details with leaveDate; payroll produces the P45 in Staffology.
What to watch for with SAP SuccessFactors and IRIS Payroll
- A recurring pay component in Employee Central has its own frequency, such as annual. Staffology works with period, basis and payAmount. KoppelHet converts an annual salary from SuccessFactors into an amount per UK period with basis Monthly, and an hourly rate into basis Hourly.
- Staffology has no PATCH; a PUT must contain all writable fields. A pay change in SuccessFactors touches only one field. KoppelHet therefore first reads the employee in Staffology and writes the whole record back, so what payroll entered in Staffology stays in place.
- Staffology records a leaver in the leaver details with hasLeft and leaveDate. There are also fields for payment after leaving and paying out the accrued balance. KoppelHet only sets hasLeft and the end date from EmpEmploymentTermination; payout choices stay with payroll.
- After marking a leaver, Staffology produces the P45, and payroll can email it when the employee has an email address. KoppelHet therefore sends the personal email from PerEmail on creation, because the work address often stops working after leaving.
- Staffology has a separate function to rehire a former employee. A rehire in Employee Central uses the same personIdExternal; KoppelHet looks up the employee by payrollCode and uses that rehire function instead of creating a second employee.
- PerNationalId stores numbers per country. Staffology wants the UK National Insurance number. KoppelHet only takes the number with country GBR; if a starter has none, the starter still goes through and payroll gets a message to complete it.
- Without its own PayOptions a new Staffology employee gets the employer's default settings. KoppelHet reads a SuccessFactors starter with a future start date with fromDate and toDate, so they are in the first UK run with their own pay.
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
Does the starter declaration also go across?
Only if SuccessFactors has a field for it. Otherwise payroll fills in A, B or C in Staffology.
Do payslips come back to SuccessFactors?
Not in the first version; that 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.
- SuccessFactors through OData v2: PerPerson, PerPersonal, PerEmail, PerNationalId, PerAddressDEFLT, EmpEmployment, EmpJob (filter on company and lastModifiedDateTime), EmpPayCompRecurring and EmpEmploymentTermination. OAuth 2.0 with SAML bearer assertion.
- Staffology Payroll REST API with an API key as password in Basic authentication, rights equal to the user per employer. POST /employers/{employerId}/employee, GET and PUT on /employers/{employerId}/employee/{id} (full JSON), lookup by payroll code, leaverDetails (hasLeft, leaveDate) and the rehire operation.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in IRIS Payroll | Notes |
|---|---|---|
PerPerson.personIdExternal | employmentDetails.payrollCode | Fixed key |
PerPersonal.firstName, lastName | personalDetails.firstName, lastName | |
PerPerson.dateOfBirth | personalDetails.dateOfBirth | |
PerNationalId (country GBR) | personalDetails.niNumber | |
PerAddressDEFLT | personalDetails.address | |
EmpEmployment.startDate | starterDetails.startDate | |
EmpPayCompRecurring (paycompvalue, frequency) | payOptions.payAmount, basis, period | Converted to the UK period |
EmpEmploymentTermination.endDate | leaverDetails.hasLeft en leaveDate |
Related
Ashby → SAP SuccessFactors
Ashby to SAP SuccessFactors integration: hire as a new employee in Employee Central
Bullhorn → SAP SuccessFactors
Bullhorn to SAP SuccessFactors integration: placements as employees or contingent workers in Employee Central
Carerix → SAP SuccessFactors
Carerix to SAP SuccessFactors integration: successful placement as a new employee in Employee Central
Greenhouse → SAP SuccessFactors
Greenhouse to SAP SuccessFactors integration: a hire as a new employee in Employee Central