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 Payworks.
| ClockLap | Sent as | Notes |
|---|---|---|
| Regular hours | Earning code REG | – |
| Overtime | OT | – |
| Holiday pay | STAT | – |
| Holiday hours worked | STATW | – |
| Vacation, sick | VAC, SICK | – |
| Location, project or department | Department | When you split |
Payworks’ time API is open to approved partners only, so ClockLap sends a file. Check the first file against your import template.
How it works
- Match peopleBy email or employee number; each person’s Payworks employee number is saved.
- Map earning codesREG, OT, STAT, STATW, VAC and SICK are suggested.
- Totals or dailyOne row per person and code, or per day.
- Pick deliveryDownload, email or SFTP.
- Import into PayworksBring the file into the pay run.
Schedules and review
Choose when hours go to Payworks. 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 only the differences for the period.
People
Matched by email or employee number; the file uses the Payworks employee number.
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
Payworks time import (CSV). Columns: Employee Number Earning Code Hours Rate Amount Date Department
Date is the period end, or the work date when sending daily.
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
- Payworks (Canada)
- Employee numbers and earning codes from Payworks
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
Can the file be dropped on an SFTP server?
Yes. ClockLap checks the server, pins its host key on the first connection, and writes under a temporary name before renaming, so nothing picks up half a file.
Is the Payworks 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 Payworks?
No. ClockLap connects to Payworks using files it can import; it isn’t affiliated with or endorsed by Payworks. The connection is in beta while we verify it with live accounts.