Odoo Changelog — 2026-02-22

Sunday, February 22, 2026

4 changes

Branch: saas-19.1

1 change

Improvements(1)

Enhancements to existing features

[IMP] l10n_in: optimize tax tag lookup

PR #249877

Coresaas-19.1l10n_in

This update optimizes the process of assigning tax tags to invoices in the Indian localization (l10n_in) module. By restricting processing to Indian invoices and using faster XMLID resolution, the system now performs more efficiently, reducing unnecessary load and improving response times. This results in a smoother user experience for our Indian customers.

Original PR description

Before this commit:
- `_get_l10n_in_tax_tag_ids()` was executed for moves unrelated to Indian localization, causing unnecessary processing.
- Profiling showed repeated `env.ref` lookups (>≈1.6% transactions each) even for a simple invoice flow (create → add products → post).

After this commit:
- Restrict execution to Indian-specific moves only.
- Replace `env.ref` with `_xmlid_to_res_id` for faster XMLID resolution.

task-5935607

Forward-Port-Of: odoo/odoo#248960

#tax#localization#performance

Branch: master

2 changes

Improvements(2)

Enhancements to existing features

[IMP] l10n_be_hr_payroll: Specific setup for BE companies

PR #107841

Enterprisemasterl10n_be_hr_payrolll10n_be_hr_contract_salaryMEDIUM

This update introduces specific settings for Belgian companies within Odoo, including key details like the joint committee, DIMONA category, and worker code. A dashboard warning alerts users to missing information, guiding them through a configuration wizard to ensure accurate payroll processing for Belgian businesses.

Original PR description

This commit adds a specific configuration for Belgian companies, including: main joint committee, DIMONA category, and worker code. A warning is displayed on the dashboard for Belgian companies with missing settings. Clicking the warning button opens a wizard to configure the required values.

task-5933795

#payroll#Belgium#HR#configuration

[IMP] hr_payroll: Payrun Mixin

PR #101565

Enterprisemasterhr_payrollMEDIUM

This update introduces a new JavaScript mixin to seamlessly display pay run cards within various views, streamlining the pay run process. It allows for multiple steps (employee, time, etc.) to be represented as individual cards, improving visibility and usability. This enhancement ensures all employees are visible, even those without records.

Original PR description

JS mixin to implement the payrun behavior in multiple Controller.
The Layout component is extended to add the custom kanban card above the main container of the Layout.

The flow is implemented:
- A Pay Run can have multiple steps: Employee, Time, (Attendance), Payslip
- Each step can have its own payrun card

To add a Pay Run Card in a view:
- make a custom view and replace the controller by PayRunMixin(OriginalController)
- the action that trigger the view have to give a kanban_view_id and the payrun_id in context
- BOOM the card appears.

task-5362147

#payroll#payrun#kanban#employee

Branch: 17.0

1 change

Improvements(1)

Enhancements to existing features

[IMP] account: add force_overwrite parameter to _load_translations

PR #236425

Core17.0accountMEDIUM

This update allows localization teams to more easily update chart translations, even for records protected by a 'no update' flag. Previously, changes required manual intervention. Now, localization modules can directly overwrite translations, ensuring charts are always aligned with the latest language versions and simplifying localization maintenance.

Original PR description

Currently, when loading chart template translations, existing translations
cannot be overwritten for records with noupdate=True flag, even when localization updates require translation corrections.

This limitation prevents proper localization maintenance, especially when:
- Chart template translations need to be updated to fix incorrect or outdated translations
- Localization modules need to ensure translations are synchronized with the latest chart template versions
- Manual translation corrections need to be applied during localization setup or updates

By adding the force_overwrite parameter, localization modules can now explicitly request to overwrite existing translations, including those protected by noupdate=True, enabling proper translation management for localization purposes.

The parameter defaults to False to maintain backward compatibility and preserve existing behavior when not explicitly requested.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

#localization#translation#chart templates

Before this commit: - `_get_l10n_in_tax_tag_ids()` was executed for moves unrelated to Indian localization, causing unnecessary processing. - Profiling showed repeated `env.ref` lookups (>≈1.6% transactions each) even for a simple invoice flow (create → add products → post). After this commit: - Restrict execution to Indian-specific moves only. - Replace `env.ref` with `_xmlid_to_res_id` for faster XMLID resolution. task-5935607 Forward-Port-Of: odoo/odoo#248960

This commit adds a specific configuration for Belgian companies, including: main joint committee, DIMONA category, and worker code. A warning is displayed on the dashboard for Belgian companies with missing settings. Clicking the warning button opens a wizard to configure the required values. task-5933795

JS mixin to implement the payrun behavior in multiple Controller. The Layout component is extended to add the custom kanban card above the main container of the Layout. The flow is implemented: - A Pay Run can have multiple steps: Employee, Time, (Attendance), Payslip - Each step can have its own payrun card To add a Pay Run Card in a view: - make a custom view and replace the controller by PayRunMixin(OriginalController) - the action that trigger the view have to give a kanban_view_id and the payrun_id in context - BOOM the card appears. task-5362147

Currently, when loading chart template translations, existing translations cannot be overwritten for records with noupdate=True flag, even when localization updates require translation corrections. This limitation prevents proper localization maintenance, especially when: - Chart template translations need to be updated to fix incorrect or outdated translations - Localization modules need to ensure translations are synchronized with the latest chart template versions - Manual translation corrections need to be applied during localization setup or updates By adding the force_overwrite parameter, localization modules can now explicitly request to overwrite existing translations, including those protected by noupdate=True, enabling proper translation management for localization purposes. The parameter defaults to False to maintain backward compatibility and preserve existing behavior when not explicitly requested. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr