HR to ERP
Sympa to 4PS Construct integration: fitters of the Dutch employer from Sympa in 4PS, with cost centre as a dimension
With an integration between Sympa and 4PS Construct, every employee of the Dutch construction or installation employer in Sympa automatically reaches 4PS, with job, work email, start date and cost centre as default dimension. Only approved rows from Sympa go along, and an end of employment becomes the end date in 4PS.
What the integration does
Organisations with a Dutch construction or installation employer in 4PS Construct and HR for the whole group in Sympa create fitters in 4PS by hand. Cost centre changes that still need approval in Sympa are sometimes already ahead in 4PS.
- The Sympa administrator creates an interface with only the fields and tables 4PS needs.
- KoppelHet reads the changed employees of the Dutch employer, with only approved table rows.
- The employee is created or updated in 4PS, with the cost centre as dimension if that value exists.
- An end of employment becomes the end date; after that day KoppelHet sets the status to terminated.
What to watch for with Sympa and 4PS Construct
- In Sympa the administrator chooses per interface which fields and tables go along, with a unique field as key. For 4PS we only expose employer, employment, job, cost centre and work email. The unique field also becomes the employee's number in 4PS, so both systems share the same key.
- A cost centre row in Sympa goes through approval. 4PS uses the default dimension right away on every new hours line. KoppelHet therefore only requests rows with the approved status, so hours never land on a cost centre HR can still decline.
- Dimension values can only be read through the Business Central API underneath 4PS. If a cost centre from Sympa does not yet exist as a value in 4PS, KoppelHet creates the employee without that dimension and asks finance to add the value. The next round fills in the dimension.
- A cost centre or job in Sympa is a table row with a validity. With the at parameter KoppelHet requests the state of the next day every night. A fitter who moves to another project team from Monday therefore gets the new dimension on Monday, not already on Friday.
- Sympa allows one hundred requests per hour per interface by default, for reading and writing combined. 4PS has its own company per entity in Business Central. KoppelHet reads Sympa in a few rounds a day and writes only what changed per company.
- A filter on a table in Sympa still returns all employees, only with fewer table rows. In a group with Nordic subsidiaries KoppelHet therefore filters on the Dutch employer first, so only those employees reach 4PS.
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
Does pay data from Sympa go to 4PS?
No. Pay is not in the interface for 4PS. Finance manages cost rates per employee in 4PS.
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. $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.
- To 4PS through the Business Central API v2.0 per company: employees (POST and PATCH; number, givenName, surname, jobTitle, email, employmentDate, terminationDate, status Active, Inactive or Terminated) and defaultDimensions with parentType Employee. dimensionValues GET only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Sympa | Field in 4PS Construct | Notes |
|---|---|---|
Uniek veld (bijv. personeelsnummer) | number | |
Voornaam, achternaam | givenName en surname | |
Functie (tabelregel) | jobTitle | |
Werkmail | email | |
Begin dienstverband | employmentDate | |
Einde dienstverband | terminationDate en status | |
Kostenplaats (tabelregel) | defaultDimensions (kostenplaats) | Existing dimension values only |
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 → Active Directory
Sympa to Active Directory integration: domain accounts in the right OU from Sympa