Overview
This article catalogues every error the UKG Ready integration can record in the iPaaS.com error logs. Each entry carries a stable error code, the message exactly as it appears, what causes it, and how to resolve it.
Errors appear in Dashboard / Integration Monitoring / Error Logs. Every message begins with its code — for example UKGR-EXTN-1002 — so you can search this page for the code to find the matching entry.
Some resolutions refer to your Managed Integration Service Provider (MiSP) — the partner who set up and looks after your iPaaS.com integration, including its mappings, its connection settings, and its credentials. If you administer the integration yourself, those steps are yours.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Not every problem produces an error. Timesheets for an employee who has not yet been transferred to UKG Ready are skipped deliberately and silently — no record is written and nothing is logged. That behaviour is described in the UKG Ready Integration Known Limitations article and in the mapping documentation for the timesheet flow, not here.
Supported Flows
Add/Update UKG Ready Employee TO iPaaS.com
Add/Update UKG Ready Timesheet FROM iPaaS.com
Error Collection
Errors That Can Occur in Any Flow
Sign-in, connection, and identifier errors apply to every transfer the integration makes, in both directions.
Sign-In Failed
UKGR-AUTH-1001 - Failed attempting to login to the UKG Ready site ({details from UKG Ready})
Description: UKG Ready rejected the sign-in attempt. The details in brackets are UKG Ready's own response. This happens when the API User, API Password, API Key, or Company ID on the subscription is wrong or has changed, when the service account has been disabled or locked in UKG Ready, or when the account has lost the Web Services permission that allows it to sign in.
Resolution: Confirm with your UKG Ready administrator that the service account is still active and that its Web Services permissions are intact. Then have the API User, API Password, API Key, and Company ID re-entered on the subscription and the change applied. Note that the Company ID and the API Key are different values in different fields — swapping them is the most common cause. If your MiSP holds the connection settings, ask them to re-apply the credentials.
Cannot Reach UKG Ready
UKGR-EXTN-1001 - Unable to connect to UKG Ready: {details}
Description: The integration could not establish a connection to the UKG Ready environment at all — as distinct from connecting and being refused. The usual causes are an incorrect API Url on the subscription, a UKG Ready environment that is unavailable or in maintenance, or network filtering between iPaaS.com and UKG Ready.
Resolution: Check that the API Url on the subscription matches the environment you intend to reach, and confirm with your UKG Ready administrator that the environment is up. Your MiSP can verify the API Url if they hold the connection settings. If UKG Ready is available and the address is correct, the problem is network reachability between iPaaS.com and UKG Ready — contact iPaaS.com Support at support@ipaas.com with the message and the time it occurred.
UKG Ready Rejected the Request
UKGR-EXTN-1002 - Error calling UKG Ready {operation}: {details from UKG Ready} (Http Code: {code})
Description: The integration reached UKG Ready and made a call, and UKG Ready refused it. The operation names the call that failed and the details are UKG Ready's own response. Common causes are a service account that can sign in but lacks permission for the specific data being requested, a record that no longer exists in UKG Ready, or a value UKG Ready will not accept.
Resolution: Read the details in the message — UKG Ready states the reason. If it indicates a permission problem, have your UKG Ready administrator confirm the service account's Web Services permissions cover the data being transferred. If it indicates the record was not found, confirm the record still exists in UKG Ready. If the reason is unclear or the call should have succeeded, contact iPaaS.com Support at support@ipaas.com with the message and the time it occurred.
Invalid Record Identifier
UKGR-VALD-1001 - The {record type} identifier supplied for this transfer is not valid (problem with the {part}): {value}
Description: The identifier supplied for the transfer is not in the form the collection expects, so the transfer stops before any call is made to UKG Ready. The record type names the collection involved — Employee, Timesheet, or Timesheet Entry. The bracketed part appears only when the identifier has the right number of components but one of them could not be read. This occurs almost exclusively on a Manual Sync, where the value is entered or composed by hand.
Resolution: For an Employee, re-enter the employee's numeric identifier from UKG Ready on its own, with no prefix, suffix, or separator — for example 12345. For a Timesheet or Timesheet Entry, the identifier has four parts — the UKG Ready employee identifier, the period start date, the period end date, and a system-generated reference — joined by pipe characters. Because the fourth part is generated by iPaaS.com and cannot be composed by hand, these collections are not intended to be driven by Manual Sync: use the outbound triggers under Outbound Data Flows instead. If you are re-sending a timesheet that has already transferred once, take the identifier from that earlier transfer rather than assembling it.
Add/Update UKG Ready Employee TO iPaaS.com
Ambiguous Employee Lookup
UKGR-BIZL-1001 - More than one employee matches the requested external ID prefix
Description: A mapping used the conversion function that finds a UKG Ready employee from the beginning of an external identifier, and more than one employee matched. The function returns a single employee or nothing, so an ambiguous match stops the transfer rather than guessing.
Resolution: Confirm that external identifiers are unique across the employees in scope in UKG Ready. If they are not, either make them unique or ask your MiSP to supply a longer prefix in the mapping so the match resolves to a single employee.
Add/Update UKG Ready Timesheet FROM iPaaS.com
Employee Not Linked
UKGR-VALD-1002 - Employee Account Id is required but was not supplied
Description: The transfer reached the point of writing to UKG Ready without a UKG Ready employee account identifier. In normal operation the mapping filter prevents this by skipping timesheets whose employee has not been linked, so seeing this error means the link was lost between the filter check and the write — most often because the employee's external-ID link was removed while the transfer was in flight.
Resolution: Confirm the employee has been transferred through Add/Update UKG Ready Employee TO iPaaS.com and is still linked, then re-send the timesheet.
Time Entries Rejected
UKGR-EXTN-1003 - There were errors saving your time entries: {code} {message from UKG Ready}
Description: UKG Ready accepted the request but refused one or more of the time entries in it, and reported the reason for each. This endpoint reports entry-level problems inside its response rather than failing the whole call, so the integration reads that response and raises what it finds. Common causes are an entry whose date falls outside the period the timesheet declares, a start or end time UKG Ready will not accept, or an entry type that does not exist in your UKG Ready configuration.
Resolution: Read the message — UKG Ready names what it objected to and the code identifies the entry. Correct the affected entry on the iPaaS.com timesheet and re-send it. If several entries fail with the same reason, check whether the timesheet's period covers all the days its entries fall on.