Odoo Changelog — 2026-02-06

Friday, February 6, 2026

5 changes · saas-18.4

Bug Fixes(5)

Resolved issues and error corrections

[FIX] account_accountant: add credit note to fully paid bank rec

Enterprisesaas-18.4accountantMedium

This update resolves an issue where Odoo incorrectly reconciled bank transactions when credit notes were involved. Now, when a credit note is applied to an invoice and the bank transaction is marked 'fully paid,' the system accurately reflects the remaining balance owed. This ensures accurate bank reconciliation reports.

Original PR description

1. Create an invoice for $1,000
2. Create a credit note of $200 and apply it to the invoice. The invoice is marked 'partially paid.' The remaining due is $800.
3. Create a bank transaction of $700, reconcile with the invoice.
4. Edit the counterpart line, and click "fully paid".
>>> Odoo does not consider the credit note and uses the full amount of $1,000 instead of the remaining due of $800 to reconcile.

With the refactor of the bank rec, the way the amount is show is computed from econciled_lines_excluding_exchange_diff_ids in apply_amount.js which only takes into account the direct invoice and not the credit notes (in _compute_reconciled_lines_excluding_exchange_diff_ids it take the matched debit and matched credit so only the partial between the transaction and the move)

opw-5485663

Forward-Port-Of: odoo/enterprise#105197

#bank reconciliation#credit notes#finance

[FIX] l10n_ch_hr_payroll_elm_transmission_5_3: Fix coordination deduction

PR #106628

Enterprisesaas-18.4hr_payrolll10n_ch_hr_payrollMedium

This update resolves an issue related to the transmission of coordination deductions for Swiss payroll (l10n_ch_hr_payroll_elm_transmission_5_3). The fix ensures accurate calculation and reporting of these deductions, improving compliance with Swiss tax regulations. This impacts payroll processing for users in Switzerland.

Original PR description

Forward-Port-Of: odoo/enterprise#106615

#payroll#switzerland#elm#tax

[FIX] spreadsheet_edition: cell thread display_name

PR #106673

Enterprisesaas-18.4spreadsheet_editionMedium

This update resolves a technical error that prevented correct display names from being set for spreadsheet cell threads. The change ensures that only one display name is retrieved, preventing a system crash and improving spreadsheet functionality. This update is a critical fix for ensuring data accuracy within the enterprise version.

Original PR description

**Before this change**
We were trying to set the `display_name` of one spreadsheet cell thread record to a set of more than one `display_name`s coming from a set of potentially multiple spreadsheets.

**After this change**
We use `record` instead of `self` when calling `_get_spreadsheet_record` so that it can only return a set of 1 `display_name`, preventing the crash that occurs when trying to set that field value.

opw-5380947

Forward-Port-Of: odoo/enterprise#106593
Forward-Port-Of: odoo/enterprise#106230

#spreadsheet#data accuracy#performance

[FIX] l10n_sg_reports: fix error on IRAS audit file generation

PR #106150

Enterprisesaas-18.4l10n_sg_reportsMedium

This update resolves an error that prevented users from generating the required IRAS Audit File for Singapore companies. The fix corrects a coding issue that caused a 'TypeError' during file generation, ensuring accurate reporting for Singapore businesses. This ensures compliance and accurate financial reporting.

Original PR description

Currently, an error occurs when generating the `IRAS Audit File` for a `Singapore` company **Steps to reproduce:** - Install the `l10n_sg_reports` and `accountant` modules (without demo data). -…

Currently, an error occurs when generating the `IRAS Audit File` for 
a `Singapore` company

**Steps to reproduce:**
- Install the `l10n_sg_reports` and `accountant` modules (without demo data).
- Create a new company with Singapore as the `country` and set `UEN` and `GST No.`, 
  then switch to this company.
- Navigate to Accounting > Reporting > Singapore > IRAS Audit File.
- Fill in the required details and click `Generate`.

**Error:**
`TypeError: 'account.account' object is not callable`

**Root cause:**
After the refactoring in PR [1], the code at [2] mistakenly calls `browse()` 
without arguments and then attempts to call the returned recordset with 
`line_account_ids`. Since `browse()` already returns a recordset, this results 
in calling an `account.account` recordset as a `function`, causing an `error`.

**Fix:**
This commit prevents an error during IRAS Audit File generation by correcting 
the `browse()` call to pass `line_account_ids` directly as its argument.

[1]:
https://github.com/odoo/enterprise/pull/72675

[2]:
https://github.com/odoo/enterprise/blob/444f120fbd4e7158b83c609ededf1b2598fc990f/l10n_sg_reports/models/iras_audit_file.py#L210

opw-5877947

[FIX] account_accountant: prevent commit cursor during import bank transactions

PR #106766

Enterprisesaas-18.4account_accountantMedium

This update resolves an issue that caused errors when importing bank transaction files with more than 80 lines. The fix prevents unnecessary database commits during the import process, ensuring stability and reliable operation for users importing large transaction sets. This improves the overall reliability of the bank statement import feature.

Original PR description

*= account_bank_statement_import_csv

An exception is currently triggered when a user attempts to import a bank
transaction file containing more than 80 transaction lines (see ref file [1]).

Steps to produce an error:
- Install `Accounting (accountant)` module
- Go to `Accounting` > Click on `Bank` > Click `Upload`
- Upload  ref file [1] and click `Test/Import` >>> Error occurs

Error: `psycopg2.errors.SerializationFailure: could not serialize access
due to concurrent update`

Error from 19.0: `InvalidSavepointSpecification : savepoint "ef05b579-df3f
-11f0-bc75-74563c5c983f" does not exist`

