Payroll integration
Oracle HCM to IRIS Payroll integration: UK starters and salaries from Oracle HCM Cloud in Staffology Payroll
An integration between Oracle HCM Cloud and IRIS Payroll (Staffology) creates a hire at the UK legal employer in Oracle as an employee in Staffology, with payroll code, starter declaration and PayOptions, and updates basic pay when the salary changes in Oracle. Leavers and rehires are reported to payroll, which completes the leaver and P45 in Staffology.
What the integration does
Organisations that record HR in Oracle HCM Cloud and run UK payroll in IRIS Staffology retype starters and pay rises in Staffology. A forgotten rise or a starter without a tax declaration then only shows up after the pay run.
- HR completes a hire at the UK legal employer in Oracle.
- KoppelHet reads the newhire feed and looks up in Staffology by payroll code whether the person already exists.
- A new person becomes an employee with starter details and their own PayOptions.
- A pay change from the empassignment feed adjusts payAmount and basis.
- Leavers, rehires and missing declarations go to payroll as a task.
What to watch for with Oracle HCM Cloud and IRIS Payroll
- Oracle reports a rehire in the same newhire feed as a new employee. Staffology has its own operation to rehire an employee and can look an employee up by payroll code. KoppelHet therefore searches by PersonNumber first and does not create a second employee for a known person.
- Staffology takes the employer's DefaultPayOptions when a new employee has no PayOptions of its own. KoppelHet therefore always sends the salary from the Oracle assignment on creation, so a UK starter does not enter the first pay run on the default amount.
- An annual salary in Oracle becomes an amount per period with basis Monthly in Staffology; an hourly rate becomes basis Hourly with the number of hours as payAmountMultiplier. KoppelHet calculates from the salary basis in Oracle, and an unknown basis goes to payroll.
- With NationalMinimumWage switched on, Staffology ignores the hourly rate and calculates the minimum wage by age. The flag only works with basis Hourly. KoppelHet never sets it from Oracle, so an hourly rate from the Oracle assignment is not silently replaced.
- Staffology wants a starter declaration A, B or C for a starter. Oracle records UK legislative data when it is set up, and the empupdate feed reports changes to it. If the declaration is missing on a hire, KoppelHet still creates the employee but puts the starter on payroll's list.
- The pay change arrives in Oracle's empassignment feed, which also carries manager and assignment changes. KoppelHet compares the salary with the current PayOptions in Staffology and only writes on a real difference, so a manager change causes no needless update in the current pay run.
- Oracle only reports employees, contingent workers and pending workers in the feeds. Only employees of the UK legal employer go to Staffology; a contractor from Oracle does not belong in UK PAYE processing.
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 Oracle's own UK payroll?
That is possible, but not every Oracle customer uses Oracle Payroll. This integration is for organisations that keep UK payroll in Staffology, in-house or with a bureau.
Does the FPS go to HMRC through the integration?
No. The RTI submission stays in Staffology with payroll.
Does this work with every IRIS payroll product?
This page is about Staffology Payroll, whose API is public. For other IRIS products we decide the route per project.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM Cloud through the employee Atom feeds (newhire, empassignment, empupdate, termination, cancelworkrelship) on /hcmRestApi/atomservlet/employee/ and the REST resource workers for names, addresses, workRelationships and assignments with salary.
- Staffology Payroll REST API with an API key. Create employee with personalDetails, employmentDetails (payrollCode, starterDetails) and payOptions; look up with Get Employee by Payroll Code; update PayOptions on the employee. Rehire an Employee and Mark as Leavers exist as operations, but stay with payroll in the first version.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in IRIS Payroll | Notes |
|---|---|---|
PersonNumber | employmentDetails.payrollCode | Key for lookups |
names (FirstName, LastName) | personalDetails (firstName, lastName) | |
addresses (thuisadres) | personalDetails.address | |
Start date van de work relationship | starterDetails.startDate | |
Legislatieve gegevens (starter declaration) | starterDetails.starterDeclaration | A, B or C; otherwise a task |
Salary (salary basis, amount) | payOptions (period, basis, payAmount, payAmountMultiplier) |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud