What syncs
Every approved timesheet is split into pay types first (regular, overtime, double time, holidays, break premiums, time off), using each site’s rules. Here’s where each lands in UKG Ready.
| ClockLap | Sent as | Notes |
|---|---|---|
| Hours worked per day | Time entry (TIME) with the day’s total | In milliseconds, as UKG Ready asks |
| Overtime and other pay types | Pay category | Optional: leave unmapped to let UKG Ready’s pay rules decide |
Pay categories are read from UKG Ready, so you pick from your own list. Periods longer than 31 days are sent in parts (UKG Ready’s limit per request).
How it works
- Create an OAuth application in UKG ReadySettings → Global Setup → Company Setup → OAuth Applications, with REST API rights for employees and time entries.
- Paste it with your address and companyThe address you sign in at (e.g. secure4.saashr.com) and your company short name or ID.
- Match peopleBy email (user name), then employee ID; saved as each person’s UKG Ready account ID.
- Map pay categories (optional)For overtime or holiday hours, if you don’t want UKG Ready to work them out.
- Choose when to send, and reviewEach period yourself, on lock, when everything is approved, or on a schedule.
Schedules and review
Choose when hours go to UKG Ready. Whatever you pick, nothing is sent twice: each period has one send, and anything after it is a correction.
I’ll send each period myself
Nothing goes until an admin presses Send. The default.
When the pay period is locked
Locking the period in Timesheets starts the send.
When every timesheet is approved
The last approval in the period starts the send.
On a schedule
A set number of days after the period ends (0 to 14), at a local time you pick.
- Which timesheets. Approved only (default), or approved and submitted.
- Rounding. Hundredths of an hour (default) or quarter hours.
- Split by. None, location, project or department, each mapped to the payroll system’s department or cost centre code.
- Holiday hours worked. As their own pay type (default) or folded into regular hours.
- Empty lines. People with no hours in the period are skipped.
- Unmatched people. Skip them and warn (default), or block the whole send until they’re matched.
Corrections, as changes
Fixed a missed clock-out after payroll went? Send the period again and ClockLap works out what changed since the last send.
Each send replaces the person’s ClockLap days for the period on their timesheet, so a correction simply sends the changed person’s period again. Nothing is added twice.
People
Matched by email (UKG Ready user name), then employee ID.
People who can’t be matched are listed in the preview: skip them with a warning (default) or block the send until they’re matched.
What you need
- UKG Ready with timekeeping
- A company admin who can create OAuth applications
- Your UKG Ready address (ends in saashr.com) and company short name
Every run keeps a history: who and what was sent, per-line results, plain-language errors with a fix, and a redacted request log for admins. Webhooks fire on payroll.run_ready, payroll.run_sent, payroll.run_failed.
Questions
Will it overwrite hours people punched in UKG Ready?
It replaces time entries for the people and dates ClockLap sends. If some people also punch in UKG Ready, send only the locations that use ClockLap.
UKG Ready said “call limit”. Is that a problem?
No. UKG Ready throttles busy companies; ClockLap waits and tries again.
Is the UKG Ready connection included in the price?
Yes. Payroll and HR connections are part of every ClockLap plan: $1 per staff member and $2 per manager or admin a month, with no add-ons.
Is ClockLap affiliated with UKG Ready?
No. ClockLap connects to UKG Ready using its published API; it isn’t affiliated with or endorsed by UKG Ready. The connection is in beta while we verify it with live accounts.