Skip to Content

Odoo Payroll in Australia: What It Covers, What It Doesn't, and What to Check

Explore the key features and benefits of Odoo v19 Payroll in Australia. Gain valuable insights to streamline your payroll processes. Read more now!
30 September 2025 by
Marlon Wambeek
| No comments yet

Free · about five minutes

Not sure if you’re ERP-ready?

Answer 20 questions and get a scored readiness report — your biggest risks, and what to fix first.

Get my readiness score

Already on Odoo? See whether your system is AI ready

Odoo payroll in Australia is now a substantial native localisation rather than a gap filled by third-party add-ons. If you are weighing it up, the useful questions are narrower than "is it any good": what does the Australian payroll module actually cover, which business flows does Odoo itself tell you not to use it for, and what should you verify before you move real people and real money onto it.

This guide answers those three questions from Odoo's own Australian payroll documentation, and is explicit about the parts that are limited. We are an Australian Odoo partner, we implement this payroll module for clients, and we are moving our own payroll onto Odoo. That gives us a view of where it works well and where it will frustrate you.

One note on scope before we start. Payroll compliance is the one area where "roughly right" is not good enough, because the consequences land on your employees and on your ATO reporting rather than on a dashboard. Everything below that concerns a compliance obligation should be confirmed against Odoo's current documentation and your own circumstances at the time you make the decision, not taken from an article.


​What is Odoo payroll for Australia?


Odoo payroll for Australia is the Australian localisation of Odoo's Payroll app: a set of country-specific salary rules, work entry types, input types, superannuation handling and ATO reporting workflows that sit on top of the generic Payroll module. It runs on the same database as Odoo accounting, Time Off, Expenses and Attendances, so a validated pay run posts its own journal entries instead of being re-keyed.


That architecture is the real difference from a standalone payroll system. In a separate payroll system, the pay run produces a file and someone imports it. In Odoo, the pay run is already inside the ledger. For Australian businesses consolidating systems, that removes a reconciliation step every single pay cycle, which is usually a bigger operational win than any individual payroll feature.


It is also the source of the main caution. Because payroll data is wired into accounting and financial reporting, a payroll configuration mistake does not stay in payroll. It shows up in your accounts. That is an argument for getting the configuration right at the start rather than iterating on it with live payroll information.


​Where does Odoo stand on STP Phase 2 and SuperStream?


Odoo's Australian localisation submits STP files to the ATO and pays superannuation through a clearing house. Start with the part that actually governs how you work, because it does not change with the version number.


STP reporting in Odoo is a workflow you configure and a responsibility you keep. An STP responsible employee is nominated for the company. Submissions are assembled from the validated pay run and reviewed before they are sent. The obligation to report on or before payday sits with you as the employer, not with the software, and no payroll system transfers it.


Corrections are deliberate rather than casual. Odoo limits a full file replacement to one per submission and one every twenty-four hours, so fixing a bad submission is a considered act with a cooling-off period rather than an undo button. That is worth knowing before you need it, because it shapes how carefully you want to review a batch.


For the record, Odoo's own Australian payroll documentation for both version 19 and version 20 now states that "Odoo is compliant with SuperStream and Single Touch Payroll Phase 2" (checked 28 October 2026). Earlier versions of the same page described that compliance as still in progress, which is exactly why the date on a statement like this matters.


On the certification question itself, our advice is the same advice we would give about any payroll software: confirm the current position with Odoo or with your implementation partner, in writing, against the release you are actually going to run, at the time you make the decision. Vendor documentation and partner blog posts both go stale, and a compliance status read from an article written months ago is not a basis for a payroll decision. We would rather point you at the source than become one.


​What does the Australian payroll localisation actually include?​

​What does the Australian payroll localisation actually include?


The localisation is broad, and the numbers give a fair sense of its depth. The documentation describes an "Australian Employee" salary structure carrying thirty-five payslip rules, sixty-three Australia-specific other input types grouped into six payment categories (allowance, deduction, ETP, leave, lump sum and other), around thirty-two recurring salary attachment types covering allowances and child support, and thirteen year-to-date salary rules used when you bring balances across from a previous system.


Work entry types are where award behaviour gets expressed. Each type carries flags for whether the hours count as ordinary time earnings, whether penalty rates apply, and which STP code the hours report under. This is the part most worth attention during configuration, because it is where modern award interpretation either becomes automatic or quietly becomes somebody's monthly manual job.


