Last quarter we sat with a Perth wholesaler who’d just renewed Employment Hero for another year and was wondering, out loud, why payroll lived in one system, time tracking lived in another, and the general ledger lived in Xero. Three logins, three exports, two reconciliations a fortnight. The bookkeeper had built a small empire of spreadsheets to keep them aligned. She was good at it. She also wanted her Wednesdays back.

That’s the question this article exists to answer. Odoo ships an Australian payroll module — but what does it actually cover, what doesn’t it, and when is the right move to consolidate onto Odoo versus keep a specialist payroll engine on the side. We run Odoo implementations across Western Australia and the eastern states, and we’ve made this call dozens of times. Here’s how we think about it.

What Odoo’s Australian payroll module actually includes

Odoo’s Australian localisation has matured fast. As of v17 it became usable for straightforward employer scenarios; as of v19 it covers the core compliance surface most small and mid-sized Australian businesses need. The module handles pay runs, generates compliant pay slips, calculates PAYG withholding, accrues leave, computes superannuation and files Single Touch Payroll events to the ATO. It is not a full enterprise payroll engine — but for many businesses, it doesn’t need to be.

Pay rules, structures and pay slips

Pay structures in Odoo are templates that bundle the salary rules applied to a category of employees. A salaried office worker, a casual warehouse picker and a full-time field technician each sit on a different structure with different pay rules — base, allowances, overtime, penalties, deductions and accruals. Australian default structures cover weekly, fortnightly and monthly cycles with PAYG, Medicare levy and the standard 11.5% super guarantee (rising to 12% on 1 July). Pay slips render as ATO-compliant PDFs with itemised earnings and YTD figures. None of this is exotic — but it works, and it works inside the same Odoo database that runs your invoicing and inventory, which is the whole point.

STP Phase 2 reporting in Odoo

Single Touch Payroll Phase 2 has been mandatory in Australia since 2022 and the v19 localisation files STP Phase 2 events natively. Each pay run generates an event with the disaggregated income types, tax categories, employment basis, country code and TFN context the ATO now requires. Submissions are sent through the Odoo-ATO connection without an intermediate clearing house. The module also handles update events for adjustments, finalisation events at end of year and back-dated corrections — the parts most teams forget about until July and then have a bad week.

Superannuation and SuperStream

Super contributions in Odoo are computed per pay run and grouped into a SuperStream-compliant batch ready for upload to your clearing house — typically the ATO Small Business Super Clearing House for businesses under twenty employees, or a commercial provider like SuperChoice for larger volumes. The module produces the standard SAFF file format. Choice of fund records sit on the employee, with stapled fund logic for new starters. From 2026 the payday super rules tighten payment timing dramatically, and the module is being updated to schedule contributions at pay run rather than quarterly — worth checking partner roadmap notes if this matters to you.

Setting up employees, awards and pay rules

Employees in Odoo carry the usual identity, banking and TFN details plus award classification, employment basis (full-time, part-time, casual, fixed-term), tax scale and stapled super fund. Pay rules are written as Python expressions tied to inputs — hours worked, rates, allowances — which gives a lot of power and an equal amount of rope. We treat the rule editor the way we treat custom code: version-controlled, peer-reviewed, tested against historical pay slips before any cutover. Most of our setups inherit from a default award template and customise from there rather than write from scratch.

What Odoo payroll does not yet cover

The module’s biggest limitation is at the complex end of award interpretation. If your business runs the Hospitality Industry General Award with split shifts, public holiday penalties, broken-shift allowances and minimum engagement rules, Odoo will not interpret those out of the box. Same applies to construction awards with multiple site allowances, the Nurses Award with shift loadings tied to start times, and most retail awards once weekend penalties stack. The module handles linear rules well; it handles conditional, time-of-day, day-of-week stacked rules less well than Employment Hero or KeyPay. Onboarding workflows, performance reviews and modern HRIS surface area are also lighter than dedicated HRIS products. None of this is fatal — it just sets the boundary.

