DyLeave, absence and time
Remote to Dyflexis integration: employments from Remote with the right employer in Dyflexis
With an integration between Remote and Dyflexis, employees in the Netherlands from Remote appear in Dyflexis automatically, with contract, office, probation date and the employer that belongs to the employment. The planner thus sees whether someone is employed through Remote as employer or by the own entity, and the contract in Dyflexis ends on the date Remote records at offboarding.
What the integration does
Organisations that hire employees in the Netherlands through Remote or record them in Remote, and schedule in Dyflexis, enter every start and departure twice. When processing hours it is often not visible whether someone is employed through Remote or by the own entity.
- HR creates an employment in Remote for an employee in the Netherlands.
- Remote sends a signed notification; KoppelHet checks the signature and fetches the employment.
- If the type is in the table and the status is far enough along, the employee goes to Dyflexis, with the employer as reference.
- An administrator links the new employee once in Dyflexis; after that every change follows automatically.
- At offboarding the employee and contract get the end date, which is updated if Remote moves it later.
What to watch for with Remote and Dyflexis
- Remote has several employment types, including employees through Remote as employer, own employees (direct_employee), global payroll and contractors. Per type we record whether someone belongs in Dyflexis. Contractors usually stay out of the schedule.
- Dyflexis can store an employer reference per employee. KoppelHet fills in the entity under which Remote recorded the employment. When processing worked hours it is then immediately clear whether the hours go to Remote or to own payroll.
- The contract details in Remote follow a separate form per country. Hours and working days are therefore in the Dutch form, not in a fixed field. KoppelHet reads the fields of that form, and reports an employment where they are missing instead of creating a contract without hours.
- Remote has many intermediate statuses, such as created, invited, review and pre_hire. KoppelHet only sends an employee to Dyflexis once onboarding is far enough along, and uses the provisional start date, which we update if Remote still moves it.
- Remote states that an offboarding end date can still change, even after the offboarding is finalised. KoppelHet therefore keeps comparing that date and adjusts the end of the Dyflexis contract, so a moved last day does not lead to empty or double shifts.
- Remote supplies the probation period as an end date per employment, and Dyflexis has its own field for it. With that date in the schedule the manager sees when the probation review is due, without opening Remote.
- Remote gives the name as one full name, while Dyflexis stores first name, prefix and last name separately and requires the last name. KoppelHet splits the name and reports a name that cannot be split unambiguously, so nobody enters the schedule without a last name.
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 worked hours go back to Remote?
Not in this integration. For employees through Remote as employer, an hours flow to Remote can be added later as an extension; hours of the own entity belong with own payroll.
What if someone moves from Remote to the own entity?
Then they are two employments in Remote. In Dyflexis the administrator links the second employment to the same employee, so the schedule history stays together.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Remote through the Remote API - GET /v1/employments and GET /v1/employments/{employment_id} (type, status, full_name, work_email, job_title, department, provisional_start_date, probation_period_end_date, engaged_by_legal_entity_id, contract_details per country, offboarding with termination_date). Signed webhooks for employment changes. For direct_employee, global_payroll_employee and contractor only List and Show employment are available.
- To Dyflexis through POST /api2/external-employees/{employeeReference} (lastName required; firstName, lastNamePrefix, email, employerReferenceId, probationDate, employmentStart, employmentEnd, jobDescription) and POST /api2/external-employees/{employeeReference}/contracts (contractReference, office, type, start, end, hours, days). Scope external_employees.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Remote | Field in Dyflexis | Notes |
|---|---|---|
id (Remote-employment) | employeeReference | Every employment its own reference |
full_name | firstName, lastNamePrefix, lastName | Split into first name, prefix and last name |
work_email | email | |
job_title | jobDescription | |
engaged_by_legal_entity_id en type | employerReferenceId | Remote as employer or the own entity |
provisional_start_date | employmentStart en start (contract) | |
probation_period_end_date | probationDate | |
department | office (contract) | Through a table to the Dyflexis office |
contract_details (Nederlands formulier) | hours en days (contract) | |
termination_date (offboarding) | employmentEnd en end (contract) |
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