Pay frequencies are deliberately constrained: daily, weekly, fortnightly, monthly and quarterly, and nothing else. If your business runs an unusual cycle, that constraint is worth knowing before you start rather than after.


The key features most Australian businesses are checking for are present: PAYG withholding and tax calculations driven by tax treatment codes, super guarantee calculation, work entry types that carry penalty rates, employment termination payments, leave management wired to Time Off, year-to-date imports, and STP reporting workflows. The localisation covers the Australian regulatory requirements a typical employer meets each cycle. What it does not do is remove your obligation to check that it is configured correctly for your award and your workforce.


One point of vocabulary worth clearing up, because it dates a lot of payroll writing: payment summaries were replaced by STP reporting and end-of-year finalisation. If you are comparing payroll software and a vendor is still describing annual payment summaries as a feature, you are reading old material.

Employee setup and the fields that matter


An employee record has to carry enough information for compliant STP reporting before a payslip can be produced. In practice that means tax settings such as residency status, tax free threshold election and TFN declaration status; personal details including address, contact information and date of birth; and super fund details covering the fund, the member number and the date membership began.


The tax treatment codes assembled from those settings are what drive PAYG withholding, so they repay checking one employee at a time rather than in bulk. Medicare levy surcharge settings, residency and the tax free threshold election all feed the same tax calculations, and a wrong flag here produces a payslip that looks plausible and is wrong. This is the single most common source of payroll data problems we see in the first month after a cutover.


Super funds themselves are records in Odoo, created as either APRA-regulated funds or self-managed funds, and identified by a USI for the former or an ESA for the latter. Getting these identifiers right is unglamorous and consequential: a wrong identifier is how a contribution goes astray.


Contracts carry the employment type, the pay frequency and the basic salary details, and the contract is what the pay run reads. A common early mistake is to update an employee's pay on the employee record and wonder why the payslip disagrees.


​How does a pay run work in Odoo?


A regular pay run is created as a batch for a pay period. Odoo handles payslip generation into a waiting stage, where payslips can be reviewed and amended before anything is committed. Validating the batch creates the draft accounting entries against the balance sheet and profit and loss accounts, after which the batch can be submitted to the ATO and paid, with ABA credit transfer available for the bank file.


Out-of-cycle payslips exist for the cases that do not fit a cycle: a bonus, a correction, a final pay. These are created individually, and Odoo's documentation specifically advises against adding an out-of-cycle payslip to an existing batch. Treating them as separate is the safer habit.


The review step in the waiting stage is the one to build a process around. Payroll errors are cheap to fix before validation and expensive afterwards, because by then they exist in the ledger and possibly in an ATO submission.

What it is like to run payroll each cycle


Once configured, the cycle is short: generate the batch, review the payslips, validate, submit, pay. Most of the administrative burden that payroll teams complain about is not the pay run itself but the chasing that surrounds it — timesheets that have not been approved, leave that was taken but never entered, a new starter whose super fund is missing. Odoo moves that work earlier rather than removing it, because the payroll data has to be right before the batch will produce the right answer.


That is the honest version of the payroll processing time argument. The saving is real and it comes from not re-entering the same payroll information into a second payroll system, not from the software thinking for you. A business whose timesheets are already disciplined will feel the benefit immediately. A business whose timesheets arrive on paper on the Monday will find that the bottleneck has not moved.


​How does Odoo handle superannuation?


Since 1 July 2026, under the ATO's Payday Super rules, super guarantee is due with each payday and is calculated on qualifying earnings, a broader base than ordinary time earnings alone. That makes the "is OTE" flag on work entry types, and the salary rules built on it, worth checking against the ATO's definition for the release you run. Quarterly contributions no longer meet the obligation, so confirm that your database and your clearing house arrangement process super every pay cycle.


We have deliberately not quoted a super guarantee percentage in this article. The rate has stepped up on a legislated schedule and the figure shown in vendor documentation is not always the current one. Take the rate from the Australian Taxation Office, and confirm what your Odoo database is actually applying, rather than trusting either an article or a help page.


Super is paid out through a clearing house, with direct debit processing of the contributions rather than a manual payment per super fund. That is the mechanism behind SuperStream compliance, and it is the part most worth confirming is live and configured in your own database before you rely on it, because it involves a payment arrangement and not only a setting.


