Recruitment to HR
Lever to SAP SuccessFactors integration: signed offers as new employees in Employee Central
With an integration between Lever and SAP SuccessFactors, a hired candidate from Lever becomes a new employee in Employee Central, with organisation, start date, probation and pay from the offer. KoppelHet only passes a hire on once the offer has been signed by all signers.
What the integration does
Organisations that recruit in Lever and have SuccessFactors Employee Central as their HR system re-enter every hire in SuccessFactors. They also want a check before a hire reaches payroll.
- The recruiter archives the candidate as hired in Lever.
- KoppelHet retrieves opportunity, offer and requisition and checks whether all parties have signed.
- The requisition code points to the position in SuccessFactors; the offer fields give start date and pay.
- KoppelHet creates person, employment and job information in Employee Central.
- A daily comparison catches hires whose notification did not arrive.
What to watch for with Lever and SAP SuccessFactors
- A hire in Lever carries the requisition code. When it matches the position in SuccessFactors, KoppelHet uses that code to put the hire on the right position in Employee Central, without a lookup table per job.
- An offer in Lever can show as signed while a second signer on behalf of the company is still missing. KoppelHet checks per signer of the offer and only writes to Employee Central once all signatures are there.
- Lever stores a candidate's name in one field. Employee Central records first name and last name separately in the personal information. KoppelHet splits the name and has names with a particle or several surnames confirmed by HR first.
- Start date and salary sit in a Lever offer as fields with a fixed code, such as anticipated_start_date and salary_interval. KoppelHet reads by those codes and puts amount, currency and period together in the pay, so an hourly rate does not arrive in SuccessFactors as an annual salary.
- Lever resends a failed webhook five times and then no more. KoppelHet therefore compares the hires in Lever with the new employees in Employee Central every day, so a missed hire does not lie silent.
- SAP is phasing out basic authentication for the SuccessFactors APIs. KoppelHet writes to Employee Central with OAuth 2.0 and a SAML bearer for a technical user, and reads Lever with its own API key that may only read opportunities, offers and requisitions.
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 national ID and Dutch payroll tax details come from Lever?
No. HR adds them in Employee Central or in the Dutch payroll.
What about audit logging, GDPR and our integration platform?
You are the controller and KoppelHet is the processor, under a data processing agreement. Only hired candidates go to SuccessFactors, and every action is in the audit logging. An existing integration platform is left alone.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Lever through the candidateHired webhook (data.opportunityId and contactId; HMAC-SHA256 over token and triggeredAt with the signing token; five retries) and the Lever API with an API key - GET /opportunities/:opportunity (name, emails, requisitionForHire with requisitionCode) and GET /opportunities/:opportunity/offers (status signed, fields with identifier, signatures for candidate and company_1 to company_3). Default 10 requests per second, bursts up to 20.
- To Employee Central through OData v2 upserts on PerPerson, PerPersonal, PerEmail, EmpEmployment and EmpJob with a hire event; position from the requisition code. OAuth 2.0 SAML bearer with an API user that has write access to these entities.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Lever | Field in SAP SuccessFactors | Notes |
|---|---|---|
name (één veld) | PerPersonal firstName en lastName | |
emails | PerEmail | |
requisitionForHire.requisitionCode | EmpJob position | |
Aanbiedingsveld anticipated_start_date | EmpEmployment startDate en EmpJob | |
Aanbiedingsvelden salary_amount, compensation_currency en salary_interval | Beloning met valuta en frequentie | |
opportunity id | Extern kenmerk bij de persoon |
Related
Lever → BambooHR
Lever to BambooHR integration: hired candidate as a new employee profile in BambooHR
Lever → Dayforce
Lever to Dayforce integration: signed offer as a validated new employee in Dayforce
Lever → Deel
Lever to Deel integration: hired candidate as own employee or EOR contract in Deel
Lever → HiBob
Lever to HiBob integration: hired candidate with offer as an employee in Bob