ClockLap + Dayforce: hours as pay adjustments, keyed by XRefCode

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

Each adjustment carries its own unique reference from ClockLap, so a retry after a timeout can’t add it twice.

Ways to connect

How it works

1. Set up a web services userA Dayforce admin creates a user for web services with access to employees and pay adjustments.
2. Enter your Company IDThe client namespace you sign in with, e.g. northwind. Choose Test while you try it.
3. Match employeesBy email, employee number, then Dayforce XRefCode.
4. Map pay codesYour pay adjustment code XRefCodes.
5. Choose when to send, and reviewThe first send is a preview.

Schedules and review

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

Direct: a correction first deletes the adjustments sent before for each changed person (or day), then adds the new ones. File: a correction file carries only the differences.

People

Matched by email, employee number, then Dayforce XRefCode, which is saved on the person.

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

Dayforce pay import (CSV). Columns: EmployeeXRefCode PayCodeXRefCode Hours Amount BusinessDate OrgUnitXRefCode Comment

Rename columns with the custom payroll file if your import template uses different headers.

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

• Dayforce (Canada or US)
• A Dayforce user set up for web services, with access to employees and pay adjustments
• Your Company ID (client namespace); optionally the API address Dayforce gave you

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