Salary sacrifice and multiple funds are supported, and both are worth testing with a real employee's numbers during implementation rather than assuming. Sacrifice arrangements interact with OTE and with net pay, and that interaction is exactly the sort of thing that is easier to verify in a test pay run than to reason about. The same goes for long service leave accruals, which are governed by state legislation rather than by the award.


Not Sure If Odoo is Right For Your Business?


Book a free 30-minute Odoo Fit Assessment ➔

We will tell you honestly whether Odoo payroll suits your award complexity and your reporting obligations, or whether you are better off keeping payroll where it is and integrating it.

​How does Odoo handle termination payments and final pay?


A termination in Odoo requires three things recorded on the employee: a contract end date, a cessation type code, and whether the termination is genuine or non-genuine. Those fields drive the STP reporting, so they are not administrative tidying.


Odoo then produces a final pay as an out-of-cycle payslip covering unused leave, with the calculated entitlements available to adjust where circumstances require it. Employment termination payment components are added as other inputs, and withholding follows the ATO's Schedule 7 and Schedule 11 treatments.


Terminations are the flow we most often recommend walking through end to end during an implementation, with a real historical example. They combine leave calculation, tax treatment, super and reporting obligations in one transaction, which makes them a good test of whether the configuration is genuinely right.


​How does Odoo payroll connect to the rest of the business?​

​When is Odoo payroll the wrong tool?


Odoo's own documentation names the business flows it does not recommend using the Payroll app for, and this is the most useful page in the whole localisation because it saves you discovering the limits yourself. We would rather you read it now than in week six of an implementation.


The documented exclusions are foreign employment income as an income stream type; the actors and performers tax treatment category; death benefits reporting; reporting obligations where you report under a WPN rather than an ABN; and allowances subject to a varied rate of withholding, with cents-per-kilometre and certain travel allowances named specifically.


If any of those describe a material part of your workforce, Odoo payroll is not the right answer for that part of your business today, and no amount of configuration changes that. The sensible responses are to keep payroll where it is, to run the excluded population elsewhere, or to confirm the current position with Odoo directly before committing. None of those is a failure of the project; discovering them late is.


There is a second, softer category: businesses whose award interpretation is genuinely complex, with multiple enterprise agreements and heavy penalty-rate structures. Odoo can express a great deal of this through work entry types, but the work to get there is real and it is specialist. Treat an estimate that does not account for it with suspicion.


​How does Odoo payroll connect to the rest of the business?


Time Off is the integration that does the most work. Leave types carry payroll settings that determine how paid leave and unpaid leave become work entries and how unused balances are treated, so an approved leave request flows into the pay run without a second entry. Attendances and Planning feed worked hours for businesses that need them.


Expenses can be reimbursed through the next payslip, which is convenient and worth a deliberate decision rather than a default, since it moves reimbursements into payroll reporting and changes take-home pay.


For businesses already on Employment Hero, the l10n_employment_hero module syncs payslip journal entries into Odoo as drafts. It is worth being precise about what this is: it brings the accounting across, not the payroll processing. The sync runs weekly by default, can be triggered manually, and needs matching accounts configured in Odoo. It is a sensible bridge for a business that wants its payroll numbers in its ledger without changing payroll systems yet.


If your wider question is how payroll sits alongside accounting, payroll tax and compliance reporting, our Odoo for financial control and compliance page covers that layer, and our Odoo payroll for Australian businesses page goes further into award interpretation in practice.


​What should you check before moving payroll to Odoo?


Migration is where payroll projects succeed or fail, and the detail that matters most is continuity of reporting. Odoo imports year-to-date opening balances through an "Import YTD Balances" process, and records a previous BMS ID once per database plus a previous payroll ID per employee. Those identifiers are how the ATO recognises that an employee record continues rather than restarting, and getting them wrong produces duplicate records.


Timing follows from that. End-of-financial-year finalisation declarations are due by 14 July, and individual employees can be finalised during the financial year. A mid-year cutover is entirely possible and is often the right call, but it makes the YTD import the critical path rather than a tidy-up task.


