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 Rippling.
| ClockLap | Sent as | Notes |
|---|---|---|
| Clock-in and clock-out | Time entry start and end | One entry per shift |
| Unpaid breaks | Breaks (start and end) | – |
| Site and notes | Comments | – |
| The worker | Worker ID | From matching |
No pay code mapping: Rippling turns time entries into regular and overtime pay itself.
How it works
- Create an API tokenIn Rippling: Settings → Company settings → API tokens, with workers and time entries access.
- Match workersBy email, employee number, then Rippling worker ID.
- Choose when to sendEntries are per shift, so there’s nothing else to set.
- Review the previewSee every shift before the first send.
- Approve in RipplingEntries appear in Rippling Time & Attendance for approval and payroll.
Schedules and review
Choose when hours go to Rippling. 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 removes the shift’s earlier time entry and sends it again with the new times.
People
Matched by email, employee number, then Rippling worker ID, which is saved on the person.
The same token keeps ClockLap’s people in step with Rippling.
- Workers with user and department details, manager, start date, status
- Work locations, to map to ClockLap sites
- Leave types and balances
Approved ClockLap time off can be recorded in Rippling as leave.
- 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
- Rippling with Time & Attendance
- An admin who can create company API tokens
- Token access to workers and time entries (and leave, for balances)
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
Why are shifts sent instead of pay codes?
Rippling applies its own overtime and pay rules to time entries. Sending the real clock-in and clock-out times keeps one set of rules, in Rippling.
How mature is this connection?
It’s in beta: the requests follow Rippling’s published REST guides. Keep “review before sending” on for your first periods and compare the preview with what lands in Rippling.
Is the Rippling 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 Rippling?
No. ClockLap connects to Rippling using its published API; it isn’t affiliated with or endorsed by Rippling. The connection is in beta while we verify it with live accounts.