Daily updates from Odoo
Sunday, May 10, 2026
4 changes · saas-19.2
Resolved issues and error corrections
This update resolves an issue where tax reports for Russian VAT (GSTR2B) displayed incorrect amounts due to a sign discrepancy with reverse charge transactions. Now, bills are shown with positive amounts and credit notes with negative amounts, ensuring accurate financial reporting.
Original PR description
In reverse charge taxes, tax tags are added on negative repartition lines, causing the amounts to appear with the opposite sign in reports. Due to this, credit notes were shown as positive amounts and bills as negative amounts. This commit fixes the sign handling so that: - bills are shown with positive amounts - credit notes are shown with negative amounts Forward-Port-Of: odoo/enterprise#116828 Forward-Port-Of: odoo/enterprise#116740
This update fixes an issue where the COGS calculation was incorrectly inflated when multiple lines of the same product were invoiced separately from a single Sale Order. The change ensures accurate COGS reporting by isolating COGS calculations to the specific invoice line, preventing overestimation of costs and maintaining accurate profitability reports. This improves the reliability of financial data.
Original PR description
### Issue: When a Sale Order has multiple lines for the same FIFO-costed product and each line is invoiced separately, the COGS posted on the second (and any subsequent) invoice is incorrectly…
### Issue: When a Sale Order has multiple lines for the same FIFO-costed product and each line is invoiced separately, the COGS posted on the second (and any subsequent) invoice is incorrectly inflated, causing the sale to appear less profitable or even at a loss in the accounting records. ### Steps to reproduce: 1. Set a product as storable with FIFO costing and real-time valuation. 2. Create a Sale Order with two lines for the same product at different prices. 3. Confirm the SO and validate the two deliveries (each consumes a different FIFO layer). 4. Invoice the first SO line and post the invoice. 5. Invoice the second SO line and post the invoice. 6. Observe that the COGS on the second invoice is higher than the actual cost of the stock move linked to that line. ### Root Cause: _get_cogs_qty() and _get_posted_cogs_value() in sale_stock filtered already-posted COGS lines by product_id. This caused them to aggregate quantities and values across ALL SO lines sharing the same product. However, _get_cogs_price_unit() derives the unit cost only from the current line's stock move. The mismatch results in: (unit_cost_of_line_2 * total_qty_of_both_lines) - cogs_already_posted ### Fix: Replace the product_id filter with a sale-line-scoped filter using cogs_origin_id. By checking cogs_origin_id.sale_line_ids & sale_lines, only COGS originating from the same SO line(s) as the current invoice line are considered, correctly isolating each line's COGS from the others. opw-6004810 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#257868
This update fixes an issue where the image cropper in the HTML editor didn't correctly display style options like rounded corners. The change ensures users see a precise preview of how the final image will look, improving the user experience and reducing errors when customizing images. This was previously addressed and temporarily lost during a website builder update.
Original PR description
When cropping images with style option applied (e.g., circle), the cropper ignored these styles, causing a mismatch between the preview and the final rendered image.This made the issue especially noticeable for rounded styles. This commit ensures the cropper reflects the applied style, allowing users to preview the final result more accurately. This behavior was previously fixed in https://github.com/odoo/odoo/pull/197374 but was lost during the website builder refactoring (see commit https://github.com/odoo-dev/odoo/commit/9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2). This change restores the expected behavior. task-6088098 Forward-Port-Of: odoo/odoo#263432 Forward-Port-Of: odoo/odoo#256966
This update corrects a flaw in how missing transactions are identified for online accounts. Previously, the system only checked transactions from the last sync date, leading to missed records. Now, the system prioritizes the provided start date, ensuring a more complete and accurate retrieval of online transaction data.
Original PR description
When you want to find missing transactions, you have to put a starting date. But we don't use this starting date to find the last statement line, we only use the last sync date, which is wrong, because if the last sync date is after the starting date, the online transaction identifier will have the wrong date. It means we will only fetch the transactions from last sync date to today. This commit makes sure we take the start date first if it exists, then the last sync date. task-6197277 Forward-Port-Of: odoo/enterprise#116624