Daily updates from Odoo
Saturday, August 23, 2025
5 changes · master
Resolved issues and error corrections
Batch payment reconciliation now handles negative bank statement lines, payments without accounting entries, and removal of reconciled payments more reliably. This helps ensure bills are correctly marked as paid and users see accurate available batch payment options during bank reconciliation.
Original PR description
[FIX] account_accountant: batch payment negative statement line When having a negative statement line that we want to reconcile with a batch payment composed with payments from bills. The different…
[FIX] account_accountant: batch payment negative statement line When having a negative statement line that we want to reconcile with a batch payment composed with payments from bills. The different line of the batch payment were not correctly split and so the bills were not put as paid. This was because of the use of the min that in case of negative amount was taking the amount of the entire batch and not the amount of the payment itself. task-4749334 [IMP] account_accountant_batch_payment: payment link and unreconcile When doing a batch payment without entries, the link to the payment was not present since there is no entry link to the aml that we create in the bank rec widget. This commit will add a new many2many field that will be a relation between the move line and the payment so that even when the batch payment has payment without entries we have a link between them This link will also be use for the unreconcile process, when removing a payment from a statement line, we put the payment has in_process and we unreconcile the batch task:4749334 [FIX] account_accountant, account_accountant_batch_payment: batch payment button When selecting or deleting a batch payment, the button was not updated correctly. For example, having just one batch and selecting it should make the button disappear for every statement line. Also, the amount of the batch was wrong since it was not the residual amount. To fix this, we move the logic of to get the different batch payment to the service and use that to update the available batch payment when selecting one or deleting one. task-4749334
After downloading the ADEME database in ESG, users are now taken directly to the emissions factors page instead of remaining on the database page. This makes the workflow clearer and adds logging to help monitor how long ADEME data retrieval takes.
Original PR description
Steps to reproduce: - go on configuration -> databases in ESG - download the ademe database What's happening: A success message is displayed, but the user stays on the database page. What's expected: The user is redirected towards the factor emissions page Additional fix: Small addition of an extra logger in the ADEME download process to allow checking the time needed to fetch the data from the ADEME website Task [link](https://www.odoo.com/odoo/project/967/tasks/4751902) task-4751902 Forward-Port-Of: odoo/enterprise#87058
Users can now clear the partner from a bank statement line after setting an account and editing the line. This fixes a small but visible accounting workflow issue, helping prevent incorrect partner details from remaining on transactions.
Original PR description
Before this commit when doing a set account on a bank statement line, and then editing this line to remove the partner was not working. This commit will allow the user to remove the partner when editing the line. task-4984569 Forward-Port-Of: odoo/enterprise#91422
Portal users can now group helpdesk tickets by customer without running into an access error. This keeps the ticket portal usable for invited customers while respecting existing customer data access limits.
Original PR description
**Issue:**
When logged in as a portal user, grouping tickets by 'Customer' raises an
access error, as portal user can only read partner records if:
```
[('id', 'child_of', user.commercial_partner_id.id)]
```
As defined in rule here:
https://github.com/odoo/odoo/blob/68a156030c366fbbf6b0841e1e2688a571355bf2/odoo/addons/base/security/base_security.xml#L22-L30
**Steps to reproduce:**
- Navigate a helpdesk team and set tickets to be visible to Invited portal
users and all internal users.
- Add a portal user as a follower to one of the team's tickets.
- Log in as the portal user, navigate to Tickets, and group by Customer.
An access error is raised
opw-4969684
Forward-Port-Of: odoo/enterprise#92985
Forward-Port-Of: odoo/enterprise#92603Belgian payroll exports now check required work entry codes before generating files, so users get a clear warning instead of a failed export. This helps payroll teams identify missing setup details earlier across supported payroll providers.
Original PR description
Before this commit no usererror was raised when the work entry type has no group s code defined which caused the export to fail. This commit adds a check at generation time for the work entry type to have a group s code defined task-4241431 Forward-Port-Of: odoo/enterprise#92595 Forward-Port-Of: odoo/enterprise#71454