Thursday, February 19, 2026
4 changes · 17.0
Resolved issues and error corrections
This update fixes an issue where payment beneficiary accounts were incorrectly assigned after merging inbound and outbound payments. Specifically, when a refund is merged, the system now correctly identifies the payment type (outbound) and assigns the appropriate bank account. This ensures accurate payment processing and reporting.
Original PR description
When we create new payments for bills and refunds, we offer the possibility to merge inbound and outbound payments together if they are from the same provider and the bills all reference the same…
When we create new payments for bills and refunds, we offer the possibility to merge inbound and outbound payments together if they are from the same provider and the bills all reference the same recipient account. Depending on the balance of the resulting payment, we assign an adequate inbound or outbound bank account as the recipient. The `partner_bank_id` can be assigned through different processes: - If the wizard has only one batch: The wizard is editable and the user can select a bank account from the computed `available_partner_bank_ids`. - If there are multiple batches: Odoo assigns a `partner_bank_id` in `_create_payment_vals_from_batch()`. For an outbound payment, it uses the batch['payment_values']['partner_bank_id']. The problem is that this value is not updated after a merge of payments. If the base line being merged on is a refund, but the result is an outbound payment, then the `partner_bank_id` should be changed accordingly. I decided to include the changes of my previous PR targeting v18 and fixing the grouping of payments, even though it was deemed unnecessary for v17, because it felt weird not to considering how close these fixes are. -Previous PR : [242863](https://github.com/odoo/odoo/pull/242863) However, I can remove these changes or re-target this PR to v18. I am not sure what would be best here. Ticket: opw-5401372
This update resolves an issue where Point of Sale (PoS) was failing to display products with single-attribute-value options (e.g., 'Small' size). The fix ensures that products with unique attribute values are correctly listed in the PoS interface, improving the user experience and preventing lost sales.
Original PR description
Steps to reproduce ------------------ 1. Create a product "P", with an attribute e.g. "Size", having only one signe possible attribute value, e.g. "Small". 2. Add it to PoS. 3. In PoS, click the "i"…
Steps to reproduce ------------------ 1. Create a product "P", with an attribute e.g. "Size", having only one signe possible attribute value, e.g. "Small". 2. Add it to PoS. 3. In PoS, click the "i" button to show this product's info popup, and click on the "Small" button. We are supposed to filter out the variants having "Small" attribute value, so we expect to see one product, however, we see NO PRODUCTS. Reason ------ When clicking the attribute value button, "Small" in this case, we filter for proucts belonging to the product template "Product", which also have "Small" in their names. This assumes that a new product have been created for that "Small" attribute value, however that's not the case, since for single-attribute-value attributes, we don't create a separate product variant. I.e. since we can only have one option for "Size" which is "Small", we don't create a separate prodduct for it. Fix ---- In the case of single-attribute-value attributes, don't add the attribute name to the search word since no products will be found. Just list all the products from that prodcuct template, they will naturally all match that single attribute value. opw-5497593
This update resolves an issue where the 13th month payment wasn't correctly included in the calculations for Swiss payroll (LPP). The change adds the 13th month to the base calculation, ensuring accurate reporting and compliance with Swiss tax regulations. This ensures accurate payroll processing for businesses using the Odoo Enterprise module in Switzerland.
This update corrects a problem preventing the automated sending of wage statements for Swiss payroll. The fix ensures accurate and timely delivery of these important documents, complying with Swiss tax regulations. This improves payroll processing efficiency and reduces the risk of late filings.