For an Australian business, NetSuite vs Odoo is mostly a question of who carries the upgrades and how much custom code your processes need. Odoo usually costs less per user and covers GST, BAS and, in recent versions, STP Phase 2 payroll. NetSuite usually costs more up front and pays back where several entities, audited approvals and heavy customization would otherwise turn every Odoo upgrade into a project.
The trap is comparing a per-user price with a per-user price. The two products are licensed, hosted and upgraded in different ways, and the difference only shows up in years three to five.
Oracle upgrades every NetSuite account twice a year. You don't choose the date or skip a release, but you also don't pay a project to move versions. Your job is to test your own scripts and workflows in the release preview, which our guide to NetSuite release preview testing by business risk covers step by step.
Odoo releases a new major version each year and supports each one for three years. On Odoo Online, a major upgrade becomes mandatory every two years. On Odoo.sh or your own servers you can stay longer, but you lose bug fixes once the version falls out of support. Odoo's upgrade service converts standard modules and Studio changes. Custom modules have to be ported to the new version by whoever wrote them before the database can move.
So ask each partner a plain question: in the next five years, how many upgrades will we go through, who ports our code, how long does testing take and what did the last three cost for a client like us? Write the answers into the cost model, not the footnotes.
At the time of review, Odoo's Australian price list showed the Standard plan at A$34.40 per user per month for the first year, then A$43.00, and the Custom plan at A$64.00, then A$80.00, on yearly billing and excluding GST. Standard runs only on Odoo Online with no custom code. You need Custom for more than one company, Studio, the external API or Odoo.sh, and Odoo.sh hosting is charged on top. Check the current list with Odoo before you rely on these figures.
NetSuite is quoted per account: a base edition (OneWorld if you run several entities), full users, modules and a renewal term. Ask for the renewal uplift cap in writing. Our AUD total cost model for a NetSuite decision lists the lines, and the post on NetSuite implementation cost for Australian multi-entity groups shows where group work adds to the quote.
Put both options on the same five-year sheet: subscription, hosting, implementation, upgrades or release testing, e-invoicing access point, payroll if it changes, support retainer and internal time. Keep the first-year discount separate so it doesn't flatter year one.
Both products ship an Australian chart of accounts, GST tax codes and a BAS report. That tells you little about your own quarter. Give each partner 40 to 60 real transactions and ask them to produce the BAS labels on a working system:
Then trace G1, 1A and 1B back to the source lines. If either partner needs a manual journal to make a label agree, write it down. That journal will come back every period. Our guide to tracing Australian GST from NetSuite transactions to the BAS shows the evidence a reviewer should expect from either system.
This is one area where Odoo has moved ahead. Odoo 19 added direct STP Phase 2 and SuperStream lodgement through an API, so an Australian business can run payroll and accounting in one database. Earlier versions prepared the data but still needed a separate service to lodge it, so check which version a partner is proposing.
NetSuite is rarely the payroll engine in Australia. Most NetSuite customers keep an STP-enabled payroll provider and post a journal for each pay run, which our post on NetSuite Single Touch Payroll integration explains. That adds a subscription, but it also keeps payroll with a specialist that tracks award and tax changes.
Whichever route you choose, test the same ledger outcome. PAYG withholding, super and payroll tax should land in liability accounts someone reconciles each month, and with Payday Super in force from 1 July 2026, super clearing can't wait for quarter end. Our post on NetSuite PAYG withholding and payroll journal reconciliation has the checks.
Peppol e-invoicing is not mandatory for business-to-business invoices in Australia today, but government agencies and some large buyers already ask for it. Neither product makes the access point question go away.
At the time of review, Odoo's own Peppol registration did not list Australia, so Australian Odoo users connect through an accredited access point or a third-party connector. NetSuite's Electronic Invoicing SuiteApp includes A-NZ Peppol templates for invoices, credit memos and inbound vendor bills, and also needs an accredited access point. In both cases, ask who holds the access point contract, where a rejected invoice shows up and who in finance is alerted.
Write down every requirement that the stock product doesn't meet, and ask each partner how they would meet it: configuration, a workflow, a script or a custom module. Rebate accruals, approval chains with delegation, landed cost split across companies and intercompany recharges are the usual suspects for Australian distributors.
In Odoo, gaps are often closed with custom Python modules. They can be well written, but each one is code your business owns and has to port at every major upgrade. In NetSuite, more of the same list is usually met with configuration and SuiteFlow, with SuiteScript for the rest, and Oracle's releases don't require you to rewrite it. Count the modules, name who wrote them and price their upkeep. Our comparison of NetSuite vs Xero in Australia uses the same habit of measuring the work done outside the standard product.
This example is hypothetical and simplified. A Perth industrial supplies distributor has A$42 million revenue, 140 staff and 34 ERP users across two Australian companies: a trading company and an equipment hire company. It imports from China and the US, lodges BAS monthly for the trading company and quarterly for the hire company, and a mining customer and a WA government agency already want Peppol invoices. Its payroll provider contract runs to 2028, so both options keep it, and payroll is left out of the figures. All amounts are illustrative and exclude GST.
The Odoo partner proposed the Custom plan on Odoo.sh with 12 custom modules. The NetSuite proposal met 10 of the same 12 requirements with configuration and SuiteFlow and needed two SuiteScripts. Both systems produced the BAS labels from the 48 test transactions. Odoo needed a second attempt for deferred GST on one import, which the partner fixed in setup.
| Five-year cost (A$) | Odoo | NetSuite |
|---|---|---|
| Subscription | 157,000 | 290,000 |
| Hosting (Odoo.sh) | 22,000 | 0 |
| Implementation | 115,000 | 150,000 |
| Major upgrades or release testing | 76,000 | 16,000 |
| Peppol access point and setup | 11,000 | 13,000 |
| Support retainer | 70,000 | 58,000 |
| Total | 451,000 | 527,000 |
Odoo's subscription line is 34 users at A$64.00 a month in year one and A$80.00 after that. Its upgrade line covers two major upgrades in five years, each porting 12 modules and repeating the BAS and approval tests. NetSuite's release testing line is about a day and a half of regression testing for each of ten releases.
On these figures Odoo is cheaper by A$76,000, about A$15,200 a year. The finance director still chose NetSuite, for three written reasons. First, upgrade risk: the Odoo partner's last three upgrades for similar clients ran 25 to 60 percent over estimate, and at 50 percent over, the gap falls to A$38,000. Second, seven of the 12 Odoo modules touched the ledger (rebates, landed cost, approvals and intercompany hire charges), so every upgrade would put the BAS and month-end close at risk. Third, the auditor's approval sampling passed on NetSuite's standard approval records and system notes, while the Odoo design needed field tracking extended to custom fields. The same two developers had written all 12 modules, which the board saw as a key-person risk.
Odoo would have been a reasonable choice for a different business: one company, standard processes on Odoo Online with no custom code, and a wish to bring STP payroll into the same system. In that case the cost gap is wider and the upgrade risk much smaller. The Australian comparison of Business Central vs NetSuite shows a wholesaler working through a similar trade-off.
A five-year ERP choice rests on a few assumptions. Write them down before you sign. For the Perth distributor they were the number of custom modules, the upgrade overrun, two companies staying two and the payroll provider staying until 2028. If a later review cut the custom modules to three or fewer, the case for Odoo would get stronger, and the finance director agreed to say so.
Recheck the assumptions against real numbers before each renewal: upgrade or release testing hours, modules added since go-live, BAS adjustments by period and Peppol rejections. CuriousRubik's business consulting team runs side-by-side ERP evaluations for Australian businesses, including the scripted BAS session and the five-year AUD model. See our NetSuite work in Australia for how we work with local finance teams.
Usually, on subscription. The gap narrows once you add Odoo.sh hosting, custom modules and the cost of porting them at each major upgrade. Model five years on your own scope before you compare.
Odoo's Australian localization includes GST tax codes and a BAS report. Odoo 19 added direct STP Phase 2 and SuperStream lodgement. Check which version your partner proposes and test both on your own pay runs and transactions.
Not as a standard module. Most Australian NetSuite customers use an STP-enabled payroll provider and post a journal into NetSuite after each pay run.
NetSuite has two releases a year, applied by Oracle to every account. Odoo releases one major version a year and supports each for three years, and custom modules must be ported before you can move.
Not for business-to-business invoices at the time of review, though government agencies and large buyers ask for it. Both products need an accredited access point, so name it in the proposal.
How to evaluate NetSuite for an Australian business through local workflows, compliance tests and an AUD cost view rather than feature lists.