Odoo

Odoo accounting in Australia: GST, BAS, payroll, and Peppol checks before rollout

A practical Australian buyer guide to Odoo accounting and localisation, covering GST, BAS, ABA payments, payroll limits, and Peppol questions before finance teams commit to rollout scope.

Odoo now has enough official Australia-specific documentation to deserve a more serious review than "cheap ERP with apps". Its current documentation describes an Australian accounting localisation, BAS and TPAR reporting, ABA batch-payment support, payroll localisation, Employment Hero payroll synchronisation, and a separate Peppol e-invoicing framework. The gap is that these pieces do not all carry the same implementation risk.

What Odoo officially documents for Australia today

• Odoo's Australia localisation page lists the core accounting module `l10n_au`, the Australian reports module `l10n_au_reports`, the Australian payroll modules, and an Employment Hero Payroll connector.
• Odoo says the Australian reports module adds the Taxable Payments Annual Report and the Business Activity Statement report.
• The same localisation page documents GST tax grids, deferred GST handling, BAS reporting, and ABA files for batch payments.
• Odoo also documents payroll-specific Australian setup, but the payroll page includes an explicit caution: Odoo is currently in the process of becoming compliant with STP Phase 2 and SuperStream, and Employment Hero can still be used for payroll administration while Odoo records journal entries.

Why this matters for Australian buyers now

• The ATO says businesses registered for GST need to lodge a Business Activity Statement to report and pay GST, PAYG instalments, PAYG withholding, and other taxes.
• That means an ERP finance design for Australia is not only about chart-of-accounts setup. It has to prove tax mapping, BAS accuracy, payroll withholding treatment, payment execution, and a realistic lodgement process.
• Odoo's official documentation is useful because it shows Australia is not an afterthought. It also shows where the buyer still carries operational responsibility rather than assuming the software completes the whole compliance loop.

Priority 1: treat BAS support as reporting support, not full lodgement automation

• Odoo describes the BAS report as a critical tax reporting requirement for businesses registered for GST in Australia and says its BAS feature helps users review GST and DGST before generating a closing entry.
• The localisation page also says PAYG withheld components are included in the BAS report, which matters if payroll is part of the ERP scope.
• The critical limitation is equally clear in Odoo's own documentation: the BAS report is not submitted directly to the ATO. Odoo says businesses can copy the values and enter them on the ATO portal.
• For buyers, that means BAS should be treated as a finance-control and reconciliation feature, not as proof that the full compliance workflow is end-to-end automated.

Priority 2: ABA support is useful, but only if your bank file path is tested early

• Odoo documents ABA files for batch payments and explains that the format is designed for Australian business customers to facilitate bulk payment processing through financial institutions.
• That is commercially relevant because many Australian finance teams still need dependable bank-file execution during AP rollout, not just modern dashboards.
• But ABA support should be validated with your real bank, approval model, and payment-reference rules. A documented export is not the same thing as a production-approved banking process.

Priority 3: payroll is the biggest scope-risk area

• Odoo's Australian payroll documentation is more substantial than many buyers assume. It covers employee setup, super fund details, pay-run preparation, STP submission flow, and EOFY finalisation paths.
• At the same time, Odoo explicitly says it is still in the process of becoming compliant with STP Phase 2 and SuperStream. That is the sentence finance and HR sponsors should focus on first.
• Odoo also documents Employment Hero integration and says payroll administration can remain in Employment Hero while journal entries sync back to Odoo. For some businesses, that may be the safer operating model in 2026.
• The practical rule is simple: if payroll is mission-critical, do not let a broad ERP demo blur the difference between documented payroll localisation, current compliance status, and the production model your business is actually willing to support.

Priority 4: Peppol and eInvoicing need a separate Australian proof test

• Odoo's e-invoicing documentation says Odoo acts as both an access point and an SMP for Peppol transactions, that Peppol registration is free, and that invoices and vendor bills can be sent and received directly through Peppol.
• However, Odoo's documented eligibility list for built-in Peppol registration does not include Australia in the current public docs.
• The ATO's eInvoicing Ready product register says businesses should use the register to confirm whether their provider is eInvoicing Ready, and if they cannot locate their existing provider they should ask when or if it plans to become eInvoicing Ready.
• On 25 May 2026, Odoo did not appear in a direct search of that ATO register. That does not prove Australian Odoo eInvoicing is impossible, but it does mean buyers should insist on a precise local provider, access-point, and support model instead of assuming the native European Peppol story carries across cleanly.

The shortlist questions that matter most

• 1. Show one Australian BAS cycle from transaction posting through GST mapping, PAYG treatment, review, and final values ready for lodgement.
• 2. Show whether payroll will run natively in Odoo, remain in Employment Hero, or require another operating model, and explain who owns STP and SuperStream risk.
• 3. Prove ABA file compatibility with the real bank accounts, payment approvals, and remittance controls the business uses today.
• 4. If Peppol is in scope, name the Australian path explicitly: native product behaviour, third-party provider, or partner-built workaround.
• 5. Separate subscription value from delivery risk. In Australian Odoo projects, finance localisation effort can move the real budget more than software licence price.

Where Odoo programmes usually go wrong in Australia

• Teams treat BAS visibility as if it automatically solves lodgement, control sign-off, and ATO workflow.
• Project sponsors assume payroll is "covered" because localisation exists, without pausing on the STP Phase 2 and SuperStream caution in Odoo's own docs.
• Buyers validate inventory, CRM, and dashboards in demos but leave banking, tax, and eInvoicing questions until late design.
• Partners position Peppol or payroll as a minor add-on instead of describing the ongoing support model and local compliance boundaries clearly.

What Australian buyers should conclude now

• Odoo has a more credible Australian accounting story than many shortlist buyers assume. GST handling, BAS reporting, ABA support, and payroll localisation are all officially documented.
• The real caution is not absence of features. It is uneven implementation certainty across finance domains. BAS is documented as a reporting and calculation tool, payroll still carries an explicit compliance-progress caveat, and Australian Peppol readiness needs harder proof.
• If Odoo is on your shortlist, the right next step is a finance-led workshop, not another generic ERP demo. Force the partner to prove BAS, payroll operating model, bank-file execution, and eInvoicing path using your own Australian scenarios.

FAQ

• Does Odoo support BAS reporting for Australia? Yes. Odoo documents an Australian BAS report with GST, DGST, and PAYG withholding treatment, but says the report is not submitted directly to the ATO.
• Is Odoo payroll fully straightforward for Australian businesses today? Not automatically. Odoo documents substantial Australian payroll functionality, but also says it is still becoming compliant with STP Phase 2 and SuperStream.
• Can Odoo generate ABA files for Australian batch payments? Yes. Odoo documents ABA file generation, but buyers should still test the output with their real bank and approval flow.
• Is Odoo clearly documented as Peppol-ready for Australia? Not in the same way as some other markets. Odoo documents Peppol broadly, but Australia is not on its current built-in registration eligibility list in the public docs.

Sources used

• Odoo 19.0 documentation for Australia fiscal localisation, including BAS, GST, ABA, payroll modules, and Employment Hero integration.
• Odoo 19.0 documentation for electronic invoicing and Peppol registration eligibility.
• Odoo 19.0 documentation for Australian payroll, including the STP Phase 2 and SuperStream compliance note.
• Australian Taxation Office guidance on how to lodge your BAS and the ATO Software Developers eInvoicing Ready product register.