Fix QuickBooks Time Issues
Timesheets, Sync & Tracking Problems

QuickBooks Time stops syncing to QuickBooks Online when the API authorization token connecting the two platforms expires or is revoked. This is an integration-layer failure — both applications continue working individually, but the connection between them is no longer active even though it appears connected in settings. The most common triggers are a QBO update that changes the API version, an Intuit account password change that invalidates the existing authorization, or a QuickBooks Time subscription change that resets the integration state.

Re-authorizing the integration — through QuickBooks Time settings under the QuickBooks Online integration section — resolves most sync breaks without needing to remove and re-add the integration from scratch. Visit the time not syncing fix page for the re-authorization steps. If a pay period is closing within 48 hours and timesheets have not synced, contact a live agent immediately — manually entered time data is the fallback for payroll processing when the sync cannot be restored in time.

QuickBooks Time GPS tracking failures on employee phones are almost always caused by device-level location permission settings rather than a problem with QuickBooks Time itself. Both iOS and Android require the location permission to be set to "Always Allow" — not "While Using App" — for GPS breadcrumb tracking and geofencing to function correctly during shifts. Battery optimization settings on Android devices frequently restrict background location access for apps not actively in use, which prevents QuickBooks Time from recording location points after the screen locks. A device OS update often resets location permissions to a more restrictive default without notifying the user.

The fix requires updating location permissions and disabling battery optimization specifically for QuickBooks Time on each affected device. Visit the GPS tracking error fix page for the per-device configuration steps. Contact a live agent if GPS failures are affecting a large number of employees simultaneously after a device OS update was pushed across the company's mobile fleet.

A QuickBooks Time kiosk PIN that does not work is caused by one of three conditions — the employee's PIN was never set up in the admin portal and the employee is attempting to use a default or assumed PIN, the PIN was changed or reset in the admin portal but the kiosk device has not synced the update and is still running the old employee list, or the kiosk device itself has lost its connection to the QuickBooks Time service and is operating on a cached state that no longer matches the current account configuration.

The fastest first step is confirming the employee's PIN directly in the QuickBooks Time admin portal — not relying on what the employee reports the PIN to be. If the PIN is correct in the portal, force a sync refresh on the kiosk device by restarting the kiosk app. Visit the kiosk PIN error fix page for the step-by-step verification and sync process. Contact a live agent if the kiosk device has lost its connection to the QuickBooks Time service and cannot be reconnected through a standard restart.

QuickBooks Time offline mode entries that do not upload after the device reconnects are caused by one of three conditions — the app was force-closed or updated before pending offline entries were transmitted, the device has reached a storage limit that prevents the sync queue from completing, or there is a sync conflict between the offline entry and a server-side entry for the same time period that the conflict resolution logic cannot automatically resolve. Offline entries are stored locally on the device in a queue — if the queue is cleared before entries upload, the time data is permanently lost from the device.

Before attempting a fix, confirm whether the offline entries are still visible in the app's pending sync queue. If they are, ensure the device has a stable WiFi or cellular connection and that the app remains open in the foreground until the sync completes. Visit the offline mode error fix page for the manual sync trigger process. Contact a live agent if entries are no longer visible in the pending queue and may need to be manually recreated before payroll processing.

Timesheet approval failures in QuickBooks Time occur when a manager account has not been assigned the correct permission level to approve the specific employees under their supervision, when a timesheet has been locked after a prior approval attempt that did not complete cleanly, or when a QuickBooks Time update reset the approval workflow settings to the default configuration, removing custom approval chains that were previously active. Approval failures block the final step of the payroll pipeline — approved timesheets cannot sync to QBO, and payroll cannot process without that sync completing before the pay period close.

Check the manager's role in QuickBooks Time settings to confirm they are assigned as an approver for the affected employees — this is separate from their general admin or manager role. Visit the timesheet approvals error fix page for the permission verification steps. Contact a live agent if approval failures are blocking payroll processing and a pay date is approaching.

For QuickBooks Time issues that are affecting payroll — timesheets not syncing before a pay period close, approval errors blocking payroll data transfer, or offline entries that may be lost — phone support is the only channel fast enough to prevent incomplete time data from reaching a payroll run. A live agent can access both the QuickBooks Time service layer and the QBO integration layer, identify whether the failure is a permission issue, a sync break, or a data conflict, and guide through the resolution before the pay date window closes. Visit the QuickBooks live agent page to connect now, view the QuickBooks support number directly, or see all contact options on the contact page.