Odoo Changelog — 2026-05-05

Tuesday, May 5, 2026

3 changes · saas-18.4

Improvements(3)

Enhancements to existing features

[IMP] l10n_be: Add new VAT provision account

Coresaas-18.4l10n_beMedium

Belgian accounting localization now includes the new VAT provision bank account and tax provision account required for periodic VAT returns from May 1. This helps Belgian companies keep their accounting setup aligned with the upcoming VAT payment process.

Original PR description

Starting May 1st, in Belgium the VAT provision account will replace the current account for periodic returns
- Adding the new bank account
- Adding a new account 'Tax Provision Account' 411800

Enterprise PR: odoo/enterprise#111599

Task [link](https://www.odoo.com/odoo/project.task/6044017)
task-6044017

Forward-Port-Of: odoo/odoo#262188
Forward-Port-Of: odoo/odoo#255272

#belgium#vat#accounting#localization

[PERF] stock: speedup _free_reservation within stock quants validation action

PR #260994

Coresaas-18.4stockMedium

Inventory validation has been optimized to avoid unnecessary repeated work when processing stock moves and packages. This significantly reduces validation time for large warehouse operations, helping teams complete bulk inventory tasks more reliably and with less waiting.

Original PR description

Applying stock quants validation was performing poorly due to multiple bottlenecks in `Picking._check_entire_pack` and `StockMoveLine._apply_putaway_strategy`:

* **Redundant updates** were performed on `location_dest_id` in the move lines and the package levels (which internally update all related move lines too), even when the location remained unchanged.
* The main loop inside `_check_entire_pack` was **O(N^2)** time relative to the number of move lines due to internal filtering logic.
* **Cache misses** triggered unnecessary SQL queries when retrieving `move_line_ids` from `package levels`, while they are already cached via the pickings and can be grouped by `package_level`.

---

### Benchmark
Benchmark conducted on a customer database with **400k** `stock_move_line` records within **800** `pickings`, testing performance of the action `StockQuant.action_validate` with different sizes of move lines. Each test was run multiple times and shown is the average mean, all with negligible variance.

| Metric | Before | After | Delta |
| :--- | :--- | :--- | :--- |
| **Benchmark (1k lines)** | 10.5s | 2.2s | -80% |
| **Benchmark (5k lines)** | 121s | 8.5s | -93% |
| **Benchmark (50k lines)** | 887s | 56s | -94% |
| **Benchmark (400k lines)** | timeout | 777s | (within time limit) |

**OPW-6045513**

Forward-Port-Of: odoo/odoo#257829

[PERF] account*: Improve upload of XML bill

PR #262838

Coresaas-18.4accountaccount_edi_ubl_ciiMedium

Large XML supplier bills imported through Peppol or manual upload now process more efficiently. This reduces long waits and timeouts for high-volume bills, making invoice handling more reliable for accounting teams.

Original PR description

### Description:

The upload and import process for large XML bills via Peppol or manual
upload was inefficient due to two primary bottlenecks. First, the
system performed individual queries per line to match products, taxes,
and accounts, leading to an N+1 query issue. Second, multiple write
operations were executed on each line to update various fields.

This commit introduces batching and improve caching for these
operations to reduce database call.

### Benchmark:

| N° of lines |  Before | After |
|-------------|---------|-------|
|       30264 | Timeout | 11min |

### Reference:
opw-5416612

Forward-Port-Of: odoo/odoo#261401
Forward-Port-Of: odoo/odoo#248680

#performance#xml bills#peppol#invoice import

Starting May 1st, in Belgium the VAT provision account will replace the current account for periodic returns - Adding the new bank account - Adding a new account 'Tax Provision Account' 411800 Enterprise PR: odoo/enterprise#111599 Task [link](https://www.odoo.com/odoo/project.task/6044017) task-6044017 Forward-Port-Of: odoo/odoo#262188 Forward-Port-Of: odoo/odoo#255272

Applying stock quants validation was performing poorly due to multiple bottlenecks in `Picking._check_entire_pack` and `StockMoveLine._apply_putaway_strategy`: * **Redundant updates** were performed on `location_dest_id` in the move lines and the package levels (which internally update all related move lines too), even when the location remained unchanged. * The main loop inside `_check_entire_pack` was **O(N^2)** time relative to the number of move lines due to internal filtering logic. * **Cache misses** triggered unnecessary SQL queries when retrieving `move_line_ids` from `package levels`, while they are already cached via the pickings and can be grouped by `package_level`. --- ### Benchmark Benchmark conducted on a customer database with **400k** `stock_move_line` records within **800** `pickings`, testing performance of the action `StockQuant.action_validate` with different sizes of move lines. Each test was run multiple times and shown is the average mean, all with negligible variance. | Metric | Before | After | Delta | | :--- | :--- | :--- | :--- | | **Benchmark (1k lines)** | 10.5s | 2.2s | -80% | | **Benchmark (5k lines)** | 121s | 8.5s | -93% | | **Benchmark (50k lines)** | 887s | 56s | -94% | | **Benchmark (400k lines)** | timeout | 777s | (within time limit) | **OPW-6045513** Forward-Port-Of: odoo/odoo#257829

### Description: The upload and import process for large XML bills via Peppol or manual upload was inefficient due to two primary bottlenecks. First, the system performed individual queries per line to match products, taxes, and accounts, leading to an N+1 query issue. Second, multiple write operations were executed on each line to update various fields. This commit introduces batching and improve caching for these operations to reduce database call. ### Benchmark: | N° of lines | Before | After | |-------------|---------|-------| | 30264 | Timeout | 11min | ### Reference: opw-5416612 Forward-Port-Of: odoo/odoo#261401 Forward-Port-Of: odoo/odoo#248680