Payroll integration
SAP SuccessFactors to SD Worx integration: changes from Employee Central as a delta to SD Worx payroll
With an integration between SAP SuccessFactors Employee Central and SD Worx, hires, changes, pay components and terminations per legal entity go to SD Worx payroll as a delta, before the cut-off date. KoppelHet delivers in the format SD Worx defines per country, as a file or through an API.
What the integration does
Organisations that record HR for all countries in SuccessFactors and have payroll in Belgium or other countries at SD Worx send SD Worx a list of changes every month.
- HR records a change in Employee Central at a legal entity SD Worx pays.
- KoppelHet fetches the changes since the previous run.
- Data that only applies to that country comes from the country-specific fields in SuccessFactors.
- SD Worx processes the changes in that country's payroll and reports errors back.
- Payroll and HR fix the error in SuccessFactors, so the next delta picks it up again.
What to watch for with SAP SuccessFactors and SD Worx
- SD Worx names files or APIs as the route into its payroll processing. KoppelHet delivers in the format SD Worx defines for that country.
- A delta from SuccessFactors is effective dated or period based. Effective dated suits a receiver that stores each record with its validity; period based also returns the retroactive changes per pay period. KoppelHet chooses per country the form SD Worx payroll expects.
- A delta from SuccessFactors only works with auditing on, and it must be switched on before the first load of employees. If auditing was switched on later, KoppelHet first builds a full baseline before deltas go to SD Worx.
- SAP reports duplicate records in delta integrations to external payroll built on SAP's standard template. KoppelHet checks every delta for lines SD Worx has already received before passing it on.
- A person in SuccessFactors can have national IDs from several countries. For Belgian payroll KoppelHet only sends the ID with country Belgium, and reports a Belgian employee without that ID to HR.
- If KoppelHet queries through OData on lastModifiedDateTime, SuccessFactors only returns today's EmpJob record for a changed employee, unless the query also contains fromDate and toDate. KoppelHet passes that period, so a retroactive correction also reaches SD Worx payroll.
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
What if we switched on auditing in SuccessFactors only later?
Then the delta misses the history from before that moment. KoppelHet first makes a full baseline and only then sends changes.
Can hours from our scheduling system go to SD Worx as well?
That is outside this integration. It can be added later as an extension, in the format SD Worx uses for that country.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Employee Central through the Compound Employee API in delta mode (effective dated or period based, with the last synchronisation in the where clause; auditing required), or through OData on lastModifiedDateTime for PerPersonal, PerNationalId, EmpEmployment, EmpJob, EmpPayCompRecurring and EmpPayCompNonRecurring.
- Towards SD Worx we use the files or APIs SD Worx defines per country; we have not found public API documentation for SD Worx payroll processing.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in SD Worx | Notes |
|---|---|---|
personIdExternal | Personeelsnummer bij SD Worx | Target fields are descriptions; SD Worx does not publish the field names |
PerPersonal (firstName, lastName) | Naam | |
PerNationalId (country BEL) | Rijksregisternummer | |
EmpJob (company, standardHours) | Werkgever en arbeidsduur | |
EmpPayCompRecurring | Vaste looncomponent | Through a lookup table per country |
EmpPayCompNonRecurring | Eenmalige looncomponent | |
EmpEmployment (endDate) | Datum uit dienst |
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