Odoo Implementation for Australian Businesses: GST, BAS and Custom Modules.
What an Odoo implementation involves, what Odoo documents for Australian GST, BAS and payments, and when custom modules are worth building.
Most Odoo projects do not fail on software. They fail on decisions that were postponed: which chart of accounts to start from, who owns product data, what happens to the old spreadsheets, and who signs off a payroll run. An implementation is the work of making those decisions once, in order, and then configuring Odoo to match.
Devvista is a software development company that builds and customises Odoo-based business systems for clients, including Australian businesses that want one system for sales, stock, purchasing and accounts. This page explains what an Odoo implementation involves for an Australian company, what the Odoo documentation says about its Australian localisation, and where a custom build is worth adding. For a start, tell us what your business runs on today.
What an Odoo Implementation Involves, Stage by Stage
Odoo is a modular system: you switch on the apps you need (sales, purchase, inventory, manufacturing, accounting, CRM, website and more) and they share one database. An implementation is everything between the decision to use it and the day your staff stop using the old tools.
| Stage | What happens | What you decide |
|---|---|---|
| Discovery | We map how quotes, orders, stock, bills and payments move today | Which processes stay, which change |
| Design | Apps, fields, approval steps and reports written down in plain language | Sign-off on the scope for release one |
| Configuration and build | Odoo set up to your design; custom modules only for what the standard apps cannot do | What is worth customising |
| Data migration | Customers, suppliers, products, opening balances and open orders cleaned and loaded | Who owns each data set |
| Training and trial | Staff work through real scenarios on a test copy | Go-live date and fall-back plan |
| Go-live and support | Cut-over, first month-end close, fixes and a support arrangement | Who looks after it afterwards |
Most of the risk sits in the middle two rows. Clean data and clear process ownership matter more than any setting. Our wider approach to bespoke systems is on the custom software development page.
Odoo for Australia: What the Documentation States
The Odoo 18 documentation has a dedicated Australia page. We read it before writing this section, and it is the baseline we configure from, not a promise that every Australian scenario is covered. What it states:
| Area | What the Odoo documentation states | What it means for you |
|---|---|---|
| Accounting base | The base accounting module for the Australian localisation is l10n_au | Australian accounts and taxes start from a localised base, then we adapt to your accountant's chart |
| GST | The standard GST rate is 10 percent; tax names carry their rate and many taxes are 0 percent or 10 percent | Sales and purchase lines carry a GST code, which your accountant should review before go-live |
| BAS and TPAR | A reports module adds the Taxable Payments Annual Report and the Business Activity Statement report. The BAS report is not directly submitted to the ATO | Odoo prepares figures; your accountant or lodgement process still files. Odoo also uses calendar quarters rather than Australian financial-year quarters, which is a setting to plan around |
| Payroll | A payroll base module exists for Australia, with built-in rules for PAYG withholding types W1 to W5, and a sync for Employment Hero pay runs | We confirm with you and your payroll provider whether payroll runs in Odoo or elsewhere before promising anything |
| Batch payments | ABA files, the format developed by the Australian Banking Association, can be generated by grouping vendor payments into a batch | Pay a run of suppliers from one file uploaded to your bank |
| E-invoicing | Odoo states it is compliant with Australia's Peppol requirements and can download a compliant XML file for an invoice. The file is uploaded to a Peppol network manually, and Odoo notes it is still in the process of becoming an access point for the ANZ region | Useful if customers such as government bodies ask for Peppol invoices; we plan the manual upload step or a separate access point |
| Shipping and retail | Starshipit connects Australasian couriers; Stripe terminals support EFTPOS in point of sale; buy now, pay later is offered for eShops through Stripe and AsiaPay | Online and retail flows have documented starting points |
Source: Odoo 18.0 documentation, Australia fiscal localisation. The page we opened did not mention Single Touch Payroll or PayTo, so we do not promise either without checking your version and provider first.
Choosing Between Standard Odoo, Custom Modules and Integrations
There are three honest routes, and the right one depends on how standard your business is.
| Route | Suits | Watch for |
|---|---|---|
| Standard apps, light configuration | Businesses whose processes look like the standard flow | Resist customising for habits that have no business reason |
| Standard plus targeted custom modules | Businesses with one or two unusual steps: a quoting rule, a production step, a portal | Every custom module is something to maintain across upgrades |
| Odoo as the core with integrations built around it | Businesses that must connect Shopify, couriers, a bank or an industry system | Integrations need ongoing monitoring |
Odoo also comes in different editions and hosting options, and what each includes changes over time. We check the current edition terms on the Odoo site with you at scoping rather than quote them here. For the connection side, see our business management software and Shopify development pages.
Data Migration: Cut-Off, Clean-Up and Reconciliation
Data migration is the stage most often underestimated. A reliable approach:
- Decide the cut-off. Opening balances are loaded as at a date your accountant chooses, usually a month-end or the start of a financial year.
- Clean before loading. Duplicate customers, inactive products and inconsistent units are removed or merged in a spreadsheet first.
- Load in a test copy. We usually propose a staging environment so a trial load can be checked line by line against your existing reports.
- Reconcile. Trial balance, receivables, payables and stock value are compared with the old system, and every difference is explained.
- Load for real once. The final load happens at cut-over, with the old system kept read-only for reference.
Stock, if you hold it, needs a physical count on the cut-over date so that the system starts from a true position. Our warehouse management software page covers counting and scanning in more detail.
Where Custom Modules Pay Off
A custom module is worth building when the work is specific to you and repeated often. These are typical cases for Australian companies:
- A quoting or pricing rule that depends on your own formulas, which a sales team would otherwise rebuild in a spreadsheet each time.
- A customer or supplier portal showing order status and documents without staff answering emails.
- A connection to a courier, marketplace, bank or industry system that Odoo does not offer as standard.
- Approval workflows with your own limits and roles, for purchasing or expenses.
- Reports that mix Odoo data with data from elsewhere, delivered on a schedule.
If a standard app already does the job, we say so. Where automation can sit on top, our AI automation page describes document handling and reporting that can use Odoo data.
What Happens in an Odoo Project, Stage by Stage
How a project runs, and what you can hold us to:
- Short online call. We learn what you run, how many users you have and what is going wrong.
- Scope and proposal. We write the scope down and split the work into releases.
- Weekly demos. You see working screens every week rather than a big reveal at the end.
- Staging first. Changes are tested on a copy before they touch live data.
- Accounts in your name. Hosting, domains and repositories are set up under your control.
- Handover. Documentation, training and an agreed support arrangement.
We work with an NDA if you want one, and we do not name our clients publicly. Our case studies show delivered work across the company, and every meeting is held online.
Who Odoo Through Devvista Suits, and Who It Does Not
| We are a good fit if | Look elsewhere if |
|---|---|
| You want Odoo shaped around your processes, with some custom parts | You want a standard Odoo set-up on the shortest timeline and no custom work |
| You want ownership of the code and accounts we create | You want a vendor that carries all hosting and licensing under its own contract |
| You are comfortable working online with weekly demos | You want a vendor that carries all hosting under its own contract |
| Your accountant will review GST and BAS set-up with us | You expect software to replace your accountant's judgement |
Tell us what you run today and we will say whether Odoo is the right tool, or whether a lighter system from our software development work would serve you better.
Straight Answers.
Tell us what your business runs on today
Describe your processes and users. On a call we tell you whether Odoo suits your processes and which parts need customising.
- 30-minute online call
- Honest feedback on fit
- No obligation
- Book a call30 minutes online. Tell us what you want to build.
- Get a straight answerHonest feedback on fit and scope.
- DecideYou choose the next step once the scope is clear.