This update introduces a 'Bonus' input type to Odoo's payroll system for the United States Regular Pay structure, allowing for additional income sources to be included in employee salaries. It also adds support for including employee expenses in the calculation, improving payroll flexibility and accuracy. This change enhances reporting and compensation management.

Add `Bonus` input type to `United States Regular Pay Salary Structure`.
Use `Expenses` and `Bonus` input types in the computation of payslips.

* Expenses:
    * Allows users to include expenses (added automatically from the Expenses app) into the salary calculation when using the Structure Type "United States: Regular Pay". The rule is  placed post taxes in the structure.

* Bonus: 
    * Add an Input type in "hr.payslip.input.type" called `Bonus`.
    * "Bonus" allows users to add an extra source of income for employees that have associated the "United States: Regular Pay" Structure type in their payslip. The rule is placed pre-taxes in the structure, it is a taxable amount.

task-4097635

This update streamlines the process of handling spreadsheet data, eliminating redundant encoding and decoding steps. This optimization reduces the time it takes to process spreadsheets, specifically improving performance by approximately 70ms. This change enhances the overall responsiveness of the Enterprise module.

This commit removes unnecessary base64 encoding and decoding operations when computing `spreadsheet_data` which contains the serialised json data.

Previously, the binary field `spreadsheet_binary_data` was base64-encoded (as is the case with all binary fields), meaning the file was read, encoded to base64, and assigned to `spreadsheet_binary_data`. To retrieve the serialized JSON, it then had to be decoded again.

By avoiding this redundant steps, with a spreadsheet file of 16.7Mb, we optimize the time spent in `_compute_spreadsheet_data`:

before: ~100ms
after: ~30ms

Task: 4256155

This update ensures the redirect button label is always present when a redirect URL is set in Odoo Enterprise. This simplifies the user interface by hiding the 'Close' button when a redirect isn't needed, improving clarity and usability. The change also updates the default redirect URL text from 'Open Link' to 'Close'.

This commits makes the redirect button label mandatory when there is a specified redirect URL. It also improves the hiding of the redirect label field when there is no redirect URL specified.

task-4174120

This update corrects a display issue where localization fields from the Uruguay localization (l10n_uy_edi) were incorrectly showing on invoices for other countries. This ensures invoices are presented accurately and consistently, regardless of the selected country setting within Odoo Enterprise. The fix improves the user experience and data integrity.

… other country's invoices

This update enhances the error messages displayed when registering the UY EDI proxy in Odoo. The change provides more detailed information to users, making it easier to troubleshoot issues and resolve registration problems. This improves the overall user experience and reduces potential delays caused by unclear error messages.

This update resolves issues where tests were failing due to reliance on demo data. The changes remove this dependency, making tests more reliable and faster to run, ultimately improving the stability of the Odoo Enterprise platform. Several modules were affected, including stock, accounting, and sales.

Forward-Port-Of: odoo/enterprise#72823

This update fixes a potential issue where payment data wasn't being accurately captured. By waiting for the completion of the payment initiation flow, the system now reliably records the transaction result, improving payment processing reliability. This ensures accurate financial records and a smoother payment experience for users.

We have to await for `_initiatePaymentFlow()` completion to ensure we correctly got the result of the transaction route.

This update automatically removes inactive WhatsApp chats after two weeks, regardless of whether they've been read. Previously, unread chats could accumulate and slow down the Discuss feature, limiting performance. This change prevents data overload and ensures a smoother user experience.

When a whatsapp conversation is inactive after 1 day, they are automatically unpinned as long as user has seen all the messages.

However, if the user never reads them, these whatsapp conversations keep being added to the pinned list of conversations, which adds more and more loads on Discuss fetched data over time. There is a practical limit of around 2000 pinned conversations, after which Discuss is very slow and hardly usable.

This is a known limitation with the current implementation.

Whatsapp conversations usually involved many operators for a given conversation, even though usually a single operator is actively communicating with the whatsapp customer. This means that all the inactive operators are keeping many unread whatsapp conversations, thus lots of whatsapp conversations stay unpinned.

This commit fixes the issue by forcing unpinning inactive whatsapp conversations after 2 weeks, regardless of whether current user has read the conversation or not.

Most of the time whatsapp conversations are short-lived conversations, therefore after 2 weeks this is almost guarantee that there's no point keeping this conversation pinned.

opw-4331007

This update fixes a bug where users could accidentally create multiple batches for the same payment, leading to validation errors. The change prevents adding payments to existing batches, ensuring batch validation processes run smoothly and reliably. This improves data accuracy and prevents export file generation issues.

## Issue:
When we create a batch from a payment by selecting it and clicking on "Create Batch", even if the payment is already in a batch or validated, it is possible to add it to a new batch, which can lead to issues when validating the batch.

## Steps to reproduce:

- Create a payment (posted but not sent) SEPA transfer.
- Select this payment and create batch payment.
- validate the batch
- Open payments list again, and select that same payment, then create a batch payment from the selection.
- a new batch payment will be created.
- If you open the batch payments list you'll notice 2 batches:
1. the original batch now has no payments inside it so the "re-generate Export File" button won't show up.
2. the second batch now contains the payment, but we can't re-generate the export file because it shows an error: The batch could not be validated, Some payments have already been sent.

Solution:
- before creating a batch with payments or adding payments to a batch we check if the payments we are adding are already in a batch.

OPW-3976563

Forward-Port-Of: odoo/enterprise#67315

This update corrects missing translations for the Modelo349 tax report specifically for Spanish businesses. Ensuring accurate reporting in Spanish is now a priority, improving compliance and user experience for our Spanish-speaking customers.

This commit fix some missing translations for the modelo349 tax report in spain.

no-task

This update corrects a configuration issue impacting payroll processing for Colorado and Washington states. The changes prioritize tax rules above post-tax deductions and standardize their categorization as 'Taxes,' ensuring accurate tax calculations and reporting. This improves the reliability of payroll data.

All the Colorado and Washington taxes rules should be above the Post Tax Deductions and should all be of the category Taxes.

Task: 4329645