Workday logoQuinyx logo

Leave, absence and time

Workday to Quinyx integration: workers, contract hours and approved time off automatically in scheduling

With an integration between Workday and Quinyx, every worker from Workday appears in Quinyx automatically, in the right site, with contract hours and an agreement, so planning can schedule them. Approved time off and leaves of absence from Workday arrive in Quinyx as absence, and time off balances as balances in the Quinyx app.

What the integration does

Anyone using Workday as HR system and building schedules in Quinyx has managers create new employees in Quinyx by hand, often only after they have started. Time off approved in Workday is not in the schedule, and a change of hours only reaches planning when the employee brings it up.

  1. HR records a new worker in Workday, with position, location and hours per week.
  2. KoppelHet creates the employee in Quinyx, in the site that belongs to the location, with a role and an agreement based on the contract type.
  3. A change of hours or transfer in Workday goes to Quinyx with its effective date, even if it is in the future.
  4. Approved time off and leaves of absence appear as absence in the schedule; balances are shown in the Quinyx app.
  5. After termination KoppelHet sets the last working day in Quinyx, so the employee can no longer be scheduled after that.
Workday → KoppelHet → QuinyxSOURCEWorkdayTARGETQuinyxKoppelHetmapping · logging · monitoringWorkday → KoppelHet → QuinyxSOURCEWorkdayTARGETQuinyxKoppelHetmapping · logging · monitoring
Out: Worker with employee ID, name and email · Home site and role · Agreement with contract hours and start date · Approved time off and leaves of absence · Time off balance per plan

What to watch for with Workday and Quinyx

  • Workday holds the standard working week for the position and the worker's scheduled hours. Quinyx calculates contract hours from a full working week and a percentage. KoppelHet sets the standard week as the full working week in the agreement and converts the scheduled hours to that percentage.
  • Quinyx does not schedule anyone without an agreement. Contingent workers in Workday often have no hours or pay. KoppelHet gives them their own agreement template based on the Workday worker type, or leaves them out of Quinyx if you do not schedule them there.
  • Workday distinguishes between time off and leaves of absence, such as maternity leave. Both become an absence in Quinyx, but with their own absence type, so the planner sees when someone is coming back.
  • Which absence types an employee may get in Quinyx depends on their agreement template. KoppelHet requests them per employee before booking time off from Workday, so a leave type is not silently rejected.
  • A transfer that takes effect next month in Workday becomes a new role in the new site in Quinyx with that start date. KoppelHet closes the role in the old site on the day before, because Quinyx does not do that itself when the home site changes.
  • Workday keeps the same employee ID on rehire. In Quinyx that is the badge number, so a former employee who returns gets their existing profile back instead of a second one.
  • Workday calculates time off balances per plan and per country. Quinyx shows balances on trackers and has a separate statutory balance for the Netherlands. KoppelHet puts each Workday plan on the matching tracker, so Dutch and Belgian employees see their own balance.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Does Quinyx not offer its own Workday integration?

Quinyx mentions integration services for Workday covering employee data, timesheets and balances, and agrees the approach per customer. We did not find an off-the-shelf app with fixed features. KoppelHet is an option if you also connect other systems from Workday and want one place for logging and support.

Do worked hours go back to Workday?

Usually not: the hours go to local payroll. If payroll runs in Workday, a flow of hours back can be added later as an extension.

What if a Workday location has no site in Quinyx yet?

Then the employee is not created and an alert appears in the platform. Planning creates the site or completes the translation table, after which the next round still creates the employee.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Workday is read with Get_Workers (Human_Resources) or a RaaS report on change date, including Scheduled_Weekly_Hours, Default_Weekly_Hours and Full_Time_Equivalent_Percentage per position. Balances through Get_Time_Off_Plan_Balances (Absence_Management); approved time off and leaves of absence through a report.
  • Quinyx is written with employees through the Employees API v3 (POST /hr/v3/employees, lookup on badgeNumber) and roles through /hr/v3/role-assignments with startDate and endDate. Agreements through wsdlUpdateAgreementsV2 (extTemplateId, fullEmploymentHrs, employmentRatesAdd), termination through wsdlUpdateEmployees (leaveDate), balances through wsdlUpdateTimeTrackers.
  • Absence through the v2 Absences API; valid absence types per employee through GET /v2/absence-types/groups/{groupId}/employees/{employeeId}. Quinyx v3 uses OAuth 2.0 client credentials with separate v3 credentials and a one-hour token.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in WorkdayField in QuinyxNotes
Employee_IDbadgeNumberFixed key, also on rehire
Legal_Name / Preferred_NamepersonalInformation.firstName, lastName
Werk-e-mailemail
Locationemployment.homeGroupIdThrough a table from Workday locations to Quinyx units
Hire_Dateemployment.employmentStartDate
Default_Weekly_HoursfullEmploymentHrs (agreement)Full working week for the position
Scheduled_Weekly_HoursContracturen (employment rate)Converted to a share of the full working week
Worker type en contracttypeextTemplateId (agreement template)Through a translation table
Termination last day of workleaveDate
Time off plan balanceTime tracker

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.