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 RUN by ADP.
| ClockLap | Sent as | Notes |
|---|---|---|
| Regular hours | Earnings code Regular | – |
| Overtime | Overtime | – |
| Holiday pay and holiday hours worked | Holiday | – |
| Vacation, sick, personal | Vacation, Sick, Personal | – |
| Department (when you split) | Department Number | – |
| Pay period | Pay Period Start / End, Pay Frequency | Weekly, every two weeks, twice a month or monthly |
Earnings codes are free text with RUN’s usual names suggested; change them to match your RUN setup.
Ways to connect
Time Sheet Import file
The usual way. The generic layout RUN documents: a version row, a heading row, then a row per person and earnings code. Delivered by download, email or SFTP.
Direct pay data
RUN’s API is only open to ADP Marketplace partners (API Central isn’t offered for RUN), so a direct connection needs an ADP Marketplace app set up for your ClockLap account. Ask us before you plan on it.
How it works
- Add your company detailsYour company code (IID) and pay frequency.
- Match peopleBy email or employee number, with each person’s ADP file number saved for the file.
- Map earnings codesRegular, Overtime, Holiday, Vacation, Sick and Personal are suggested.
- Choose when and how to deliverDownload it, email it to whoever runs payroll, or drop it on an SFTP server.
- Import into RUNImport the file into the pay run for the period.
Schedules and review
Choose when hours go to RUN by ADP. 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 second file for the same period carries only the differences (+ or − hours per person and code), so importing it on top of the first gives the right totals.
People
Matched by email, employee number or saved ADP ID. The file identifies people by ADP file number; direct pay data uses the associate OID.
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
RUN Time Sheet Import (generic layout). Columns: IID Pay Frequency Pay Period Start Pay Period End Employee Id Earnings Code Pay Hours Dollars Separate Check Department Number Rate Code
File name: ADP_RUN_{company}_{period_start}.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
- RUN Powered by ADP (US)
- Your company code (IID) and pay frequency
- Each person’s ADP file number (Employee Id) in ClockLap or matched once
- Earnings codes as they’re named in your RUN 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
Is there a direct RUN connection?
Only through an ADP Marketplace app, because RUN’s API is limited to Marketplace partners. Most RUN customers use the import file, which needs no API access at all.
Where do I import the file in RUN?
In your pay run, use RUN’s time sheet import and choose the file ClockLap built. Check the first one against your RUN setup, especially earnings code names.
Can I get the file emailed to my accountant?
Yes. Pick email delivery and add up to 20 recipients; the file arrives as an attachment when the send runs.
Is the RUN by ADP 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 RUN by ADP?
No. ClockLap connects to RUN by ADP using its published API; it isn’t affiliated with or endorsed by RUN by ADP. The connection is in beta while we verify it with live accounts.