Odoo Changelog — 2026-05-29

Friday, May 29, 2026

4 changes · saas-18.4

Bug Fixes(4)

Resolved issues and error corrections

[FIX] l10n_mx_edi_pos: correct the timezone of pos order date

Enterprisesaas-18.4l10n_mx_edi_posMEDIUM

This update fixes an issue where global invoices created after a POS order at the end of the month were incorrectly displaying the following month. The system now accurately converts POS order dates to the correct Mexican timezone to ensure accurate invoice month calculations. This prevents discrepancies in reporting and invoicing for Mexican businesses using the POS module.

Original PR description

**PROBLEM**
When creating a global invoice, with the last order being at the end of the last day of the month, the month of the global invoice will not be correct. (e.g, order made at the end of May and global invoice created for June).
date_order is stored in utc.
To compute the day the order was made, we need to convert to a MX timezone.

**STEP TO REPRODUCE**
1. Create an pos order at the end of the last day of a month (for example, at 10PM in local MX time).
2. Create a global invoice with this order.
3. Notice the global invoice month will be the month after the one of the order.

opw-6221049

Forward-Port-Of: odoo/enterprise#118170

#accounting#mexico#pos#timezone

[FIX] sale_commission: correct overlap for other plans based on salesperson date

PR #118680

Enterprisesaas-18.4sale_commission

This update fixes an issue where commission plans were incorrectly listed in the 'Other Plans' section for salespeople, even when their assignment periods didn't overlap. The system now accurately checks if salesperson assignment dates intersect with plan effective dates, ensuring only relevant plans are displayed. This improves the accuracy of sales reporting and commission calculations.

Original PR description

Version
- 18.0

Steps to reproduce:
1. Create a commission plan A with effective period 2025–2026
2. Assign salesperson to plan A from 01/01/2025 to 31/12/2025
3. Create another commission plan B with effective period 2026
4. Assign the same salesperson to plan B from 01/01/2026 to 31/12/2026
5. Open plan B and check the 'Other Plans' section in the salespeople tab

Issue:
Plans are shown in 'Other Plans' even when salesperson assignment periods do not overlap.
System incorrectly relies on plan effective dates instead of salesperson-specific assignment dates

Fix:
A plan is now considered overlapping only if the salesperson assignment periods intersect. Non-overlapping plans are properly excluded from 'Other Plans'.

Taskid-6055253

Forward-Port-Of: odoo/enterprise#118559
Forward-Port-Of: odoo/enterprise#112694

#commission#sales#reporting

[FIX] mrp_workorder: avoid traceback on empty workorder

PR #118707

Enterprisesaas-18.4mrp_workorder

This update fixes a technical issue that caused a traceback when attempting to mark workorders as done in certain scenarios, specifically when no workorders were open. The fix ensures the system handles empty recordsets gracefully, preventing errors and maintaining stability.

Original PR description

When calling on a empty recordset action_mark_as_done, it creates a traceback.

**Observation**

When calling action_mark_as_done, the method first loops over each workorder to perform various safety checks, and then calls button_finish to close all workorders:
https://github.com/odoo/enterprise/blob/24008b550c5e7cf04cde2028c40f8a32d5b0e504/mrp_workorder/models/mrp_workorder.py#L881-L888 
Inside button_finish, it retrieves all open workorders and marks them as done:
 - Retrieve open workorders: https://github.com/odoo/odoo/blob/36a1c6300f52f408b6af3f769e26686e07810e5a/addons/mrp/models/mrp_workorder.py#L659 
 - mark them as done:
https://github.com/odoo/odoo/blob/36a1c6300f52f408b6af3f769e26686e07810e5a/addons/mrp/models/mrp_workorder.py#L675-L678

Returning to action_mark_as_done, it attempts to set the state to 'done' on the last workorder outside of the loop, referencing the loop variable:
https://github.com/odoo/enterprise/blob/24008b550c5e7cf04cde2028c40f8a32d5b0e504/mrp_workorder/models/mrp_workorder.py#L894 

-> If self is empty, the loop never executes. This leaves the loop variable empty, which ultimately triggers a traceback.

opw-6239910

Forward-Port-Of: odoo/enterprise#118403

#workorders#stability#error handling

[FIX] account_reports: account codes & consolidation

PR #118823

Enterprisesaas-18.4account_reportsMEDIUM

This update improves the accuracy of consolidated financial reports by ensuring that all accounts, even those without a direct code mapping, are included in the consolidation process. Previously, accounts lacking a code on the company selector were filtered out, leading to incorrect report totals. This fix ensures all relevant accounts are considered for consolidation, providing more reliable financial data.

Original PR description

When having an horizontal group with domain including two companies that share the same account codes, report lines with account codes engine don't display the two companies values when both are…