Modern award interpretation: where Odoo stops and where you need help

Award interpretation is where most Australian payroll projects live or die. The Fair Work modern award system has 121 awards, each with its own classifications, allowances, penalties and engagement rules. Odoo’s pay rule engine can express most of them — but expressing them and maintaining them as Fair Work updates rates each July are different problems.

Where we see Odoo work well: salaried staff, simple casuals on a single classification, professional services with billable timesheets feeding into a flat hourly cost rate, manufacturing on day shifts with fixed overtime multipliers. Where we route clients toward a specialist tool: any award where penalty rates depend on the time the shift started, where allowances are conditional on task type, or where the award has been recently varied with retrospective effect. We’ve seen well-meaning teams try to encode the Restaurant Industry Award in Odoo pay rules and then quietly migrate to Employment Hero ten months later. The right answer was always to pair them.

A useful rule of thumb: if your payroll officer can describe the rules on a single A4 page, Odoo will hold them. If it takes a chapter, you need a dedicated award interpretation engine sitting in front.

When Employment Hero or KeyPay still makes sense alongside Odoo

For maybe a third of the businesses we implement, the right architecture is Odoo for everything except the payroll engine itself, with Employment Hero or KeyPay (now Employment Hero Payroll) handling award interpretation and STP filing. That looks like: rosters and timesheets in the specialist tool, hours flowing into Odoo as journals or as direct labour cost on jobs, super and PAYG liabilities posted as accounts payable for treasury to settle.

KeyPay has a published Odoo integration that posts pay run journals into Odoo’s accounting module on completion. Employment Hero offers a similar handoff — manual at the bottom tier, API-driven on higher plans. We’ve also built bespoke SFTP and webhook bridges where the standard integrations don’t fit.

The trade-off is honest: you keep two logins and two vendor relationships, but you also keep the best-of-breed award engine. For a Perth construction client running 60 site staff across three EBAs and the Building and Construction General On-Site Award, that handoff was the difference between a working project and a stalled one. For a 15-person professional services firm with everyone on salary, it would’ve been overkill — Odoo native payroll was plenty.

Migrating payroll mid-financial year vs at 1 July

The textbook answer is to cut over payroll on 1 July, when YTD figures reset and STP finalisation closes the prior year cleanly. The real-world answer is more nuanced. We move clients mid-year often — usually because the rest of the ERP go-live falls in March or October and forcing payroll to wait creates more pain than it saves.

A mid-year cutover means importing YTD earnings, PAYG, super and leave balances per employee into Odoo, then running parallel pay runs for one or two cycles to confirm the numbers match the outgoing system to the cent. It also means STP finalisation for the partial year happens out of the old system, and the first full-year finalisation out of Odoo covers the back half only. The ATO accepts this — it’s a known pattern — but the documentation and reconciliation overhead is real.

Our default: align with 1 July if the broader ERP timeline allows. If it doesn’t, plan two parallel cycles, document the cutover memo for the auditor, and get the bookkeeper extra coffee for that fortnight. We’ve never regretted being deliberate here; we have regretted rushing.

Real cost of running Odoo payroll in Australia

The payroll module sits inside the standard Odoo Enterprise licence — there’s no separate per-employee charge from Odoo itself. At AUD$47.40 per user per month for the All Apps tier (current Australian pricing as of 2026, billed annually), payroll is included. A 25-staff business with five Odoo users runs about AUD$2,840 in licences a year, all-in.

Implementation cost is where the real spend lives. A clean Odoo payroll setup for a single-entity business with one award, weekly pay cycle, super clearing house already in place and minimal historical data to migrate runs from about AUD$8,000 to AUD$15,000 of partner time. Add a second entity, a second award, mid-year cutover and timesheet integration into project costing and that figure climbs toward AUD$25,000 to AUD$40,000. Compare those numbers to a typical Employment Hero Payroll implementation at AUD$3,000 to AUD$8,000 plus AUD$6 to AUD$12 per employee per month ongoing — and the calculus depends entirely on how much else lives in Odoo.