The issue occurs because, in `model.py` code line [2] creates a `savepoint`.
Before this `savepoint` is closed, code line [3] is triggered during the
creation of the bank statement line [4] and attempts to commit the
cursor using `self.env.cr.commit()`. Because a commit is executed while
the savepoint is still active, the system fails when trying to close the
previously created savepoint.

This commit fixes the issue by avoiding cursor commits during the import
process. The `import_file=True` flag is added to the context when
`_cron_try_auto_reconcile_statement_lines` is called from `execute_import`,
allowing the method to safely skip commit/rollback logic when
`import_file` is present in the context.

[1]: https://docs.google.com/spreadsheets/d/19hKnR8pGB27xkbEHgYYXIkBaPXV8RZZE/edit?usp=sharing&ouid=111844484867458262929&rtpof=true&sd=true
[2]: https://github.com/odoo/odoo/blob/11c469086cb4d08453a70cd7bd30d7391f635ae3/odoo/orm/models.py#L971-L973
[3]: https://github.com/odoo/enterprise/blob/2683b77cd6688877c308d0733bccfc5ad84530c1/account_accountant/models/account_bank_statement.py#L218
[4]: https://github.com/odoo/enterprise/blob/2683b77cd6688877c308d0733bccfc5ad84530c1/account_accountant/models/account_bank_statement.py#L1780

sentry-6974536471
opw-5359810

Forward-Port-Of: odoo/enterprise#102760

1. Create an invoice for $1,000 2. Create a credit note of $200 and apply it to the invoice. The invoice is marked 'partially paid.' The remaining due is $800. 3. Create a bank transaction of $700, reconcile with the invoice. 4. Edit the counterpart line, and click "fully paid". >>> Odoo does not consider the credit note and uses the full amount of $1,000 instead of the remaining due of $800 to reconcile. With the refactor of the bank rec, the way the amount is show is computed from econciled_lines_excluding_exchange_diff_ids in apply_amount.js which only takes into account the direct invoice and not the credit notes (in _compute_reconciled_lines_excluding_exchange_diff_ids it take the matched debit and matched credit so only the partial between the transaction and the move) opw-5485663 Forward-Port-Of: odoo/enterprise#105197

**Before this change** We were trying to set the `display_name` of one spreadsheet cell thread record to a set of more than one `display_name`s coming from a set of potentially multiple spreadsheets. **After this change** We use `record` instead of `self` when calling `_get_spreadsheet_record` so that it can only return a set of 1 `display_name`, preventing the crash that occurs when trying to set that field value. opw-5380947 Forward-Port-Of: odoo/enterprise#106593 Forward-Port-Of: odoo/enterprise#106230

Currently, an error occurs when generating the `IRAS Audit File` for a `Singapore` company **Steps to reproduce:** - Install the `l10n_sg_reports` and `accountant` modules (without demo data). - Create a new company with Singapore as the `country` and set `UEN` and `GST No.`, then switch to this company. - Navigate to Accounting > Reporting > Singapore > IRAS Audit File. - Fill in the required details and click `Generate`. **Error:** `TypeError: 'account.account' object is not callable` **Root cause:** After the refactoring in PR [1], the code at [2] mistakenly calls `browse()` without arguments and then attempts to call the returned recordset with `line_account_ids`. Since `browse()` already returns a recordset, this results in calling an `account.account` recordset as a `function`, causing an `error`. **Fix:** This commit prevents an error during IRAS Audit File generation by correcting the `browse()` call to pass `line_account_ids` directly as its argument. [1]: https://github.com/odoo/enterprise/pull/72675 [2]: https://github.com/odoo/enterprise/blob/444f120fbd4e7158b83c609ededf1b2598fc990f/l10n_sg_reports/models/iras_audit_file.py#L210 opw-5877947

*= account_bank_statement_import_csv An exception is currently triggered when a user attempts to import a bank transaction file containing more than 80 transaction lines (see ref file [1]). Steps to produce an error: - Install `Accounting (accountant)` module - Go to `Accounting` > Click on `Bank` > Click `Upload` - Upload ref file [1] and click `Test/Import` >>> Error occurs Error: `psycopg2.errors.SerializationFailure: could not serialize access due to concurrent update` Error from 19.0: `InvalidSavepointSpecification : savepoint "ef05b579-df3f -11f0-bc75-74563c5c983f" does not exist` The issue occurs because, in `model.py` code line [2] creates a `savepoint`. Before this `savepoint` is closed, code line [3] is triggered during the creation of the bank statement line [4] and attempts to commit the cursor using `self.env.cr.commit()`. Because a commit is executed while the savepoint is still active, the system fails when trying to close the previously created savepoint. This commit fixes the issue by avoiding cursor commits during the import process. The `import_file=True` flag is added to the context when `_cron_try_auto_reconcile_statement_lines` is called from `execute_import`, allowing the method to safely skip commit/rollback logic when `import_file` is present in the context. [1]: https://docs.google.com/spreadsheets/d/19hKnR8pGB27xkbEHgYYXIkBaPXV8RZZE/edit?usp=sharing&ouid=111844484867458262929&rtpof=true&sd=true [2]: https://github.com/odoo/odoo/blob/11c469086cb4d08453a70cd7bd30d7391f635ae3/odoo/orm/models.py#L971-L973 [3]: https://github.com/odoo/enterprise/blob/2683b77cd6688877c308d0733bccfc5ad84530c1/account_accountant/models/account_bank_statement.py#L218 [4]: https://github.com/odoo/enterprise/blob/2683b77cd6688877c308d0733bccfc5ad84530c1/account_accountant/models/account_bank_statement.py#L1780 sentry-6974536471 opw-5359810 Forward-Port-Of: odoo/enterprise#102760