Teamtailor logoOracle HCM Cloud logo

Recruitment to HR

Teamtailor to Oracle HCM integration: hired candidate as a future worker in Oracle

With an integration between Teamtailor and Oracle HCM Cloud, a candidate hired in Teamtailor arrives in Oracle as a future worker, at the right employer and with start date, location and hours. HR in Oracle completes onboarding and converts the future worker, so nobody needs to retype the candidate from Teamtailor.

What the integration does

Organisations that run HR in Oracle HCM Cloud and recruit in Teamtailor now enter a hired candidate in Oracle by hand, often only in the week someone starts. Accounts and workplace are therefore not ready on the first day.

  1. The recruiter moves the candidate in Teamtailor to the stage of the hired type.
  2. KoppelHet fetches the application with candidate, vacancy, division, location and the offer.
  3. In Oracle a future worker appears at the employer of that country, with start date, location and hours.
  4. HR adds the BSN and other data in Oracle and converts the future worker once onboarding is complete.
  5. If the candidate is rejected in Teamtailor later, HR gets a notification.
Teamtailor → KoppelHet → Oracle HCM CloudSOURCETeamtailorTARGETOracle HCM CloudKoppelHetmapping · logging · monitoringTeamtailor → KoppelHet → Oracle HCM CloudSOURCETeamtailorTARGETOracle HCM CloudKoppelHetmapping · logging · monitoring
Out: Future worker with name, date of birth and address · Employer from the division and country of the vacancy · Start date and work email · Location, department and hours · Notification on an error or later rejection

What to watch for with Teamtailor and Oracle HCM Cloud

  • Oracle has a future worker who is not yet employed. KoppelHet creates the hired candidate in that form, and HR in Oracle decides when they become a worker.
  • Divisions in Teamtailor split vacancies over countries or business units, and Oracle works with an employer per country. Per division and country we record which employer in Oracle belongs to it.
  • With Teamtailor onboarding, start date and work email are already on the candidate. KoppelHet takes both to Oracle, so IT can prepare the account in time.
  • Oracle works in FTE, and Teamtailor has no hours per week. We add a number field for hours to Teamtailor, and KoppelHet converts it against the employer's full-time week.
  • Custom fields in Teamtailor have a fixed type. Date of birth and start date are recorded as date fields and hours as a number, so Oracle does not reject a value entered as free text.
  • The Teamtailor candidate number goes along to Oracle. If the same application comes in again, for example after a changed start date, KoppelHet updates the existing future worker.
  • Teamtailor limits the number of requests per short period. After a recruitment day with many hires KoppelHet spreads the requests, so no hire gets lost.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Is the hired candidate a worker in Oracle straight away?

No, first a future worker. HR in Oracle converts them once onboarding is complete.

If we recruit for several countries in Teamtailor, does it still work?

Yes. Division and country of the vacancy determine the employer in Oracle, and we record that at the start.

What if a candidate withdraws after the hire?

HR then gets a notification. KoppelHet deletes nothing in Oracle itself; HR decides.

What about the GDPR?

You are the controller and KoppelHet is the processor, under a data processing agreement. Only data of hired candidates goes to Oracle, and every action is in the audit logging.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Teamtailor is read through the job_application.update webhook to a stage of the hired type and the Teamtailor API (job-applications, candidates, jobs with department, division and locations, job-offers and the onboarding add-on with start-date and work-email). Custom fields of type CustomField::Date and ::Number.
  • Oracle HCM Cloud is written through the workers REST API as a pending worker (worker type P) with ProjectedStartDate, LegalEmployerName, LocationCode, DepartmentName and workMeasures (FTE); the Teamtailor ID in ApplicantNumber. Conversion through ready-to-convert and a scheduled process in Oracle. Integration user with rights to create workers for the relevant legal employers.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in TeamtailorField in Oracle HCM CloudNotes
Kandidaat-IDApplicantNumberTo recognise a second notification
first-name en last-nameNaam van de persoon
Geboortedatum (custom field, datum)DateOfBirth
Divisie en land van de vacatureLegalEmployerNameThrough a lookup table
start-date (onboarding)ProjectedStartDate
work-email (onboarding)Werk-e-mailadres
Locatie van de vacatureLocationCodeThrough a lookup table
Afdeling van de vacatureAfdeling (DepartmentName)
Uren per week (custom field, getal)workMeasures (FTE)Converted against the employer's full-time week

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.