ClockLap + Wagepoint: an hours file for every pay run

Approved hours, stat holidays and time off, laid out per employee and pay type, ready to bring into your Wagepoint pay run.

PayrollFileCAUSBeta
Preview before every sendBeta

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 Wagepoint.

ClockLapSent asNotes
Regular hoursPay type Regular–
OvertimeOvertime–
Holiday payStat Holiday–
Holiday hours workedStat Holiday Worked–
Vacation, sickVacation, Sick–

Wagepoint has no public API for hours (its time integrations are built by partners), so ClockLap sends a file. The layout is a long-format CSV; check the first one against your import template.

How it works

  1. Match peopleBy email or employee number; each person’s Wagepoint employee number is saved for the file.
  2. Map pay typesRegular, Overtime, Stat Holiday, Stat Holiday Worked, Vacation and Sick are suggested.
  3. Pick deliveryDownload, email (up to 20 recipients) or SFTP.
  4. Choose when to build itEach period yourself, on lock, when all is approved, or on a schedule.
  5. Bring it into WagepointEnter or import the hours in the pay run.

Schedules and review

Choose when hours go to Wagepoint. 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.

Review before sending. With “Let me review before sending” on (the default), ClockLap prepares a preview run instead of sending: who is included, hours per pay code, and any warnings. Admins get a notification with Send and Review buttons. Turn it off and scheduled sends go straight through.
  • 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 for the same period carries only the differences (+ or − hours per person and pay type).

People

Matched by email or employee number; the file uses the Wagepoint 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

Wagepoint hours (CSV). Columns: Employee Number First Name Last Name Pay Type Hours Pay Period Start Pay Period End

Employee Number,First Name,Last Name,Pay Type,Hours,Pay Period Start,Pay Period End 0007,Ava,Singh,Regular,80.00,2026-10-05,2026-10-18 0007,Ava,Singh,Stat Holiday,8.00,2026-10-05,2026-10-18

File name: wagepoint_hours_{period_start}_{period_end}.csv.

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

  • Wagepoint (Canada or US)
  • Employee numbers in Wagepoint
  • Pay type names as they appear in your Wagepoint account

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 a file and not a direct connection?

Wagepoint doesn’t offer a public API for hours. A file keeps you in control and works today.

Does it handle Canadian statutory holidays?

Yes. ClockLap works out holiday pay (including Ontario’s public holiday pay formula) and hours worked on a holiday, and maps each to its own pay type. Holiday rules are starting points to check, not legal advice.

Is the Wagepoint 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 Wagepoint?

No. ClockLap connects to Wagepoint using files it can import; it isn’t affiliated with or endorsed by Wagepoint. The connection is in beta while we verify it with live accounts.

Clock in by arriving. Paid without retyping.

Try ClockLap free for 30 days with your own Wagepoint account. No card needed.