RUN POWERED BY ADP SETUP GUIDE

One complete import.
Everyone accounted for.

Review the full employee selection and worked hours for a RUN pay frequency, then verify the imported timesheet before completing payroll.

RUN US hourly employeesFor company managersWorkspace links require sign-in

Start with the supported ADP product

This guide covers TakeUrTime's RUN Powered by ADP US integration for active US hourly W-2 employees paid in USD. Workforce Now credentials are not interchangeable with RUN, and other ADP products require separate integrations.

Integrations are available on every TakeUrTime plan. Live RUN delivery also requires an authorized ADP client subscription and setup by the application operator. Your internal TakeUrTime Payroll workspace can remain off.

TakeUrTime supplies worked hours; payroll is completed in RUN.
IncludedHandled separately
Approved regular, overtime and second overtime worked hours using mapped earning codes.PTO, holidays, local payroll adjustments and pay-rate overrides are excluded.
Paid breaks included once; unpaid breaks excluded from worked hours.Schedules and individual clock punches are not delivered by this import.
One complete timesheet import for the selected pay frequency, using RUN's BASE rate.Importing into payroll, resolving payroll errors, final approval and payment remain in RUN.

Verify the provisioned RUN company

Open Company Settings → Integrations → ADP.

  1. Ask the application operator to provision the ADP-approved RUN client subscription, credentials and client certificate for your company. No credential entry is required in the browser.
  2. Read the displayed Provisioned RUN US company name. Confirm that this authorized subscription belongs to your TakeUrTime company.
  3. Select Verify and save connection.
  4. Enable and save Employees and Payroll inputs in the company feature controls.
  5. Confirm the Recorded time zone used by existing TakeUrTime clocks, then select Save time settings.

While access is being arranged, use Open sample ADP demo in the integration workspace. It uses synthetic data and requires no API account or connection. The demo does not send real payroll hours.

Match eligible hourly employees

  1. Select Load ADP RUN employees.
  2. Choose the TakeUrTime employee and the corresponding active US hourly W-2 employee in RUN.
  3. Compare the full name and business email. Correct missing or ambiguous email details before matching.
  4. Confirm the identity and select Verify and save employee match.

For a review, each selected employee must belong to the chosen RUN pay frequency, with a hire date on or before the period's first date. Check the hourly BASE rate in RUN before proceeding.

After reconnecting, verify employee and earning mappings again. Removing an employee match removes its earning mappings; it does not remove an import already delivered to RUN.

Map earning codes and confirm BASE rates

  1. Choose the matched TakeUrTime employee and select Load earning codes.
  2. Select the Worked-hours category and its existing ADP RUN earning code.
  3. Verify that the code accepts hours, the employee has a valid hourly BASE rate, and RUN applies the intended regular or overtime treatment.
  4. Confirm and select Save earning-code mapping. Repeat for every category used by the employee.
Required mappings for this integration.
TakeUrTime categoryRUN mapping
Regular hoursREG
Overtime hoursOVT
Second overtime hoursA distinct employee hours code with its hours and multiplier treatment confirmed in RUN. Do not use REG, OVT or a 1099 code.

Mappings are saved per employee. Verify earning-code effective dates for the work period and check date. TakeUrTime sends hours using the BASE rate code; it does not send its local rate or monetary amounts.

Review the whole pay-frequency import together

  1. Resolve open shifts, missing approvals, overlapping records and outstanding corrections in TakeUrTime.
  2. Select Load open pay cycles. Choose the intended RUN pay cycle and check its first date, last date and check date.
  3. Select all intended matched employees in that frequency. One review supports up to 32 completed days, 50 employees and 100 earning lines.
  4. Select Prepare payroll-hours review. Resolve every listed issue.
  5. Expand inspect proposed hours and supporting records for each employee. Compare earning codes, BASE-rate treatment, rounded hours and supporting work dates. Inspect the original complete import if shown.
  6. Verify that the hours are not entered elsewhere. Coordinate with other payroll administrators so RUN pay setup and the import stay unchanged during delivery.
  7. Confirm the complete selection and select Queue complete RUN import.

