Friday, March 20, 2026
6 changes · 17.0
Resolved issues and error corrections
This update resolves an issue where the W4 filing date was incorrectly associated with the employee's W4 form completion. The change ensures the system accurately records when the W4 is submitted to the employer, improving payroll accuracy and compliance. This fix addresses a previous reporting discrepancy.
Original PR description
This field is about when the W4 is filed with the employer, not when it's filled in. opw-5096780
This update fixes a reporting issue where the KMD INF report incorrectly included partners with turnover below 1,000 EUR. Now, the report accurately filters partners based on total invoice and credit note amounts, ensuring more precise financial reporting. The logic considers both invoices and credit notes, as well as Part B transactions.
Original PR description
The KMD INF report should only include partners whose total turnover for the period reaches 1,000 EUR. Before this PR: - The report did not check this threshold, so partners below €1,000 were still shown. After this PR: - The threshold is now calculated correctly based on specific rules: - The threshold is calculated separately for invoices and credit notes per partner. - If invoices total base amount >= €1,000 OR credit notes total base amount >= €1,000, both invoices and credit notes are included in the report - The same logic applies to bills and refunds in Part B. task-5373606
This update fixes an issue where repositioning signs within PDFs caused inconsistent resizing. By ensuring only one resize listener is attached to each sign item, the system now provides a stable and predictable resizing experience for users.
Original PR description
Previously, repositioning a sign item inside the PDF iframe would attach multiple resize event listeners. This led to inconsistent and unintuitive resizing behavior. This commit ensures that only a single resize listener is registered per item, avoiding duplicated handlers and restoring stable interaction. task-6048759
This update resolves an issue preventing successful migrations of the 'stock_mts_mto_rule' module in version 17.0. The fix ensures that route names are correctly handled during migration processes, addressing a translation-related failure. This improvement guarantees smoother and more reliable module installations.
Original PR description
Description of the issue/feature this PR addresses: if the method `_find_or_create_global_route` is invoked during a migration process, it will fail as the term `route_name` is translated, but the call is made clearing it Current behavior before PR: a migration process failed for an external module: `stock_mts_mto_rule` Desired behavior after PR is merged: the migration process succeeds --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves a bug where downpayment invoices for orders with fixed taxes incorrectly lacked tax line items. This prevented proper invoice generation for Peppol integration, causing errors. The fix removes the problematic downpayment processing related to fixed taxes.
Original PR description
When making a downpayment for an order containing product using fixed taxes, the downpayment invoice would contain line without tax associated This is an issue when sending these invoices to Peppol. Steps to reproduce: ------------------- * Create a fixed tax of 5€ * Set this tax on any product along another tax * Create a sale order for this product * Make a downpayment of 10% * The invoice created has a line without any tax set > Observation: When sending to Peppol we get an error Why the fix: ------------ We remove the downpayment part that concerns fixed tax to avoid having lines without tax set. opw-5853070
This update fixes an issue where kit products were incorrectly reporting the full sales price of each component on delivery DDTs. Previously, the system didn't properly account for kits, leading to inaccurate value summaries. Now, the DDTs accurately reflect the value of each component within the kit.
Original PR description
Steps to reproduce: - Have an IT company setup - Create a product with a Sales Price and define a kit BOM with 2 components - Create SO with product - Confirm, go to delivery, validate - Print Issue: In the delivery DDT, there is a summary of the delivery where each item has its own entry (product, quantity, value). However, in case of kit BOM, each component is reported with the full value of the sale operation. Analysis: This occurs because in the report code we don't consider the possibility of kit products, where multiple components are associated to the same sale line. Ticket [link](https://www.odoo.com/odoo/project.task/5013606) opw-5013606