Recruitment to HR
Recruitee to SAP SuccessFactors integration: new hires straight into Employee Central
With an integration between Recruitee and SAP SuccessFactors, a candidate hired in Recruitee automatically appears as a new employee in Employee Central, at the right Dutch company, with department, job and start date. The shared service centre no longer retypes anything or asks by email.
What the integration does
Organisations with SAP SuccessFactors as global HR system that recruit in the Netherlands through Recruitee enter every new colleague into Employee Central again, often through a shared service centre. It does not always know which company, department and job code belong to the vacancy, and asks by email.
- The recruiter marks the candidate as hired. Recruitee passes the vacancy with department and the location.
- KoppelHet fetches date of birth, nationality, start date and job and uses the location to determine the company in Employee Central.
- The new employee then appears in Employee Central, with person, employment and job data.
- If something goes wrong, the integration stops and the SAP error message shows in the KoppelHet platform.
- If the candidate is rejected in Recruitee afterwards, HR gets a notice to reverse the hire in Employee Central.
What to watch for with Recruitee and SAP SuccessFactors
- Employee Central expects a fixed order for a new hire, first the person, then the employment, and only then the job data. KoppelHet enforces that order, so no employment is created without a person.
- Recruitee passes the location's country with the hire. If the organisation also recruits for other countries in Recruitee, each candidate goes to their country's company in Employee Central.
- Nationality is stored in Recruitee as a country code, Employee Central uses its own picklist. KoppelHet translates the code, so creation does not fail on an unknown value.
- Dutch fields such as the BSN must be configured in Employee Central. They do not come from Recruitee; HR or local payroll completes them after the hire.
- If a candidate is rejected after being hired, KoppelHet deletes nothing in Employee Central but notifies HR, because withdrawing a hire in SAP follows its own process.
- SAP is phasing out its older integration method for Employee Central. KoppelHet only uses the method SAP supports for new hires.
- Departments and jobs have their own codes in Employee Central. The Recruitee department name goes to the right code through a lookup table; a new department without a translation raises a notice.
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
Do we use SuccessFactors Onboarding for this?
It can, but it does not have to. KoppelHet puts the employee directly into Employee Central. If you use Onboarding, we agree where the candidate should land.
Does this work for countries other than the Netherlands?
Yes, if those countries recruit in Recruitee. The location decides the company; required fields can differ per country.
What if the shared service centre already created the employee?
KoppelHet first searches by name and date of birth. On a match the integration does not create a second person but puts the match to HR.
Do you build the Recruitee side from scratch for us?
No. KoppelHet is a Recruitee partner and already has the connection to Recruitee. For SuccessFactors we set up the lookup tables per customer.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Recruitee is read through the candidate_moved webhook to a stage with the hire category (with candidate, offer.department and placement_locations with country_code) and the ATS API for profile fields.
- SAP SuccessFactors Employee Central is written through OData v2 upserts in the order PerPerson and PerPersonal, EmpEmployment and EmpJob with a hire event; PerEmail and PerPhone for contact details; personIdExternal as the key.
- Departments and job codes are foundation objects (FODepartment, job classification). The Employee Central SOAP APIs are deprecated, except for the CompoundEmployee API. API user with OAuth and write access to the person, employment and job entities.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in SAP SuccessFactors | Notes |
|---|---|---|
id (kandidaat) | personIdExternal | Or a separate number range; agreed per customer |
name | PerPersonal: voornaam en achternaam | Split from the single Recruitee name field, with care for name prefixes |
Profielveld date_of_birth | PerPerson: geboortedatum | |
Profielveld nationality (country_code) | PerPersonal: nationaliteit | Translate the country code to the Employee Central picklist value |
emails[0] | PerEmail (privé) | |
phones[0] | PerPhone | |
placement_locations[0].country_code | EmpJob: bedrijf (company) | NL goes to the Dutch company |
offer.department | EmpJob: afdeling | Through a lookup to FODepartment |
Startdatum (profielveld) | EmpEmployment en EmpJob: startdatum | |
Functie (profielveld) | EmpJob: functiecode | Through a lookup to the job classification |
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