Odoo 20 Is Out: What Changed, and What Australian Businesses Should Plan For
Odoo 20 was unveiled on 24 September 2026. What changes for Australian businesses: AI agents that write records, Basiq bank feeds, Field Service in Planning.
By Josh Craig, Managing Director, Auboros · · Updated
Updated 30 September 2026: Odoo 20 has been released, so this post moves from roadmap to release. Rewritten against the official Odoo 20 release notes and the 20.0 documentation: short answer, At a glance, module-by-module table, Field Service merged into Planning, Basiq bank feeds for Australia, AI agents and the MCP server, IAP credits, and the upgrade timing section. The 5 April 2026 roadmap version is superseded.
Odoo 20 was unveiled at Odoo Experience in Brussels on 24 September 2026 and the official release notes are dated September 2026. The headline changes: AI agents that create and update records and run from scheduled actions, a built-in MCP server, Basiq open-banking bank feeds for Australia, the Field Service app folded into Planning, and IAP credits required for every AI feature. Documentation still defaulted to 19.0 on 30 September.
At a glance
- Who it is for: Australian businesses running Odoo 17, 18 or 19 Enterprise who need to decide when to move, and businesses choosing a version for a new implementation this quarter.
- Problem it solves: the Odoo 20 release notes list several hundred changes across 60 apps with no Australian reading. This post pulls out what changes day-to-day work for an Australian finance, warehouse, factory or service team, and what the timing looks like.
- Platforms: Odoo 20 Enterprise and Community (the AI features, MCP server, Studio and most accounting reports are Enterprise only, per Odoo’s edition comparison).
- Typical cost: the Odoo upgrade service is included with an Enterprise subscription; partner time to test customisations and cut over is the cost that varies, and our Odoo version upgrade guide sets out how we scope it. Licence pricing is on our Odoo pricing page.
- Typical timeline: Odoo’s documentation says each major version is supported for three years and, on Odoo Online, an upgrade is mandatory every two years; we plan most Enterprise upgrades as a 4 to 10 week project with a test upgrade first.
- Last verified: 30 September 2026 against the Odoo 20 release notes, the 20.0 upgrade documentation and the Odoo Experience 2026 programme.
We wrote the first version of this post in April, when Odoo 20 was a roadmap talk. The release notes are now public, the 20.0 documentation branch is live, and three of the things we expected have turned out bigger than the roadmap suggested: the AI agents can now write to your database, Odoo has shipped its own MCP server, and the Field Service app no longer exists as a separate app. Here is the release from an Australian angle.
What is new in Odoo 20 for Australian businesses?
The one line under Australia in the localisation section of the release notes is bank synchronisation through Basiq, the open-banking provider that already appeared in the 19.0 bank synchronisation documentation. Nothing else in the release notes is Australia-specific, which is the normal pattern: the Australian chart of accounts, GST and Business Activity Statement (BAS) reporting live in the localisation modules and carry across versions. We covered how those work in our Odoo Australian localisation guide, and the 20.0 notes give us no reason to expect a change there.
The changes that matter for Australian teams sit in the general accounting, inventory, manufacturing and AI sections. The table below is our reading of the release notes, not an exhaustive list.
| Module | What changed in Odoo 20 | Why it matters here |
|---|---|---|
| Accounting | Every journal entry touching a bank account must originate from a bank transaction; payment statuses renamed (In Process becomes Paid, Paid becomes Reconciled); bank reconciliation summary report; bill line prediction from bill history; matching rules for automatic bill and invoice reconciliation; invoice reminders can be automated from settings | Cleaner BAS periods, fewer manual bank journals to explain at year end, and follow-ups without a spreadsheet. See our Odoo bank reconciliation guide for the 19 baseline |
| Accounting (structure) | Account groups replaced by parent accounts; account codes now optional; Cumulative Translation Adjustment line on the balance sheet, trial balance and general ledger | Multi-entity groups with a NZ or overseas subsidiary get an auditable FX balancing line instead of a manual adjustment |
| Accounting (expenses) | The standalone Employee Expenses menu is gone; approved expenses generate draft bills in the expense journal | Expense claims are reviewed and posted alongside vendor bills, which is how most Australian bookkeepers want it |
| Bank feeds (Australia) | Basiq open-banking integration listed under the Australian localisation | The first Australia-specific bank feed provider named in the release notes; check your bank and account type against Basiq’s coverage before relying on it |
| Inventory | Suggested minimum and maximum levels for reordering rules based on demand history; landed costs on individual products in a transfer; retroactive COGS updates when a cost changes after delivery; stock aging report; inventory at a past date with a precise timestamp; intercompany resupply routes and deliveries from another company’s warehouse | Landed costs and retroactive COGS fix a long-standing gripe for importers; the past-date report helps with stocktake variances at 30 June |
| Manufacturing | Continuous production (next operation starts as soon as some quantity is ready); manufacturing orders planned ASAP by default; split ongoing orders; reset validated orders to draft; MO cost shows provisional cost in progress and real cost on completion; flexible consumption always on | Job shops and food manufacturers get shorter lead times without custom development; real MO cost on completion is what your accountant has been asking for |
| Field Service | The Field Service app has been discontinued and its features are integrated into the Planning app | Trades and service businesses on our field service app for Odoo and MYOB Acumatica need an upgrade test of every FSM workflow before moving; this is the biggest structural change in the release for our clients |
| CRM | Lead auto-assignment rotation rules per team member; pipeline switcher between teams; upsell and renewal quotations from a lead’s existing subscriptions; lead generation now uses the Dun and Bradstreet database | Better for businesses running several sales teams or subscription revenue |
| AI | Agents can create and update records, be summoned by automated and scheduled actions, ask for permission with buttons, and read uploaded files; Topics renamed Skills; automatic model selection per provider; conversations stored for 30 days; all AI features need IAP credits | The write capability is the change that needs governance. See the Odoo 20 MCP server permissions post and our AI agents for ERP in Australia hub |
| Platform | Built-in MCP server (“Connect Odoo to anything”); simplified access rights with a domain on the access right instead of record rules; offline mode for create, edit and archive; Material Symbols replace Font Awesome icons; tax included or excluded switch on sales orders, purchase orders and invoices | The access-rights change is a security review item for any customised database; the tax toggle removes a common GST display complaint |
Does Odoo 20 change the AI story from Odoo 19?
Yes, and more than the roadmap talk implied. In Odoo 19, the built-in agents answered questions and the AI server actions could run tools, but the release notes for 20 add “Ask an AI agent to create anything for you” and “Ask an AI agent to update records” as headline features, alongside agents summoned by automated and scheduled actions. Odoo also says agents can now update themselves to suit their use case, that permission requests are answered by clicking buttons, and that every AI feature now needs credits bought through IAP.
Two consequences for an Australian business. First, budget: AI in Odoo 20 is a consumable, not a licence line, so a finance team that leans on agents will see an IAP bill. Second, control: an agent that writes records is an agent that can post a wrong record, and the 20.0 AI server action documentation keeps the 19.0 line that a called tool runs unconditionally unless the code itself prevents it. We build every write-capable agent with the drafts-first pattern described in our Odoo AI server action approval gate post, and the same rule applies to the new MCP server, where Create and Update Records tools stay hidden until an administrator exposes them.
If you are deciding what the AI features are worth before you upgrade, our AI in Odoo for Australian businesses post covers what shipped in 19 and what a Brisbane finance team has used in practice.
When will Odoo 20 be ready for Australian production use?
The release notes carry the date September 2026 and the 20.0 documentation is published, but on 30 September 2026 the documentation’s default version still redirected to 19.0, which is a fair signal of where Odoo itself sees the release. Odoo Online databases move on Odoo’s rolling-release schedule with notice a few weeks ahead of a mandatory upgrade; Odoo.sh and on-premise databases upgrade when you choose, using the upgrade service that comes with an Enterprise subscription.
Our advice for Australian businesses is unchanged from the version of this post we published in April, only the dates have moved:
- Already live on 18 or 19 with no urgent need for a 20 feature. Run a test upgrade in the sandbox in the next quarter, fix custom modules and third-party apps, and plan production for early 2027 once a couple of minor releases have landed. The Field Service merge alone justifies a full test for any business using FSM.
- Implementing now. We are still starting new projects on 19 for a go-live this year, because the Australian localisation, the app store connectors and our own FieldPro work are proven on it. A 19 database upgrades to 20 through the same free service; you are not creating debt by going live on 19.
- On 17 or earlier. The 20.0 upgrade documentation says each major version is supported for three years and that the smaller the version gap, the easier the upgrade. Our Odoo version support guide sets out the dates; the short version is that 17 is the one to move off first.
“Every client has asked the same question since Experience: should we wait for 20? My answer is that the version you go live on matters far less than how clean the implementation is. A tidy 19 database will be on 20 by mid next year with a test upgrade and a few weeks of partner time. A messy one will be messy on 20 too.”
Josh Craig, Director, Auboros
What should Australian businesses check before upgrading to Odoo 20?
Four things from the release notes go on every upgrade checklist we run, on top of the usual custom-module and connector testing:
- Field Service workflows. Every scheduling, dispatch, worksheet and invoicing step that lived in the Field Service app now lives in Planning. Test each one in the upgraded sandbox, including the mobile flow your technicians use on site.
- Access rights. Odoo 20 replaces record rules with a domain on the access right. Any database with customised security (multi-branch, sales reps limited to their own customers, warehouse staff limited to their site) needs a security review after the test upgrade, not before.
- Bank journals. With every bank-account journal entry now required to originate from a bank transaction, any manual bank journals your bookkeeper relies on will need a different treatment. Sort this out in the test upgrade, well before a BAS period closes on the new version.
- AI credits and agent permissions. If you use any AI feature, confirm the IAP credit cost before go-live, and review which agents and MCP tools can write records. The Odoo 20 MCP server post has the tool-by-tool recommendation.
Then the standard items: the upgrade service test run, third-party app compatibility on the Odoo app store, report templates, and a reconciliation of the trial balance before and after. Our Odoo implementation and support services include this as a scoped upgrade project, and if you want a local team, we are an Odoo partner in Brisbane who has run these test cycles on every version since 16.
Goes well with
- How the Odoo version upgrade process works and when to schedule one
- Odoo 20 MCP server: what to expose and what to keep read-only
- Odoo version support: how long each version lasts
Planning an Odoo 20 upgrade, or choosing a version for a new implementation?
Auboros is a Brisbane-based Odoo partner supporting businesses across Queensland, NSW and Victoria. We run the test upgrade, review the Field Service and access-rights changes, and give you a dated plan for moving to Odoo 20 when it suits your BAS calendar. If you want a clear picture of what the release means for your database, book a free consultation. We will tell you if waiting is the right call.
FAQ
Frequently asked questions
When was Odoo 20 released?
Odoo 20 was unveiled at Odoo Experience in Brussels on 24 September 2026 and the official release notes are dated September 2026. The 20.0 documentation is published, although on 30 September 2026 the documentation's default version still redirected to 19.0. Odoo Online databases move on Odoo's rolling-release schedule; Odoo.sh and on-premise databases upgrade when you choose.
What are the biggest new features in Odoo 20?
The release notes headline AI agents that can create and update records and run from automated and scheduled actions, a built-in MCP server, automatic AI model selection and IAP credits for all AI features. Beyond AI: bank entries must originate from bank transactions, bill line prediction, suggested reorder levels from demand history, continuous production in manufacturing, and the Field Service app merged into Planning.
What changed in Odoo 20 for Australia specifically?
The Australian entry in the localisation section lists one change: bank synchronisation through Basiq, an open-banking provider. GST, BAS reporting and the Australian chart of accounts live in the localisation modules and carry across from Odoo 19. The accounting, inventory and AI changes in the general release notes apply to Australian databases like any other.
Is the Odoo 20 upgrade free for Enterprise customers?
The upgrade service at upgrade.odoo.com is included with an Odoo Enterprise subscription for any supported version. The cost that varies is partner time to test custom modules, third-party apps and, in Odoo 20, the Field Service to Planning move and the new access-rights model. Odoo's documentation says each major version is supported for three years.
Should we implement Odoo 19 now or wait for Odoo 20?
For most Australian businesses, going live on Odoo 19 now is still the better call. The localisation and connectors are proven on 19, and a 19 database upgrades to 20 through the same included service after a test cycle. Businesses that depend on the Field Service app or on customised access rights should plan a full test upgrade before moving to 20.