HR to ERP
Sympa to AllSolutions integration: approved employee data of the Dutch employer in AllSolutions
With an integration between Sympa and AllSolutions, every employee of the Dutch employer in Sympa automatically reaches AllSolutions, with department, job, work email and start date. Only approved table rows go along, and a transfer takes effect in AllSolutions on the validity date from Sympa.
What the integration does
Organisations that run HR for the Nordic countries and the Netherlands in Sympa and run projects, hours and invoices in AllSolutions retype every Dutch colleague in AllSolutions. A change that is still awaiting approval in Sympa is sometimes already in AllSolutions.
- The Sympa administrator sets up an interface with only the fields and tables AllSolutions needs.
- KoppelHet reads the changed employees of the Dutch employer, with only approved table rows.
- KoppelHet creates new employees in AllSolutions; changes take effect on their validity date.
- An end of employment becomes an end date; AllSolutions keeps the employee and their hours.
What to watch for with Sympa and AllSolutions
- Sympa has no fixed API fields. The administrator builds an interface and chooses which fields and tables are in it. For AllSolutions we only expose employer, employment, department, job and work email, so pay and personal data never pass through the integration.
- Every table row in Sympa has an approval status, from waiting to be saved to approved or declined. A transfer still awaiting approval does not belong in the project administration. KoppelHet only requests rows with the approved status per table.
- With the at parameter Sympa returns the table rows valid on a given day, if the table has effectivity settings. Every night KoppelHet requests the state of the next day. A new department from the first of the month is then in AllSolutions on that day, not earlier.
- A Sympa interface may make one hundred requests per hour by default, for reading and writing combined. KoppelHet only fetches changed employees per round, in pages, and reads AllSolutions with a cursor. That leaves room for other integrations on the same interface.
- A filter within a table in Sympa still returns all employees, only with fewer rows. The AllSolutions integration account works per company. KoppelHet therefore filters on the Dutch employer first and then switches to the right AllSolutions company, so colleagues from Finland or Sweden never end up in AllSolutions.
- Sympa reads from a reporting database that can run up to thirty minutes behind the screen. An employee HR has just created may therefore still be missing. KoppelHet remembers the time of the previous round with a wide margin, so such an employee still reaches AllSolutions in the next round.
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 right after every change?
Sympa sends no notifications to the integration and allows one hundred requests per hour by default. A few rounds a day fit well within that. A higher limit can be requested from Sympa.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Sympa Integration API (OData v4 subset, JSON) on its own interface under https://api.sympahr.net/api, with X-ApiKey or basic authentication. Employees with $filter on employer and modification date, $top and $skip; table rows with $expand and Approval eq 5; at, since or until for validity (requires effectivity settings). Unique field or DataCardCode as key. By default 100 requests per hour per interface, shared across GET, POST and PATCH; reporting database usually within a minute, exceptionally up to 30 minutes behind.
- AllSolutions through the REST API: POST /api/v1/Login and the token, with RefreshToken after the fixed validity expires. GET on the view with pageSize and cursor, POST on the employee screen with the same checks as the form, PUT /api/v1/{browser}/{RecordID} with only changed fields. Switching company with GET /api/v1/mwzbdr and afdelingWijzig.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Sympa | Field in AllSolutions | Notes |
|---|---|---|
Uniek veld (bijv. personeelsnummer) | Personeelsnummer | Key of the interface |
Naam | Naam | |
Werkmail | E-mailadres | |
Werkgever | AllSolutions-bedrijf (inlogbedrijf) | Through a table |
Afdeling (tabelregel) | Afdeling | |
Functie (tabelregel) | Functie | |
Begin en einde dienstverband | Datum in dienst en datum uit dienst |
Related
Greenhouse → Sympa
Greenhouse to Sympa integration: hired candidate as a data card with contract row in Sympa
Recruitee → Sympa
Recruitee to Sympa integration: hired candidates as a data card in Sympa
SmartRecruiters → Sympa
SmartRecruiters to Sympa integration: ready to onboard becomes a data card in Sympa
Sympa → 4PS Construct
Sympa to 4PS Construct integration: fitters of the Dutch employer from Sympa in 4PS, with cost centre as a dimension