What Xero says itself
This is not an inference. On Xero's own product ideas forum, a request for automatic award wage setting carries the status "Not in pipeline". Xero's David Reynolds responded that they do not have immediate plans to build this directly into Xero Payroll, and directed users to the Xero App Store, noting that several third-party integrations offer embedded awards and are designed to handle complex award interpretation.
That is a clear and honest position from Xero, and it is worth taking at face value. Xero has decided award interpretation is somebody else's job. The trouble is that plenty of businesses using Xero have not realised a decision was made.
What Xero automates, and what it does not
| Task | Xero | Notes |
|---|---|---|
| PAYG withholding | Automatic | Uses current ATO tax tables |
| Superannuation guarantee | Automatic | Calculated and lodged |
| Single Touch Payroll | Automatic | Reported each pay run |
| Leave accrual | From your setup | Accrues per the rules you enter |
| Which award covers the employee | You | Xero holds no award data |
| Which classification level applies | You | The step where most errors begin |
| Base rate for that classification | You | A number you type in |
| Penalties, overtime, loadings | You | Configured as pay items with multipliers |
| Allowances | You | Must be identified and added manually |
| 1 July rate increases | You | Xero cannot know the new correct rate |
Where this actually goes wrong
A Xero pay template is a photograph of somebody's interpretation of an award on the day it was set up. It is usually correct on that day. It degrades quietly afterwards, in four predictable ways.
- The 1 July increase. The Fair Work Commission lifts award rates annually. Xero does not know the new number, so unless a person updates every affected pay template, the business underpays from the first pay run in July and keeps doing it.
- Classification drift. Someone takes on supervision, or a qualification, or a different set of duties. Their classification should move up. The pay template does not, because nothing connects the two.
- Missing allowances. First aid, laundry, tools, travel, meals. These are small individually and invisible in a payslip that otherwise looks fine, and they compound across a team and a year.
- Shift context the payslip never records. This is the one that catches people out. A flat hourly rate can look generous against the base rate and still be an underpayment, because the work was performed at night, or on a public holiday, or at a higher classification for part of the week. Nothing in Xero knows that, so nothing flags it.
Three ways to close the gap
Do it by hand, properly. Map every employee to award and classification, build the pay items from the award text, and diarise a review each 1 July and whenever a role changes. This works for a simple award and a stable, small team. It fails when the person who understood the setup leaves.
Add an award-aware rostering tool. Deputy, Tanda, RosterElf and similar hold award rule libraries, interpret the shift data, and pass calculated hours into Xero. This is a good fit for shift-based workforces. The cost is that your award logic now lives in two systems and can drift apart.
Check the output independently. Read the pay run Xero produced and test it back against the award. The point of doing it this way is that it catches an error in the original configuration rather than faithfully repeating it, which is the one thing neither of the first two options can do for you.
Common questions
Does Xero update award rates on 1 July each year?
Not by itself. Because Xero does not hold the award, it does not know what an employee's minimum rate should become when the Fair Work Commission announces the annual wage review increase. The rates in your pay templates are values you entered, so somebody has to update them each year. Xero publishes reminders about award changes, but applying the correct new rate to the correct classification remains a manual task.
How do you handle Modern Award interpretation with Xero?
There are three common approaches. The first is to configure pay items and pay templates by hand from the award and diarise a review every 1 July and whenever a role changes. The second is to add a rostering or time and attendance app with an award rules library, such as Deputy, Tanda or RosterElf, which interprets the shift data and passes calculated hours into Xero. The third is to add an independent check layer that reads the pay run Xero produced and tests it against the award, so an error in the original configuration is caught rather than repeated.
Is it safe to use Xero Payroll for award-covered employees?
Yes, provided the award interpretation happens somewhere. Xero is reliable at calculating and disbursing pay from correct instructions. The risk is not that Xero calculates badly, it is that nothing in Xero verifies that the rate, classification, penalties and allowances you configured were the right ones. Under the Fair Work Act that obligation sits with the employer, so an award-covered workforce needs either a rigorous manual process, an award-aware tool feeding Xero, or an independent check on the output.
Keep Xero. Add the check.
FairCheck reads the payslips and pay run data your payroll produced and tests them against the award or agreement that actually applies, including the classification step Xero never sees. In beta now, with early access opening to the waitlist first.
Join the waitlist Compare all four systemsFairCheck is an independent product and is not affiliated with, endorsed by or sponsored by Xero. Xero is a trade mark of Xero Limited. This page describes publicly documented product behaviour as at 2 September 2026 and is general information, not legal advice.