Odoo Changelog — 2026-01-18

Sunday, January 18, 2026

7 changes · saas-18.2

Bug Fixes(7)

Resolved issues and error corrections

[FIX] l10n_hr_edi: Minor UI, API and error handling fixes

Coresaas-18.2l10n_hr_edi

This update addresses several small issues within the l10n_hr_edi module, primarily focused on improving the reliability and user experience of fiscal document processing. Specifically, it enhances error handling related to API responses and clarifies settings for multi-company environments, ensuring smoother operations.

Original PR description

- Adjusting error handling for receiving an empty response from MER for a document fiscalization status.
- Adding additional checks for running multi-company-wide MER API methods.
- Adjusting how approval API call is handled when confirming a bill.
- Adding a tooltip about Company BU in MER settings and missing "company dependent" indicators for the credentials.
Continuation of task-4925745
Related to opw-5477846

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#244023

#HR#EDI#Fiscalization

[IMP] certificate, account_edi_proxy_client: manage CA certificate stores

PR #244356

Coresaas-18.2account_edi_proxy_clientcertificateMEDIUM

This update enhances the security of our web service connections by allowing administrators to manage certificate stores. Previously, our system struggled to verify server identities, now we can securely use certificate records to establish connections. This improves overall system reliability and security.

Original PR description

Our webservice client (`zeep`) connections lacked a way to use `certificate.certificate` models to verify the connection with server identification. 
This is rather complicated, since PyOpenSSL only allows filenames with their default methods. 
We now add the feature to pass these certificate records, load them into memory buffers, and add them to the CA store.

IAP PR: odoo/iap-apps#1308

