HR to ERP
Remote to 4PS Construct integration: own employees of the construction entity from Remote in 4PS
With an integration between Remote and 4PS Construct, every own employee (direct employee) of a Dutch construction or installation entity in Remote automatically reaches that entity's 4PS company, with job, work email, start date and department as default dimension. The end date of an offboarding in Remote becomes the end date in 4PS, and a cancelled termination undoes it again.
What the integration does
Organisations with a Dutch construction or installation entity in 4PS Construct that keep their own people in Remote HRIS create fitters and site managers in 4PS by hand. Remote also holds EOR employees in other countries, and they do not belong in the 4PS planning.
- At the start we link every Dutch entity in Remote that works with 4PS to a 4PS company.
- Remote reports a change; KoppelHet fetches the employment and only continues with own employees of those entities.
- The employee is created or updated in 4PS, with the department as dimension if that value exists.
- The end date goes along as soon as the offboarding runs; after the last working day KoppelHet sets the status to terminated.
What to watch for with Remote and 4PS Construct
- In Remote an own employee is an employment of type direct_employee; EOR employees have another type and model. An EOR fitter in Belgium is on Remote's payroll and does not belong in the Dutch 4PS company as an employee. KoppelHet filters on type and on the entity that employs the person.
- The Business Central API underneath 4PS has no department field on the employee. Remote gives a department with an ID per employment. Finance records per Remote department which dimension value belongs in 4PS, and KoppelHet sets that as the default dimension on the employee.
- Dimension values can only be read through the Business Central API. If the department value does not yet exist in 4PS, KoppelHet creates the employee without that dimension. Finance gets an alert and the next round fills in the dimension.
- The end date of an offboarding can still move in Remote after the offboarding is finalised. KoppelHet then puts the new date in terminationDate and waits with the terminated status until after the last working day. A fitter thus stays plannable until their real last day.
- If a termination is cancelled in Remote, Remote sends a separate webhook for it. KoppelHet then clears the end date in 4PS and sets the status back to active, so the employee does not drop out of the planning.
- Remote only gives read access for a direct employee, and has no employee number in the employment schema. KoppelHet therefore uses its own number series or the employment ID in 4PS, and keeps the link between the two itself.
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 the manager from Remote go to 4PS?
No. The employee in the Business Central API has no field for a manager. That can be added later as an extension through a custom field in 4PS.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Remote through GET /v1/employments for the first load (filters employment_model and employment_type) and GET /v1/employments/{employment_id} per webhook (type, employment_model, department_id, job_title, work_email, engaged_by_legal_entity_id, provisional_start_date and termination_date). Webhooks through POST /v1/webhook-callbacks, including employment.updated, offboarding.* and termination.cancelled. Company-scoped API token, for direct_employee only List and Show.
- 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 Remote | Field in 4PS Construct | Notes |
|---|---|---|
id (employment) | number | Or a number series in 4PS |
full_name | givenName en surname | |
job_title | jobTitle | |
work_email | email | |
provisional_start_date | employmentDate | |
termination_date | terminationDate en status | |
department_id | defaultDimensions (afdeling) | Through a table; existing values only |
engaged_by_legal_entity_id | Company in 4PS | Through a table |
Related
Greenhouse → Remote
Greenhouse to Remote integration: foreign hires as EOR employment with the country's form
Recruitee → Remote
Recruitee to Remote integration: hires abroad straight into an employment at Remote
Remote → Active Directory
Remote to Active Directory integration: accounts for colleagues in other countries
Remote → AFAS Profit
Remote to AFAS integration: only your own entity's employees from Remote to AFAS Profit