Tuesday, July 7, 2026
4 changes · saas-19.2
Enhancements to existing features
UK VAT returns now guide users to file through the relevant tax unit when their company belongs to one. The system uses the tax unit VAT number for HMRC connections and submissions, reducing filing errors and ensuring reports are sent under the correct entity.
Original PR description
BEFORE: - Before this commit, when the current company is a member of the tax unit, there is no blocking level error for the user to select the tax unit. - And the vat used while creating a connection to the HMRC or while sending a tax report to the HMRC is of the current company. AFTER: - After this commit, there is one blocking level error, which tells the user that the current company is part of a tax unit, and on confirmation, the tax unit will automatically be selected for the current report. - And if the return contains the data of a tax unit, then the vat set on the tax unit will be considered while establishing the connection and sending the tax report to HMRC. Task-5865605 Forward-Port-Of: odoo/enterprise#122965 Forward-Port-Of: odoo/enterprise#107253
Belgian payroll rules were updated with the new employment bonus parameters taking effect on 1 July 2026 and 1 September 2026. This helps ensure payroll calculations remain aligned with upcoming legal requirements and reduces the risk of incorrect payslips.
Original PR description
Update the employment bonus parameters for 1st July 2026 and 1st September 2026. task-6369633
Belgian payroll calculations now include updated employment bonus parameters taking effect on 1 July 2026 and 1 September 2026. This helps ensure payroll remains aligned with the latest Belgian rules for eligible employees.
Original PR description
Update the employment bonus parameters for 1st July 2026 and 1st September 2026. task-6369633
Creating employees will now process future public holiday time entries much faster. This prevents long waits or timeouts when many holidays have been set up far into the future, improving reliability for HR and planning teams.
Original PR description
**Problem:** When creating a new employee, the future timesheets due to public holidays are computed. If the number of public holidays is large (i.e. if the user creates them for each year, several…
**Problem:** When creating a new employee, the future timesheets due to public holidays are computed. If the number of public holidays is large (i.e. if the user creates them for each year, several years in the future), then it takes excessively long and the action may not complete. **Cause:** The pytz method `localize` and comparing times with non-static timezones is done repeatedly and unnecessarily which becomes costly with more records. **Solution:** Only localize the time when absolutely necessary (determining the date of the leave in the calendar timezone). **Performance Stats:** |Record count|Time before|Queries before|Time after|Queries after| |------------|-----------|--------------|----------|-------------| |100 |3.1s |393 |0.8s |117 | |1,000 |22.3s |2,090 |1.5s |183 | |10,000 |Timeout |N/A |6.7s |541 | opw-6087422 Forward-Port-Of: odoo/odoo#270684 Forward-Port-Of: odoo/odoo#263953