Payroll integration
Dayforce to Silae integration: French employees and pay changes from Dayforce in mySilae Paie
An integration between Dayforce and Silae creates a new employee of the French org unit in Dayforce as a salarié with an emploi in mySilae Paie, and updates that emploi when work assignment or pay changes in Dayforce. The Silae API with write access is only for Silae partners, so the integration runs on the API account of the accounting firm or reseller that handles French payroll.
What the integration does
Organisations that use Dayforce as their HR system for several countries and keep French payroll with a firm in Silae send a list of new French employees, pay changes and leavers every month. The firm retypes it, and a backdated rise then falls outside the right period.
- KoppelHet requests the employees of the French org units in Dayforce with a hire date in the past period or later.
- For each employee KoppelHet reads address, work assignment and compensation on the start date and checks the NIR.
- KoppelHet creates the salarié with an emploi based on the firm's model employee.
- Changed work assignments and compensation go to the existing emploi.
- Leavers go on the firm's list with their date, and the firm chooses the leaving reason in Silae.
What to watch for with Dayforce and Silae
- Dayforce can filter employees by org unit. KoppelHet only requests the French units, so employees from other countries never end up in a Silae dossier, and links each unit to the numeroDossier of the right French company.
- Without a context date Dayforce returns today's version. KoppelHet reads a French hire for next month on the start date itself, so the emploi in Silae starts with the work assignment and pay valid on that day.
- Silae rejects an emploi with a contract date after its start date and then creates a salarié without an emploi. KoppelHet fills both with the hire date from Dayforce, and reports an employee with a different contract date to the firm rather than creating them halfway.
- KoppelHet fetches changes with the update date filter, limited to work assignments, employment status and compensation. Dayforce ignores that limit unless both start and end date are passed, so KoppelHet always sends both.
- A pay change from Dayforce goes to the existing emploi with the number Silae returns through ListeSalarieEmplois. With emploi number 0 Silae would open a new emploi, and there would be two running contracts on the payslip.
- Data only comes back from Dayforce when the API account's role has the authorisation for personal information. An empty NIR is therefore a rights check first; without a valid fifteen-character NIR KoppelHet creates no salarié.
- Dayforce's termination date filter also returns leavers with a future date. Silae has a coded list of leaving reasons; KoppelHet passes on the date and lets the firm choose the right code, because Dayforce reasons do not map one to one.
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 Dayforce not pay France itself?
This integration is for organisations that deliberately keep French payroll with a firm in Silae. Which countries Dayforce pays itself is separate from this page.
Does leave from Dayforce also go to Silae?
Not in the first version. Silae counts absence according to the dossier settings; 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.
- Dayforce through the REST API on /api/{clientName}/v1/Employees with OrgUnitXRefCode, FilterHireStartDate/EndDate, FilterTerminationStartDate/EndDate and FilterUpdatedStartDate/EndDate with filterUpdatedEntities, and per employee expand for Addresses, WorkAssignments, EmploymentStatuses and CompensationSummary with contextDate.
- Silae payroll API with OAuth 2.0 on the partner account. POST /v1/SalarieEmplois/CreationSalarieEmplois with identifiantEmploi (0 for new), matriculeSalarieModele, copieIntegraleSalarieModele false and b flags per field; ListeSalarieEmplois first. numeroDossier per French company.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Silae | Notes |
|---|---|---|
XRefCode | matriculeSalarie | Key; never empty |
LastName | nomNaissance | Required |
FirstName | prenom | |
National ID (FRA) | numeroSecuriteSociale | Fifteen characters with key |
Addresses (postcode) | codePostal met calculerCommune | |
HireDate | dateDebutContrat en dateDebut | |
CompensationSummary (basisloon) | salaireDeBase |
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