Choices and edge cases

Rehires, internal candidates and withdrawn offers in an ATS integration

A former employee who is hired again gets a new employment with the existing person in the HR system, and an offer withdrawn after Hired becomes an alert for HR instead of a silent deletion. KoppelHet looks up existing employees in AFAS, Visma Raet YouForce and Personio, and leaves the final step to HR, also in Dayforce and SAP SuccessFactors.

What it is

The handover from ATS to HR usually goes well. It goes wrong in the exceptions: a candidate who worked here before, an offer withdrawn after the candidate was already marked Hired, and internal candidates who are already employees.

Without rules a second person appears with a new personnel number and no history, or a half-created employee stays in the HR system.

How the integration handles it

  • First search by BSN or date of birth with name. On a match the integration creates no second person but a new employment, or queues the change for HR.
  • In AFAS the onboarding then uses the existing employee, so history and personnel number are kept.
  • YouForce checks whether the candidate already has a personnel number. The hiring workflow also exists for rehires and contract changes.
  • If an offer is withdrawn after the candidate was marked Hired, the employee is still in the AFAS workflow and HR can reject it there.
  • Where the HR system cannot roll back an employee, as in Dayforce and SAP SuccessFactors, the integration deletes nothing but alerts HR, which ends the employment or adjusts the start date.
  • An internal candidate does not become a new person. The internal move goes to HR as an alert, and HR adjusts the contract.
  • In Teamtailor a hire belongs to an application. A candidate who applies for two vacancies and is hired for one reaches the HR system once, with the right vacancy's data.

Edge cases we handle

  • Care organisations also recruit volunteers in Recruitee. The integration recognises those vacancies and does not put the hires into SDB as employees.
  • Dayforce can validate a new employee without creating it. The integration always validates first, so a missing location or job produces an alert and not a half-created employee.
  • Deel does not link a new contract back to an application. KoppelHet tracks which contract belongs to which candidate, so a second notification does not create a second contract.
  • A hire in Workday needs a position. If the vacancy has none, the integration stops with an alert instead of guessing.

What KoppelHet does

We go through these cases with HR beforehand: how we recognise a former employee, what happens with a withdrawn offer and how an internal move comes in. The final step stays with HR. The integration deletes nothing itself and reports what it is not sure about.

Common integrations

Frequently asked questions

What if the candidate already exists in the HR system?

We first search by BSN or date of birth with name. On a match we do not create a second person but a new employment, or queue the change for HR.

What happens if we withdraw an offer after Hired?

The integration deletes nothing. In AFAS HR rejects the open workflow; in systems where an employee cannot be rolled back, HR gets an alert to end the employment or adjust the start date.

Does the integration handle internal candidates?

Yes, but KoppelHet then creates no new person. The internal move goes to HR as an alert, and HR adjusts the contract.

More on Recruitment to HR

Recruitment to HR: the overview

From hire to HR

Choices and edge cases

  • Rehires and withdrawn offersFormer employees, internal candidates and an offer that lapses after Hired.

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.