Payroll integration
SuccessFactors to YouForce integration: new hires and contract changes without retyping
With an integration between SAP SuccessFactors and Visma Raet YouForce, every new Dutch employee and every contract change from SuccessFactors automatically starts as a request in YouForce, with the data already filled in. Dutch HR only checks and completes, and a change in hours or job no longer surfaces only on the payslip.
What the integration does
Employers with SAP SuccessFactors Employee Central as central HR system and Visma Raet YouForce for Dutch payroll record every hire twice, first in Employee Central and then in YouForce. Changes in hours or job sometimes only come to light on the payslip.
- The shared service centre records a new Dutch employee in SuccessFactors.
- KoppelHet fetches the employee, with the job data valid on the effective date.
- KoppelHet checks whether the person is already known in YouForce. A new person becomes a hire, a former employee a rehire and a current employee a contract change.
- A request is ready in YouForce. If it is rejected, the reason shows in the KoppelHet platform.
- Dutch HR completes the request and adds collective agreement scale and step. A termination arrives as a notice in the platform for payroll.
What to watch for with SAP SuccessFactors and Visma Raet YouForce
- YouForce does not let new hires and contract changes come in directly. Every change starts a request that HR completes in YouForce.
- SuccessFactors often delivers several changes at once, such as a job change and an hours change on different dates. KoppelHet sends them as separate contract changes, each with its own effective date.
- YouForce can check whether someone already has an employee number. A former employee returning through SuccessFactors thus becomes a rehire rather than a duplicate person.
- A termination cannot be entered in YouForce automatically. KoppelHet turns it into a notice in the platform, so payroll processes the termination in YouForce.
- Jobs and departments must exist in YouForce before the request starts. KoppelHet fetches the valid codes from YouForce and keeps the lookup table current with them.
- In SuccessFactors someone can hold ID numbers from several countries. KoppelHet only sends the Dutch number to YouForce as the BSN.
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 not write directly to YouForce?
YouForce offers no way to do that. The request with workflow is the route Visma provides, and HR keeps control over what enters payroll.
What do we need to arrange in SuccessFactors?
An integration user that may read the data of the Dutch employees. Nothing more.
What if a request in YouForce gets stuck?
KoppelHet follows every request. If it stays open too long or is rejected, you see it in the platform with the message from YouForce.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- SuccessFactors Employee Central is read through the OData API with OAuth 2.0 on lastModifiedDateTime (EmpEmployment, EmpJob with standardHours, jobCode and department; PerNationalId with country NLD). Technical user with read access for the Dutch legal entity.
- YouForce is addressed through the Youforce Recruitment API (hire, rehire and contract adjustment, each as a self-service workflow; asynchronous processing with status polling). The Recruitment API has no termination. personIdExternal is passed as external number.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in Visma Raet YouForce | Notes |
|---|---|---|
PerPerson.personIdExternal | Extern nummer in YouForce | Key to link later changes to the same person |
PerPersonal.firstName, lastName | Voornamen, voorvoegsel, achternaam | |
PerNationalId.nationalId (country NLD) | BSN | |
EmpEmployment.startDate | Datum in dienst | |
EmpJob.standardHours | Uren per week | |
EmpJob.jobCode | Functie | Through a lookup to existing YouForce jobs |
EmpJob.department | Organisatie-eenheid | Through a lookup table |
Employee class of contracttype | Soort arbeidsrelatie en soort contract | To the codes YouForce uses |
EmpEmployment.endDate | Melding uitdiensttreding | Not a write action, see specifics |
Related
Ashby → SAP SuccessFactors
Ashby to SAP SuccessFactors integration: hire as a new employee in Employee Central
Bullhorn → SAP SuccessFactors
Bullhorn to SAP SuccessFactors integration: placements as employees or contingent workers in Employee Central
Carerix → SAP SuccessFactors
Carerix to SAP SuccessFactors integration: successful placement as a new employee in Employee Central
Greenhouse → SAP SuccessFactors
Greenhouse to SAP SuccessFactors integration: a hire as a new employee in Employee Central