Summary
iPaaS.com timesheets can be transferred to UKG Ready through outbound triggers, sending the time entries that make up each timesheet into the employee's UKG Ready time record. Each transfer merges the incoming entries with what UKG Ready already holds for that employee and period rather than replacing them. The transfer is one-way; time entered directly in UKG Ready is not brought back into iPaaS.com.
ID Format
Manual Sync ID Format
This collection expects four values joined by pipe characters: the UKG Ready employee identifier, the period start date, the period end date, and a system-generated reference.
All four parts must be present and correctly formed — a whole number, two valid dates, and the system-generated reference — or the value is rejected and the transfer does not run.
The fourth part cannot be composed by hand. iPaaS.com creates it when the timesheet is prepared for transfer, and it is not visible anywhere a subscriber could copy it from beforehand. A Manual Sync identifier for this collection can therefore only be taken from a transfer that has already run. Use the outbound triggers described under Mapping Collection Status to move timesheets rather than entering identifiers manually.
External ID Format
After a successful transfer, iPaaS.com records the link between the iPaaS.com timesheet and the UKG Ready time entries it produced. A repeat transfer of the same timesheet follows that link and updates those entries rather than creating a second set.
UKG Ready holds a single set of time entries per employee per day and does not expose a stable identifier for the set as a whole, so the link is maintained on the iPaaS.com side. Several iPaaS.com timesheets covering the same day contribute to that one UKG Ready set rather than existing independently.
Deleted Record Support
Outbound delete is supported. Deleting a timesheet in iPaaS.com removes the corresponding time entries from UKG Ready, and the timesheet/deleted trigger is available for subscribers who want deletions to propagate automatically. Subscribers or their MiSP who do not want deletions to reach UKG Ready should leave that trigger disabled.
Mapping Collection Status
Status: Enabled, with a mapping filter applied to the parent collection. See the Mapping Filter block under Mappings for which timesheets are processed and which are skipped. The child collection carries no filter of its own.
Trigger Events: the events timesheet/created, timesheet/updated, timesheet/deleted, and timesheet/bulk, enabled by subscribers or their MiSP in the subscription configuration's Outbound Data Flows section. No timesheets transfer automatically until at least one is enabled. Whether a transfer adds new entries or updates existing ones is decided by whether the timesheet is already linked to UKG Ready, not by which event triggered it.
Duplicate or Conflicting Mappings
No other mapping collection in this integration writes timesheets or time entries to UKG Ready, so there is no risk of two collections competing for the same records.
Within UKG Ready the transfer updates only the values these mappings supply on an entry it matches, and adds entries it does not find. It does not clear time entries that already exist for the same employee and period, so time recorded directly in UKG Ready — and detail such as a pay category or cost centre applied there — survives a transfer.
Supported Child Collections
Parent Collection: Add/Update UKG Ready Timesheet FROM iPaaS.com
Add/Update UKG Ready Timesheet Entry FROM iPaaS.com: supplies the individual time entries that make up the timesheet — the day, the start and end times, and the entry type. The entries are written as part of the parent transfer, in a single operation, and are linked back to the iPaaS.com timesheet entries they came from.
System Caveats
UKG Ready Caveats
The employee must exist in UKG Ready and be linked: this is what the mapping filter checks. An employee created directly in UKG Ready but never transferred into iPaaS.com is not linked, and timesheets referencing them are skipped.
Write results are reported inside the response rather than as a failure: UKG Ready accepts the write and reports the outcome for each entry within its reply. The integration inspects that reply and raises any problems it reports, so a rejected entry does appear in Dashboard / Integration Monitoring / Error Logs — but a transfer that reports no problems is the only confirmation that the entries were accepted.
Time entries are organised by day: UKG Ready holds a single set of entries per employee per day.
Calculated values are UKG Ready's own: UKG Ready maintains a calculated start time, end time, and total for each entry. The integration does not supply or overwrite those values.
Service account permissions: the API credentials configured on the subscription must retain the Web Services permission that allows writing time entries, or transfers fail with an authentication error.
iPaaS.com Caveats
Employees must be transferred first: transfer employees through Add/Update UKG Ready Employee TO iPaaS.com before enabling outbound timesheet triggers, so that early timesheets are not silently skipped.
Outbound triggers must be enabled: no timesheet transfers automatically until an event is subscribed in Outbound Data Flows.
Timestamps without a time zone offset are treated as UTC: confirm in a staging environment that entries land on the expected clock time for the UKG Ready company before relying on this in production.
Setup Requirements
iPaaS.com Configuration
Enable the outbound triggers this collection should respond to under Outbound Data Flows in the subscription configuration. Enable timesheet/deleted only if deletions should propagate to UKG Ready.
UKG Ready Configuration
No timesheet-specific configuration is required in UKG Ready beyond the service account already used by the integration, which must retain permission to write time entries. Credential setup is covered in the UKG Ready Installation Instructions article.
Ordering
Employees must be transferred into iPaaS.com and linked before timesheets for those employees will transfer. Enabling the outbound triggers before employees are linked results in timesheets being skipped without notice.
Integration Flow
An outbound trigger fires for a timesheet, or a subscriber runs a transfer for one.
The mapping filter checks whether the employee named on the timesheet is already linked to a UKG Ready employee. If not, the timesheet is skipped silently and the flow ends here.
The integration resolves the UKG Ready employee identifier from that link.
It retrieves the time entries UKG Ready already holds for that employee across the period the timesheet covers.
It merges the incoming entries with what UKG Ready already holds. An incoming entry that matches an existing one updates it, changing only the values these mappings supply; an incoming entry with no match is added.
It writes the merged set of entries back to UKG Ready for that employee and period in a single operation.
It reads the entries back to confirm what was recorded, matching each one to the iPaaS.com timesheet entry it came from — by identifier where one is available, otherwise by start and end time.
Mappings
Add/Update UKG Ready Timesheet FROM iPaaS.com
iPaaS.com data type: Timesheet
Mapping Filter
GetExternalId(EmployeeId, "Employee", SpaceportSystemId) != null
Filter Description. The filter checks whether the employee named on the iPaaS.com timesheet has already been transferred to UKG Ready and linked to their UKG Ready employee record.
Timesheets whose employee is linked pass the filter and are sent to UKG Ready. Timesheets whose employee is not linked are skipped silently — no record is written and no error is raised, so nothing appears in Dashboard / Integration Monitoring / Error Logs to indicate the timesheet was passed over.
This is deliberate: without the employee link the integration has no UKG Ready employee to attach the time to. The practical consequence is that subscribers or their MiSP must transfer an employee before any of that employee's timesheets can reach UKG Ready, and should re-send any timesheets submitted before the employee was linked.
Description: Identifies the UKG Ready employee and the period the timesheet covers, then writes the timesheet's entries through the child collection.
Mapping Type | Source Field (iPaaS.com) | Destination Field (UKG Ready) | Description |
Dynamic Formula |
| EmployeeId | Required. Resolves the UKG Ready employee account identifier from the external-ID link recorded when the employee was transferred. UKG Ready is addressed by its own account identifier rather than the iPaaS.com one, so this translation is what allows the timesheet to reach the right employee. When no link exists the formula returns no value and the transfer fails. |
Field | StartDateTime | StartDate | Required. The beginning of the period the timesheet covers. With EndDate it defines the range used to locate the employee's existing entries in UKG Ready. Sent as a date; any time component is not used to bound the period. The transfer fails if the value is empty or not a valid date. |
Field | EndDateTime | EndDate | Required. The end of the period the timesheet covers. With StartDate it defines the range used to locate the employee's existing entries in UKG Ready. Sent as a date; any time component is not used to bound the period. The transfer fails if the value is empty or not a valid date. |
Add/Update UKG Ready Timesheet Entry FROM iPaaS.com (Child)
iPaaS.com data type: Timesheet Entry
Description: Supplies the individual time entries written into UKG Ready as part of the parent transfer. This collection runs only as part of its parent; it has no filter, no independent trigger, and no Manual Sync entry point.
Mapping Type | Source Field (iPaaS.com) | Destination Field (UKG Ready) | Description |
Dynamic Formula |
| Date | Required. Reformats the entry's date into the year-month-day form UKG Ready expects, for example 2026-01-12. UKG Ready organises time entries by day, so an entry without a date cannot be placed. The iPaaS.com entry always carries a date, so the formula always produces a value. |
Dynamic Formula |
| StartTime | Required. Reformats the start time into the date-and-time-with-offset form UKG Ready expects, for example 2026-01-12T08:00:00.000+00:00. Values with no offset of their own are treated as UTC. When the source is empty the formula returns no value and the field is sent empty; the entry is still submitted. |
Dynamic Formula |
| EndTime | Required. Reformats the end time into the same form, for example 2026-01-12T17:00:00.000+00:00. Values with no offset of their own are treated as UTC. When the source is empty the formula returns no value and the field is sent empty; the entry is still submitted. |
Static |
| Type | Required. Tells UKG Ready what kind of time entry is being created. Fixed to TIME, UKG Ready's entry type for worked time. The other value UKG Ready accepts is EXTRA_PAY, for amounts paid outside worked time; sending those would require a separate mapping collection, because the start and end times these mappings supply do not apply to extra pay. Being a Static mapping, there is no source value that could be empty. |
StartTime and EndTime carry a second responsibility: when the integration reads the entries back after writing them, it uses the pair to identify which iPaaS.com entry each UKG Ready entry came from. Two entries for the same employee on the same day with identical start and end times cannot be told apart.
Error Handling
"Employee Account Id is required but was not supplied": the transfer reached the write step without a UKG Ready employee identifier. In normal operation the mapping filter prevents this by skipping timesheets for unlinked employees, so seeing this error means the link was lost between the filter check and the write. Confirm the employee is still transferred and linked, then re-send the timesheet.
"There were errors saving your time entries: [detail]": UKG Ready accepted the request but rejected one or more entries, and the detail names what it objected to. Common causes are an entry whose day falls outside the period the timesheet declares, or a value UKG Ready will not accept on a time entry. Correct the entry in iPaaS.com and re-send the timesheet.
Authentication failures during a transfer: the API credentials on the subscription are wrong, expired, or have lost the Web Services permission that allows writing time entries. Confirm the service account is still active in UKG Ready and that its credentials on the subscription still match, then re-send.
Timesheets that never appear in UKG Ready and produce no error: this is the filter behaving as designed, not a failure. The employee is not linked. Transfer the employee, then re-send the timesheet.
For the full catalogue of errors this integration can raise, see the UKG Ready Error Messages article.
Testing & Validation
Test Scenarios
Transfer an employee into iPaaS.com, confirm the link exists, then create a timesheet for that employee with several entries and confirm all of them appear in UKG Ready against the correct day.
Change one entry's start and end times in iPaaS.com, re-send the timesheet, and confirm the existing UKG Ready entry is updated in place rather than duplicated.
Add a time entry directly in UKG Ready for the same employee and period, then re-send the timesheet from iPaaS.com and confirm the directly-entered time is still present afterwards.
Create a timesheet for an employee who has not been transferred to iPaaS.com and confirm it is skipped with no record written and no error raised.
Delete a timesheet in iPaaS.com with timesheet/deleted enabled and confirm the corresponding entries are removed from UKG Ready.
Confirm entries land on the expected clock time in UKG Ready for a timesheet whose entries carry no time zone offset.
Send two timesheets covering the same day for the same employee and confirm both contribute to the single UKG Ready set for that day.
Validation Checklist
Employees in scope have been transferred to iPaaS.com and are linked to their UKG Ready records.
The outbound triggers the subscriber wants are enabled under Outbound Data Flows.
timesheet/deleted is enabled only if deletions should propagate to UKG Ready.
The service account retains permission to write time entries in UKG Ready.
Entry times have been checked against the expected UKG Ready clock time in a staging environment.
Any timesheets submitted before their employee was linked have been identified and re-sent.
Additional Notes
Out of Scope
Reading timesheets or time entries from UKG Ready into iPaaS.com.
Approving or processing time — the integration records entries; approval, calculation, and payroll processing remain UKG Ready functions.
Pay categories, cost centres, premium shifts, and piece work on a time entry.
Time-off and extra-pay entries.
Entry totals and amounts, which UKG Ready derives from the start and end times.