Version differences

PLANA Business Cloud is updated every year to follow the upstream Odoo release. Most of the day-to-day workflow stays the same across versions; the deltas are documented here so you know what to expect if you migrate, or if you read a guide for a version that is not the one you are on.

Audience

Customers and tenant administrators comparing versions, plus PLANA staff planning migrations.

Supported versions

Version	Released	Status	Support window
v19	October 2025 (upstream)	Limited release — some optional modules pending	Through 2028
v18	October 2024 (upstream)	Current — default for new customers	Through 2027
v17	October 2023 (upstream)	Legacy — supported, EOL 2027	Through October 2027

We support the current version and the previous one in full production. Older versions stay accessible for read-only access and migration only.

What you actually notice as a user

The vast majority of screens, fields, and workflows are unchanged across v17 → v18 → v19. The visible differences a user encounters in PLANA are:

v18 vs v17

• List view label — internal references and a few help texts say "list" instead of "tree". Visually identical.
• Quotation and invoice forms have a tighter layout and the action buttons sit in a single row.
• Bank reconciliation received a redesigned interface — the same actions in a cleaner panel.
• Activities show a richer summary popover when you hover the clock icon.
• Search panel can be docked permanently on the left for some views.
• A small set of keyboard shortcuts changed; the full list is in Reference → Keyboard shortcuts.

v19 vs v18

• Search and filter got a cleaner panel with grouping by tag.
• Spreadsheet dashboards support pivot tables with dynamic groupings.
• AI helpers appear in some Odoo forms — note that PLANA's own AI capabilities live in BOS, not inside the ERP forms.
• A few advanced OCA modules used in v18 are not yet ported to v19. On v19, the corresponding screens are hidden and the workflow is documented as "coming soon" on the relevant page. The list is on this page below.

What does not change

The following are identical across v17, v18, and v19:

• Login flow — single sign-on through your PLANA account
• Workspace selection — https://<your-workspace>.planapulse.app
• Chart of accounts — the PLANA Bulgarian chart is the same template on every version, with regulatory updates applied in-place when the National Revenue Agency changes the rules
• VAT, NPR, VIES and Intrastat reports — submission formats follow the Bulgarian regulator, not the version of the underlying Odoo
• Payhawk × PLANA connector behaviour — the integration semantics are identical; only the module package differs (details)
• PSD2 open banking — the bank list, consent flow and statement format
• PLANA support channel — Matrix room, response times, and escalation path

Modules pending on v19

The following optional modules are part of v17 and v18 but have not yet shipped on v19 from the upstream community. We are tracking each one and will roll them into v19 as they land:

Module	What it does	Status
account_analytic_sequence	Custom numbering for analytic accounts	Tracking upstream
agreement_legal	Customer / supplier framework agreements	Tracking upstream
helpdesk_mgmt and its submodules	Internal help-desk app	Tracking upstream
dms	Document management with folder ACLs	Tracking upstream

If your business relies on any of these, stay on v18 for now. PLANA will prompt you to migrate to v19 only when the modules you actually use are available on v19.

Choosing between v17 and v18 for a new tenant

New tenants default to v18. Choose v17 only if you are migrating from an existing v17 installation outside PLANA and need to preserve customisations that are not yet ported to v18. In all other cases, v18 is the right starting point — it is the version we will keep supporting longest.

How upgrades work for existing tenants

A version upgrade is a coordinated operation:

1. We audit which modules your tenant uses, and confirm every one is available on the target version.
2. We take an insurance backup to our object storage before any change.
3. We clone your database into a staging copy, run the upgrade there, and validate the result — invoice totals, account balances, open transactions, attachments.
4. The production cutover happens during an agreed off-peak window; typical downtime is 15–30 minutes for a normal-sized tenant.
5. We soak the upgrade for 48–72 hours, with the old database retained as rollback insurance for 7 days.

The complete operator-side procedure is on the platform side at Operations → Upgrading a tenant.