HR to ERP
Remote to Unit4 integration: Remote employments as employees in the Unit4 company that bears the costs
With an integration between Remote and Unit4 ERP, every employment from Remote becomes an employee in Unit4, in the company of the legal entity that bears the costs, with department, job title and a personnel type per kind of employment. A moved start date or a changed end date in Remote is updated properly in Unit4, and on the end date the employee is terminated.
What the integration does
Organisations that employ people in other countries through Remote, as EOR, contractor or own employee, and use Unit4 ERP for projects and time entry add those people to Unit4 by hand. Moved start dates and end dates that still change during offboarding then get out of step.
- At the start KoppelHet loads all employments once; after that, changes come through webhooks.
- Per employment KoppelHet picks the Unit4 company and the personnel type.
- Unit4 validates the data beforehand; new employees go to Unit4 per company.
- A moved start date replaces the employment row in Unit4.
- When the end date in Remote is reached, the employee is terminated in Unit4.
What to watch for with Remote and Unit4 ERP
- Remote gives two legal entities per employment: the entity that engaged someone and the entity that is billed. In Unit4 an employee belongs to the company where their hours and costs land. KoppelHet therefore picks the billed entity for the Unit4 company, and falls back on the other if it is empty.
- Remote has four kinds of employment: EOR employee, contractor, own employee and global payroll employee. In Unit4 the personnel type determines what someone may book. KoppelHet converts each of the four with a table into a personnel type, so a contractor does not appear as employee in Unit4 reports.
- Remote reports a moved start date with its own event. Unit4 does not allow an employment's start date to be set later. KoppelHet then removes the employment row and sets it again with the new date, as long as nothing has been booked on it yet.
- According to Remote, the end date of an employment can still change during offboarding, even after it has been finalised. In Unit4 terminating is a final status. KoppelHet already sets the end date on the employment row, adjusts it on every change and only terminates the employee once Remote reports that the end date has been reached.
- Remote recommends loading the employment list once and then relying on webhooks, not polling per employee. Unit4 accepts new employees per batch for one company. KoppelHet builds the initial load per company from that one list, and afterwards only processes what the webhooks report.
- In Remote the manager only has their own employment ID if they also run through Remote; otherwise there is only a name and email address. KoppelHet looks up the manager in Unit4 by that email address, so a manager not hired through Remote also becomes approver.
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 invoices or payroll costs from Remote go to Unit4?
Not in this integration. It keeps employees current; invoices and payroll costs can be added later as an extension.
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 (status, employment_model eor, peo or global_payroll, employment_type, company_id) for the initial load and webhooks through POST /v1/webhook-callbacks for employment.updated, employment.details.updated, employment.start_date.changed, employment.status.updated, offboarding.submitted, offboarding.deleted and contract.termination_date_reached. Fields type (employee, contractor, direct_employee, global_payroll_employee), engaged_by_legal_entity_id, bill_to_legal_entity_id, department, manager_email, manager_employment_id, job_title, provisional_start_date, termination_date.
- Unit4 ERPx through the Employees API - POST /v1/employees/validate, POST /v1/employees/batch (at most 200, one companyId), 202 with an active workflow, PATCH with AddOrReplaceById and RemoveById on employments (positionId, startDate, endDate) and relatedValues, startDate cannot be set later, DELETE /v1/employees/{personId} as Terminate.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Remote | Field in Unit4 ERP | Notes |
|---|---|---|
employment id (short_id) | personId | |
Naam, work_email | Naam en e-mailadres | |
bill_to_legal_entity_id | companyId | Lookup table; otherwise engaged_by_legal_entity_id |
type en employment_model | personnelType | |
department | relatedValues afdeling | By name, through a lookup table |
manager_email | relatedValues leidinggevende | |
job_title | employments.positionId | |
provisional_start_date en termination_date | employments.startDate en endDate |
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 → 4PS Construct
Remote to 4PS Construct integration: own employees of the construction entity from Remote in 4PS
Remote → Active Directory
Remote to Active Directory integration: accounts for colleagues in other countries