Payroll teams can now control the appearance of salary rule lines on printed payslips, including color, bold, italic, and underline styles. This makes payslip formatting easier to adjust directly from salary rules instead of relying on fixed hard-coded presentation.

In this commit, add styling effect on rule to render on printed payslip. Now you are able to change the rule color, bold, underline, italic styling effect dynamically on the rule. Previously, these styling effects had been hard coded.

task-3810365

Subscription lists now include clearer filters that separate automatic payments, manual payments, and automatic invoicing without payment. This helps users quickly understand how each subscription will be billed, while demo data now supports automatic invoice generation by scheduled jobs.

In this PR, added filters to categorize subscription based on payment_token and online_payment values.
- Filter for automatic payments when there is payment token.
- Filter for manual payment when there is no payment token and online payment is require.
- Filter for automatic invoicing without payment when no payment token and online payment is not require.
- rename "Failed Payments" filter to "In Error" for better user understanding
- make online payment false in demo data of subscription so automatic invoice will be generated by cron.

task-4295759

Payroll now prevents salary attachments from being deleted when they are already linked to a payslip. This helps avoid payroll record inconsistencies and gives users a clear error message explaining why the deletion cannot proceed.

This PR improves the deletion process for salary attachments linked to payslips. An error message is now displayed when attempting to delete a salary attachment associated with any payslip.

task-4007473

Point of Sale orders now automatically include related sub-record information when serialized across several localization and POS add-ons. This improves consistency and reduces manual handling for processes such as fiscal reporting, preparation displays, and rental stock flows.

*: l10n_cl_edi_pos, l10n_de_pos_res_cert, l10n_mx_edi_pos, pos_preparation_display, pos_sale_stock_renting

Automatically mapping sub records of pos_order to be serialized in the pos_order model.

This update cleans up the mail features after recent changes and fixes a small typo affecting mobile mail notification handling. It also adds groundwork to let some email notifications be delayed or handled in batches, which can improve reliability and efficiency for larger mail operations.

The helpdesk portal grouping option now uses the label "Sales Order Item" instead of "Sales Order". This makes the interface more accurate and avoids confusion, since the grouping already worked at the sales order item level and no behavior has changed.

Renamed the group by field from 'Sales Order' to 'Sales Order Item'. The behavior was not changed as it was already grouping by Sales Order Item.

task-4260389

This update streamlines the website signup form in Studio by removing actions that are not needed in that context. This should make the form editing experience clearer and reduce the chance of users selecting unsuitable options.

WIP

India payroll salary rules were simplified by removing duplicate entries for salary assignment and attachment. This reduces confusion in payroll configuration while keeping the net salary calculation unchanged.

Currently, the 'Assignment of Salary' and 'Attachment of Salary' rules are duplicated in the salary rules, and the NET formula is the same. I have removed these duplicate rules from the India payroll.

task-4383807

First-time Documents users now get guided onboarding to help them understand and start using the app more easily. This improves the initial experience by showing relevant guidance only when there is content to work with, reducing confusion during setup.

This commit adds on-boarding support for a user using documents for the first time.

Task-[3729929](https://www.odoo.com/web?debug=assets#id=3729929&cids=2&menu_id=6478&action=4043&model=project.task&view_type=form)

This update adds support for Spain's Bizkaia Batuz Modelo 140 reporting format, used by freelancers. It automatically identifies eligible companies by VAT format and adds the extra activity information needed for freelancer vendor bill reporting, helping businesses meet local tax filing requirements.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This update improves how Odoo handles manually adjusted tax and base amounts, making tax calculations easier to customize and more consistent. It also fixes an issue where point of sale cashiers could not print a proforma invoice after a failed Italian EDI document generation due to missing invoice line access rights.

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This change lets multiple own checks be recorded together in a single journal entry instead of creating separate split entries. This improves payment and invoice status accuracy and simplifies accounting workflows for businesses using Latin American check localization.

This PR introduces an improvement to the account and l10n_latam_check modules that allows for multiple liquidity lines (one per check) to be recorded in a single journal entry. Currently, a split journal entry is created for each liquidity line, which presents several disadvantages:
   - Incorrect computation of payment and invoice states
   - Simplified workflow: By using a single journal entry for all liquidity lines, the workflow is significantly simplified and accounting complexity is reduced.
   - First step towards a refactor: This improvement is a first step towards a broader refactor that will allow adapting the own check flow in payment registration without the need to create journal entries.

Changes made:
   - Enhanced _synchronize_to_moves() method: 
        - Allows for the creation and update of multiple liquidity lines within a single journal entry. 
        - Removes excess liquidity lines if _prepare_move_line_default_vals() returns fewer lines than currently exist. 
        - Account type-based counterparty identification: Replaces the previous position-based identification with an approach based on account types. 
        - The starting index for extra line values is now dynamic, determined by the number of liquidity lines

   - Removed _l10n_latam_check_split_move method:
       - This method is no longer necessary given the new implementation that supports multiple liquidity lines in a single journal entry.
   - Modified _prepare_move_line_default_vals() method: - Now returns one liquidity line for each registered own check, simplifying the generation of journal entries.
   - Preserved _l10n_latam_check_unlink_split_move() method:
       - Maintained for backward compatibility purposes, allowing payments containing split moves to be set to draft status.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:


opw-4236815

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The Mexico payroll module now includes the new official minimum daily wage value for 2025. This helps ensure payroll calculations use the correct wage reference for the new year.

There is a new value for the minimum daily wage for 2025.

Task: 4510726

The Mexican payroll module now includes the official UMA value for 2025. This keeps payroll-related calculations aligned with the latest required reference amount, helping businesses remain accurate and compliant.

New UMA value for 2025.

Task: 4465318

Financial reports can now group results using searchable fields even when those fields are not physically stored in the database. This gives businesses more flexibility for reporting scenarios such as consolidation, where custom related fields may be needed for analysis.

At the moment, the allowed groupbys for the standard report engines (account codes, domain, tax tags) need to be stored fields on `account.move.line`, or be defined in the custom handler.

We want to be able to group by any field that is searchable and has `_field_to_sql` implemented for it. For example, for consolidation, users might want to create a non-stored field related to `account_id.code` and group by it.

After this commit, groupbys can be any searchable field for which `_field_to_sql` is defined, regardless of whether it is stored or not.

task-4259552

The Documents app is easier to use on mobile devices, with clearer navigation, better action button display, and a more practical folder and file layout. Selecting records on mobile no longer causes an error, making the experience more reliable for users working from phones or tablets.

Changes:

1. On click chatter button, scrolldown to chatter so that we know what happens.
2. Don't show 'Folders' if a record is selected.
3. Properly show control action buttons.
4. Display folder/files into 2 columns, 3 columns if landscape on mobile.

Task-4380904