Recruitment to HR
Teamtailor to Simployer integration: hired candidates with employment and salary in Simployer One
Simployer itself imports a candidate set to Hired in Teamtailor into Simployer One, with name, contact details, job title and photo, as a candidate or as a new hire. KoppelHet is needed when the employment, the salary and the team from the Teamtailor offer must also be in Simployer straight away.
What the integration does
Organisations that recruit in Teamtailor and use Simployer One as their HR system, often with offices in Scandinavia and the Netherlands, import hired candidates with Simployer's integration. HR then still retypes contract and salary from the offer, and an employee without an employment falls outside reports and leave.
- The recruiter moves the candidate to Hired; the Teamtailor offer contains start date, hours and salary.
- KoppelHet creates the employee in Simployer with work email, department, office and manager.
- Then follows the employment with type, country, start date and rate.
- The salary is added with the fixed values per employment type that HR has recorded.
- Finally KoppelHet places the employee in the right team.
What to watch for with Teamtailor and Simployer
- Simployer's import takes over name, contact details, title and photo. Employment and salary are separate objects in Simployer One; KoppelHet creates them after the employee, and stops with a notification if a step fails, so no half-created employee remains.
- An employment in Simployer requires a rate relative to the full-time hours of the employment type. KoppelHet calculates it from the hours in the Teamtailor offer, so a hire for 32 hours in a 40-hour full-time type comes out at 80 percent.
- With Simployer's import you choose whether a profile arrives as a candidate or as a new hire; Simployer recommends new hire. KoppelHet creates an employee with employment straight away, so onboarding and leave accrual in Simployer run from the start date.
- A salary in Simployer requires not only amount and currency but also the period, the payout frequency, the payout day and whether overtime is paid. Teamtailor only knows the amount from the offer; HR records the rest per employment type in the integration.
- Simployer picks the country of an employment from a fixed list. KoppelHet derives it from the job location in Teamtailor, so a hire for the Utrecht office arrives as NL and not as the country of headquarters.
- For Simployer Classic there is a separate integration on Teamtailor's Hire trigger, which takes over name, address and national ID number through custom fields. This page is about Simployer One; with Classic we first check whether that integration is enough.
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
Why not just Simployer's import?
It is enough if HR enters contract and salary in Simployer itself. If they come from the Teamtailor offer, KoppelHet adds them straight away.
Does the BSN come along?
No. HR adds the BSN in Simployer; it does not belong in the recruitment system.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Teamtailor through the company webhook job_application.update on a stage of type hired (signature in TT-Signature) and the Teamtailor API (job-applications, candidates, jobs with department and locations, job-offers with start-date and salary, onboarding with work-email).
- Simployer One through the HRM One API (https://api.alexishr.com/v1, sandbox at api.sandbox.alexishr.com, bearer access token) - POST /employee (firstName, lastName, workEmail, privateEmail, departmentId, officeId, managerEmployeeId), POST /employment (employeeId, userId, typeId, startDate, terminated, rate, country), POST /compensation (amount, currency, effectiveDate, 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 Teamtailor | Field in Simployer | Notes |
|---|---|---|
first-name en last-name | firstName en lastName | |
Werkmail uit de onboarding | workEmail | |
email van de kandidaat | privateEmail | |
Department | departmentId | Lookup table |
Locatie van de vacature | officeId | |
Startdatum en uren uit het aanbod | employment startDate en rate | |
Salaris uit het aanbod | compensation amount, currency en effectiveDate | |
Division of afdeling | employee-team-reference |
Related
Teamtailor → ADP Workforce Now
Teamtailor to ADP Workforce Now integration: hired candidates as in-progress hires
Teamtailor → AFAS Profit
Teamtailor to AFAS integration: hired candidates straight in as new employees
Teamtailor → BambooHR
Teamtailor to BambooHR integration: hired candidates as employees in BambooHR
Teamtailor → BuddeeHR
Teamtailor to BuddeeHR integration: hired candidate as a new employee in BuddeeHR