For a clearer breakdown of the total platform spend including hosting and support, see our notes on implementation cost in Australia. The short version: payroll rarely changes the answer if you’re already running Odoo for the rest of the business, and rarely justifies the move on its own if you aren’t.

Implementation considerations for Australian businesses

Three things consistently separate Odoo payroll projects that land cleanly from the ones that don’t. The first is data hygiene — TFNs, super fund USIs, opening leave balances, YTD figures. Get these audited before cutover, not during. We’ve watched a well-scoped go-live unravel because three employees had stapled super fund details that didn’t match the ATO’s records. Fix that on day one, not in week four.

The second is who owns the rule library. Odoo pay rules are powerful and editable, which means anyone with admin access can quietly break a calculation and not notice until a payslip is wrong. We lock the rule library to a small group, version-control changes, and require a test pay run against a fixture set of employees before any rule change deploys. This is the discipline mid-market businesses build by default and small ones often skip — and then regret.

The third is timing. Payroll cutovers want to land between BAS lodgement weeks and away from STP finalisation. The Australian compliance calendar is busy; respect it. Our implementation method walks BAS, STP and EOFY constraints into the Gantt before we set a go-live date. If you’re also moving off Xero, the Xero to Odoo migration playbook sits next to the payroll workstream and the two need to be sequenced together. Same for Odoo vs Xero for Australian businesses if you’re still in the comparison phase. And once invoicing is on Odoo, native Peppol e-invoicing usually goes live in the same release.

If you’re weighing whether Odoo’s native payroll, an Odoo plus Employment Hero pairing, or staying on your current stack is the right call for your business, we’re happy to spend an hour talking through it. We do that conversation often, the compliance fit and the award detail are what we’ll want to understand first, and we won’t push the answer that doesn’t fit. Reach out via the contact form and we’ll set up a time.

Frequently asked.

Can I use Odoo in Australia?

Yes. Odoo runs natively in Australia with an ATO-aligned chart of accounts, BAS-ready GST handling, Peppol e-invoicing and an Australian payroll module that covers STP Phase 2 and SuperStream. Odoo S.A. has a Sydney office and an accredited partner network, and Australian customers can host on AWS Sydney, Azure Australia East or Odoo's own cloud.

Which Payroll software is best in Australia?

It depends on award complexity. For simple pay rules under twenty staff, Xero Payroll or MYOB are usually fastest. For modern award interpretation, casual loadings and rosters, Employment Hero, KeyPay or Tanda lead. Odoo payroll fits when you want pay runs to live on the same database as accounting, inventory and projects, and your award structure is moderate rather than highly variable.

What is the difference between Odoo and Xero Australia?

Xero is a focused accounting platform with strong bank feeds and a mature Australian payroll product. Odoo is a full ERP — accounting, inventory, manufacturing, CRM, projects, field service and payroll on one database. Once you outgrow pure-play accounting and start adding inventory, jobs or production, Odoo usually wins on cost and clarity.

Does Odoo offer Payroll services?

Odoo ships a payroll module with Australian localisation. It generates pay slips, calculates PAYG and super, files STP Phase 2 events to the ATO and produces SuperStream-compliant contributions. Odoo does not provide outsourced payroll bureau services — pay runs are operated by you or your partner inside the platform.

Is Odoo better than Xero?

Better at different jobs. Xero wins on pure-play small business accounting and bank feeds. Odoo wins where accounting needs to share a database with inventory, manufacturing, jobs or field service. For payroll specifically, Xero is simpler at the small end; Odoo is more capable once payroll has to interact with timesheets on jobs, project costing or shop-floor labour.

Is Odoo an Australian company?

No. Odoo S.A. is Belgian, headquartered in Ramillies near Brussels. It has an Australian office in Sydney and an accredited partner network, including Perth-based specialists. Australian hosting options include AWS Sydney and Azure Australia East. Localisation — chart of accounts, GST, BAS, STP Phase 2, SuperStream, Peppol — is maintained by Odoo with input from local partners.