Saturday, October 18, 2025
4 changes · 19.0
Enhancements to existing features
Tax rounding has been adjusted to match updated calculation rules, helping invoices produce more accurate totals. This reduces discrepancies in Mexican electronic invoicing and related tax handling across affected localizations.
Original PR description
Forward-Port-Of: odoo/enterprise#97443 Forward-Port-Of: odoo/enterprise#96809
CODA bank statement imports now include extra point-of-sale and SEPA reference details in the payment reference when available. This helps Odoo match imported payments with open items more accurately, reducing manual reconciliation work for Belgian accounting teams.
Original PR description
When importing a coda file, we deduce the payment ref depending on what is put in the coda. In the case of pos and sepa, we could add the reference in the payment ref to ease the process of auto reconcile. task-5065438 Forward-Port-Of: odoo/enterprise#94093
Accounting users now get clearer warnings when bank statements are invalid, including dashboard alerts, reconciliation warnings, and form-level messages. The update also avoids misleading balances by excluding locked or empty statements and protects valid statement transactions from accidental deletion.
Original PR description
* accountant|bank_statement_import 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 Forward-Port-Of: odoo/enterprise#97479 Forward-Port-Of: odoo/enterprise#92078
Accounting users now get clearer warnings when bank statements may be invalid, including dashboard alerts, reconciliation warnings, and statement form messages. The change also prevents risky deletion of transactions tied to valid statements and avoids showing outdated or empty statements in key balances, helping teams trust bank data and spot issues faster.
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 Forward-Port-Of: odoo/odoo#232081 Forward-Port-Of: odoo/odoo#222447