Leave, absence and time
Deel to UKG Dimensions integration: own employees from Deel in UKG, approved time off in the schedule
With an integration between Deel and UKG Dimensions, own employees from Deel appear in UKG automatically, with their time zone, manager and a pay rule that matches how they are paid. Time off a manager approves in Deel then appears in the UKG schedule as a paycode edit, also when it is half a day.
What the integration does
Organisations that record their own employees in Deel HR and schedule shifts in UKG Dimensions retype every new colleague into UKG. Approved time off from Deel does not reach the schedule by itself, and a departure stays in UKG until someone notices.
- HR records an own employee in Deel, under one of the organisation's own legal entities.
- Deel sends a webhook; KoppelHet fetches the full profile, with time zone, manager and payment scale.
- KoppelHet creates the person in UKG at the right place in the structure, after the manager is there.
- A manager approves time off in Deel; KoppelHet adds a paycode edit per day in UKG.
- On a changed or deleted request, or a last working day, KoppelHet updates UKG.
What to watch for with Deel and UKG Dimensions
- Deel's guide for own employees describes them as people hired under the organisation's own legal entity, with their own payroll. Deel has separate webhooks for that group on creation and change. KoppelHet subscribes to those, so EOR employees and contractors do not end up in UKG unless you want them to.
- Deel's webhook for an own employee gives job title and seniority as IDs, and the legal entity as an ID. UKG wants a path with names in the business structure. KoppelHet therefore fetches the full profile after each notification and translates location and job title to that path.
- Deel stores a time zone per person and per contract. UKG uses the employee's time zone to assign shifts to a day. KoppelHet takes over the contract's time zone, so a night shift in another country falls on the same day as in Deel.
- For the manager Deel also returns their worker ID. KoppelHet uses the worker ID as personNumber in UKG, so the manager can be found in UKG at once. UKG only links to a manager that already exists; KoppelHet therefore creates a new manager first.
- For a half day Deel only says that the first or last day is half. UKG wants a duration for a paycode edit. KoppelHet fetches the work schedule from Deel, with hours per weekday, and books half of that day's hours as minutes.
- Deel gives a payment scale per contract, such as hourly or monthly. In UKG the pay rule determines how the timecard is calculated. KoppelHet chooses the pay rule based on that scale and the contract's country.
- For an own employee Deel reports the last working day from the termination of the primary contract. UKG works with status records that have an effective date. KoppelHet sets the UKG status to terminated from the day after that last working day, so the final timecard can still be completed.
- A time off review in Deel arrives as approved or denied, linked to a contract. KoppelHet only books approved time off and finds the right UKG person through the contract, even if someone has more than one contract in Deel.
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 EOR employees go to UKG too?
Not by default; the integration follows own employees. If you also schedule EOR employees in UKG, we include them per entity.
Do worked hours go back to Deel?
Not in this integration. A flow of hours to payroll 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.
- Deel through the REST API (version 2026-01-01) with an API token or OAuth2 app (scopes people:read and time-off:read). Own employees through the webhooks Employee Created Direct and Employee Updated Direct (contract, team_information with legal_entity_id, job_information with IDs) and GET /rest/people/{hris_profile_id} (worker_id, timezone, direct_manager with worker_id, work_location, employments with payment.scale, start_date and direct_employee_termination_last_day). Work schedule through GET /rest/time_offs/dailies (work_schedule with hours per weekday). Time off through the webhooks time-off.reviewed, time-off.updated and time-off.deleted.
- UKG through the UKG Pro Workforce Management API. POST /v1/commons/persons or /persons/multi_create (personNumber, employmentStatusList, primaryLaborAccounts.organizationPath, payRuleName, timeZoneName, supervisorPersonNumber). Time off with POST /v1/scheduling/schedule/pay_code_edits/apply_import (payCodeEdit with employee, startDate, payCodeRef and durationInDays or durationInMinutes; shiftOverrideOptions).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in UKG Dimensions | Notes |
|---|---|---|
worker_id | personNumber | Fixed key |
first_name, last_name | firstName, lastName, fullName | |
timezone | timeZoneName | |
direct_manager.worker_id | supervisorPersonNumber | |
work_location en job_title | primaryLaborAccounts.organizationPath | Through a table to a job in the UKG business structure |
employments[].payment.scale | payRuleName | Hourly or monthly pay to a pay rule |
start_date en direct_employee_termination_last_day | employmentStatusList met effectiveDate | |
Time off (approved), start_date_is_half_day en end_date_is_half_day | Paycode edit met durationInDays of durationInMinutes |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions