Odoo Changelog — 2026-09-01

Tuesday, September 1, 2026

2 changes · saas-18.3

Improvements(2)

Enhancements to existing features

[PERF] l10n_it_edi: Reduce import line overhead

Coresaas-18.3l10n_it_ediMedium

Large Italian electronic invoices now import much faster by reducing repeated per-line processing and creating invoice lines in batches. This shortens waiting time for finance teams handling bills with many lines, especially in high-volume scenarios.

Original PR description

### Description:

When importing a large invoice, the process can take a lot of time. This is caused by how `l10n_it_edi` handles the creation and writing of each line of the bill.

To improve performance, most of the process is now performed in memory and record creation is deferred to a single batch at the end. Additionally, the check related to `account_accountant` is cached to avoid superfluous calls.

### Benchmark:

**For `history.limit`[^1] of 50 (= 21002 `account.move.line`):**

| Invoice lines | Before   | After   | Speedup |
|---------------|----------|---------|---------|
| 33            | 4.75s    | 2.23s   | 2.1×    |
| 172           | 2.3min   | 45.1s   | 3.1×    |
| 1,934         | 44.4min  | 6.8min  | 6.6×    |

[^1]: System parameter `account.bill.predict.history.limit`

### Reference:
opw-5937519

Forward-Port-Of: odoo/odoo#282880

#performance#invoicing#italy#edi

[PERF] account_accountant: Improve field prediction

PR #129817

Enterprisesaas-18.3account_accountantMedium

Invoice field prediction has been optimized for databases with many accounting entries. This should make supplier invoice processing, including Peppol-based matching, faster and reduce long waits when suggesting products, accounts, or taxes.

Original PR description

### Description:

Predicting fields can be slow when the database has a large amount of move lines (AML). This is caused by the fact that `_predicted_field` will search on all these AMLs to find the ones related to the searched fields. It can be an issue when using Peppol since it is used a lot in most localizations to match each line to its product/account/tax.

To speed up the queries, the move IDs have been inlined in `_build_predictive_query` to avoid suboptimal execution plans caused by LIMIT and ORDER BY clauses. Additionally, materialization of the `account_move_line` CTE has been removed so the planner can inline filters and stream rows directly, which improves performance in most use cases.


### Benchmark:

**For a `history.limit`[^1] of 100:**

| Nb of invoice line | Before    | After   | AMLs scanned |
|--------------------|-----------|---------|--------------|
|                 33 | 7s        | 4s      | 232          |
|                172 | 11.39min  | 5min    | 99859        |
|               1934 | 3h+ [^2]  | 1h40min | 102503       |

**For a `history.limit`[^1] of 50:**

| Nb of invoice line | Before  | After   | AMLs scanned |
|--------------------|---------|---------|--------------|
|                 33 | 6s      | 4s      | 187          |
|                172 | 2.52min | 1.27min | 21002        |
|               1934 | 40min   | 20min   | 21002        |

[^1]: System parameter `account.bill.predict.history.limit`
[^2]: Stopped manually after 3h; full runtime not measured

### Reference:
opw-5937519

Forward-Port-Of: odoo/enterprise#128172

### Description: When importing a large invoice, the process can take a lot of time. This is caused by how `l10n_it_edi` handles the creation and writing of each line of the bill. To improve performance, most of the process is now performed in memory and record creation is deferred to a single batch at the end. Additionally, the check related to `account_accountant` is cached to avoid superfluous calls. ### Benchmark: **For `history.limit`[^1] of 50 (= 21002 `account.move.line`):** | Invoice lines | Before | After | Speedup | |---------------|----------|---------|---------| | 33 | 4.75s | 2.23s | 2.1× | | 172 | 2.3min | 45.1s | 3.1× | | 1,934 | 44.4min | 6.8min | 6.6× | [^1]: System parameter `account.bill.predict.history.limit` ### Reference: opw-5937519 Forward-Port-Of: odoo/odoo#282880

### Description: Predicting fields can be slow when the database has a large amount of move lines (AML). This is caused by the fact that `_predicted_field` will search on all these AMLs to find the ones related to the searched fields. It can be an issue when using Peppol since it is used a lot in most localizations to match each line to its product/account/tax. To speed up the queries, the move IDs have been inlined in `_build_predictive_query` to avoid suboptimal execution plans caused by LIMIT and ORDER BY clauses. Additionally, materialization of the `account_move_line` CTE has been removed so the planner can inline filters and stream rows directly, which improves performance in most use cases. ### Benchmark: **For a `history.limit`[^1] of 100:** | Nb of invoice line | Before | After | AMLs scanned | |--------------------|-----------|---------|--------------| | 33 | 7s | 4s | 232 | | 172 | 11.39min | 5min | 99859 | | 1934 | 3h+ [^2] | 1h40min | 102503 | **For a `history.limit`[^1] of 50:** | Nb of invoice line | Before | After | AMLs scanned | |--------------------|---------|---------|--------------| | 33 | 6s | 4s | 187 | | 172 | 2.52min | 1.27min | 21002 | | 1934 | 40min | 20min | 21002 | [^1]: System parameter `account.bill.predict.history.limit` [^2]: Stopped manually after 3h; full runtime not measured ### Reference: opw-5937519 Forward-Port-Of: odoo/enterprise#128172