Odoo Changelog — 2026-07-18

Saturday, July 18, 2026

3 changes · 19.0

Improvements(1)

Enhancements to existing features

[IMP] account_online_payment: Add payer's data for payment initiation

Enterprise19.0account_online_paymentMEDIUM

Online payment initiation can now include the payer's bank account number and account holder name when required by providers such as Powens. This helps banks process payment requests that need payer identity details, reducing failed or blocked payment initiations.

Original PR description

With Powens, some banks requires the payer's bank information
such as bank account number and bank holder name.

This commit adds those informations to the odoofin route to be
sent to the payment providers.

task-6373634

Forward-Port-Of: odoo/enterprise#124088

#online payments#bank details#payment initiation

Bug Fixes(2)

Resolved issues and error corrections

[FIX] account_reports: don't keep inconsistent return states when updating the type's workflow

PR #124144

Enterprise19.0account_reportsMEDIUM

This fixes cases where tax returns could keep an old status after the allowed workflow steps changed, which could cause errors when viewing return lists. It helps upgrades run more reliably by automatically aligning existing returns with the updated workflow and ensuring return types have a defined workflow.

Original PR description

To reproduce the issue: 1) Create a company in Belgium 2) Instantiate its returns and review, submit and pay one of the VAT returns 3) Change the states_worklfow of the VAT return so that it only…

To reproduce the issue:

1) Create a company in Belgium
2) Instantiate its returns and review, submit and pay one of the VAT returns 3) Change the states_worklfow of the VAT return so that it only accepts "review" and "submit" stages, not "paid" anymore 4) Go to the list of returns, remove the TODO filter => traceback

The problem is here that the existing returns don't recompute their state when the workflow of the type is modified. In some cases, this is fine, but it others, it's annoying. In our example, the terminal state changed, so all the returns in that terminal stage should change their state to the new terminal one. "paid" is not an accepted value anymore, it should become "submitted".

Moreover, when the workflow is changed, the selection field actually containing the state must also change. As it is, it seems to work because "state" of account.return is stored, but the value it's based on (the workflow field) won't be consistent with it. It's not annoying now, but those inconsistencies could become a big source of trouble in the future (we know that from experience ... I'm looking at you, version 8 ! è-é).

This issue typically happens at upgrade. We had cases in FR and AE already. We solve that by a generic override of the write to sort things out when such change needs to happen. An upgrade PR will also be done to adapt the script so that we eventually solve the inconsistencies on dbs that have already migrated to 19.0.

#tax returns#workflow#upgrade#stability

[FIX] pos_self_order_iot: prep print on mobile self

PR #124652

Enterprise19.0pos_self_order_iotMEDIUM

Mobile self-ordering can now print preparation receipts when the configured preparation printer is connected through an IoT Box. This fixes a gap for restaurants using IoT printers, helping kitchen preparation orders print reliably from customer mobile orders.

Original PR description

IoT Boxes can be used to print preparation receipts from self ordering mobile, as they can use the WebSocket connection.

We now allow printing from self mobile if the preparation printer is an IoT one.

see odoo/odoo#276886
opw-6127663

#point-of-sale#self-ordering#iot#printing

With Powens, some banks requires the payer's bank information such as bank account number and bank holder name. This commit adds those informations to the odoofin route to be sent to the payment providers. task-6373634 Forward-Port-Of: odoo/enterprise#124088

To reproduce the issue: 1) Create a company in Belgium 2) Instantiate its returns and review, submit and pay one of the VAT returns 3) Change the states_worklfow of the VAT return so that it only accepts "review" and "submit" stages, not "paid" anymore 4) Go to the list of returns, remove the TODO filter => traceback The problem is here that the existing returns don't recompute their state when the workflow of the type is modified. In some cases, this is fine, but it others, it's annoying. In our example, the terminal state changed, so all the returns in that terminal stage should change their state to the new terminal one. "paid" is not an accepted value anymore, it should become "submitted". Moreover, when the workflow is changed, the selection field actually containing the state must also change. As it is, it seems to work because "state" of account.return is stored, but the value it's based on (the workflow field) won't be consistent with it. It's not annoying now, but those inconsistencies could become a big source of trouble in the future (we know that from experience ... I'm looking at you, version 8 ! è-é). This issue typically happens at upgrade. We had cases in FR and AE already. We solve that by a generic override of the write to sort things out when such change needs to happen. An upgrade PR will also be done to adapt the script so that we eventually solve the inconsistencies on dbs that have already migrated to 19.0.

IoT Boxes can be used to print preparation receipts from self ordering mobile, as they can use the WebSocket connection. We now allow printing from self mobile if the preparation printer is an IoT one. see odoo/odoo#276886 opw-6127663