Task [link](https://www.odoo.com/odoo/project.task/5068741)
task-5068741

Forward-Port-Of: odoo/odoo#238717

#security#connections#certificates

[FIX] l10n_ma_reports: tax report: properly consider cash basis taxes in the XML export

PR #104657

Enterprisesaas-18.2l10n_ma_reportsMEDIUM

This update corrects a critical issue in the Moroccan tax report XML export, ensuring it properly accounts for the country's cash basis accounting system. Previously, all bills were reported regardless of the period, leading to inaccurate data. This change improves data consistency and export efficiency.

Original PR description

[FIX] l10n_ma_reports: tax report: properly consider cash basis taxes in the XML export

Moroccan taxes are cash basis by default. The former version of the XML generation completely disregarded that, and always reported all bills in the period. Solving this requires using an SQL query so that cash basis can be properly computed, like in the report. This also makes the export much more efficient, and resilient to bigger amount of data.

Steps to reproduce:
- Install `l10n_ma_reports` and switch to the MA company
- Create and confirm a bill:
	Bill Date: 10/01/2025
	Vendor: Azure Interior
	Invoice Lines: Price 100, Taxes 20% (S 140)
- Go to `Bank Reconciliation`
- Add a transaction (Vendor: Azure Interior, Amount: -120 DH, any Memo)
- Select the transaction and the invoice, then click Validate
- Open the Tax Return for November.
	Section D should show data linked to the created invoice
- Export the XML using the Gear → XML
	The created bill is missing in the XML and others may be present, showing inconsistent data

opw-5002779


[IMP] l10n_ma_reports: call the report to compute the prorata value

Searching explicitly for external values is a bad practice ; calling the report ensures consistency between the data displayed, and the one exported into the file.

Forward-Port-Of: odoo/enterprise#104619

#taxes#morocco#cash basis

[FIX] website_sale_stock_renting: fix rental availability with continue selling

PR #104648

Enterprisesaas-18.2website_sale_stock_rentingMEDIUM

This update corrects a display issue on rental product pages within the e-commerce system. When 'continue selling' is enabled, the available quantity was incorrectly shown as 2 instead of reflecting the selected rental period. The fix ensures accurate availability is displayed, allowing customers to see the correct quantity available for rent.

Original PR description

**Issue**: The displayed available quantity on the ecommerce product page is incorrect for rental products when "continue selling" is enabled. **Steps to reproduce**: - Create a rental product…

**Issue**:
The displayed available quantity on the ecommerce product page is incorrect for rental products when "continue selling" is enabled.

**Steps to reproduce**:
- Create a rental product tracked in stock with a quantity of 5
- Enable "continue selling" and "show available quantity below 10"
- Go to the ecommerce page of this product
- Rent 3 units for a given period, confirm and pay
- Return to the ecommerce product page
-> Whatever the selected renting period, the displayed quantity is always 2

**Cause**:
The website displays `free_qty`:
https://github.com/odoo/enterprise/blob/41c729e22c5fd1abb690f8335e933f793be0b319/website_sale_stock_renting/static/src/xml/website_sale_stock_renting_product_availability.xml#L15

`free_qty` is computed in:
https://github.com/odoo-dev/odoo/blob/0935829ddaecd7b2b6eec9157f8f790b546d06ff/addons/website_sale_stock/models/product_template.py#L36

which leads to:
https://github.com/odoo/enterprise/blob/41c729e22c5fd1abb690f8335e933f793be0b319/website_sale_stock_renting/models/website.py#L10

and ultimately relies on:
https://github.com/odoo/odoo/blob/37bf1703c7478a3010b71cd60bbb43b3295a605b/addons/stock/models/product.py#L213

This computation does not take the selected renting period into account.

There is a period-aware computation here:
https://github.com/odoo/enterprise/blob/41c729e22c5fd1abb690f8335e933f793be0b319/website_sale_stock_renting/models/website.py#L15C17-L21C1

but it is only triggered when `product.allow_out_of_stock_order` is False (i.e. when "continue selling" is disabled).

opw-[5354163](https://www.odoo.com/web#id=5354163&view_type=form&model=project.task)

Forward-Port-Of: odoo/enterprise#103333

#rental#ecommerce#availability

[FIX] account_followup: show activity in list view only when schedule activity is enabled

PR #104637

Enterprisesaas-18.2account_followup

This update ensures that the 'Activity' column in the Follow-up Levels list view only displays when 'Schedule Activity' is enabled. Previously, it incorrectly showed activity even when the option was disabled, leading to potentially confusing data. This change improves the clarity and accuracy of the follow-up level information.

Original PR description

Currently, follow-up levels display an `activity` in the list view even when the `Schedule Activity` option is not enabled on the record. **Steps to reproduce:** - Install the `account_followup`…

Currently, follow-up levels display an `activity` in the list view even 
when the `Schedule Activity` option is not enabled on the record.

**Steps to reproduce:**
- Install the `account_followup` module.
- Navigate to Accounting > Configuration > Invoicing > Follow-up Levels.
- Click `New` and enter a `description`.
- Open the `Activity tab`, `enable` Schedule Activity, set an Activity Type and Summary, then `save`.
- `Disable` Schedule Activity, `save` the record again, and return to the `list view`.
- Observe the `Activity` for the newly created follow-up level.

**Observation:**
The Activity column still shows a value in the list view, even though Schedule Activity is unchecked.

**Root Cause:**
At [1], `activity_type_id` is always shown in the list view without 
considering `create_activity`, causing the `activity` to remain visible 
even when `Schedule Activity` is `disabled`.

**Fix:**
This commit ensures that the `Activity` is displayed in the list view only 
when `Schedule Activity` (`create_activity`) is enabled for the record.

[1]:
https://github.com/odoo/enterprise/blob/d7882a8f97802d7302d81c1fa375a81bb4ca4717/account_followup/views/account_followup_line_views.xml#L13

opw-5476176

Forward-Port-Of: odoo/enterprise#104427

#follow-up#activity#invoicing

[FIX] l10n_ke_edi_oscu: hide eTIMS warning for non-Kenyan companies

PR #104631

Enterprisesaas-18.2l10n_ke_edi_oscu

This update resolves an issue where a warning about eTIMS configuration was incorrectly displayed for companies outside of Kenya. The fix ensures that eTIMS validation only applies to Kenyan companies, improving the user experience and preventing unnecessary alerts.

Original PR description

**Steps to reproduce:**
* Install the **l10n_ke_edi_oscu** module.
* Use a **non-Kenyan company** (e.g., “My Company (San Francisco)”).
* Open any invoice for that company.

**Observed behavior:**
* A warning about **incomplete eTIMS configuration** is shown on invoices, even though the company is not based in Kenya.

**Cause:**
* The eTIMS validation logic runs for **all companies**.
* Non-Kenyan companies, which do not require eTIMS setup, are still evaluated and trigger the warning.

**Fix:**
* Run the eTIMS validation only for **Kenyan companies**.
* Suppress the warning for companies outside Kenya.

opw-5435558

Forward-Port-Of: odoo/enterprise#103158

#eTIMS#Kenya#compliance

[FIX] spreadsheet_edition: Insert record from grouped list

PR #103869

Enterprisesaas-18.2spreadsheet_edition

This update removes an unnecessary restriction that prevented users from inserting records into lists grouped by many2many fields. The change clarifies the process for inserting records from these lists, improving usability and functionality. This resolves a previous bug that was blocking users without a clear reason.

Original PR description

When we introduced the record-specific insertion from a list, we added a limitation on lists grouped by many2many fields but this limitation makes no sense, it only blocks the users without any clear reason.

Task: 5267035

Forward-Port-Of: odoo/enterprise#103161

#spreadsheet#list#many2many

- Adjusting error handling for receiving an empty response from MER for a document fiscalization status. - Adding additional checks for running multi-company-wide MER API methods. - Adjusting how approval API call is handled when confirming a bill. - Adding a tooltip about Company BU in MER settings and missing "company dependent" indicators for the credentials. Continuation of task-4925745 Related to opw-5477846 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#244023

Our webservice client (`zeep`) connections lacked a way to use `certificate.certificate` models to verify the connection with server identification. This is rather complicated, since PyOpenSSL only allows filenames with their default methods. We now add the feature to pass these certificate records, load them into memory buffers, and add them to the CA store. IAP PR: odoo/iap-apps#1308 Task [link](https://www.odoo.com/odoo/project.task/5068741) task-5068741 Forward-Port-Of: odoo/odoo#238717

[FIX] l10n_ma_reports: tax report: properly consider cash basis taxes in the XML export Moroccan taxes are cash basis by default. The former version of the XML generation completely disregarded that, and always reported all bills in the period. Solving this requires using an SQL query so that cash basis can be properly computed, like in the report. This also makes the export much more efficient, and resilient to bigger amount of data. Steps to reproduce: - Install `l10n_ma_reports` and switch to the MA company - Create and confirm a bill: Bill Date: 10/01/2025 Vendor: Azure Interior Invoice Lines: Price 100, Taxes 20% (S 140) - Go to `Bank Reconciliation` - Add a transaction (Vendor: Azure Interior, Amount: -120 DH, any Memo) - Select the transaction and the invoice, then click Validate - Open the Tax Return for November. Section D should show data linked to the created invoice - Export the XML using the Gear → XML The created bill is missing in the XML and others may be present, showing inconsistent data opw-5002779 [IMP] l10n_ma_reports: call the report to compute the prorata value Searching explicitly for external values is a bad practice ; calling the report ensures consistency between the data displayed, and the one exported into the file. Forward-Port-Of: odoo/enterprise#104619

**Issue**: The displayed available quantity on the ecommerce product page is incorrect for rental products when "continue selling" is enabled. **Steps to reproduce**: - Create a rental product tracked in stock with a quantity of 5 - Enable "continue selling" and "show available quantity below 10" - Go to the ecommerce page of this product - Rent 3 units for a given period, confirm and pay - Return to the ecommerce product page -> Whatever the selected renting period, the displayed quantity is always 2 **Cause**: The website displays `free_qty`: https://github.com/odoo/enterprise/blob/41c729e22c5fd1abb690f8335e933f793be0b319/website_sale_stock_renting/static/src/xml/website_sale_stock_renting_product_availability.xml#L15 `free_qty` is computed in: https://github.com/odoo-dev/odoo/blob/0935829ddaecd7b2b6eec9157f8f790b546d06ff/addons/website_sale_stock/models/product_template.py#L36 which leads to: https://github.com/odoo/enterprise/blob/41c729e22c5fd1abb690f8335e933f793be0b319/website_sale_stock_renting/models/website.py#L10 and ultimately relies on: https://github.com/odoo/odoo/blob/37bf1703c7478a3010b71cd60bbb43b3295a605b/addons/stock/models/product.py#L213 This computation does not take the selected renting period into account. There is a period-aware computation here: https://github.com/odoo/enterprise/blob/41c729e22c5fd1abb690f8335e933f793be0b319/website_sale_stock_renting/models/website.py#L15C17-L21C1 but it is only triggered when `product.allow_out_of_stock_order` is False (i.e. when "continue selling" is disabled). opw-[5354163](https://www.odoo.com/web#id=5354163&view_type=form&model=project.task) Forward-Port-Of: odoo/enterprise#103333

Currently, follow-up levels display an `activity` in the list view even when the `Schedule Activity` option is not enabled on the record. **Steps to reproduce:** - Install the `account_followup` module. - Navigate to Accounting > Configuration > Invoicing > Follow-up Levels. - Click `New` and enter a `description`. - Open the `Activity tab`, `enable` Schedule Activity, set an Activity Type and Summary, then `save`. - `Disable` Schedule Activity, `save` the record again, and return to the `list view`. - Observe the `Activity` for the newly created follow-up level. **Observation:** The Activity column still shows a value in the list view, even though Schedule Activity is unchecked. **Root Cause:** At [1], `activity_type_id` is always shown in the list view without considering `create_activity`, causing the `activity` to remain visible even when `Schedule Activity` is `disabled`. **Fix:** This commit ensures that the `Activity` is displayed in the list view only when `Schedule Activity` (`create_activity`) is enabled for the record. [1]: https://github.com/odoo/enterprise/blob/d7882a8f97802d7302d81c1fa375a81bb4ca4717/account_followup/views/account_followup_line_views.xml#L13 opw-5476176 Forward-Port-Of: odoo/enterprise#104427

**Steps to reproduce:** * Install the **l10n_ke_edi_oscu** module. * Use a **non-Kenyan company** (e.g., “My Company (San Francisco)”). * Open any invoice for that company. **Observed behavior:** * A warning about **incomplete eTIMS configuration** is shown on invoices, even though the company is not based in Kenya. **Cause:** * The eTIMS validation logic runs for **all companies**. * Non-Kenyan companies, which do not require eTIMS setup, are still evaluated and trigger the warning. **Fix:** * Run the eTIMS validation only for **Kenyan companies**. * Suppress the warning for companies outside Kenya. opw-5435558 Forward-Port-Of: odoo/enterprise#103158

When we introduced the record-specific insertion from a list, we added a limitation on lists grouped by many2many fields but this limitation makes no sense, it only blocks the users without any clear reason. Task: 5267035 Forward-Port-Of: odoo/enterprise#103161