When having an horizontal group with domain including two companies that
share the same account codes, report lines with account codes engine
don't display the two companies values when both are selected in the
company selector.

Steps to reproduce:

- Install l10n_ch and create two CH companies (CH1 and CH2)
- Create an horizontal group with the field 'Company' and domain '["|",
  ("name", "=", "CH Company"), ("name", "=", "CH 2")]"
- Apply the Horizontal group to CH balance sheet report
- Select both companies in the company selector
- Open CH BS report and activate the horizontal group
-> Only the column of one company is filled

Fix:

https://github.com/odoo/enterprise/commit/9b775ed9d8b2a18e708219c72e95652571f3936a
was introduced in 19.0 to fix the same issue, we fix by backporting it
but we also need to backport this perf commit https://github.com/odoo/enterprise/commit/7da3123dc4487a7092deef8503a9791ceffddcfb
that refactored the code before in a first place

opw-6204601

Forward-Port-Of: odoo/enterprise#118544
Forward-Port-Of: odoo/enterprise#117103

#reporting#consolidation#accounts

**PROBLEM** When creating a global invoice, with the last order being at the end of the last day of the month, the month of the global invoice will not be correct. (e.g, order made at the end of May and global invoice created for June). date_order is stored in utc. To compute the day the order was made, we need to convert to a MX timezone. **STEP TO REPRODUCE** 1. Create an pos order at the end of the last day of a month (for example, at 10PM in local MX time). 2. Create a global invoice with this order. 3. Notice the global invoice month will be the month after the one of the order. opw-6221049 Forward-Port-Of: odoo/enterprise#118170

Version - 18.0 Steps to reproduce: 1. Create a commission plan A with effective period 2025–2026 2. Assign salesperson to plan A from 01/01/2025 to 31/12/2025 3. Create another commission plan B with effective period 2026 4. Assign the same salesperson to plan B from 01/01/2026 to 31/12/2026 5. Open plan B and check the 'Other Plans' section in the salespeople tab Issue: Plans are shown in 'Other Plans' even when salesperson assignment periods do not overlap. System incorrectly relies on plan effective dates instead of salesperson-specific assignment dates Fix: A plan is now considered overlapping only if the salesperson assignment periods intersect. Non-overlapping plans are properly excluded from 'Other Plans'. Taskid-6055253 Forward-Port-Of: odoo/enterprise#118559 Forward-Port-Of: odoo/enterprise#112694

When calling on a empty recordset action_mark_as_done, it creates a traceback. **Observation** When calling action_mark_as_done, the method first loops over each workorder to perform various safety checks, and then calls button_finish to close all workorders: https://github.com/odoo/enterprise/blob/24008b550c5e7cf04cde2028c40f8a32d5b0e504/mrp_workorder/models/mrp_workorder.py#L881-L888 Inside button_finish, it retrieves all open workorders and marks them as done: - Retrieve open workorders: https://github.com/odoo/odoo/blob/36a1c6300f52f408b6af3f769e26686e07810e5a/addons/mrp/models/mrp_workorder.py#L659 - mark them as done: https://github.com/odoo/odoo/blob/36a1c6300f52f408b6af3f769e26686e07810e5a/addons/mrp/models/mrp_workorder.py#L675-L678 Returning to action_mark_as_done, it attempts to set the state to 'done' on the last workorder outside of the loop, referencing the loop variable: https://github.com/odoo/enterprise/blob/24008b550c5e7cf04cde2028c40f8a32d5b0e504/mrp_workorder/models/mrp_workorder.py#L894 -> If self is empty, the loop never executes. This leaves the loop variable empty, which ultimately triggers a traceback. opw-6239910 Forward-Port-Of: odoo/enterprise#118403

When having an horizontal group with domain including two companies that share the same account codes, report lines with account codes engine don't display the two companies values when both are selected in the company selector. Steps to reproduce: - Install l10n_ch and create two CH companies (CH1 and CH2) - Create an horizontal group with the field 'Company' and domain '["|", ("name", "=", "CH Company"), ("name", "=", "CH 2")]" - Apply the Horizontal group to CH balance sheet report - Select both companies in the company selector - Open CH BS report and activate the horizontal group -> Only the column of one company is filled Fix: https://github.com/odoo/enterprise/commit/9b775ed9d8b2a18e708219c72e95652571f3936a was introduced in 19.0 to fix the same issue, we fix by backporting it but we also need to backport this perf commit https://github.com/odoo/enterprise/commit/7da3123dc4487a7092deef8503a9791ceffddcfb that refactored the code before in a first place opw-6204601 Forward-Port-Of: odoo/enterprise#118544 Forward-Port-Of: odoo/enterprise#117103