ClockLap + ADP Workforce Now: approved hours into your pay data batch

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 ADP Workforce Now.

Pay data goes in as one event per person, so a problem with one person’s data doesn’t hold up everyone else. Earning codes are read from your company in ADP, so you pick from your own list.

Ways to connect

How it works

1. Create a project in ADP API CentralAdd Workers v2, Payroll Data Input, Time Entries (only with Time & Attendance) and worker event notifications, and give the project access to your company codes.
2. Upload ClockLap’s certificate requestClockLap makes a private key and a certificate signing request (CSR). The key never leaves ClockLap; you upload the CSR under Manage certificate and paste back the signed certificate with the client ID and secret.
3. Match peopleClockLap reads your ADP workers and matches them by email, then employee number, then ADP associate ID. Anyone left over is listed for you to match or ignore.
4. Map earning codesPick an ADP earning code for each pay type you use. Suggestions are filled in (REG, O/T, HOL, VAC, SCK).
5. Choose when to send, and reviewSend each period yourself, when the period locks, when everything is approved, or on a schedule. The first send is a preview you check line by line.

Schedules and review

Choose when hours go to ADP Workforce Now. 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.

Pay data adds to the open batch, so a correction sends only the difference: +1.5 hours of O/T, or −2 hours of REG. Time cards are corrected by removing the earlier entries for the changed day and adding the new ones. If ADP times out or fails mid-send, ClockLap doesn’t resend pay data blindly (ADP may already have it); the run tells you exactly what to check.

People

Matched by email, employee number, then ADP associate OID. The match is remembered as the person’s ADP ID, and the Paydata file uses each person’s ADP file number.

Turn on the HR side of the same connection and Workforce Now becomes the source of truth for your people.

• Workers: name, email, employee number, department, work location, manager, hourly pay rate, hire date, status
• Time off balances per leave type

Approved time off isn’t sent to ADP: requests there go through ADP’s own approvals.

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

The file

Paydata import (EPI). Columns: Co Code Batch ID File # Temp Dept Reg Hours O/T Hours Hours 3 Code Hours 3 Amount Hours 4 Code Hours 4 Amount

Regular and overtime have their own columns; other codes go in coded hours, with extra rows when someone has more than two. A correction file is numbered 02.

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

• ADP Workforce Now (Canada or US) with access to ADP API Central for your company (ask your ADP representative if you don’t see it)
• An admin who can create an API Central project and manage its certificate
• Your 3-character ADP company code (e.g. 4FX)
• For time cards: ADP Time & Attendance
• For instant people updates: the project subscribed to worker event notifications

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