Odoo Changelog — 2026-01-28

Wednesday, January 28, 2026

5 changes · saas-18.4

Bug Fixes(5)

Resolved issues and error corrections

[FIX] ai: keep AI chat window above dialogs only

Enterprisesaas-18.4aiMedium

This update fixes an issue where dialog windows were hidden behind chat windows, making them difficult to use. Now, the AI chat window remains prominently displayed above all other dialogs, ensuring users can easily interact with both.

Original PR description

**Description of the issue this PR addresses:**
------------------------------------------------

Dialogs were rendered behind chat windows, making them difficult to see and interact with.

**Current behavior before PR:**
---------------------------------

- The dialog appears behind the chat window

**Desired behavior after PR is merged:**
-----------------------------------------

- Dialogs are displayed above all chat windows except AI
- The AI chat window remains intentionally above dialogs

**Task:** 5367135

Forward-Port-Of: odoo/enterprise#103076

#chat#ui#user experience

[FIX] l10n_syscohada_reports: Inverted sign on gross margin

PR #105698

Enterprisesaas-18.4accountMedium

This update fixes an error in the SYSCOHADA Profit and Loss report where the gross margin calculation was incorrectly adding instead of subtracting values. The change ensures the report accurately reflects the financial data as defined in the SYSCOHADA documentation, improving reporting accuracy for Ginea businesses using this localization.

Original PR description

