INTEGRATION SETUP GUIDE
Connect with confidence.
Check every handoff.
Choose what your company shares, match the right records and understand the result before taking the next step.
Check access and scope first
Integrations are available on every TakeUrTime plan, including free. You still need a supported provider account and any access, permissions or approval required for that connection. Read the selected provider's availability message before starting.
- Sign in as a company manager and confirm the provider company or legal entity you intend to connect.
- Have the employee and earning identifiers needed for matching.
- Review the supported operation and any recorded-time-zone setting. Confirm how a sample shift's dates will appear in the destination.
- Decide who will review delivery results and complete payroll inside the provider.
Know what each connection sends
The workflows below describe the TakeUrTime integration screens. Use the selected provider's setup message for the access requirements and operations available to your company.
| Connection | TakeUrTime workflow |
|---|---|
| QuickBooks Online setup guide | Approved, non-billable time entries. This does not create accounting transactions or run payroll. |
| Gusto setup guide | Reviewed approved shifts using existing employees, with a separate step to apply approved time to payroll. |
| Rippling setup guide | Reviewed time and breaks as drafts. Rippling applies its own overtime and payroll policies. |
| Paycor setup guide | Reviewed worked hours for the paygrid. A successful submission still requires checking the full paygrid. |
| Paychex setup guide | Draft checks from reviewed worked hours. Check the resulting earnings before submitting payroll there. |
| RUN Powered by ADP setup guide | A timesheet import of reviewed hours. Check import results and payroll in RUN. |
| OnPay setup guide | Reviewed approved hours for matched employee pay items. Payroll processing remains in OnPay. |
| Xero Payroll Australia setup guide | Australian draft timesheets for matched hourly employees. This workflow is not a general worldwide Xero payroll connection. |
Connect and choose company features
Open Company Settings → Integrations.
- Choose the provider and read its connection availability and setup instructions.
- Complete the provider's connection or authorization process. Confirm the connected company or account shown afterward.
- Under Company feature preferences, enable only the supported data types your company intends to share.
- Select Save feature preferences. Provider-specific panels may have additional settings and confirmation steps.
- Review the integration status and any setup issues before preparing a delivery.
Each feature switch applies to that provider only. Turning a feature off stops new deliveries from starting, but requests already in progress may still finish.
A provider is listed, but I cannot connect.
Read its availability message. A TakeUrTime plan does not remove provider approval, account-product, regional or configuration requirements. Give support the provider name and displayed message if the reason is unclear.
Match employees and required codes
- Load the provider's employees or identifiers using its setup controls.
- Match each TakeUrTime employee to the correct existing provider employee. Check identity rather than relying only on a similar display name.
- Complete any job, earning, leave, site or other matching required by the selected workflow.
- Save and review validation results. Resolve missing or invalid matches before preparing time.
The shared Employee and code mappings panel accepts provider identifiers. Manual mappings are unverified until the provider adapter validates them. Leaving an identifier blank removes that mapping.
Prepare a review, then inspect the send result
- Resolve source-time issues, approvals and required reviews in TakeUrTime.
- In the provider panel, choose the required dates, employees or payroll period and prepare its review.
- Check the matched employees, hours, categories, destination period, recorded time zone and warnings.
- Confirm only when the saved review matches the intended handoff. If sources or mappings change, prepare a fresh review.
- Open Delivery history and inspect individual records, not just a batch total.
- Compare the result inside the provider before approving or processing payroll there.
Acceptance confirms the operation described by that provider's receipt. It is not a universal guarantee that payroll totals are correct, payroll is approved or wages are paid.
Read delivery status before taking action
Use Delivery history filters such as Needs attention, Pending and retrying, or Accepted. Open a record for Delivery detail, Original captured source and Recorded events.
| Status | Next step |
|---|---|
| Pending / Retry | Check prerequisites and the next eligible attempt. Do not create a duplicate delivery. |
| Sending / Processing | Work is in progress. Follow the status check available for that provider; pausing cannot recall an in-flight request. |
| Accepted | Inspect the destination result. Accepted records are preserved and cannot simply be retried. |
| Uncertain | Do not send again. Check or reconcile the original provider operation; a timeout may still have created a record. |
| Rejected | Read the reason, correct the source and prepare a newly reviewed source. The original rejected record remains intact. |
| Failed | Non-acceptance was confirmed. Retry only when the application offers it, within the delay and attempt limits. |
| Blocked | Resolve the source or credentials issue. No automatic retry will start. |
| Cancelled | The unsent record was cancelled. Its captured source and history remain available. |
Handle uncertain or partial results carefully
Retry when eligible attempts an eligible failed delivery. Reconcile with provider or a provider-specific status check looks for the outcome of the original operation. They are different actions.
Paycor reports an uncertain result.
This import workflow does not provide a published import-status lookup. Keep the record held and give Paycor support the Process ID and saved payload through an appropriate support channel. Do not resend, append or replace the import to work around uncertainty.
ADP or Paychex cannot find the original result.
Follow the record's provider-specific message. ADP reconciliation relies on a known returned item ID; a missing ID or batch does not prove absence. Paychex uses its returned check ID or exact correlation; a missing record does not authorize a resend.
Only part of a batch succeeded.
Open each result and compare it with the provider. Preserve accepted records and resolve only the affected records using the supported workflow. Do not resend the entire batch. For a partial Gusto payroll sync, inspect the provider receipt and resolve the affected employees there.
Optional name, leave and schedule workflows
Employee profile updates
Where supported, choose a provider as the source for first or last names, compare matched active employees, and review the selected changes before applying them. Only one provider can supply each name field. Email remains the TakeUrTime login; contact details, access and pay settings stay in their existing screens.
Rippling leave and balances
The leave workflow uses TakeUrTime approvals and sends reviewed approved leave or cancellations only after a manager confirms a saved review. Match leave types and verify recorded time-zone dates. Provider balances can be shown alongside TakeUrTime balances; neither balance is overwritten.
Rippling published schedules
Enable the required Employees and Schedules controls, then review published assignments before confirming delivery. Planned hours remain separate from worked time and payroll. Employee-visible notes are optional and off by default; manager-only notes are not shared. Planned break minutes are reference text because their timing is not recorded in the schedule.
Pause, reconnect or switch providers
- Inspect pending, sending and uncertain records before changing the connection.
- Turn off the relevant feature if you want to stop new deliveries from starting. Allow for already-started requests to finish.
- Resolve outstanding outcomes against the original provider account.
- When reconnecting or selecting another company, review employee and code mappings again.
- If moving name-field ownership, turn it off in the current provider before enabling the new source.
- Prepare fresh reviews under the new connection and confirm the destination account before sending.
Disconnecting does not recall an accepted record or erase the need to resolve an uncertain one. Later changes to accepted data require the provider-specific update, correction or reversal process.
Common setup problems
Connected, but nothing has been sent.
Check saved feature preferences, provider-specific setup, validated matches and whether a manager has confirmed a saved review. Connection alone is not permission to send every record automatically.
The review expired or the source changed.
Follow the delivery message, correct the source or mapping, and prepare a fresh review. Accepted records remain recorded. Cancel an unsent record only when that action is offered and appropriate.
Old QuickBooks time IDs block another send.
Legacy time IDs need reconciliation before those shifts are sent again. Reconnecting does not make old delivered shifts new. Review the preserved history and follow the QuickBooks workflow.
What information helps support?
Provide the provider, connected company, review or delivery ID, status, time of the action and exact error. Include the provider receipt or Process ID where available. Do not send access tokens, passwords or client secrets.