Before you commit, we would check: that none of the documented exclusions apply to your workforce; that your award and penalty-rate structures can be expressed in work entry types, tested against real timesheets; that your super fund identifiers are correct; that a termination and a final pay produce the right numbers for a real historical case; and that the rates your database applies match the current ATO figures rather than any documentation.


If you want that checked properly rather than optimistically, our Odoo Success Blueprint is a fixed-price scoping exercise that produces a real plan, and Odoo implementation in Australia explains how we run the work itself. We bill implementation as time rather than fixed price, because a payroll scope quoted before anyone has looked at your awards is a guess.


​Frequently asked questions about Odoo payroll in Australia


Yes. Odoo has a native Australian payroll localisation covering salary rules, work entry types with OTE and penalty-rate flags, superannuation funds and contributions, employment termination payments, year-to-date balance imports and STP reporting workflows. Whether this payroll software suits your business depends on your award complexity and on whether any of the flows Odoo does not recommend apply to your workforce.

Odoo's documentation names foreign employment income, the actors and performers tax treatment category, death benefits reporting, reporting under a WPN rather than an ABN, and allowances subject to a varied rate of withholding such as cents-per-kilometre and certain travel allowances. If one of these covers a material part of your workforce, that part needs a different answer.

Yes. Odoo provides an "Import YTD Balances" process, and records a previous BMS ID for the database and a previous payroll ID for each employee so the ATO can link an employee's history across the change of system. This is the part of a payroll migration most worth testing carefully, because errors here create duplicate employee records rather than obvious failures.

Award behaviour is expressed through work entry types, which carry flags for ordinary time earnings, penalty rates and STP codes, and through salary rules and other input types. A great deal is achievable, but it is configuration rather than something that arrives pre-built for your award, and complex enterprise agreements take specialist work. Test it against real timesheets before go-live.

Yes. The l10n_employment_hero module brings payslip journal entries into Odoo as drafts, syncing weekly by default or on demand, with matching accounts configured in Odoo. It moves the accounting rather than the payroll processing, which makes it a reasonable bridge if you want payroll numbers in your ledger without changing payroll systems yet.

Daily, weekly, fortnightly, monthly and quarterly. Other frequencies are not accepted, so an unusual pay cycle is something to confirm before starting rather than during configuration.

Yes. Single Touch Payroll reporting is a requirement for employers, and the reporting obligations apply on or before each payday rather than at the end of the year. Whichever payroll software you choose, the obligation sits with you as the employer, so the question to ask of any payroll system is not whether it mentions Single Touch Payroll but whether your people can actually complete a submission correctly every cycle. Confirm your own obligations with the Australian Taxation Office.

It can, mainly by removing the gap between payroll and the ledger so that what you report and what you have recorded agree. But software does not deliver ATO compliance on its own. The configuration has to match your award, the employee data has to be right, and somebody has to review each submission. The compliance risks that matter in practice come from wrong settings and unreviewed payroll data, not from a missing feature.

​Talk to someone who will tell you if it doesn't fit


WAO Group is an Australian Odoo partner with 10+ certified Odoo experts, 60+ client references and 95%+ client satisfaction (Odoo partner directory), and winner of the Odoo Customer Choice Award (ANZ) 2026. We are moving our own payroll onto Odoo, which is a reasonable signal of what we think of it, and it is also why we are specific about the limits.


Payroll is the one module where we will tell a prospective client not to proceed. If your workforce sits inside the flows Odoo does not recommend, or your award structure is complex enough that the configuration cost outweighs the integration benefit, the better answer is to keep payroll where it is and connect it. We would rather say that now than bill you to find it out.


If you want a straight read on which of those applies to your Australian business, book a free 30-minute Odoo Fit Assessment and bring your award, your pay cycle and one awkward termination.



The information and tips shared on this blog are meant to be used as learning and personal development tools as you launch, run and grow your business. While a good place to start, these articles should not take the place of personalised advice from professionals. As our lawyers would say: “All content on WAO’s blog is intended for informational purposes only. It should not be considered legal or financial advice.” Additionally, WAO is the legal copyright holder of all materials on the blog, and others cannot re-use or publish it without our written consent.

Not Sure if You're ERP‑Ready?

Answer 20 questions and get a scored readiness report — your biggest risks, and what to fix first. Free, about five minutes.

Get my readiness score

Already on Odoo? See whether your system is AI ready

Share this post
Our blogs
Archive
Sign in to leave a comment