Odoo Changelog — 2026-06-09

Tuesday, June 9, 2026

3 changes · 19.0

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_ch_hr_payroll: Base activity rate on version instead of em…

PR #119659

Enterprise19.0l10n_ch_hr_payrollMEDIUM

This update fixes an issue where the activity rate used for payroll calculations was incorrectly tied to individual employees instead of the Odoo Enterprise version. This ensures consistent and accurate payroll processing across all users of the system, aligning with the correct version-based configuration. The change improves payroll accuracy and reduces potential discrepancies.

Original PR description

…ployee

Forward-Port-Of: odoo/enterprise#119658

#payroll#ch#hr#versioning

[FIX] account_accountant: credit limit warning should consider bank payments

PR #119774

Enterprise19.0accountantMEDIUM

This update fixes an issue where credit limit warnings were incorrectly triggered when customers received bank payments. The system now accurately considers outstanding bank payments in its calculations, ensuring warnings only appear when the credit limit is genuinely exceeded. This improves the accuracy of credit risk management.

Original PR description

Before this fix:
The credit limit warning calculation only considered credit notes but ignored outstanding bank payments 
when computing the partner's effective outstanding balance. For example, if a customer had a credit limit
of 1,000 and an invoice of 2,000 was created, then a bank payment of 1,500 was received, the warning 
would still incorrectly appear showing the customer exceeded their limit (2,000 > 1,000), even though the
actual outstanding amount was only 500.

After this fix:
The credit limit warning now properly includes outstanding bank payments in the calculation. Two cases 
are handled:
- Bank payments received but not yet matched to any invoice, these are identified by their open suspense
  account entry and deducted from the partner's outstanding exposure.
- Bank payments already matched to the invoice, the reconciled amount is read from the invoice's receivable
  line and deducted accordingly.

So with this fix, after a 1,500 bank payment, the system correctly recognises the outstanding amount as 500
and does not show a warning since it is within the 1,000 credit limit.

task-5427613

Forward-Port-Of: odoo/enterprise#119691
Forward-Port-Of: odoo/enterprise#118957

#finance#credit#payments

[FIX] account_reports: css perf on hover

PR #119242

Enterprise19.0accountMEDIUM

This update optimizes the performance of account reports when hovering over tables with many columns. Previously, hovering caused significant lag and browser slowdowns. This change reduces the number of style calculations, resulting in a smoother and faster user experience.

#performance#reporting

Before this fix: The credit limit warning calculation only considered credit notes but ignored outstanding bank payments when computing the partner's effective outstanding balance. For example, if a customer had a credit limit of 1,000 and an invoice of 2,000 was created, then a bank payment of 1,500 was received, the warning would still incorrectly appear showing the customer exceeded their limit (2,000 > 1,000), even though the actual outstanding amount was only 500. After this fix: The credit limit warning now properly includes outstanding bank payments in the calculation. Two cases are handled: - Bank payments received but not yet matched to any invoice, these are identified by their open suspense account entry and deducted from the partner's outstanding exposure. - Bank payments already matched to the invoice, the reconciled amount is read from the invoice's receivable line and deducted accordingly. So with this fix, after a 1,500 bank payment, the system correctly recognises the outstanding amount as 500 and does not show a warning since it is within the 1,000 credit limit. task-5427613 Forward-Port-Of: odoo/enterprise#119691 Forward-Port-Of: odoo/enterprise#118957