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 Square Payroll.
| ClockLap | Sent as | Notes |
|---|---|---|
| Each finished shift | A closed timecard | Start and end in the location’s time zone |
| Unpaid breaks | Cut out of the timecard | The shift is sent as one timecard per worked stretch |
| The team member’s job | Timecard wage (job, title, hourly rate) | From their Square job assignment |
Square works out overtime from timecards itself, so ClockLap sends worked time, not pay codes. Time off isn’t sent.
How it works
- Sign in with SquareAs the account owner or an admin; ClockLap asks for team, timecard and business profile access only.
- Match peopleBy email, then reference ID; saved as each person’s Square team member ID.
- Pick a location (optional)Timecards use each person’s first assigned location, or the one you choose.
- 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 Square Payroll. 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 changed shift’s earlier timecards are deleted and the shift is sent again. Each timecard has its own idempotency key, so a retry never creates a second one.
People
Matched by email, then Square reference 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
- Square with Square Payroll (US) and hourly team members
- An owner or admin to sign in
- Your ClockLap provider’s Square application (set up by whoever hosts ClockLap)
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
Do my team still clock in on Square?
No need: ClockLap’s geofenced clock-ins become the timecards. If some people still use Square’s clock, leave their locations out of the connection.
Is the Square Payroll 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 Square Payroll?
No. ClockLap connects to Square Payroll using its published API; it isn’t affiliated with or endorsed by Square Payroll. The connection is in beta while we verify it with live accounts.