Hours are rounded to two decimals per work date and earning category. Paid leave and holiday credits are excluded. The review expires after 30 minutes; changed records, approvals, rates, mappings or cycles may require a fresh review.

Why does the review show one submission for several employees?

The selected employees are sent together as one complete pay-frequency import. The submission count is not a count of employees. Check every employee row before confirming.

What if the complete group exceeds the limits?

Coordinate an alternative payroll process with your administrator. Do not split the same pay frequency into successive imports or omit employees simply to fit the limit.

Verify the timesheet and its payroll import

An Accepted result means the RUN import was read back using its returned item ID and the submitted hours matched. RUN can still report errors when the payroll practitioner imports that timesheet into payroll.

  1. Inspect the delivery in Delivery history and retain the recorded ADP import ID.
  2. Open Saved reviews → Inspect review and select Check current RUN import.
  3. Compare the returned employee hour lines and earning codes with the complete saved review.
  4. In RUN, inspect the full timesheet and any errors when importing it into payroll. Verify rates and payroll amounts before final processing.
Use the recorded import ID when investigating results.
ResultNext action
Submitted hour lines matchReview the full timesheet and payroll in RUN. Matching hours do not mean payroll has been processed.
Recorded import differsCompare the original review with the complete RUN timesheet and resolve the difference there.
Recorded import no longer returnedIt may have been consumed or removed in RUN. Investigate the original import; its absence does not authorize a resend.
No provider receipt ID confirmedKeep the outcome unresolved. A current import with matching hours alone is not proof that it belongs to this delivery.

Resolve corrections against the original import

An unchanged delivered review shows Already delivered. Changes to the original import or connection show Correction held. There is no automatic whole-batch replacement.

Example: one employee was missed.

If an import for eight employees has already been sent and a ninth should have been included, inspect the original complete import and coordinate the correction in RUN. Do not send a second import containing only the ninth employee.

The same care applies to changed hours, empty results and imports created elsewhere. TakeUrTime does not overwrite an external import or treat an empty review as a deletion. Preserve the original delivery history while correcting payroll in RUN.

If delivery is uncertain

  1. Keep the delivery held. A timeout can still leave a created import in RUN.
  2. Open Delivery history and select Reconcile with provider. Reconciliation can verify the original operation only when a returned item ID is known.
  3. Use Check current RUN import in the saved review, then resolve the original outcome with your payroll administrator or ADP support.

No ID, a missing batch or a failed lookup does not prove that nothing was created. Do not resend, adopt another batch by matching hours, disconnect or remap employees to bypass the hold.

Common setup and review questions

There is no provisioned company, or live delivery is disabled.

Ask the application operator to check the authorized RUN US subscription, server credentials, certificate and company pilot verification. Workforce Now access cannot substitute for RUN access. The sample demo remains separate from live delivery.

Prepare or Queue is unavailable.

Check the connection, saved Employees and Payroll inputs controls, confirmed recorded time zone, open pay cycle and selected matched employees. Queue also needs a current review with no issues, a ready import and your confirmation.

The employee will not match or cannot join this review.

Check active status, US hourly W-2 eligibility, USD pay, full name and business email. For the review, also check the assigned pay frequency, hire date and hourly BASE rate. Correct the profile and verify the match again.

A shift crosses the cycle boundary or a daylight-saving change.

The import requires complete, approved, non-overlapping shifts within the selected cycle. Shifts crossing a time-zone offset change are blocked. Have a manager review the original records; do not reinterpret old clocks by changing the recorded time zone.

The review expired or source data changed.

Inspect Delivery history first, then prepare a fresh complete review for the original cycle when instructed. If the earlier import was delivered or its result is uncertain, resolve that record before attempting another submission.

What information helps support investigate?

Provide the RUN company, pay frequency, period and check date, affected employees, review or delivery ID, returned import item ID if available, and exact error. Include what RUN shows for the original import. Exclude credentials, certificates and private keys.