Deel logoSimplicate logo

Accounts in applications

Deel to Simplicate integration: direct employees, EOR colleagues and freelancers in Simplicate

With an integration between Deel and Simplicate, everyone who onboards in Deel and books hours on projects automatically appears in Simplicate, with manager, team and the right type, whether a direct employee, an EOR colleague or a freelancer. On offboarding in Deel, KoppelHet closes the employee in Simplicate on the last working day and the administrator gets a task to block the user.

What the integration does

Organisations that hire people in several countries through Deel, partly through EOR and partly as freelancers, and that track projects and hours in Simplicate, add every new project worker to Simplicate by hand. A freelancer who has stopped often keeps costing a licence there for months.

  1. In Deel the onboarding of a new colleague or freelancer starts.
  2. KoppelHet picks up the change and checks whether the hiring type belongs in Simplicate.
  3. KoppelHet creates person and employee in Simplicate, with manager, team and the type in a custom field.
  4. The administrator invites the colleague as a user.
  5. On offboarding KoppelHet sets the end date and the administrator gets a task to block the user.
Deel → KoppelHet → SimplicateSOURCEDeelTARGETSimplicateKoppelHetmapping · logging · monitoringDeel → KoppelHet → SimplicateSOURCEDeelTARGETSimplicateKoppelHetmapping · logging · monitoring
Out: Person with name and work email · Employee with manager, status and type (direct, EOR or freelance) · Team based on the Deel team or department · Timetable end date

What to watch for with Deel and Simplicate

  • Deel distinguishes direct employees, EOR employees, contractors and PEO. Freelancers in particular often book hours in Simplicate. KoppelHet includes per type what you agree on, and puts the type in a custom field, because the Simplicate API does not let you write the employee type itself.
  • Someone can have several contracts in a row in Deel, for example first as a freelancer and later through EOR. For Simplicate it stays one person with one hours history. KoppelHet therefore links on the person in Deel, not on the contract.
  • The onboarding status in Deel comes before the first working day. KoppelHet prepares the colleague in Simplicate at that point, so the project lead can schedule them; the administrator only invites once the status becomes active.
  • Deel includes the manager's work email. Simplicate wants an existing employee as manager. KoppelHet looks them up by work email; if the manager is not in Simplicate, the field stays empty and they appear on a list for the administrator.
  • Departments in Deel have a parent department, and teams sit per contract. Teams in Simplicate are a flat list the API can only read. KoppelHet translates the Deel team or department to an existing Simplicate team and reports an unknown value.
  • Deel disables a webhook subscription after ten failed attempts in a row, and it then has to be switched on again by hand. KoppelHet monitors the subscriptions and compares the Deel list with Simplicate daily, so a missed offboarding is still picked up.
  • Simplicate cannot invite or block users through its public API. For freelancers on short contracts, that is the biggest risk of a forgotten licence. KoppelHet gives the administrator a task on the last working day from Deel, and keeps reminding them as long as the user is active.

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 · Basic

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

Do EOR colleagues abroad also go into Simplicate?

If they book hours on projects, yes. Per hiring type in Deel we record at the start who goes in.

Do freelancer rates come along?

No. Rates cannot be written through the Simplicate API. The controller sets them in Simplicate.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Deel through the REST API with an API token: GET /people with hiring_types (direct_employee, eor, contractor, peo) and hiring_statuses (onboarding, active, offboarding, inactive), fields with dot notation, and per person employments with work_email, team, start_date and termination_last_day; direct_manager with work_email and department with parent. Webhooks with x-deel-signature (HMAC-SHA256), 30 second response time, ten attempts up to 16 hours and disabling after ten failures in a row; event types through GET /webhooks/events/types.
  • Simplicate REST API v2 (Authentication-Key and Authentication-Secret; at least 60 requests per minute): POST /crm/person (first_name, family_name_prefix, family_name, email, teams), POST and PUT /hrm/employee (only person_id, supervisor, status and custom_fields), PUT /hrm/timetable for end_date. Teams and employee types read-only; no users endpoint.

Which fields are transferred

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

Field in DeelField in SimplicateNotes
id (persoon in Deel)Eigen veld bij de medewerker (custom_fields)Fixed key across all contracts
first_name en last_namefirst_name, family_name_prefix, family_name (persoon)
employments[].work_emailemail (persoon)
hiring_typeEigen veld met de soortdirect_employee, eor or contractor
direct_manager.work_emailsupervisor (medewerker)Looked up by work email in Simplicate
employments[].team of departmentteams (persoon)Lookup to existing teams
hiring_statusstatus (medewerker)
termination_last_dayend_date (rooster) en taak voor de beheerder

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.