Saturday, December 13, 2025
4 changes · 19.0
Enhancements to existing features
This update streamlines the bank reconciliation process by automatically triggering reconciliation when records are created through the Kanban or List views, rather than relying solely on manual posting. It also centralizes the auto-processing logic, improving efficiency and reducing manual steps. This change enhances the user experience and simplifies bank statement integration.
Original PR description
this pr will do multiple things: - Remove the calls to the cron when posting the move, now adding through the kanban or list view will trigger the try_auto_reconcile from the create with the auto_statement_processing context key - Tries to unify the auto processing in the create (except in account online sync where we kept the logic since we need the start time to compute the cron limit) no task id
Resolved issues and error corrections
This update fixes a calculation error in financial reports for Arabic-speaking customers. The issue stemmed from a missing 'distinct' clause in a database query, which was incorrectly multiplying account balances. The fix ensures accurate reporting by prioritizing account tags and correctly determining operation types.
Original PR description
For ease of reuse, we use a CTE to find the operation type of the lines we care about. This works great however, a `DISTINCT ON (aml.id)` was missed on the CTE as if an account had multiple tags associated with it, it would end up appearing multiple times and multiplying the total balance by the number of tags, making the report wrong. We need to use a special CASE in the order by because we want to prioritize the right account tag on the account that way we can properly determine when to set the operation type to whatever it needs to be. The same issue appears in both the purchase and sales exports, so it has been fixed in both queries. opw-5406043
This update resolves an issue where exporting batch payments with mixed IBAN and Swedish payment methods (Bankgiro, Plusgiro, BBAN) was generating incorrect XML files. The team reverted a previous, flawed fix and is now focusing solely on generating the necessary zip file, correctly identifying payment types.
Original PR description
Here https://github.com/odoo/enterprise/pull/95463, we add the possibility to export
batch payments with mixed IBAN and Bankgiro/Plusgiro/BBAN payments, but this introduced
few bug in the xml format.
The reason is, we were using new custom logics and not the main one. The problem is
the custom logics is wrong, not the main one.
This commit remove most of the custom logics we added and use all the main one.
This has been done by:
1 - Reverting the original commit
2 - Adding only the zip file generation, passing a context key to know if we are
with bban or iban payments.
opw-5181340
Forward-Port-Of: odoo/enterprise#101917
Forward-Port-Of: odoo/enterprise#100014This update enhances the accuracy of tax calculations within the bank reconciliation widget. It prevents accidental tax line deletions, automatically creates tax lines when default taxes are added, and ensures correct tax recomputation across various scenarios, improving the reliability of financial reporting.
Original PR description
This commit will do multiple things: - Prevent users from deleting a tax line - Adding default taxes on an account will create a tax line for it - Removing a taxes from a line will recompute the taxes correctly - Removing and adding new taxes will recompute the taxes correctly - Removing a base line that has a tax linked to it will recompute the taxes correctly - Add a simple way for users to delete the tax directly from the ui without going to the edit line button task: 5081786 Forward-Port-Of: odoo/enterprise#101858 Forward-Port-Of: odoo/enterprise#94552