These are the known limitations of the UKG Ready integration. They are inherent to the current design of the integration and to the capabilities of the UKG Ready API, and they apply to all subscribers at the time this documentation was written.

This integration was built for UKG Ready, the workforce management product formerly sold as Kronos Workforce Ready.

Not built for. This integration does not work with other UKG products, which have different APIs and different data models:

If UKG launches a separate product line or a materially different API version in the future, this integration will not automatically support it.

Employees flow from UKG Ready into iPaaS.com. The integration does not create, update, or delete employees in UKG Ready.

What this means for you. UKG Ready is the system of record for employee data. Maintain employees there, and let the integration bring them into iPaaS.com. If your workflow needs employees created in iPaaS.com to reach UKG Ready, submit a feature request through your iPaaS.com partner channel describing the flow you need — input like this informs future enhancement releases.

Every field iPaaS.com exposes on the Employee and Employee Address records is mapped by the default template, and each transfer rewrites all of them from UKG Ready.

What this means for you. Edits made directly to an employee's name, email address, photo link, or address in iPaaS.com are replaced the next time that employee transfers. Make those changes in UKG Ready instead. Because every available field is mapped, no field is silently cleared — there are no unmapped fields to lose data.

iPaaS.com requires an email address on every Employee record and rejects one that is empty. UKG Ready does not impose the same requirement, so an employee can exist there with the field blank.

What this means for you. Those employees will not reach iPaaS.com, and the attempt appears in Dashboard / Integration Monitoring / Error Logs so you can identify them. You have two options: populate the primary email address in UKG Ready, which is preferable because the stored value is then a real contact address; or ask your MiSP to change the EmailAddress mapping to supply a fallback value when the source is empty, accepting that the stored address is not a working contact.

UKG Ready does not notify iPaaS.com when an employee record changes. The integration retrieves changes on the schedule you set for the employee/poll event.

What this means for you. A change made in UKG Ready becomes visible in iPaaS.com on the next scheduled run. Choose a polling frequency that matches how quickly your downstream processes need employee data. When you need a specific employee updated immediately, transfer that one employee from the Manual Sync page.

UKG Ready only reports employees changed within the last 30 days. The integration records where each run finished and asks for changes since that point.

What this means for you. If polling does not run for more than 30 days — a paused subscription, an expired credential, a disabled event — changes made during the gap are never reported, and the run that resumes will not report success any differently. Set the schedule well inside the 30-day window, and re-check it after any period when the integration was paused or disconnected. To recover employees missed during a longer gap, transfer them individually from the Manual Sync page.

UKG Ready can hold a separate mailing address alongside an employee's primary address. This release transfers the primary address only.

What this means for you. An employee whose correspondence address differs from their primary address will show only the primary one in iPaaS.com. If your workflow depends on the mailing address, submit a feature request through your iPaaS.com partner channel describing how you use it — input like this informs future enhancement releases.

The address is transferred as part of its employee, not on its own.

What this means for you. There is no way to sync an address by itself, and no Manual Sync entry point for addresses. To refresh an address, re-sync the employee it belongs to. Addresses also arrive on the same polling schedule as their employees.

The integration covers the employee's core record and their primary address. Profile detail, pay rates, and rate tables remain in UKG Ready.

What this means for you. Compensation data is not available in iPaaS.com through this integration. Reporting or downstream processes that need pay rates should read them from UKG Ready directly.

The integration does not transfer custom field values on employees, addresses, timesheets, or time entries in either direction.

What this means for you. Any custom data your organisation maintains in UKG Ready stays there. If a specific custom field is important to your workflow, submit a feature request through your iPaaS.com partner channel naming the field and how you use it — input like this informs future enhancement releases.

Removing an employee in UKG Ready does not remove or deactivate the corresponding iPaaS.com Employee record, and delete mappings are not included in the default templates.

