QuickBooks Users in Australia Automate Allowances With Payroll Rule Sets
QuickBooks Online Advanced Payroll users in Australia can automate meal, tool, cold work and site allowances through pay condition rule sets.
A question that keeps surfacing from Australian employers asks how to stop adding employee allowances to each pay run by hand. The accepted answer, authored by Intuit, lays out a working method. It leans on pay condition rule sets inside QuickBooks Online Advanced Payroll, the Employment Hero powered tier sold in Australia.
The problem: allowances keyed in one employee at a time
Australian payroll often carries payments beyond ordinary wages. Meal money, tool payments for people who supply their own gear, extra rates for cold conditions, and site allowances all need to land in the right run.
Handled manually, these payments become a recurring chore. Someone has to remember who qualifies, check the hours or the location, and add the line before the run closes. Miss one and an employee goes underpaid, which then needs a correction.
Users raising the question want that judgment moved into the software. The payroll engine, in their view, should read the timesheets and apply each allowance on its own.
Do the rules work without timesheets?
No. The accepted answer states the limit plainly: pay condition rules interpret timesheet data into the pay run. Without timesheets, the rules have nothing to read and will not act.
That constraint shapes the whole setup. Every trigger in this method, overtime hours, work types, tags, and locations, reaches the pay run through the timesheet layer. Businesses that pay allowances without recording hours in the system get no automation from this route.
Only one payroll tier carries these settings
The steps apply to QuickBooks Online Advanced Payroll powered by Employment Hero, the version documented for the Australian market. Employers on other payroll tiers will not find the settings described here. The thread offers them no alternative, so manual entry remains their route.
The fix starts with pay categories
The accepted answer breaks the setup into stages, and stage one handles the money side. In payroll settings, you add a new pay category called Allowance, or a name like it, and set its units to Fixed.
Tax and superannuation treatment then depends on the allowance. For meal and tool allowances, the guidance marks the category as PAYG exempt and drops the superannuation rate to zero percent. Site allowances run the other way: no exemption, and the superannuation rate stays at its default.
Work types and tags carry the trigger
Stage two creates the signal a rule will read. For the cold work scenario, you add a work type under the pay conditions settings, named something like Work under 0 degrees, and switch it on for full time, part time, and casual employees.
One detail matters here. The work type maps to the Permanent Ordinary Hours pay category, not to the allowance category. The rule set adds the allowance when its condition is met, so the timesheet line itself stays as ordinary time.
Tags offer a second kind of signal. You tag the employees who supply their own tools, for example, and then aim a rule at that tag. One tag can steer a rule at a single person or a whole crew without touching anyone else.
The rule set applies the allowance
The last stage also sits under pay conditions, in the rule sets area. You can add rules to an existing rule set or award, or create a new rule set and edit its rules from there.
The answer then splits into four scenarios:
- Meal allowance: triggered by overtime hours, paying one unit once a set threshold of overtime is passed.
- Tool allowance: aimed at employees who carry a chosen tag.
- Cold work allowance: driven by a work type recorded on the timesheet.
- Site allowance: keyed to the employee’s location.
The takeaway for payroll admins
We traced the thread to its accepted resolution, and the method holds together. Once built, the setup does the remembering for you. Timesheets carry the overtime, the work types, and the locations, and the rule set turns those signals into allowance lines on its own.
The effort is front loaded. Pay categories, work types, tags, and rule conditions all need creating first, and each allowance type needs its own rule. Testing across a couple of pay runs before you rely on it is sensible practice.
The standing limit remains. Rules only translate timesheet data into pay, so a business without timesheets gains nothing here. For those employers, the manual method, allowance by allowance and run by run, is what the accepted answer leaves in place.