QuickBooks Time Settings Are Moving Into QuickBooks Online

QuickBooks Time administrators are working through a slow-moving settings migration. Intuit is consolidating the time product’s configuration into QuickBooks Online, and the stated aim is simple: fewer places to hop between when something needs changing. During the transition, most settings can be edited from either product. The catch is that a growing share of them can only be edited from one.

The settings move, in short

QuickBooks Time has always kept its own company settings area, separate from the books. That separation is going away. The destination is a single settings home reached from QuickBooks Online, and until the move finishes, both entry points stay open. You can carry on in QuickBooks Time’s Company Settings as before, or reach the same controls through QuickBooks Online.

Nothing needs migrating by hand. The consolidation happens on Intuit’s side, and existing configuration carries across. Your job is narrower: know which product owns a field before you try to change it. The confusion around this move tends to trace back to that one point.

Two doors into the same controls

From QuickBooks Online, open the Settings gear, choose Account and settings, and select Time. From QuickBooks Time, go straight to Company Settings. While the migration runs, both paths expose the same options. One habit is worth forming now: save after each individual change. These pages do not batch edits, and an unsaved toggle is easy to lose when you move between screens. The QuickBooks Online route adds a Done button to close out a session.

Fields that answer to QuickBooks Online

Company details are the clearest case. Where QuickBooks Online or its payroll sits behind the time subscription, the company name, address, website, and admin contact flow in from the accounting side. Those fields still show in QuickBooks Time, but only as a view. Edits belong where the data originates. One small exception: a custom company logo can still be uploaded from the time product’s own settings.

Billing behaves the same way. The subscription is managed where it lives, and the billing screen inside QuickBooks Time is a window onto it rather than a second editing surface. Accountant access follows the same pattern. An invitation to a firm grants that firm full administrative rights over the time product, and firms on QuickBooks Online Accountant can accept on the spot. The invitation itself is handled alongside the books.

The pay schedule belongs to QuickBooks Online as well. Weekly, every two weeks, twice a month, every four weeks, and monthly are the available options. Set it once, at the source.

Why does overtime need setting in two places?

Here the vendor’s guidance is explicit. Overtime rules must be configured in QuickBooks Online and again in QuickBooks Time. The pay schedule travels with the books, but the overtime calculation does not, so a company that sets it once will find the other product still running on defaults. Where standard rules are not enough, a Manage Pay Rates option opens more granular settings. This split is easy to miss, and it is the one place where doing the work twice is the correct outcome.

The rest of the settings pages

Plenty remains fully editable in either product. Time management options, time rounding, timesheet customisation, locations, the team roster, kiosk management, and notification preferences all live in the shared settings. A system log completes the set, recording changes as they happen. If a preference ever seems to have moved itself, that log is the first place to look before assuming a fault.

If a field will not budge

Locked fields are not breakage; they are the migration working as designed. A greyed-out address, a billing screen without edit controls, or a missing pay schedule editor all point the same way. The data belongs to QuickBooks Online, and the change has to happen there. Make the edit, then check the time product to confirm the value arrived. Where a setting genuinely exists twice, treat the two entries as separate tasks rather than expecting one to propagate to the other.