What this means for you. Employees who leave the organisation remain in iPaaS.com until they are removed there. Plan a periodic reconciliation if your downstream processes depend on the iPaaS.com employee list reflecting only current staff.

iPaaS.com records the link between a UKG Ready employee and their iPaaS.com Employee record on a dedicated external-ID record. For some record types the platform can fall back to matching on a primary-identifier field, but the iPaaS.com Employee record has no such field — it holds only the name, email address, and photo link.

What this means for you. The external-ID record is the only link between the two systems for an employee. If it is removed, a later transfer of that employee has nothing to match on and creates a second record. Treat removing an employee's external-ID link as a deliberate action, and expect to clean up a duplicate if that employee transfers again afterwards.

Timesheets flow from iPaaS.com into UKG Ready. Time entered directly in UKG Ready is not brought back into iPaaS.com.

What this means for you. If time is captured in more than one place, iPaaS.com will not show the full picture. Decide which system captures time, and use the other for its own purposes. Time entered directly in UKG Ready is preserved — the integration adds to a day's entries rather than replacing them — but it stays only in UKG Ready.

A timesheet only transfers when its employee has already been transferred to iPaaS.com and linked to their UKG Ready record. Timesheets for unlinked employees are skipped deliberately, and nothing is written to the error log.

What this means for you. This is the one limitation that produces no visible signal, so it is worth planning around. Transfer employees before enabling the outbound timesheet triggers. If timesheets were submitted before their employee was linked, they will not have reached UKG Ready and will need to be re-sent once the employee is in place.

The identifier this collection expects has four parts, and the fourth is generated by iPaaS.com when the timesheet is prepared for transfer. It is not visible anywhere a subscriber could copy it from beforehand.

What this means for you. Move timesheets using the outbound triggers under Outbound Data Flows rather than by entering identifiers by hand. A Manual Sync identifier for a timesheet can only be taken from a transfer that has already run.

UKG Ready distinguishes worked time from extra pay. The shipped mappings send worked time.

What this means for you. Extra-pay amounts are not delivered by this integration. Transferring them would need a separate mapping collection, because the start and end times these mappings supply do not apply to extra pay. If extra pay is part of your process, submit a feature request through your iPaaS.com partner channel describing the entries you need to send — input like this informs future enhancement releases.

UKG Ready supports pay categories, cost centres, premium shifts, piece work, and time-off types on a time entry. The default mappings supply the day, the start and end times, and the entry type.

What this means for you. Entries arrive in UKG Ready without that additional detail, and anyone who needs it applies it in UKG Ready. Detail applied there is preserved — a later transfer of the same timesheet changes only the values the mappings supply and leaves everything else on the entry untouched.

UKG Ready maintains its own calculated start time, end time, and total for each entry. The integration does not supply or overwrite them.

What this means for you. Totals and calculated times in UKG Ready are produced by UKG Ready's own rules, not by iPaaS.com. Differences between what iPaaS.com recorded and what UKG Ready shows are the result of those rules — rounding, shift policies, or pay rules — and should be investigated in UKG Ready.

After writing a timesheet, the integration reads the entries back to link each one to the iPaaS.com entry it came from. Where UKG Ready supplies no identifier, it matches on the pair of start and end times.

What this means for you. Two entries for the same employee on the same day with exactly the same start and end times are indistinguishable. Avoid creating duplicate entries with identical times, and use the additional detail UKG Ready offers to separate them if your process genuinely produces two such entries.

Currently, initialization is not supported for UKG Ready in iPaaS.com.

What this means for you. No separate initial load is needed for employees — the first run of the employee poll retrieves the complete employee list, so the subscription populates itself. Timesheets have no historical backfill; they flow to UKG Ready as outbound triggers fire. To move a large volume of existing timesheets, see the iPaaS.com guidance on bulk sync using Postman.

This article covers 19 known limitations. For detailed technical documentation of each transfer, see the mapping collection descriptions in the iPaaS.com mapping configuration page and the mapping documentation articles below.