Odoo Changelog — 2025-09-26

Friday, September 26, 2025

6 changes · saas-18.4

Improvements(6)

Enhancements to existing features

[IMP] account_accountant: tolerance of matching

Enterprisesaas-18.4account_accountantMedium

Bank reconciliation no longer uses a fixed matching tolerance for invoices. Instead, businesses can control the tolerance through a system setting, with existing and new databases defaulting to no tolerance unless enabled.

Original PR description

This commit: https://github.com/odoo/enterprise/commit/9bea3f2c517e77fdb822eb53b9648e9fc5478dac introduce a tolerance. If an invoice has a bigger amount than the bank line but within the tolerance of 3%, reconcile the invoice automatically and leave the difference in the suspense account.
The statement line will be partially matched.

This commit will change that tolerance to use a system parameter instead. For old DB the tolerance is at 0 and for new DB a system parameter (0 by default) will be put so that people that want to use it can.

task-5106655

Forward-Port-Of: odoo/enterprise#95301

#bank reconciliation#invoice matching#configuration

[IMP] hr: add tracking on hr.version fields

PR #92601

Enterprisesaas-18.4hr_contract_salaryhr_contract_salary_holidayshr_payrollhr_payroll_accounthr_signhr_work_entry_attendancel10n_ae_hr_payrolll10n_au_hr_payrolll10n_au_hr_payroll_accountl10n_be_hr_contract_salaryl10n_be_hr_payrolll10n_be_hr_payroll_fleetl10n_be_hr_payroll_group_sl10n_ch_hr_payrolll10n_eg_hr_payrolll10n_fr_hr_payrolll10n_hk_hr_payrolll10n_id_hr_payrolll10n_in_hr_payroll

[IMP] hr: add tracking on hr.version fields

PR #223342

Coresaas-18.4hrhr_work_entryMedium

Employee version records now automatically track changes to most business-relevant fields. This strengthens audit trails and makes it easier for HR teams to understand when important employee information changed.

Original PR description

Most fields in hr.version represent business-relevant employee data that should be tracked to ensure a complete audit trail. This commit adds `tracking=True` by default on hr.version fields across community and enterprise modules.

task-5022109

#employee records#audit trail#HR

[IMP] web: include stacktrace when converting a run() error to a MacroError

PR #228714

Coresaas-18.4webweb_tour

This update makes internal web automation errors easier to diagnose by including the original technical trace when a run step fails. It helps support and development teams find the source of issues faster, reducing time spent investigating unclear browser error messages.

Original PR description

Because it only embeds the error message, and because it ultimately gets `console.error`-ed, an error during a `run()` function is currently extremely unhelpful e.g.

    Cannot read properties of undefined (reading 'ownerDocument')

might be all you get. And despite what one might assume, browsers (or at least chrome) don't seem to chain stacktraces when using `{cause}`, so even printing stacktraces on `console.error` does not yield useful information, the stacktrace point to `performAction` instead of a useful location.

So use the `Error#stack` if it's available. In chrome that includes both the error message and the full stack, so a formatted error message is unnecessary. Fall back on a formatted error message if the error has no stack for some reason.

Forward-Port-Of: odoo/odoo#227169

#debugging#automation#error reporting

[PERF] point_of_sale: avoid loading attribute values unnecessarily

PR #228726

Coresaas-18.4point_of_salepos_self_orderMedium

Point of Sale now avoids loading large sets of product attribute values until they are actually needed. This reduces unnecessary data loading and can improve startup performance for stores with many product options, without changing how products are linked or sold.

Original PR description

Before this commit, when loading PoS, all product template attribute value (ptav) IDs linked to a product attribute were loaded. This caused performance issues when attributes had a large number of values, even though they were not needed at that stage.

With this commit, the values are no longer preloaded, since the reverse fields in ptav and ptal are fetched when needed, ensuring they can still be linked correctly without degrading performance.

opw-5006818

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#226999
Forward-Port-Of: odoo/odoo#224497

#performance#point of sale#product attributes

[IMP] hr_payroll: prevent edition in payslip line report

PR #95297

Enterprisesaas-18.4hr_payroll

Payroll report views have been tightened so users can no longer edit payslip line or worked days report data from reporting screens. This helps preserve payroll data integrity while making the reports easier to browse and search.

Original PR description

-In payslip line report, some  fields can be edited, which should not be allowed. 
-Views have been adjusted to prevent the navigation from pivot to list view.
-Search view has been modified for easier data reaching.

Forward-Port-Of: odoo/enterprise#94284

#payroll#reports#data integrity

This commit: https://github.com/odoo/enterprise/commit/9bea3f2c517e77fdb822eb53b9648e9fc5478dac introduce a tolerance. If an invoice has a bigger amount than the bank line but within the tolerance of 3%, reconcile the invoice automatically and leave the difference in the suspense account. The statement line will be partially matched. This commit will change that tolerance to use a system parameter instead. For old DB the tolerance is at 0 and for new DB a system parameter (0 by default) will be put so that people that want to use it can. task-5106655 Forward-Port-Of: odoo/enterprise#95301

Most fields in hr.version represent business-relevant employee data that should be tracked to ensure a complete audit trail. This commit adds `tracking=True` by default on hr.version fields across community and enterprise modules. task-5022109

Because it only embeds the error message, and because it ultimately gets `console.error`-ed, an error during a `run()` function is currently extremely unhelpful e.g. Cannot read properties of undefined (reading 'ownerDocument') might be all you get. And despite what one might assume, browsers (or at least chrome) don't seem to chain stacktraces when using `{cause}`, so even printing stacktraces on `console.error` does not yield useful information, the stacktrace point to `performAction` instead of a useful location. So use the `Error#stack` if it's available. In chrome that includes both the error message and the full stack, so a formatted error message is unnecessary. Fall back on a formatted error message if the error has no stack for some reason. Forward-Port-Of: odoo/odoo#227169

Before this commit, when loading PoS, all product template attribute value (ptav) IDs linked to a product attribute were loaded. This caused performance issues when attributes had a large number of values, even though they were not needed at that stage. With this commit, the values are no longer preloaded, since the reverse fields in ptav and ptal are fetched when needed, ensuring they can still be linked correctly without degrading performance. opw-5006818 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#226999 Forward-Port-Of: odoo/odoo#224497

-In payslip line report, some fields can be edited, which should not be allowed. -Views have been adjusted to prevent the navigation from pivot to list view. -Search view has been modified for easier data reaching. Forward-Port-Of: odoo/enterprise#94284