Recruitment to HR
Recruitee to Simployer integration: hired candidates with employment and salary in Simployer One
With an integration between Recruitee and Simployer, a candidate hired in Recruitee automatically arrives as an employee in Simployer One, with department, office, manager, employment, part-time percentage and the salary from the offer. The team is set too, so the new colleague is in the right place in the organisation on day one.
What the integration does
Organisations with Simployer One as HR system that recruit in Recruitee enter three things by hand in Simployer after every hire - the employee, the employment and the salary. If one is missed, the export to payroll is wrong.
- The recruiter marks the candidate as hired and fills in work email, start date, hours and salary in Recruitee.
- KoppelHet creates the employee in Simployer One, with department, office and manager.
- Then the employment follows, with type, start date, country and percentage.
- The salary from the offer is added as compensation effective on the start date.
- Finally KoppelHet links the employee to the job's team.
What to watch for with Recruitee and Simployer
- In Simployer One employee, employment and salary are separate objects. KoppelHet creates them one after another and stops if a step fails, so no employee is left without an employment.
- An employment requires a type, a country and a percentage. KoppelHet calculates the percentage from the hours in the offer and the full-time hours of the chosen employment type.
- A salary in Simployer requires not only the amount but also the period, such as month or year, the payout frequency, the payout day and whether overtime is paid. Recruitee only knows amount and currency, so HR records the rest per employment type in the integration.
- Simployer picks the country of an employment and of the national ID from a fixed list that includes NL. KoppelHet sets NL for a Dutch hire, and leaves the BSN empty for HR.
- Teams in Simployer are a separate link between employee and team. Recruitee only has a department, so KoppelHet sets the team from a table HR maintains.
- Simployer offers a sandbox next to production. KoppelHet tests the three steps there first with test candidates from Recruitee.
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
Are failed steps lost?
No. KoppelHet remembers at which step it stopped and continues from there once HR has fixed the cause.
What if the offer names no salary?
Then KoppelHet creates employee and employment and HR gets a task to enter the salary.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Recruitee reports the hire with the candidate_moved webhook and the hire stage category, signed in X-Recruitee-Signature; KoppelHet reads offer and profile fields with the ATS API.
- To Simployer One through the HRM One API (https://api.alexishr.com/v1, sandbox at api.sandbox.alexishr.com) with an access token as bearer. POST /employee (firstName, lastName, workEmail, privateEmail, title, departmentId, officeId, managerEmployeeId), POST /employment (required employeeId, userId, typeId, startDate, terminated, rate, country), POST /compensation (required employeeId, userId, amount, effectiveDate, currency, payoutDay, payoutPeriod, payoutFrequency, paidOvertime) and POST /employee-team-reference.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Simployer | Notes |
|---|---|---|
name | firstName en lastName | Recruitee name split |
Zakelijk e-mailadres (profielveld) | workEmail | |
emails[0] | privateEmail | |
Vacaturetitel | title | |
offer.department | departmentId | Through the department list from Simployer |
placement_locations[0] | officeId | |
E-mail leidinggevende (profielveld) | managerEmployeeId | |
Startdatum (profielveld) | employment.startDate | |
Uren per week (profielveld) | employment.rate | As a percentage of the employment type's full-time hours |
Profielveld salary (amount, currency) | compensation amount, currency, payoutPeriod |
Related
Recruitee → ADP Workforce Now
Recruitee to ADP Workforce Now integration: hired candidates as an in-progress hire
Recruitee → AFAS Profit
Recruitee to AFAS integration: from hired candidate to new employee
Recruitee → AlexisHR
Recruitee to AlexisHR integration: hired candidates as employees in Simployer One
Recruitee → BambooHR
Recruitee to BambooHR integration: hired candidates in BambooHR without clicking and retyping