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 Knit.
| ClockLap | Sent as | Notes |
|---|---|---|
| Every pay type you use | A column each | Stat holiday and stat holiday worked are separate |
Knit has no public API or published hours import, so ClockLap prepares a sheet instead of a file to import.
How it works
- Map pay typesName the columns the way they read in Knit.
- Pick deliveryDownload or email.
- Enter the hoursCopy each person’s hours into the Knit pay run.
Schedules and review
Choose when hours go to Knit. 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 sheet lists only the changes since the last sheet.
People
The sheet shows each person’s name and 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
Hours to enter (CSV). Columns: Employee Employee number Period start Period end one column per pay type Total hours
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
- Knit payroll (Canada)
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
Does it handle provincial stat holidays?
Yes. ClockLap works out holiday pay and hours worked on a holiday per province and puts each in its own column. Holiday rules are starting points to check, not legal advice.
Is the Knit 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 Knit?
No. ClockLap connects to Knit using files it can import; it isn’t affiliated with or endorsed by Knit. The connection is in beta while we verify it with live accounts.