HR to ERP
Remote to AllSolutions integration: own employees of the Dutch entity in AllSolutions
With an integration between Remote and AllSolutions, every own employee (direct employee) of the Dutch entity in Remote automatically becomes an employee in AllSolutions, with department, job, work email and start date. EOR employees and contractors stay out of AllSolutions, and the end date of an offboarding becomes the end date in AllSolutions.
What the integration does
Organisations that keep their own Dutch employees in Remote HRIS and have foreign colleagues work through Remote as employer of record run projects, hours and invoices in AllSolutions. They enter new own employees there by hand, and a departure arrives late or not at all.
- At the start KoppelHet reads the employments once and links the existing employees in AllSolutions.
- Remote reports a change; KoppelHet fetches only that employment and checks type and entity.
- An own employee of the Dutch entity is created or updated in the right AllSolutions company.
- The end date from the offboarding becomes the end date; a cancelled termination removes it again.
What to watch for with Remote and AllSolutions
- Remote has employments of type employee, contractor, direct_employee and global_payroll_employee, with a model such as eor or peo. Only direct_employee is an own employee in Remote's HRIS. KoppelHet only puts those of the Dutch entity into AllSolutions; an EOR employee reaches finance as an invoice from Remote.
- A direct employee can only be read in the Remote API. Writing an AllSolutions number back to Remote is therefore not possible. KoppelHet stores Remote's employment ID in a free field in AllSolutions, so the integration finds every employee there.
- Remote asks integrations to read the employments once as a list and then work from webhooks. KoppelHet only does the full read at the start. After that it fetches one employment per webhook, with department, job and end date.
- According to Remote, the end date of an offboarding can still change, even after the offboarding is finalised. AllSolutions accepts a change with only the field that differs. KoppelHet compares the end date daily until after the last working day and only adjusts the end date if it moves.
- Remote sends a separate webhook when a termination is cancelled. KoppelHet then removes the end date in AllSolutions again, so the employee can keep booking hours on their projects.
- Every employment in Remote names the legal entity that employs the person. AllSolutions works with companies, and the integration account logs in to one default company. If you have several Dutch entities in Remote, KoppelHet switches per entity to the matching AllSolutions company.
- In AllSolutions an employee with hours or projects cannot be deleted; the API then returns the same message as the screen. If an employment in Remote is deleted or archived, KoppelHet therefore deletes nothing, but reports it to HR.
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
Should EOR employees be able to book hours in AllSolutions?
That can be added later as an extension, with a separate type so project administration keeps them apart. The first version only takes own employees.
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 (page, page_size, filters employment_model and employment_type) for the first load and GET /v1/employments/{employment_id} per changed employment (type, employment_model, status, department, department_id, job_title, work_email, engaged_by_legal_entity_id, provisional_start_date, manager_employment_id and termination_date). Webhooks through POST /v1/webhook-callbacks for employment.updated, employment.work_email.updated, offboarding.* and termination.cancelled. Company-scoped API token.
- AllSolutions through the REST API: POST /api/v1/Login and the token, RefreshToken after the fixed validity expires. 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 the afdelingWijzig action. Free fields with their own REST API label.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Remote | Field in AllSolutions | Notes |
|---|---|---|
id (employment) | Vrij veld met REST API-label | Fixed key |
full_name | Naam | |
work_email | E-mailadres | |
engaged_by_legal_entity_id | AllSolutions-bedrijf (inlogbedrijf) | Through a table |
department_id | Afdeling | Through a table |
job_title | Functie | |
provisional_start_date | Datum in dienst | |
termination_date | Datum uit dienst |
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