Daily updates from Odoo
Wednesday, November 19, 2025
4 changes · saas-18.3
Enhancements to existing features
The Point of Sale sales report now includes a more detailed view of payments, grouped by payment method. This makes it easier for teams to understand how customers paid and to review sales performance more clearly.
Original PR description
In this commit: ----------- - Enhances the PoS sales report by adding detailed breakdowns of payments grouped by payment method. task-5184319 Forward-Port-Of: odoo/odoo#234486
The mail plugin now includes a way to identify the Odoo version it is connecting to. This lets Odoo display a clear message when the add-in is used with an older, unsupported version instead of failing without explanation.
Original PR description
Purpose ======= The new addin has been refactored and doesn't work with older Odoo version, and so we add an endpoint to be able to show a message if we don't support that Odoo version. Task-4727609 Forward-Port-Of: odoo/odoo#236286 Forward-Port-Of: odoo/odoo#236047
Invoice delivery to customers and government EDI systems is now deferred until after the payment transaction is fully committed. This reduces the risk of invoices being sent and then lost due to a rollback, helping keep Odoo records aligned with external government numbering and customer communications.
Original PR description
When the payment transactions trigger the creation of invoices and then the sending of those invoices by mail and through the EDI to the government, any concurrent update can make that entire process…
When the payment transactions trigger the creation of invoices and then the sending of those invoices by mail and through the EDI to the government, any concurrent update can make that entire process fail all at once. This mainly happens when the user himself is paying through the portal as this will create the invoice from the payment. When invoices are sent to the government however, we want to be sure that when sent, it gets updated in Odoo as well, so we are aware what is happening. The problem we got is that invoice 1 is sent to the government (l10n_in_edi) as number 01 and then that transaction is totally rolled back that the invoice is not even there anymore, it risks that the government's numbers and your numbers do not correspond anymore. So, we should avoid that that invoice can be sent when before there is a concurrent update (on payment transaction in this case) waiting for destroying it when committing. So, the simple idea would be to only do the invoice sending through a post commit. As we are locking the invoice itself for the sending to the government that should be enough to avoid the invoice sending for not being registered in Odoo. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Finnish tax reporting now includes triangular taxes, which helps generate the EC Sales List more accurately. This improves compliance and reduces manual adjustments for businesses operating across EU borders.
Original PR description
The aim of this commit is adding the triangular taxes into the tax report to use it in EC Sales List report. task-5126664 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#229269