QuickBooks Time overtime rules: only one rule pays per timesheet
QuickBooks Time applies only one overtime rule per timesheet, and daily rules beat weekly ones; here is how the Pay Rate Engine decides.
QuickBooks Online teams that track hours in QuickBooks Time keep hitting the same wall. Custom overtime rules that look right on paper pay out differently in practice. We read the accepted guidance on the Pay Rate Engine, and most surprises trace back to a single principle: a timesheet can carry only one rule.
The affected product and the design behind the confusion
QuickBooks Time, the time tracking service that works alongside QuickBooks Online, offers a Pay Rate Engine for customized pay rules. Users build daily overtime, holiday premiums, night differentials, and weekly overtime in it, then watch the results diverge from expectations. The accepted answer describes the behavior as designed rather than broken. Every outcome traces back to that one policy.
The symptoms that show up in community threads
The pattern repeats across threads. Weekly overtime fails to appear on a short final day. A night premium vanishes on a holiday. Overtime will not export to payroll until the right pay types exist there. In each case the engine followed its own rules; the setup assumed a stacking the system does not support.
One rule per timesheet, and the highest rate wins
Once a rule has been applied to a timesheet, no second rule can attach to that time. Where rules overlap or conflict, exactly one survives. For daily, consecutive day, time of day, and holiday rules, the comparison happens on the day the timesheet is created. Whichever rule carries the highest rate multiplier is the one that pays.
Two quirks follow. Shift differential and holiday hours count as overtime inside the system even when they technically are not. If one of those rules lands on the time first, no other rule will apply to it.
Why didn’t weekly overtime trigger?
Weekly overtime does not calculate until a team member logs 40 hours of regular time, or whatever weekly threshold you set. Daily rules run first, and that includes the final days of the week. The guidance offers a plain illustration: a week of 8, 8, 8, 8, and 9 hours produces one hour of daily overtime. The ninth hour never becomes weekly overtime, because the daily rule already claimed it.
Overtime rules also apply only to regular time. They skip other overtime, time off, and breaks. Once a timesheet is flagged as overtime, it accepts no further rules. A shift cannot collect both a differential and weekly overtime; it gets one or the other.
What happens when time flows into QuickBooks Online Payroll?
Exporting adds its own requirements. Employees who track overtime in QuickBooks Time need the matching pay types added in Payroll, with overtime set up there, or the export will not land correctly. Teams using the Pay Rate Engine with the integration must also map the overtime pay items for each rule inside the rule editor.
The mapping has a hard ceiling. Only rates of 1.5x and 2.0x can map to the Overtime and Double Overtime pay types in QuickBooks Online Payroll. A 1.75x night premium has no standard slot to land in.
A worked example from the guidance
The accepted answer walks through a sample setup with four rules. Daily overtime pays 1.5x above 8 hours in a day, a holiday rule pays 2x, and a time of day rule covers 8 PM to 8 AM at 1.75x. A weekly rule then pays 1.25x above 40 hours.
A short Sunday shift earns plain regular time, because nothing in the setup qualifies. A holiday shift that runs into the evening is more telling. The holiday rate outranks the night rate, so the higher multiplier takes the qualifying hours.
The guidance attaches a caution of its own. The example illustrates the mechanics; it is not a pay recommendation. Anyone customizing these settings should check the labour laws that apply to their workforce first.
Getting the numbers you expect
The practical fix is design, not repair. Plan rules knowing that only one will pay on any given timesheet, and that the highest multiplier wins on the day the timesheet is created. If you need a premium and daily overtime on the same hours, the engine will not stack them.
For clean exports, keep mapped rules at 1.5x or 2.0x, and confirm the pay types exist in Payroll before you send time over. Anything beyond those multipliers needs a plan for how it will be paid outside the two standard overtime types. Once the one-rule principle sinks in, the payouts stop surprising you.