Recruitment to HR
Recruitee to Cezanne HR integration: hired candidates through Cezanne's New Hire function
With an integration between Recruitee and Cezanne HR, a candidate hired in Recruitee automatically arrives as a new employee in Cezanne, with person record, employment at the right company and deployment in the org unit. Cezanne then starts the New Starter process with the HR user who owns the vacancy.
What the integration does
Organisations with Cezanne HR as HR system and Recruitee for recruiting put new employees into Cezanne by hand. If that happens without an address or company, the employment is missing, and the New Starter process for HR stays idle.
- The recruiter marks the candidate as hired and fills the start date and home address in Recruitee's profile fields.
- KoppelHet determines the company, org unit, position and vacancy owner in Cezanne for the job.
- KoppelHet calls Cezanne's New Hire function.
- Cezanne creates person record, employment and deployment and puts the starter under the org unit manager.
- The HR user gets the New Starter process task in Cezanne and completes the rest.
What to watch for with Recruitee and Cezanne HR
- Cezanne has a separate New Hire function for recruitment systems. It creates a person record, an employment and a deployment in one call and starts a New Starter process for HR.
- An employment is only created if a company code and a first address line are sent. Recruitee does not ask for an address, so KoppelHet makes sure the home address is in a profile field before the hire goes through.
- Without a date of birth Cezanne fills in today's date. KoppelHet does not let that happen and asks for the date of birth as a profile field, or holds the hire for HR.
- With an org unit the starter automatically reports to that unit's manager. A position can only be sent if there is also a unit, and then preferably as a code instead of the deprecated position title.
- The New Starter process only starts if the vacancy owner is a valid username in Cezanne and that user's role is linked to a New Hire process. KoppelHet translates the recruiter in Recruitee into that username.
- Only a user with the HR Professional role may add new employees through this function. The integration therefore runs on its own Cezanne user with that role and nothing more.
- Whether Cezanne picks the person code itself depends on the automatic numbering setting; otherwise the code gets the REC prefix by default. KoppelHet follows the customer's setting.
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 the New Hire function and not separate tables?
The function creates person, employment and deployment at once and starts the process for HR. Separate tables need more calls and miss that task.
Does the salary come along?
Not with the hire. Cezanne has a separate compensation table; that can come later as an extension.
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 with to_stage.category hire and the signature in X-Recruitee-Signature, plus the ATS API for offer and profile fields.
- To Cezanne through the OData data service with OAuth 2.0 - POST /People_NewHire with required firstName, familyName and hireDate (YYYYMMDD); also personId and employmentId (depending on automatic numbering), gender, birthDate, companyCode, orgUnitCode, positionCode, email, mobileNumber, address fields and vacancyOwner.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Cezanne HR | Notes |
|---|---|---|
name | firstName en familyName | Recruitee name split |
Startdatum (profielveld) | hireDate | Format YYYYMMDD |
Geboortedatum (profielveld) | birthDate | Format YYYYMMDD |
emails[0] | email | |
phones[0] | mobileNumber | |
Thuisadres (profielvelden) | addressLine1, city, postcode en country | Needed for the employment |
Vacature (vertaaltabel) | companyCode | |
offer.department | orgUnitCode | |
Positie bij de vacature | positionCode | |
Recruiter of hiring manager | vacancyOwner | Username in Cezanne |
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