Odoo 20: what’s new and why there’s no need to rush to upgrade

0

Odoo 20 was unveiled on September 24, 2026 at Odoo Experience (Brussels). It brings AI agents that work inside the ERP, an offline mode and fundamental changes to permissions and accounting. Here is what matters, and why, if your company is on Odoo 16, there is no need to rush to upgrade.

Odoo 20 highlights

  • AI agents inside Odoo. They can create and update records, run on a schedule and connect to other systems through MCP (Model Context Protocol). When they reach their action limit, they ask the user for confirmation before continuing.
  • Offline mode. You can create, edit and search records without a connection; changes are synchronized once it is restored.
  • Accounting. Parent accounts replace account groups in the chart of accounts, reconciliation can be done against several accounts at once, and consolidation improves for groups of companies.
  • Invoicing. Manual or automatic payment reminders, line prediction on vendor bills and per-line prices with or without taxes.

What to look at before upgrading

Demos showcase what’s new, but the real scope of an upgrade is determined by the technical changes. According to analyses published after the launch:

  • Permissions: record rules disappear and their filter is now defined in the access right itself. Custom modules with their own permissions are the ones that need the most review.
  • Payment statuses: “In Process” is renamed “Paid” and “Paid” becomes “Reconciled”. Reports, filters and integrations that read those statuses need to be checked.
  • Pay-per-use AI: Odoo’s AI features consume in-app purchase (IAP) credits, which are not included in the plans.

What if my company is on Odoo 16?

The release of a new version doesn’t oblige you to upgrade. According to sources published after the launch, with Odoo 20 version 17 leaves Odoo S.A.’s standard support, and version 16 was already out. But that doesn’t mean your Odoo will stop working: in the Community edition, maintenance is provided by your partner and the community (OCA), and a well-implemented, well-maintained version remains a solid foundation for years.

Before considering the jump to a new version, it’s worth taking a calm look at:

  • Whether the Community version has everything you use. Each version moves features between Community and Enterprise; you need to check it process by process.
  • Whether the community modules have already been migrated, starting with the Spanish localization, Verifactu and TicketBAI, and those for banking and reconciliation.
  • Your custom developments and integrations, especially those that depend on permissions or payment statuses.
  • The maturity of the version. The first revisions of a new version usually fix bugs; there’s no need to be among the first.

How we see it at Binovo

At Binovo we implement stable versions, not the latest one just for being the latest. Today we implement and maintain Odoo 16, which we know inside out and which gives our clients the stability an ERP needs. Odoo 20 is on our roadmap: before bringing it to clients, we will stabilize the Community version and verify that it has all the functionality they need, including the Spanish localization, Verifactu and TicketBAI. When it’s ready, we’ll tell you about it here.

In the meantime, you don’t need to wait for version 20 to take advantage of AI: our AI modules for Odoo work on Community and Enterprise, with the AI model of your choice and no per-user fees.

If you want to know where your Odoo stands, start with an inventory: installed modules, custom developments, integrations (online store, Verifactu and TicketBAI, banks) and reports your team uses. You can watch what Odoo does on video or find out how we approach Odoo ERP implementation.

Tell us which version you’re on and we’ll tell you, with no rush and no fads, what’s best for you.

Sources

Transparency: this article was produced with the help of artificial intelligence based on the cited sources, and was reviewed and validated by the Binovo team before publication.

Leave a Reply