Customising Overtime Rules in QuickBooks Time for Australian Users

Sydney, Australia, QuickBooks Time users often seek to tailor overtime calculations to match local labour agreements or internal policies. The process relies on the Pay Rate Engine, which lets administrators create rules that apply different multipliers to regular hours. However, many encounter unexpected results when rules overlap or when exporting data to QuickBooks Online Payroll. This report explains how the engine works, where confusion typically arises and what steps produce the expected outcome.

Understanding How Overtime Rules Are Applied

The Pay Rate Engine evaluates several rule types on the day a timesheet is created. Daily, consecutive days, time of day and holiday rules are assessed first. If more than one rule could apply to the same block of time, the engine selects the rule with the highest rate multiplier and applies only that one. Weekly overtime rules are calculated later, after the day‑level rules have been applied. Weekly overtime only triggers once the employee has accumulated the configured threshold of regular hours, commonly 40 hours per week.

It is important to note that once a timesheet segment is labelled as overtime, no further rule can be stacked on top of it. For example, if a shift differential rule marks certain hours as overtime, a weekly overtime rule will not also be applied to those same hours. This prevents double counting but can lead to situations where users expect both a daily premium and a weekly premium to appear on the same timesheet.

Common Points of Confusion

Users frequently report that their custom overtime settings do not produce the anticipated pay amounts. A typical symptom is seeing only one type of premium on a timesheet even though multiple rules were configured. This usually stems from the precedence rule described above: the engine picks the highest multiplier and discards lower ones for that segment.

Another point of confusion involves the treatment of shift differential and holiday hours. The system counts these as overtime internally, which means they block any additional rule from being applied to the same time. Users who expect holiday pay to stack with weekly overtime may find that only the holiday rate appears.

When sending time to QuickBooks Online Payroll, mismatches can occur if the overtime pay items in Payroll do not correspond to the rules defined in the Pay Rate Engine. Exported data may show regular pay instead of the expected overtime or double overtime amounts, leading to underpayment errors that require manual correction.

Setting Up Custom Overtime in the Pay Rate Engine

To create a custom overtime configuration, administrators navigate to the Pay Rate Engine within QuickBooks Time Settings. Here they can add a new setting, assign it to specific teams or individuals and define one or more rules. Each rule requires a type (daily, holiday, time of day or weekly) and a rate multiplier. The engine only accepts multipliers of 1.5 or 2.0 for direct mapping to the overtime pay types in QuickBooks Online Payroll, although other values can be used for internal calculations if the data is not exported.

When creating rules, it is helpful to think about the order in which they should apply. Because the engine selects the highest multiplier for overlapping periods, placing a rule with a lower multiplier after a higher one will never result in the lower rule being applied to the same block of time. If a business needs both a daily premium and a weekly premium, the daily rule must be set to a lower multiplier than the weekly rule, or the schedule must be structured so that the two rule types never apply to the same hours.

Mapping Overtime Pay Types for QuickBooks Online Payroll

For customers who use QuickBooks Online Payroll, the Pay Rate Engine includes a mapping step. In the rule editor, each rule can be linked to either the Overtime Pay Type or the Double Overtime Pay Type that exists in the Payroll module. The mapping ensures that when time is exported, the correct pay item is used.

Only the 1.5 and 2.0 multipliers can be mapped directly to those pay types. If a rule uses a different multiplier, the exported time will be treated as regular pay unless a custom pay type is created in Payroll to match the multiplier. Administrators should verify that the mapping is saved and that the pay types in Payroll are active for the relevant employees.

After mapping, a test export is recommended. Running a payroll preview for a sample employee helps confirm that the overtime amounts appear as expected before processing a full pay run.

Example Calculation for a Work Week

Consider an employee who works the following schedule during a week:

• Sunday: 4 hours (12 pm – 4 pm)
• Monday: 8 hours (1 pm – 9 pm) – a public holiday
• Tuesday: 9 hours (8 am – 5 pm)
• Wednesday: 9 hours (8 am – 5 pm)
• Thursday: 9 hours (8 am – 5 pm)
• Friday: 9 hours (8 am – 5 pm)
• Saturday: 0 hours

Assume the Pay Rate Engine setting includes four rules:

1. Daily rule – 1.5× for hours over 8 per day
2. Holiday rule – 2.0× for hours worked on the holiday
3. Time of day rule – 1.75× for hours between 8 pm and 8 am
4. Weekly rule – 1.25× for hours over 40 in the week

Applying the engine:

• Sunday yields 4 regular hours (no rule applies).
• Monday is a holiday, so the holiday rule (2.0×) applies to all 8 hours, blocking any other rule for that day.
• Tuesday through Friday each have 9 hours. The first 8 hours are regular; the ninth hour exceeds the daily threshold, so the daily rule (1.5×) applies to that extra hour. No time‑of‑day premium occurs because none of the hours fall between 8 pm and 8 am.
• Total regular hours across the week equal 4 (Sunday) + 8×4 (Tuesday‑Friday) = 36 hours. The holiday hours are not counted toward the weekly threshold because they are already marked as overtime.
• Weekly overtime only triggers after 40 regular hours, which is not reached, so the weekly rule does not apply.

The resulting pay consists of 4 regular hours at base rate, 8 holiday hours at 2.0×, 4 daily‑overtime hours at 1.5× and the remaining 32 hours at base rate. This example illustrates how rule precedence and the blocking effect of holiday or shift differential rules shape the final calculation.

Final Tips for Users

When customising overtime, start with a clear list of the premiums that must appear and the conditions under which each should apply. Build rules in the Pay Rate Engine with the highest multipliers first, then add lower‑multiplier rules only if they apply to mutually exclusive time blocks. Verify mappings to QuickBooks Online Payroll before running a live payroll, and use the preview feature to catch mismatches early.

If unexpected results persist, review the timesheet details to see which rule the engine selected for each segment. The system highlights the applied rule in the timesheet view, making it easier to trace why a particular premium appeared or was omitted. By following these steps, QuickBooks Time users in Australia can achieve overtime calculations that align with their payroll policies and avoid common pitfalls.