Payroll integration
SuccessFactors to Loket integration: Employee Central as the source for Dutch payroll
With an integration between SAP SuccessFactors Employee Central and Loket, new Dutch employees from SuccessFactors arrive in Loket as concept employees, and employment, hours, recurring and one-off pay components go to the right employment with their effective date. The group keeps SuccessFactors as the source, and Dutch payroll works in Loket without double entry.
What the integration does
Groups that use SuccessFactors Employee Central for all countries and have their Dutch entities paid through Loket enter every new employee and every pay rise twice. Allowances granted in SuccessFactors are sometimes forgotten.
- KoppelHet reads the records of the Dutch companies in SuccessFactors that changed since the previous round, including changes that take effect later.
- A new employee becomes a concept employee at the Loket employer that belongs to the company. Payroll completes and converts.
- Hours and job go to the working hours and the employment, with the effective date from SuccessFactors.
- Recurring pay components become recurring components in Loket; one-off payments arrive in the period of payment.
- A termination in SuccessFactors ends the employment in Loket.
What to watch for with SAP SuccessFactors and Loket
- SuccessFactors can record several changes on one day, each with a sequence number. Loket holds one line per start date for each part. KoppelHet therefore takes the last change of that day, so payroll does not get three lines for the same date.
- If someone works for two companies at once in SuccessFactors, those are two employments. If both belong to the same Dutch employer, they become two employments under one employee in Loket; with two BVs it becomes an employee per employer.
- Pay components in SuccessFactors are set up for the whole group. A lookup table links each component to a pay component in Loket, and a component without an agreement arrives as a notification for payroll instead of silently in the payroll run.
- Dutch data such as the payroll tax credit and the right collective agreement are only in SuccessFactors if the group has set up country-specific fields for the Netherlands. Otherwise payroll completes them in Loket, and the integration does not overwrite them.
- Someone working in the Netherlands on a temporary assignment is a global assignment in SuccessFactors. Whether such a person belongs in the Dutch payroll run is agreed per situation; by default a global assignment does not go to Loket.
- SuccessFactors shows only what applies today by default. KoppelHet also requests future records, so a hire or pay rise from next month is ready in Loket during the current period.
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 SAP's own payroll?
That is possible, but many groups keep Dutch payroll with a local package or payroll bureau. This integration is for that situation: SuccessFactors stays the source, Loket calculates.
Can we set this up while Employee Central is still being rolled out?
Yes. We build against the SuccessFactors and Loket test environments and go live once the Dutch setup in SuccessFactors is finished.
We already have an integration platform. Does this fit alongside it?
Yes. This integration runs on the KoppelHet platform and asks nothing of your existing integration platform. Every action is in the audit logging, so operations and audit know what happened.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- SAP SuccessFactors Employee Central is read through the OData API v2 with OAuth 2.0 and a SAML bearer assertion, on lastModifiedDateTime and with fromDate and toDate for effective-dated records (startDate and seqNumber). Entities PerPerson, PerPersonal, PerNationalId (country NLD), EmpEmployment, EmpJob (company, standardHours, jobCode), EmpPayCompRecurring, EmpPayCompNonRecurring and EmpEmploymentTermination. Technical user with role permissions on the Dutch companies only.
- Loket is written through the Loket REST API with OAuth - concept employee, convert to employee, employment, wages, working hours, recurring pay components (benefits and deductions), one-off components per period and end employment. Loket has an acceptance environment with test data.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in Loket | Notes |
|---|---|---|
personIdExternal | Personeelsnummer of vrij veld | Fixed key |
PerPersonal (firstName, lastName) | Voornaam en achternaam | |
PerNationalId (country NLD) | Burgerservicenummer | With the eleven test |
EmpJob.company | Werkgever | |
EmpEmployment.startDate | Begindatum dienstverband | |
EmpJob.standardHours | Arbeidstijd | |
EmpJob.jobCode | Functie | |
EmpPayCompRecurring | Loon en vaste looncomponenten | Through a lookup table per pay component |
EmpPayCompNonRecurring | Eenmalige looncomponent | |
EmpEmploymentTermination | Einde dienstverband |
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