Daily updates from Odoo
Wednesday, September 10, 2025
4 changes · 18.0
Enhancements to existing features
Accounting now highlights invalid bank statements more clearly across dashboards, reconciliation, and statement forms. This helps finance teams spot issues earlier, avoid misleading balances, and protect transactions tied to valid statements from accidental deletion.
Original PR description
This commit brings more clarity on invalid statements. The reflected changes are : - Hiding Last Statement if its date is <= Lock Date - "Invalid Statement(s)" alert on the journal dashboard - Red balance amount and warning in the BankRecW when it contains invalid statements (clicking on the warning applies the filter) - Possibility to choose a statement when creating a transaction - Invalid statement warning in the statement creation form - Displays all warnings in the statement form view - When a file generate a statement, it is kept in its attachments - Prevent deletion of transactions if they belong to a valid statement - Empty statement are not taken into account for the dashboard Last Statement and the BankRecW balance task-4413473
Odoo can now communicate properly with IoT Boxes whose version is fixed to the latest stable Odoo release, even when that version is newer than the database. This helps keep IoT-connected workflows such as Belgian POS blackbox operations compatible during version transitions.
Original PR description
In odoo/odoo#221948, we make the IoT Box version "fixed" to the last stable odoo version. We then need to make databases send/accept requests from an higher IoT Box version. Forward-Port-Of: odoo/enterprise#91937
IoT boxes now receive a clear unauthorized error when the database cannot identify them during driver downloads. This replaces an empty response, making setup or connection issues easier to diagnose and resolve.
Original PR description
When an iot box tries to download drivers from the database, but the db doesn't have a record corresponding to the IoT Box, the IoT Box receives an empty string, making it hard to debug why it couldn't download handlers. We now raise an unauthorized error to make it clearer. Forward-Port-Of: odoo/enterprise#93813
Accounting screens now make invalid bank statements easier to spot and manage, with dashboard alerts, reconciliation warnings, and clearer statement form messages. The update also protects valid statement transactions from deletion and improves balance accuracy by excluding empty or locked statements where appropriate.
Original PR description
* accountant|bank_statement_import|reports This commit brings more clarity on invalid statements. The reflected changes are : - Hiding Last Statement if its date is <= Lock Date - "Invalid Statement(s)" alert on the journal dashboard - Red balance amount and warning in the BankRecW when it contains invalid statements (clicking on the warning applies the filter) - Possibility to choose a statement when creating a transaction - Invalid statement warning in the statement creation form - Displays all warnings in the statement form view - When a file generate a statement, it is kept in its attachments - Prevent deletion of transactions if they belong to a valid statement - Empty statement are not taken into account for the dashboard Last Statement and the BankRecW balance task-4413473