ClockLap + Gusto: approved hours into your next payroll, automatically

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

ClockLap finds the unprocessed regular payroll whose dates match your ClockLap pay period, prepares it, and sets each employee’s hours.

How it works

1. Sign in with GustoAn admin approves ClockLap’s access to the company.
2. Match employeesBy email, then employee number, then Gusto employee ID.
3. Check the compensation namesGusto’s standard names are filled in; adjust them if your company uses others.
4. Choose when to sendMost teams send when the period is locked, with review on.
5. Run payroll in GustoOpen the payroll: hours are already there. Review and submit as usual.

Schedules and review

Choose when hours go to Gusto. Whatever you pick, nothing is sent twice: each period has one send, and anything after it is a correction.

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

Gusto’s payroll update sets values rather than adding to them, so a correction sends each changed person’s full hours again, including people whose hours went back to zero. Corrections only work while the payroll is still unprocessed.

People

Matched by email, employee number, then Gusto employee UUID, which is saved on the person.

The same sign-in can keep your people in step with Gusto.

• Employees: name, email, department, work location, manager, hourly rate, start date, status
• Company locations, to map to ClockLap sites
• Paid time off balances (accrual balance, in hours)

Gusto’s API doesn’t accept time off from other systems, so approved ClockLap time off isn’t sent back.

• Who wins, per field. The HR system by default: ClockLap is updated to match. Set any field to “ClockLap” and it’s only filled in when the person is added.
• New people. Added automatically, without an invite unless you turn invites on. You choose the role they get.
• People who leave. Suggested for turning off (default), or turned off automatically. Their history stays.
• Sites and teams. Map the HR system’s locations or departments to ClockLap sites once; moves follow on every sync.
• Single sign-on users. People your identity provider manages through SCIM keep what SCIM writes; the sync skips those fields and says so.
• Schedule. Hourly, daily (default) or manual. A scheduled sync can apply itself or only prepare a preview for an admin.

What you need

• Gusto (US) with an admin who can manage payroll and connect apps
• A pay schedule whose periods line up with ClockLap’s pay periods
• The regular payroll for the period still unprocessed when hours are sent

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, people_sync.completed.

Questions