The SYSCOHADA gross margin is defined on page 330 - 331 of the document [Guide-d-application-du-SYSCOHADA.pdf](https://www.ohada.com/uploads/actualite/3504/Guide-d-application-du-SYSCOHADA.pdf). It is TA (701) - RA (601) +/- RB (6031). TA and RA should always be positive and negative, respectively.

In the report "Profit and Loss (SYSCOHADA)", the line RA is negated. XA then subtracts this value from TA, adding the two values instead of subtracting them.

Steps to reproduce:

1. Create a new company on runbot.
2. In Accounting > Configuration > Settings, set their Fiscal Localization to Ginea - SYSCOHADA for Companies.
3. Make a MISC journal entry.
    1. Set a credit of 110,000,000 on account 701100 and balance it with 411100.
    5. Set a debit of 75,000,000 on account 601100 and balance it with 401100.
    6. Set a credit of 5,000,000 on account 603100 and balance it with 411100.
7. Post the entry.
8. Navigate to Accounting > Reports > Profit and Loss.
9. Set the l10n version, Profit and Loss (SYSCOHADA).
10. Set the current date.
11. See XA = 110 million + 75 million + 5 million = 190 million; this does not match the example given on pg 357 of Guide-d-application-du-SYSCOHADA.pdf, where XA = 40 million.

[opw-5482300](https://www.odoo.com/odoo/project.task/project.task/5482300)

Forward-Port-Of: odoo/enterprise#104736
Forward-Port-Of: odoo/enterprise#104479

[FIX] l10n_ro_saft: handle missing partner info

PR #105641

Enterprisesaas-18.4l10n_ro_saftMedium

This update resolves errors in the SAF-T export process for Romanian companies when partner information (country or name) is incomplete. Specifically, it corrects issues related to generating the RegistrationNumber and prevents report errors caused by missing partner details, ensuring accurate financial reporting.

Original PR description

Fix SAF-T export errors when partners have no country or name.

For Romanian companies, the RegistrationNumber should be
generated as “04 + partner ID” for customers not subject to VAT
and with unknown CNP, without including the country code.

Steps to reproduce country issue:
- Configure a Romanian company with l10n_ro_saft installed
- Create a contact without a country
- Create and validate an invoice for this contact
- Export the SAF-T file from the General Ledger report

You you will get a TypeError because you cant concatenate Bool and String.

Steps to reproduce name issue:
- Create a main contact
- Add a child contact without a name
- Change the child type to “Company”
- Create and validate an invoice
- Export the SAF-T file from the General Ledger report

This prevents KeyError when printing the first 70 characters
of the partner name in the report.

opw-5499918

Forward-Port-Of: odoo/enterprise#105579
Forward-Port-Of: odoo/enterprise#105020

#Romania#SAF-T#Accounting

[FIX] l10n_mx_edi_sale: ensure CFDI to Public is set when partner address is invalid

PR #105622

Enterprisesaas-18.4l10n_mx_edi_saleMedium

This update resolves an issue where sales orders with incomplete Mexican address information could prevent payment processing. The fix automatically enables 'CFDI to Public' when the address is missing, ensuring transactions are correctly validated and payments are recorded. This prevents silent errors and improves the reliability of online payments for Mexican customers.

Original PR description

### Issue: On a Mexican sale order, it was possible to have an invalid partner address while `CFDI to Public` was not enabled In this situation, an online payment could be initiated, but a silent…

### Issue:
On a Mexican sale order, it was possible to have an invalid partner address while `CFDI to Public` was not enabled
In this situation, an online payment could be initiated, but a silent error occurred during move validation:
the transaction was created, but the payment was never recorded, and no error appeared in the portal or the SO chatter

### Cause:
The CFDI validation error is raised internally but never surfaced to the user
https://github.com/odoo/enterprise/pull/91655
The PO (MIAL) recommended automatically enabling `CFDI to Public` when the partner address is incomplete,
forcing the user to complete the data This also ensures that the payment can be confirmed properly

### Steps to reproduce:
- Install `l10n_mx_edi_sale` and switch to the MX company
- Configure a Payment Provider and Payment Method (e.g., demo)
- Create a customer without ZIP or country
- Create a Sale Order for that customer
- In Other Info, set Online Payment to 100%
- Send the quotation and open the link in a private window
- Sign and Pay

Before the fix: the transaction is created, but no payment is recorded, and no error is shown

opw-5023724

Forward-Port-Of: odoo/enterprise#101881

[FIX] l10n_ch_hr_payroll_elm_transmission: perform read in sudo

PR #105292

Enterprisesaas-18.4l10n_ch_hr_payrollMedium

This update corrects a technical issue preventing accurate payslip updates, particularly for employees. By adding a 'sudo' call, the system now correctly accesses necessary data, resolving a previous error and ensuring payroll information is updated reliably. This improves the stability and accuracy of payroll processing.

Original PR description

From a previous PR (103147), the payslip update logic was moved to the write function which gets called when a field is changed. In doing so, a sudo call is necessary to avoid problems with users modifying their own record (and not having access rights to read slip_ids). This also applies to tests and solves the following runbot error:

Runbot Error: 237743

Forward-Port-Of: odoo/enterprise#105287

#payroll#ch#payslip

**Description of the issue this PR addresses:** ------------------------------------------------ Dialogs were rendered behind chat windows, making them difficult to see and interact with. **Current behavior before PR:** --------------------------------- - The dialog appears behind the chat window **Desired behavior after PR is merged:** ----------------------------------------- - Dialogs are displayed above all chat windows except AI - The AI chat window remains intentionally above dialogs **Task:** 5367135 Forward-Port-Of: odoo/enterprise#103076

The SYSCOHADA gross margin is defined on page 330 - 331 of the document [Guide-d-application-du-SYSCOHADA.pdf](https://www.ohada.com/uploads/actualite/3504/Guide-d-application-du-SYSCOHADA.pdf). It is TA (701) - RA (601) +/- RB (6031). TA and RA should always be positive and negative, respectively. In the report "Profit and Loss (SYSCOHADA)", the line RA is negated. XA then subtracts this value from TA, adding the two values instead of subtracting them. Steps to reproduce: 1. Create a new company on runbot. 2. In Accounting > Configuration > Settings, set their Fiscal Localization to Ginea - SYSCOHADA for Companies. 3. Make a MISC journal entry. 1. Set a credit of 110,000,000 on account 701100 and balance it with 411100. 5. Set a debit of 75,000,000 on account 601100 and balance it with 401100. 6. Set a credit of 5,000,000 on account 603100 and balance it with 411100. 7. Post the entry. 8. Navigate to Accounting > Reports > Profit and Loss. 9. Set the l10n version, Profit and Loss (SYSCOHADA). 10. Set the current date. 11. See XA = 110 million + 75 million + 5 million = 190 million; this does not match the example given on pg 357 of Guide-d-application-du-SYSCOHADA.pdf, where XA = 40 million. [opw-5482300](https://www.odoo.com/odoo/project.task/project.task/5482300) Forward-Port-Of: odoo/enterprise#104736 Forward-Port-Of: odoo/enterprise#104479

Fix SAF-T export errors when partners have no country or name. For Romanian companies, the RegistrationNumber should be generated as “04 + partner ID” for customers not subject to VAT and with unknown CNP, without including the country code. Steps to reproduce country issue: - Configure a Romanian company with l10n_ro_saft installed - Create a contact without a country - Create and validate an invoice for this contact - Export the SAF-T file from the General Ledger report You you will get a TypeError because you cant concatenate Bool and String. Steps to reproduce name issue: - Create a main contact - Add a child contact without a name - Change the child type to “Company” - Create and validate an invoice - Export the SAF-T file from the General Ledger report This prevents KeyError when printing the first 70 characters of the partner name in the report. opw-5499918 Forward-Port-Of: odoo/enterprise#105579 Forward-Port-Of: odoo/enterprise#105020

### Issue: On a Mexican sale order, it was possible to have an invalid partner address while `CFDI to Public` was not enabled In this situation, an online payment could be initiated, but a silent error occurred during move validation: the transaction was created, but the payment was never recorded, and no error appeared in the portal or the SO chatter ### Cause: The CFDI validation error is raised internally but never surfaced to the user https://github.com/odoo/enterprise/pull/91655 The PO (MIAL) recommended automatically enabling `CFDI to Public` when the partner address is incomplete, forcing the user to complete the data This also ensures that the payment can be confirmed properly ### Steps to reproduce: - Install `l10n_mx_edi_sale` and switch to the MX company - Configure a Payment Provider and Payment Method (e.g., demo) - Create a customer without ZIP or country - Create a Sale Order for that customer - In Other Info, set Online Payment to 100% - Send the quotation and open the link in a private window - Sign and Pay Before the fix: the transaction is created, but no payment is recorded, and no error is shown opw-5023724 Forward-Port-Of: odoo/enterprise#101881

From a previous PR (103147), the payslip update logic was moved to the write function which gets called when a field is changed. In doing so, a sudo call is necessary to avoid problems with users modifying their own record (and not having access rights to read slip_ids). This also applies to tests and solves the following runbot error: Runbot Error: 237743 Forward-Port-Of: odoo/enterprise#105287