Deel logoSilae logo

Payroll integration

Deel to Silae integration: own French employees from Deel as a salarié with an emploi in the Silae dossier

An integration between Deel and Silae creates an own employee of the French legal entity in Deel as a salarié with an emploi in the firm's Silae dossier, with NIR, contract type, start date and base pay. EOR employees in France and contractors in Deel stay out of Silae, and writing goes through the API account of the firm that runs French payroll.

What the integration does

Organisations that use Deel as their global HR system and have their own French SAS paid by a firm in Silae send the firm a form for every French hire. The payroll officer copies name, NIR, contract form and pay, and a fixed-term contract in Deel sometimes ends up in Silae as a CDI.

  1. HR records an own employee at the French legal entity in Deel.
  2. On the Employee Created Direct webhook KoppelHet checks the legal entity and fetches the full profile.
  3. KoppelHet creates the salarié with one emploi in the dossier of the French entity, based on the firm's model employee.
  4. A pay change goes to the same emploi; a last working day waits for the reason from HR and then goes through.
  5. Rejections from Silae go on a list for the firm, with the error message.
Deel → KoppelHet → SilaeSOURCEDeelTARGETSilaeKoppelHetmapping · logging · monitoringDeel → KoppelHet → SilaeSOURCEDeelTARGETSilaeKoppelHetmapping · logging · monitoring
Out: Salarié with name and NIR · Emploi with CDI or CDD and start date · Base pay, monthly or hourly · End date with reason

What to watch for with Deel and Silae

  • Deel's guide for own employees calls this the case where the employee is paid through your own payroll provider. KoppelHet only takes those employees and only the French legal entity, so someone Deel pays as EOR in France does not also get a payslip from Silae.
  • Writing in Silae is only allowed in the API model for internal HR use, which is reserved for partners such as accountants and payroll bureaus. An organisation with Deel usually has no such contract. KoppelHet therefore works with the firm's client credentials, and the firm opens the API per dossier.
  • In the Deel profile end_date is empty for an open-ended contract and filled for a fixed-term one. Silae wants a codeContratTravail. KoppelHet derives 01 for a CDI or 02 for a CDD from it, so the firm does not have to get the contract form from an email.
  • Deel stores pay with a scale, ANNUAL by default, and also knows HOURLY. Silae takes a salaireDeBase with a flag for whether it is an hourly wage. KoppelHet converts an annual salary to a monthly amount, sends an hourly wage with the flag on, and holds back an amount in a currency other than euro.
  • Silae rejects a salarié without a valid fifteen-character NIR. Deel only returns national numbers in additional_details if the feature flag is on and the request does not redact personal data. If the number is missing, KoppelHet does not create a partial salarié but puts the starter on the firm's list.
  • For a leaver Silae asks for a motifFinEmploi besides dateFin, such as 010 for resignation by the employee. Deel's people list does give the last working day, but no French reason code. KoppelHet asks HR or the firm to choose the reason and only then sends both fields together.
  • Silae only accepts characters from Windows-1252, while Deel stores names from every country. KoppelHet converts letters outside that set, and those employees go on a check list for the payslip.

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, architecture and compliance

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.

Price indication · Complex

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Does the firm need to do anything?

Yes. The firm opens the API for the dossier, provides the client credentials and chooses a model employee for new salariés.

Do time off and variables go across as well?

Not in the first version. Absence and bonuses can follow 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.

  • Deel through the HRIS API with a bearer token: Employee Created Direct and Employee Updated Direct webhooks (legal_entity_id, contract_oid, start_date, gross_annual_salary), GET /rest/people for name, employments and direct_employee_termination_last_day; additional_details only with feature flag.
  • Silae through https://payroll-api.silae.fr/payroll with the firm's OAuth 2.0 client credentials: POST /v1/SalarieEmplois/CreationSalarieEmplois with numeroDossier, matriculeSalarieModele, codeContratTravail and salaireDeBase; ListeSalarieEmplois for the emploi ID; dateFin and motifFinEmploi on a leaver.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in DeelField in SilaeNotes
Webhook Employee Created Direct (legal_entity_id)numeroDossier van de Franse entiteit
Deel profiel-idmatriculeSalarieFixed key between both systems
last_name, first_namenomNaissance, prenom
additional_details (NIR)numeroSecuriteSocialeOnly with feature flag in Deel
employment.end_date (leeg of gevuld)codeContratTravail (01 CDI, 02 CDD)
employment.start_datedateDebutContrat en dateDebut
compensation_details (salary, currency, scale)salaireDeBase met salaireDeBaseEstHoraire
direct_employee_termination_last_day plus motif van HRdateFin en motifFinEmploi

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.