Odoo Changelog — 2026-08-26

Wednesday, August 26, 2026

2 changes · saas-19.3

Improvements(2)

Enhancements to existing features

[IMP] account,l10n_ma,l10n_in: default outstanding accounts on bank journals

Coresaas-19.3accountl10n_mal10n_inMedium

Bank journals now automatically receive the right outstanding payment accounts for Moroccan companies, and the shared account setup is also reused for India. This helps payments be reflected correctly in cash-basis tax reporting even when no bank synchronization or reconciliation transaction is available.

Original PR description

Reason:
- Moroccan companies usually use cash basis accounting. And the cash basis
  entries are only made when the invoices are reconciled with the bank
  transactions. However, in Morocco, there is no Moroccan bank available for
  bank synchronization.

Before this commit:
- We are not assigning the outstanding accounts on the bank journals by default.
- Which is causing the issues when the user creates a payment without an entry
  and without having any bank transactions to reconcile it with. Therefore, the
  tax report won't show the moves and taxes that occurred in the period.

After this commit:
- Introduced a method for updating the accounts on the payment method lines of
  the bank journal in the account module, as we need the same functionalities in
  l10n_in as well.
- For Moroccan localization, from now on, we are setting the outstanding accounts
  automatically on the bank journals.
- The payment accounts are applied by default during CoA loading and whenever
  payment method lines are recomputed, ensuring accounts remain consistent.

Task-6041119

Forward-Port-Of: odoo/odoo#254642

#bank journals#payments#tax reporting#cash basis

[IMP] l10n_be_pos_blackbox: log FDM errors in ir.logging

PR #129124

Enterprisesaas-19.3l10n_be_pos_blackboxMedium

Belgian point-of-sale systems now save errors from fiscal device checks and signatures in the backend, instead of relying on cashier browser logs. This makes it easier for support teams to diagnose blackbox problems with full context while automatically clearing old entries after 30 days.

Original PR description

The FDM is only reachable from the browser, so an error occurring during a signature left no trace in the backend: diagnosing a blackbox issue on a client database meant asking the cashier for their console logs.

Errors caught while signing or pinging the FDM are now stored as `ir.logging` entries, holding the whole context of the error, the data sent to the FDM and its answer. Logging is asynchronous and entries are dropped after 30 days when a session is closed

Forward-port of PR: https://github.com/odoo/enterprise/pull/129016

#Belgium#point_of_sale#fiscal_device#diagnostics

Reason: - Moroccan companies usually use cash basis accounting. And the cash basis entries are only made when the invoices are reconciled with the bank transactions. However, in Morocco, there is no Moroccan bank available for bank synchronization. Before this commit: - We are not assigning the outstanding accounts on the bank journals by default. - Which is causing the issues when the user creates a payment without an entry and without having any bank transactions to reconcile it with. Therefore, the tax report won't show the moves and taxes that occurred in the period. After this commit: - Introduced a method for updating the accounts on the payment method lines of the bank journal in the account module, as we need the same functionalities in l10n_in as well. - For Moroccan localization, from now on, we are setting the outstanding accounts automatically on the bank journals. - The payment accounts are applied by default during CoA loading and whenever payment method lines are recomputed, ensuring accounts remain consistent. Task-6041119 Forward-Port-Of: odoo/odoo#254642

The FDM is only reachable from the browser, so an error occurring during a signature left no trace in the backend: diagnosing a blackbox issue on a client database meant asking the cashier for their console logs. Errors caught while signing or pinging the FDM are now stored as `ir.logging` entries, holding the whole context of the error, the data sent to the FDM and its answer. Logging is asynchronous and entries are dropped after 30 days when a session is closed Forward-port of PR: https://github.com/odoo/enterprise/pull/129016