HR to ERP
Rippling to 4PS Construct integration: own employees of the construction entity in 4PS, with department as a dimension
With an integration between Rippling and 4PS Construct, every own employee of a Dutch construction or installation entity in Rippling automatically becomes an employee in that entity's 4PS company, with job, work email, start date and the department as default dimension. An end date in Rippling becomes an end date in 4PS, and after the last working day KoppelHet sets the status to terminated.
What the integration does
Organisations with a Dutch construction or installation entity in 4PS Construct and HR for every country in Rippling create fitters and site managers in 4PS by hand. Contractors and people through a PEO or EOR are also in Rippling, but do not belong in 4PS as employees.
- At the start we link every own Dutch entity that works with 4PS to a 4PS company.
- KoppelHet fetches the updated workers every hour and keeps own employees of those entities.
- The employee is created or updated in 4PS, with the department as dimension if that value exists in 4PS.
- On an end date KoppelHet sets the end date, and after the last working day the status to terminated.
What to watch for with Rippling and 4PS Construct
- Rippling marks a legal entity that runs through a PEO, EOR or COR with a management type. People working there are not on the payroll of the own construction or installation entity. KoppelHet leaves those workers out of 4PS and only takes employees of own Dutch entities.
- The type of employment in Rippling is EMPLOYEE or CONTRACTOR. A self-employed fitter hired for a project runs through purchasing in 4PS, not as an employee. KoppelHet therefore only creates employees; contractors only go along if agreed at the start.
- The employee in the Business Central API, which 4PS runs on, has no department field. The department from Rippling therefore goes onto the employee as a default dimension, with the reference code of the Rippling department as dimension value. A department without a reference code becomes an alert.
- Dimension values can only be read in the Business Central API. If the department code from Rippling 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 then fills in the dimension.
- Rippling records a job change with its own effective date. The employee in 4PS only has one current job. KoppelHet only changes jobTitle in 4PS on that date, so a fitter who becomes site manager next month stays a fitter in the planning until then.
- An offer that is declined or rescinded in Rippling ends as a termination of that type. KoppelHet does not delete an employee who was already in 4PS, because planning or hours may already be linked to them. They go to inactive and planning gets an alert.
- The Business Central employee has a separate field for the middle name. Rippling provides first and last name. If the name particle is part of the last name, such as van Dijk, KoppelHet puts it in the middle field on request, so 4PS sorts on the surname.
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 Rippling go to 4PS?
No. The integration does not request compensation. 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.
- Rippling through the REST API: GET /workers with filter on updated_at, expand on user, legal_entity, employment_type and department, order_by updated_at, cursor and limit (1 to 100). Fields number, status, start_date, end_date, title with title_effective_date, work_email, employment_type.type (EMPLOYEE or CONTRACTOR), legal_entity.management_type (PEO, EOR, COR), department.reference_code and termination_details.type.
- To 4PS through the Business Central API v2.0 per company: employees (POST and PATCH; number, givenName, middleName, surname, jobTitle, email, employmentDate, terminationDate, status Active, Inactive or Terminated; no department) and defaultDimensions with parentType Employee (dimensionCode, dimensionValueCode, postingValidation). dimensionValues GET only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in 4PS Construct | Notes |
|---|---|---|
number | number | |
user (voornaam en achternaam) | givenName, middleName en surname | |
title | jobTitle | |
work_email | email | |
start_date | employmentDate | |
end_date | terminationDate en status | |
department.reference_code | defaultDimensions (afdeling) | Existing dimension values only |
legal_entity | Company in 4PS | Through a table |
Related
Carerix → Rippling
Carerix to Rippling integration: successful match as a hire for review in Rippling
Greenhouse → Rippling
Greenhouse to Rippling integration: every hire straight into Rippling for review
Recruitee → Rippling
Recruitee to Rippling integration: hired candidates ready to hire
Rippling → Active Directory
Rippling to Active Directory integration: accounts in your own domain through the hybrid app from Rippling and Microsoft