Daily updates from Odoo
Tuesday, March 10, 2026
8 changes · master
Enhancements to existing features
This update introduces a new field to track whether an employee is retired. This change is necessary to accurately calculate tax exemptions for employees who remain active while meeting specific criteria. It also prepares the system for future flexi-job functionality.
Original PR description
Retired employees that are still working can qualify for tax exemptions. This commit adds a boolean field to check if the employee is retired. Will be used for tax reporting and when flexi jobs are introduced. Task: 5976320
This update addresses an issue where excessive Many-to-Many tags could create a cluttered user interface. The commit limits the displayed tags, enhancing the visual appeal and usability of forms. A default limit of 8 tags is now enforced, with the option to display all tags (0) for greater flexibility.
Original PR description
Currently we don't have a way to limit the number of m2m tags displayed, which can lead to ugly UI. This commit introduces such a limit, making it editable via studio. As for default values, we use 8 as a default number of m2m tags displayed (which is also the number of records we display in m2m dropdowns). Setting a value of 0 can be used to display all tags regardless of how many they are. Community PR: https://github.com/odoo/odoo/pull/251159 Documentation PR: odoo/documentation#16667 task#5799365
This update adjusts the timing of changes to marital status for withholding tax calculations. Switching from an isolated status (single, divorced, widow) now takes effect at the start of the next calendar year, while becoming isolated (e.g., adding a spouse) is immediate. This aligns with Belgian tax regulations.
Original PR description
For withholding taxes: ----------------------- Switching from an isolated status (single, divorced, widow) to a non isolated will take effect the start of the next calendar year. But the other way around (becoming isolated) takes effect immediately. Task-5449907
This update optimizes Odoo's reporting functionality, specifically addressing memory usage issues with large datasets and improving report stability. The team removed unused code and refactored report generation to enhance performance and reduce resource consumption.
Original PR description
Forward-Port-Of: odoo/enterprise#102808
This update simplifies our payroll structure for Belgium, aligning with new regulations regarding joint committees. It consolidates previous CP200 structures into a single 'Belgium' structure, ensuring compliance and streamlining payroll processing. Additionally, the update introduces key features for worker compensation, including unpaid time off, sick leave calculations, and adjusted ONSS base rates.
This update streamlines invoice reports for Ecuador by removing redundant information previously displayed in the standard header. The changes also adjust the report formatting to ensure proper spacing and avoid overlapping with required legal headers. This improves the clarity and compliance of the reports.
Original PR description
The standard report header contains info that the legally required headers already contain. We hide the standard headers by using the custom_header mechanism in l10n_latam_invoice_document. This also changes an `<h4>` to an `<h5>` to avoid it overflowing the standard header_spacing of the A4 report.paperformat. task-5949275
This update simplifies the approval process by replacing a complex 'approval_type' field with a straightforward boolean. The change clarifies required approvals and streamlines the flow for managers, making it easier to manage purchase requests. This enhancement improves efficiency and reduces potential confusion.
Original PR description
This commit aims to make some enhancement to the approval Category and Request Forms. Given that approval_type will either be 'purchase' or empty, it's better to replace it with a boolean field. The field "manager_approval" is now a Boolean with False being the old None and True being "Is required Approver", and the third option "Is Approver" is now dropped. odoo/upgrade#9373 Task - 5410747
This update adds quick access to key payroll reports directly within the pay run interface. HR and payroll teams can now easily verify work entries and payroll codes, detect anomalies, and improve data accuracy – ultimately reducing the time spent on pay run audits.
Original PR description
Purpose As an HR officer or payroll consultant, add quick access to pay run verification reports to efficiently identify and validate potential errors. Changes - Add Work Times report button to pay run kanban view - Add Payroll Journal report button to pay run kanban view Benefits - Verify work entry types and payroll codes used in the pay run - Detect anomalies by comparing values with previous periods - Provide quick access to detailed reports without additional navigation - Reduce time spent verifying pay run data for accuracy This enables users to perform comprehensive pay run audits directly from the pay run interface, improving data quality and compliance. Task: 5974389