ADP Time Tracking Integration for Field Crews

If you run payroll in ADP, Friday usually means re-typing a week of crew hours from texts, notes, and paper. Clox lets your crew clock in from their phones, then hands you an ADP-ready file to import. Here is how the export works with both ADP RUN and Workforce Now.

If you run your crew's payroll through ADP, you already know how Friday goes. Someone texts you their hours. Someone else wrote them on the back of a receipt. You reconcile it all in your head, then re-type every number into ADP by hand. One transposed digit and you are cutting a correction the following week.

Clox closes that gap. Your crew clocks in with one tap on their phones, hours accumulate by person and project all week, and when it is time to run payroll you export a file that ADP is built to read. You pick ADP RUN or ADP Workforce Now depending on which product you use, and the file matches what that product expects. No re-keying, no reconciling texts.

How the export works

The whole flow is four steps, and only the last two happen at payroll time.

1. Your crew clocks in and out on Clox all week. It is one tap on their phone, it works offline, and you can lock clock-in to a geofenced worksite as a deterrent against off-site punches.
2. You review the week on the web. Hours are already totaled by person and project, and overtime is calculated for you.
3. You approve the hours and export the ADP-ready file from the Reports page.
4. You import that file into ADP RUN or Workforce Now the same way you import any timesheet file.

The export menu lives on the Reports page. It only shows the payroll systems you have turned on, so once you pick ADP you get one clean button instead of a wall of options.

What is in the file

Clox writes exactly the columns ADP expects. The layout depends on which ADP product you run, because RUN and Workforce Now import hours differently.

ADP RUN (Time Sheet Import)

For RUN, Clox writes a generic Time Sheet Import CSV. It opens with a version line, ##GENERIC## V1.0, followed by the header row. RUN splits pay by earnings code rather than by column, so Clox writes one row per employee per earnings code: a regular row and a separate overtime row.

Overtime is pre-split by Clox before the file is written, so the OT row already carries the correct hours. If you use the optional California rule set, double-time comes through as its own DT earnings-code row rather than being folded into overtime.

ADP Workforce Now (Import Paydata)

For Workforce Now, Clox writes an Import Paydata CSV with one row per employee. Regular and overtime hours sit in their own columns on the same row, and ADP matches each row to a worker by File number.

Here overtime is pre-split into the O/T Hours column. Under the California rule set, double-time is folded into overtime for Workforce Now, so it lands in that same column.

Set it up once

Setup takes a few minutes and you only do it once. After that, every payroll run is just review, approve, export.

1. In Clox, go to Settings, then Integrations, then Payroll, and select ADP. Choose whether you run ADP RUN or ADP Workforce Now.
2. Enter your company-level ADP settings in Clox: your Co Code, pay frequency, earnings codes, and any rate or batch values ADP expects for your setup.
3. On the Team page, give each worker their payroll ID. That is the same ID ADP knows them by. RUN uses it as the Employee ID and Workforce Now uses it as the File number.
4. Run a small test export and import it into ADP to confirm the codes and IDs line up before your first live payroll.

You can see the plans on the pricing page, or start a free trial and connect ADP the same day.

Common questions

We already do it by hand. Why change?

Doing it by hand works right up until it does not. The cost is not just the hour you spend re-typing, it is the corrections when a number is wrong and the hours you cannot easily prove later. Clox replaces the re-typing with a file ADP already reads, and keeps a record of who clocked in where and when.

Does it handle overtime?

Yes. Clox calculates overtime automatically, with standard daily-8 and weekly-40 defaults that you can configure per employee. The engine splits regular and overtime hours before the file is written, so in RUN they arrive as separate earnings-code rows and in Workforce Now they arrive in separate columns. There is an optional California rule set that adds daily double-time and a meal-break review flag.

What if a job runs across two pay periods?

You export by pay period, not by job. When you run the export you pick the pay-period start and end dates, and Clox only includes the hours that fall inside that window. A job that spans two periods simply shows up in both exports, each with the hours worked during that period.

How does ADP know which worker is which?

By the payroll ID you set on the Team page. In RUN it becomes the Employee ID and in Workforce Now it becomes the File number. As long as that ID matches the one ADP has on file, every row lands on the right person. That is why the setup test is worth doing once.

Use a different payroll system?

Clox exports to more than ADP. If you run something else, the setup is the same idea. Read the guide for Gusto, Paychex, or QuickBooks. There is also a universal Payroll summary CSV that always appears in the export menu and maps into any provider.