Payroll integration
Oracle HCM to Silae integration: French hires, pay and leavers from Oracle HCM Cloud in mySilae Paie
An integration between Oracle HCM Cloud and Silae turns a hire at the French legal employer in Oracle into a salarié with an emploi in mySilae Paie, and sends later pay and job changes to that same emploi. Writing to Silae runs through the API account of a Silae partner, usually the firm that processes French payroll.
What the integration does
Organisations that record HR worldwide in Oracle HCM Cloud and have French payroll processed in Silae by an accounting firm often email new French colleagues and pay rises to that firm as a form. A hire cancelled in Oracle then sometimes only reaches the firm after the first payroll run.
- HR records a hire at the French legal employer in Oracle and assigns the French payroll.
- KoppelHet reads the newhire feed, fetches the worker through the REST API and checks the NIR.
- KoppelHet creates the salarié with an emploi in the Silae dossier of that legal employer, based on the firm's model employee.
- Pay changes from the assignment feed go to the existing emploi.
- A cancelled hire or a changed start date goes to the firm as a task.
What to watch for with Oracle HCM Cloud and Silae
- Oracle already sends a newhire event as soon as a future-dated hire is saved. Silae rejects an emploi whose contract date is after its start date and then creates a salarié without an emploi. KoppelHet fills both dates with the start date of the Oracle work relationship, so that does not happen.
- The newhire feed also reports a rehire. Because Silae recognises an employee by the matricule, KoppelHet first looks up the PersonNumber from Oracle. If the salarié already exists, they get a new emploi instead of a second record.
- Silae only generates a matricule itself when that option is enabled in the company dossier, and a salarié without a matricule cannot be reached through the API. KoppelHet therefore always sends the Oracle PersonNumber, whatever the firm's setting.
- A pay change arrives in Oracle through the empassignment feed, together with manager and assignment changes. KoppelHet first fetches the existing emploi IDs from Silae and writes only the salary to that emploi; an ID of 0 would create a new emploi.
- Oracle has a separate feed for a cancelled work relationship, for example after a no-show or a rejected offer. KoppelHet then deletes nothing in Silae, but puts the salarié on the firm's list with the reason from Oracle.
- When creating an employee, Silae copies settings from a model employee. KoppelHet sets copieIntegraleSalarieModele to false, so the collective agreement and status come from the model but name and address come from Oracle, and picks the model per French legal employer.
- The Oracle feeds only report employees, contingent workers and pending workers. A pending worker does not yet have a final hire; KoppelHet only creates a salarié once it is an employee with the French payroll from the payupdate feed.
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 leave from Oracle also go to Silae?
Not in the first version. Silae counts absence according to the dossier settings, so it needs agreements per leave type; it can be added later as an extension.
Who arranges the API account?
Silae reserves the API models with write access for Silae partners. Usually that is the accounting firm; they enable access per dossier.
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 on /hcmRestApi/atomservlet/employee/ (newhire, empassignment, payupdate, termination, cancelworkrelship, workrelshipupdate) and then the REST resource workers for names, addresses, nationalIdentifiers, workRelationships and assignments.
- Silae through the payroll API with OAuth 2.0 on a partner account. Create and change with POST /v1/SalarieEmplois/CreationSalarieEmplois (identifiantEmploi 0 for new, existing number to change, ListeSalarieEmplois first), with matriculeSalarieModele and b flags per field. Every call names the numeroDossier.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Silae | Notes |
|---|---|---|
PersonNumber | matriculeSalarie | Key in Silae |
names (LastName) | nomNaissance | Required |
names (FirstName) | prenom | |
nationalIdentifiers (FRA) | numeroSecuriteSociale | Fifteen characters with key |
addresses (postcode) | codePostal met calculerCommune | Silae fills in the commune |
Start date van de work relationship | dateDebutContrat en dateDebut | |
Salary (assignment) | salaireDeBase |
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