From hire to HR
Hiring for several employers and countries: every hire to the right entity
When an organisation hires for several entities or countries in one ATS, the integration decides per vacancy which employer or HR system a hired candidate goes to. KoppelHet derives that from the vacancy, the location or a choice field on the offer, for example from Recruitee to the right company in Nmbrs or Loket, or from Greenhouse and SmartRecruiters only the Dutch hires to AFAS.
What it is
An ATS often has no notion of employer or legal entity. Recruitee does not, and Greenhouse and SmartRecruiters often serve all of an organisation's countries at once. The HR system works per employer: in Nmbrs each entity is its own company, with its own departments and jobs.
Without a fixed rule a candidate for home care ends up with the nursing home's employer, or a Belgian hire under the Dutch entity.
How the integration handles it
- The employer follows from the vacancy or from a choice field on the offer form, for example with three employers in Loket or several companies in Nmbrs.
- The vacancy's office or location decides whether the candidate goes to the Dutch HR system. Hires for other countries are skipped or sent to their own HR system.
- Departments and jobs exist per company in Nmbrs. If the department does not exist in the chosen company, the integration reports it instead of creating a department in payroll itself.
- In SmartRecruiters the integration gets its own access that only sees what belongs to the Dutch vacancies.
- With Deel the integration chooses by country and contract type whether it becomes an EOR contract, a contractor agreement or a contract with your own entity. Hires for your own Dutch entity go to your own HR system.
- An offer in another currency or as an annual salary is recognised and converted to the Dutch gross monthly salary, with a check that the amount is in euros.
Edge cases we handle
- Departments in Greenhouse can be nested, and jobs are often named globally. Per department and job we record the YouForce code; if it is missing, the integration stops with an alert.
- When the organisation recruits for several countries in Recruitee, the vacancy's site decides the location in Dayforce. A Belgian site never ends up under the Dutch entity.
- Oracle works in FTE. The integration converts the weekly hours from the offer against the full-time week of the Dutch entity.
- The BSN does not belong in an ATS that is often managed in the United States. HR enters it during onboarding in the Dutch HR system.
What KoppelHet does
We settle the rules per employer and country in the design, together with HR and payroll: which field decides the entity, which countries are included and what happens to a vacancy without a choice. A value that does not fit produces an alert, not a candidate with the wrong employer.
Common integrations
Recruitee → Loket
Recruitee to Loket integration: hired candidates automatically as draft employees in Loket
Greenhouse → AFAS Profit
Greenhouse to AFAS integration: an accepted offer starts onboarding in AFAS Profit
SmartRecruiters → AFAS Profit
SmartRecruiters to AFAS integration: hired candidate starts onboarding, status back to SmartRecruiters
Greenhouse → Visma Raet YouForce
Greenhouse to YouForce integration: hired candidate as a hire request
Recruitee → Dayforce
Recruitee to Dayforce integration: hired candidates in Dayforce without retyping
Recruitee → Deel
Recruitee to Deel integration: from hired candidate to a contract in Deel
Workable → Workday
Workable to Workday integration: hired candidates as pre-hire and hire in Workday
Recruitee → UKG Pro
Recruitee to UKG Pro integration: European hires through the Global New Hire service in UKG Pro
Frequently asked questions
Our ATS has no employer field. How does the integration know which entity someone belongs to?
We derive the entity from the vacancy or add a choice field to the offer form. Which of the two fits is decided in the design.
What happens to hires for Belgium or Germany?
They do not go to the Dutch HR system. If that country's HR system can receive data, KoppelHet can send those hires there.
Does the integration create departments in the HR system itself?
No. If a department does not exist, an alert follows. HR or payroll creates the department or completes the translation.
More on Recruitment to HR
Recruitment to HR: the overview
From hire to HR
- Hired candidate to HRThe Hired stage starts onboarding, with the offer already filled in.
- Multiple employers and countriesEvery hire with the right entity, country and HR system.