ClockLap + Paycom: an hours file, and people from your export

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

Paycom switches its API on per company and doesn’t publish its reference, so ClockLap connects with files. The layout is a long-format CSV; check the first file with your Paycom specialist.

How it works

1. Match peopleBy employee code (saved as each person’s Paycom employee code), email or employee number.
2. Map earning codesType your Paycom earning codes; common ones are suggested.
3. Pick deliveryDownload, email or SFTP.
4. For people sync: the employee exportUpload Paycom’s employee export, or have it dropped on SFTP. The Employee Code column becomes each person’s Paycom ID.

Schedules and review

Choose when hours go to Paycom. 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.

A correction file for the same period carries only the differences.

People

Payroll files use each person’s Paycom employee code. People sync matches by earlier links, email and employee code.

Add a people sync connection to read Paycom’s employee export.

• Employee code, name, work email, department, location, manager, hire and termination dates, status

Time off isn’t read from the export.

• 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

Paycom hours (CSV). Columns: Employee Code Employee Name Earning Code Hours Date Department Code

Daily files carry one row per day.

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

• Paycom (US)
• Earning codes and employee codes from Paycom
• For people sync: a scheduled employee export (CSV), uploaded or on SFTP

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