Monday, March 2, 2026
5 changes · saas-18.3
Resolved issues and error corrections
This update ensures that transactions imported via the Odoo cron process are correctly split according to the journal configuration, mirroring the behavior of manual imports. Previously, the cron process bypassed this splitting logic, leading to incorrect accounting. This fix improves the accuracy of financial data processing.
Original PR description
When importing CODA files manually, transactions are correctly split according to the journal configuration. However, when processed via the cron, the splitting logic is bypassed because the journal recordset is empty at the time of parsing. This occurs because the journal is identified only after the file has been parsed, which is too late for the cron flow. This commit ensures the journal is available early enough to respect the "Split Transactions" setting regardless of the import method. opw-4954539 Forward-Port-Of: odoo/enterprise#107560 Forward-Port-Of: odoo/enterprise#106344
Previously, users couldn't reply to messages received from other companies within Odoo. This update fixes a bug that prevented responses, allowing users to properly acknowledge and respond to communications across different company environments. This improves collaboration and ensures timely responses to all messages.
Original PR description
Before these changes, messages from other companies were received, but when trying to reply to them, an error occurred that prevented the response. Steps to reproduce the issue in runbot: 1. In one tab, log in as admin, and in another incognito tab, open demo. 2. Make sure demo has Handle Notifications in Odoo enabled. 3. Set admin in one company and demo in another company. 4. Assign a task to demo. 5. Click on the notification to open the chatter and try to reply. An error is thrown With these changes, the response can be logged when the user has access to the company from which the task was assigned. cc @Tecnativa TT61176 ping @pedrobaeza --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#250677
This update ensures self-order transactions in Point of Sale (POS) systems – including online payments, restaurant POS, and standard self-order – now use the same data validation rules as regular POS orders. This enhances data accuracy and reliability, reducing potential errors and improving the overall POS experience.
Original PR description
*: pos_online_payment_self_order, pos_restaurant, pos_self_order This commit improves the data validation of pos self order by using the same validation as the one used for regular pos order. Forward-Port-Of: odoo/odoo#251004 Forward-Port-Of: odoo/odoo#250415
This update partially reverses a previous change that caused an error in how Odoo predicts account information during invoice processing. The original change impacted tax calculations, but now account prediction is failing. This fix addresses the core issue of incorrect account prediction.
Original PR description
…x at import" Bug introduced by: https://github.com/odoo/odoo/commit/9cc26a154381e51e3f4188aa7c251d959538676e Since this, the taxes are predicted only once but the prediction of account is no longer working. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#251480
This update ensures that timesheet updates accurately reflect the cost of sales order lines, regardless of the invoice policy used (ordered_prepaid, delivered_manual, or delivered_milestones). Previously, updates were prevented under certain conditions, leading to inaccurate cost calculations. This change improves the reliability of sales reporting and timesheet tracking.
Original PR description
Originally, timesheet updates for tasks associated with sale order lines would cause the cost (purchase_price) to be recomputed. However, this was prevented if the invoice policy was 'ordered_prepaid.' This should also apply to 'delivered_manual' and 'delivered_milestones.' Otherwise, any timesheet updates will recompute the sales.order.line purchase_price field. Steps to reproduce: 1. Create a service product that creates a project/tasks 2. Create a sales order with the product and manually set the cost 3. Assign the timesheets of the task to an employee 4. Have the employee update their timesheet for the task 5. The cost on the sales order line gets recomputed to the default product price task-5902688 related-pr-205415 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#250495