Odoo Changelog — 2025-08-07

Thursday, August 7, 2025

3 changes · saas-18.4

Improvements(3)

Enhancements to existing features

[IMP] hr,hr_work_entry: UX refactor of contract template

Coresaas-18.4hrhr_work_entryMEDIUM

The contract template form has been reorganized to restore important information that was lost after HR and contract features were merged. This makes it easier for HR users to review and configure contract templates with the fields they previously relied on.

Original PR description

Since the merge of hr and contract, we only have a form view for contracts for templates. Thus, during the merge, a lot of info has been lost on contract template form view.
This commit, reintroduce fields that were present in saas-18.3 and re-organize them.

task-4904024

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

#contract templates#HR#user experience

[IMP] *: UX refactor of contract template

PR #89832

Enterprisesaas-18.4hr_contract_salaryhr_payrollhr_payroll_accounthr_work_entry_attendancehr_work_entry_planningl10n_ae_hr_payrolll10n_au_hr_payrolll10n_au_hr_payroll_accountl10n_be_hr_payrolll10n_be_hr_payroll_fleetl10n_ch_hr_payrolll10n_eg_hr_payrolll10n_hk_hr_payrolll10n_id_hr_payrolll10n_in_hr_payrolll10n_jo_hr_payrolll10n_ke_hr_payrolll10n_lt_hr_payrolll10n_lu_hr_payrolll10n_mx_hr_payrolll10n_nl_hr_payrolll10n_ro_hr_payrolll10n_sa_hr_payrolll10n_sk_hr_payrolll10n_us_hr_payrollMEDIUM

Contract template screens now restore important information that was lost after HR and contract features were merged. The layout is reorganized across payroll, salary, work entry, and country-specific payroll modules, making templates easier for HR teams to review and configure.

Original PR description

* = hr_contract_salary, hr_payroll{,_account}, hr_work_entry_{attendance,planning}, l10n_{ae,au,be,ch,eg,hk,id,in,jo,ke,lt,lu,mx,nl,ro,sa,sk,us}_hr_payroll, l10n_au_hr_payroll_account,

Since the merge of hr and contract, we only have a form view for contracts for templates. Thus, during the merge, a lot of info has been lost on contract template form view.
This commit, reintroduce fields that were present in saas-18.3 and re-organize them.

task-4904024

#contracts#payroll#templates#user-experience

[IMP] account_accountant: auto creation of multiple reco model with same account

PR #91855

Enterprisesaas-18.4account_accountantMEDIUM

Accounting can now automatically create separate reconciliation suggestions even when they use the same account, company, and journal. This helps teams handle different recurring transaction labels, such as rent and location payments, without one suggestion blocking another.

Original PR description

Backport of: https://github.com/odoo/enterprise/pull/89358 - Before this commit: The automatic creation of reco model is constrained by company, account and journal. So if the reco model with this…

Backport of: https://github.com/odoo/enterprise/pull/89358

- Before this commit: The automatic creation of reco model is constrained by company, account and journal. So if the reco model with this config exists then new reco model will not be created.

- After this commit: Now we have removed the constraint entirely. Because we want to have more than one reco model with the same account in it.

- Example: Suppose we have 3 statement lines with 'Rent' as a label in them, and 3 statement lines with 'Location' as a label in them.

  So before this commit when user sets same account on the first two lines with 'Rent' label, will create a new reco model with 
  '{Common substring} - {account code}' as a model name and common substring from labels of both lines will be set as a 
  match_label_param of the model. And then user next set that same account on the first two lines with 'Location' label, will not    
  create a new reco model automatically, because for this config one reco model already exists.
  
   But now after this commit when user sets same account for first two lines with 'Location' label will also create a new reco 
   model automatically with '{Common substring} - {account code}' as a model name and common substring from labels of both 
   lines will be set as a match_label_param of the reco model.

Task: 4876374

Forward-Port-Of: odoo/enterprise#91414

#accounting#bank reconciliation#automation

Since the merge of hr and contract, we only have a form view for contracts for templates. Thus, during the merge, a lot of info has been lost on contract template form view. This commit, reintroduce fields that were present in saas-18.3 and re-organize them. task-4904024 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

* = hr_contract_salary, hr_payroll{,_account}, hr_work_entry_{attendance,planning}, l10n_{ae,au,be,ch,eg,hk,id,in,jo,ke,lt,lu,mx,nl,ro,sa,sk,us}_hr_payroll, l10n_au_hr_payroll_account, Since the merge of hr and contract, we only have a form view for contracts for templates. Thus, during the merge, a lot of info has been lost on contract template form view. This commit, reintroduce fields that were present in saas-18.3 and re-organize them. task-4904024

Backport of: https://github.com/odoo/enterprise/pull/89358 - Before this commit: The automatic creation of reco model is constrained by company, account and journal. So if the reco model with this config exists then new reco model will not be created. - After this commit: Now we have removed the constraint entirely. Because we want to have more than one reco model with the same account in it. - Example: Suppose we have 3 statement lines with 'Rent' as a label in them, and 3 statement lines with 'Location' as a label in them. So before this commit when user sets same account on the first two lines with 'Rent' label, will create a new reco model with '{Common substring} - {account code}' as a model name and common substring from labels of both lines will be set as a match_label_param of the model. And then user next set that same account on the first two lines with 'Location' label, will not create a new reco model automatically, because for this config one reco model already exists. But now after this commit when user sets same account for first two lines with 'Location' label will also create a new reco model automatically with '{Common substring} - {account code}' as a model name and common substring from labels of both lines will be set as a match_label_param of the reco model. Task: 4876374 Forward-Port-Of: odoo/enterprise#91414