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 Justworks.
| ClockLap | Sent as | Notes |
|---|---|---|
| Regular hours | Regular hours column | – |
| Overtime and double time | Overtime / Double time hours | – |
| Vacation, sick, personal, holiday pay | Paid time off hours | Or keep synced Justworks PTO by leaving them unmapped |
Justworks’ public API doesn’t take hours, so ClockLap builds the file. Justworks matches people by first name, last name and work email, and weeks run Sunday to Saturday.
How it works
- Check names and emailsJustworks matches on first name, last name and work email, so they should be the same in both.
- Map pay typesRegular, Overtime, Double time and Paid time off are suggested.
- Pick deliveryDownload or email.
- Import itIn Justworks: Timecards → Import Hours, upload the CSV and submit.
Schedules and review
Choose when hours go to Justworks. 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.
A correction file carries the changes per person and week. Justworks keeps the most recent import for a person, so check the totals before submitting.
People
No matching step: the file carries names and work emails, which is how Justworks matches.
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.
The file
Justworks Import Hours (CSV). Columns: First name Last name Work email Start date End date Regular hours Overtime hours Double time hours Paid time off hours
Check the first file against the template Justworks offers on the Import Hours screen.
Delivered by download (kept with the run), email to up to 20 people, or SFTP: ClockLap checks the server, pins its host key on the first connection and writes under a temporary name before renaming, so a payroll system watching the folder never picks up half a file.
What you need
- Justworks with default payroll periods and the “Manage All Timecards” permission
- Matching names and work emails in ClockLap and Justworks
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
Why not the Justworks API?
Justworks’ public API reads people and payroll but doesn’t accept hours. The Import Hours file is the documented way in.
Is the Justworks 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 Justworks?
No. ClockLap connects to Justworks using files it can import; it isn’t affiliated with or endorsed by Justworks. The connection is in beta while we verify it with live accounts.