HR to ERP
SAP SuccessFactors to AllSolutions integration: Employee Central employees per company in AllSolutions
With an integration between SAP SuccessFactors and AllSolutions, every employee of a Dutch company in Employee Central automatically becomes an employee in the right AllSolutions company, with department, job and manager. Changes with a future effective date go through on that date, and a leaver becomes an end date in AllSolutions instead of a deletion.
What the integration does
Organisations that manage the group in SAP SuccessFactors and run projects, hours and finance in AllSolutions in the Netherlands enter new colleagues into AllSolutions by hand. Anyone moving to another company from the first of the month then keeps booking hours in the old company for weeks.
- HR saves a hire, transfer or termination for a Dutch company in Employee Central.
- KoppelHet fetches the job information daily, including records with a future effective date.
- Per Employee Central company KoppelHet switches to the matching AllSolutions company.
- A new employee is created; a change goes through on its effective date with only the fields that differ.
- On termination KoppelHet sets the end date; the employee and their hours remain.
What to watch for with SAP SuccessFactors and AllSolutions
- Employee Central returns only the job information valid today by default. An integration would then only see a transfer from next month on that day. KoppelHet requests the data with a date range, so future changes are already known and reach AllSolutions on their effective date.
- SAP warns that a filter on the last modified date for job information can also return an unchanged record. KoppelHet therefore compares with the previous state and only sends AllSolutions fields that really differ.
- Every company in Employee Central belongs to its own AllSolutions company. The AllSolutions integration account logs in to one default company and must be explicitly allowed to switch; KoppelHet switches per Employee Central company before writing.
- A transfer to another Dutch company is often a new job record with a different company in Employee Central. In AllSolutions those are two companies. KoppelHet gives the employee an end date in the old company and creates them in the new one, so hours up to that day stay with the right company.
- When creating through the API, AllSolutions runs the same checks as on screen, including fields the customer made mandatory. KoppelHet records at the start which mandatory fields exist and where they come from in Employee Central, so a new employee does not get stuck.
- Besides the job information, Employee Central has a separate termination per employment. AllSolutions does not delete an employee who still appears in hours or projects. On termination KoppelHet therefore only sets the end date, and removes it if HR reverses the departure.
- According to the documentation we found, SAP stops basic authentication for the SuccessFactors APIs around 20 November 2026. KoppelHet uses OAuth with a SAML assertion, so the integration to AllSolutions does not stop because of it.
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 salaries go to AllSolutions too?
No. The integration fills employee data for hours and projects. Finance manages cost rates in AllSolutions.
What if a department does not yet exist in AllSolutions?
AllSolutions then rejects the employee. KoppelHet reports the missing department to finance and tries again afterwards.
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 through the OData API (v2) with OAuth 2.0 and a SAML bearer assertion. EmpEmployment (personIdExternal, userId, startDate, endDate), EmpJob (company, department, costCenter, jobTitle, managerId, startDate) and PerPersonal. Without a date parameter asOfDate is today; KoppelHet uses fromDate and toDate to see future records. According to SAP KBA 2920680, a filter on lastModifiedDateTime for EmpJob can also return unchanged segments.
- AllSolutions through the REST API: login with signature and refresh token; GET with filters on a view, POST per record (same checks as the form, including customer-mandatory fields), PUT on the record ID with only changed fields. Switching company through the login-company function, which must be authorised for the API user. Fields and labels are set by the customer with views and settings for the REST API.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in AllSolutions | Notes |
|---|---|---|
EmpEmployment.personIdExternal of userId | Personeelsnummer | Fixed key, chosen per customer |
PerPersonal (firstName, lastName) | Naam | |
EmpJob.company | AllSolutions-bedrijf (inlogbedrijf) | Lookup per company |
EmpJob.department | Afdeling | |
EmpJob.costCenter | Kostenplaats | |
EmpJob.jobTitle | Functie | |
EmpJob.managerId | Leidinggevende | |
EmpEmployment.startDate en endDate | Datum in dienst en 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