Monday, February 3, 2025
7 changes · 18.0
Enhancements to existing features
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.
Original PR description
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.
Original PR description
--- 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.
Original PR description
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…
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-prThe 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.
Original PR description
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.
Original PR description
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.
Original PR description
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.
Original PR description
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