Leave, absence and time
Remote to Quinyx integration: employees from Remote in Quinyx, approved time off per day in the schedule
With an integration between Remote and Quinyx, every employee employed through Remote appears in Quinyx automatically, with a role from the start date and an end as soon as Remote records the last day. KoppelHet puts time off approved in Remote into Quinyx as absence per day, and processes a later change or cancellation too.
What the integration does
Organisations that employ people through Remote and schedule their shifts in Quinyx add every new employee to Quinyx themselves and keep time off in two places. A moved start date or a changed day off in Remote only reaches the planner when the schedule is already wrong.
- An employment in Remote reaches the agreed status; KoppelHet creates the employee in Quinyx with a role in the unit.
- If Remote moves the start date, KoppelHet adjusts the start in Quinyx.
- The employer approves time off in Remote; KoppelHet adds an absence in Quinyx for each day with hours.
- On a date change or cancellation KoppelHet removes the old absence, with the shifts back, and books the new one where needed.
- After an offboarding KoppelHet ends the role in Quinyx on the last day.
What to watch for with Remote and Quinyx
- Remote creates public holidays itself as approved time off, based on the employee's location, and sends the same notification as for approved time off. Quinyx handles public holidays in its own settings. KoppelHet therefore leaves out time off of the public holiday type, so a holiday does not also appear as an absence in the schedule.
- For time off Remote gives the number of hours off per day, with zero for weekends and days off. Quinyx has a full absence and a partial one with a percentage of the shift. KoppelHet skips days with zero hours and converts a day with fewer hours than the shift into a partial absence.
- An employee can ask in Remote to withdraw approved time off; the request then gets the status cancellation requested until the employer decides. KoppelHet keeps the absence in Quinyx until Remote confirms the cancellation, so the planner does not fill a shift too early.
- Remote sends a separate notification when the dates of a time off request change. Quinyx documents only creating and deleting absences. KoppelHet then deletes the old absence, gives the shifts back to the employee and books the new period.
- Remote reports separately that an employer has moved the start date of an employment. In Quinyx the start date and the role in the unit depend on that date. KoppelHet adjusts both, so the employee cannot be scheduled before the day they actually start.
- The end date of an offboarding in Remote can still change, even after the offboarding is completed. Quinyx refuses absence for someone whose employment has ended. KoppelHet keeps comparing the end date and resets the end date of the role, so time off submitted late for the final weeks can still be booked.
- For own employees and global payroll Remote only offers retrieving employments, while time off through the API belongs to employments with Remote as the employer. KoppelHet puts both groups in Quinyx, but time off only comes from Remote for those whose leave Remote also manages.
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
Can time off also be requested in Quinyx?
Not in the smallest setup: Remote stays leading for time off. Time off from Quinyx back to Remote can be added later as an extension.
Do worked hours go to Remote's payroll?
Not in this integration. Hours as pay items to Remote 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 the Remote API with a company token. Employments through GET /v1/employments and /v1/employments/{employment_id} (type, status, full_name, work_email, department, provisional_start_date) and webhooks employment.updated, employment.start_date.changed, employment.work_email.updated and offboarding.completed (termination_date). Time off through webhooks timeoff.approved, timeoff.date_changed, timeoff.updated, timeoff.cancellation_requested and timeoff.canceled, with timeoff_type (including paid_time_off, sick_leave, public_holiday) and timeoff_days with day and hours.
- Quinyx through the Employees API v3 (POST /hr/v3/employees with badgeNumber, personalInformation and employment with homeGroupId and employmentStartDate; PATCH /hr/v3/employees/{id}) and /hr/v3/role-assignments with startDate and endDate. Absence through POST /v2/schedule/groups/{groupId}/absences and /absences/part-time (absenceRate, absenceRateDirection), DELETE with reassignBackShifts. INACTIVE_EMPLOYEE and MISSING_AGREEMENT are reported.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Remote | Field in Quinyx | Notes |
|---|---|---|
employment id | badgeNumber | Or an employee number, chosen per customer |
full_name | personalInformation.firstName, lastName | Split |
work_email | email | |
department | employment.homeGroupId | Through a table to Quinyx units |
provisional_start_date | employmentStartDate en role-assignment startDate | |
termination_date (offboarding) | role-assignment endDate | |
Time off (approved), timeoff_type | Absence, absenceTypeId | |
timeoff_days (hours per dag) | Absence of part-time absence (absenceRate) |
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