Daily updates from Odoo
Tuesday, August 26, 2025
8 changes · master
Enhancements to existing features
Payroll teams can now manage salary adjustments directly from an employee record in a dedicated tab. The new view shows key details such as type, dates, amount, payment progress, remaining periods, and status, making salary attachment follow-up clearer and more centralized.
Original PR description
- Add a tab Salary Adjustments in the employee - Add a list view with Type, Start, Note, Amount, Until and Status (optional hide, Amount Paid (computed from payslips lines), Periods Left, End Date) -Add a line opens a form view popup. One column for the inputs, the other is for the description Task: 4930543
Brazilian localization users can now set a CFOP code directly on operation types, giving businesses more control over how fiscal operations are classified. This value is used consistently in tax calculation and electronic invoicing, reducing manual corrections and helping align invoices with local tax requirements.
Original PR description
In this PR: - Added `l10n_br_cfop_code` field to operation types in form view for providing users with greater flexibility in selecting the appropriate CFOP. - Modified Avatax tax calculation service to send the custom CFOP value when configured, overriding automatic determination. - Updated invoice line CFOP computation logic to prioritize operation type override over standard Avatax response. - Modified EDI submission to preserve CFOP overrides by re-applying them when reusing stored Avatax tax calculation data. Task-4947957
French VAT report exports now combine tax declarations and related reimbursement requests into one submission. This reduces duplicate export steps and improves tracking of each included document through the external filing process.
Original PR description
This commit merges the tax export and tax reimbursements into a single export. New model `account_report_async_document` was created for handling document specific fields, like `deposit_uid`, `declaration_uid`, `state`, and the logs, as these fields are set from the response of the ASPone API. Before this commit, we couldn't merge multiple documents into a single export due to these fields. These fields were removed from the `account_report_async_export` models and moved to the `account_report_async_document`. Also, most methods in `account_report_async_document` are taken from `account_report_async_export` with minimal changes. The export creation was modified to account for handling multiple documents. task-4546529
Manufacturing planners can now open a suggestion pop-up in the Master Production Schedule to estimate and fill forecasted demand for a selected product. Suggestions use historical or actual demand across periods, helping teams plan faster and with less manual entry.
Original PR description
This PR enables the user to use a pop-up suggestion for the MPS. The tool suggests for the user the forecasted demand and fills it out in all periods for the chosen product in the MPS based on historical demand (last year, before last year or actual demand). If the user chooses to apply the suggestion for a certain period and not all the periods in MPS, the suggestion will be based only on last year. Task-4827486
The departure process now gives HR teams the option to remove a departing employee’s linked user account when archiving the employee. This helps streamline offboarding and reduces the chance of inactive staff retaining system access.
Original PR description
When you archive an employee and he has a user we need to have the ability to remove this user from the departure wizard Task: 4680081
Mexican accounting now uses dedicated accounts for credit notes, discounts, bonuses, returns, and certain POS re-invoicing entries instead of mixing them with regular sales. This helps businesses comply with local accounting rules and better see how much revenue was reduced by these operations, while allowing users to customize the default accounts.
Original PR description
[IMP] l10n_mx_*: provide different account for credit notes modules: l10n_mx_reports, l10n_mx_edi, l10n_mx_edi_pos When handling credit notes for accounting purposes it's not correct (or even legal…
[IMP] l10n_mx_*: provide different account for credit notes modules: l10n_mx_reports, l10n_mx_edi, l10n_mx_edi_pos When handling credit notes for accounting purposes it's not correct (or even legal in mexico) to use the same account for anything related to credit notes (discounts, bonuses or returns). Instead, all of these are accounted for in a different account that reduces the sales but also tell us how much of the sales were reduced by this account. This commit provide an account for these cases, and make it customizable for the user to set the account he wants (with a setting in the 'Default Accounting' section). Also, POS returns are now associated with this account. A second account is created to handle the "re-invoicing" concept: when a pos order is done and the session is closed, if the customer wants to self-invoice the system perform a reversal of the session and create 2 new invoices, 1 for the customer and 1 for all other orders from the original session. The new account is associated to the debit lines of the reversal (not vat), the credit lines of the customer invoice (not vat) Task-4576187
Users can again mark individual invoices or journal items so they do not trigger customer payment follow-ups. Follow-up reports, exports, and reminder emails now exclude those marked items, while entries without due dates are shown as due rather than overdue.
Original PR description
During the [rework of the follow-up report][1], we removed the "No Follow-Up" field from journal items, making it impossible to exclude individual journal items from triggering a follow-up. In the…
During the [rework of the follow-up report][1], we removed the "No Follow-Up" field from journal items, making it impossible to exclude individual journal items from triggering a follow-up. In the related community commit, we re-introduce a field for that, since it is a common requirement to be able to exclude individual items from the follow-up reports. In this commit we do the following: 1. Adapt the Follow-Up Report and Customer Statement variants of the Partner Ledger to add a toggle for the "No Follow-Up" field on each report line, that toggles the field on the corresponding journal item(s). 2. Prevent the follow-up status on the partner to change when all of the overdue journal items are marked as "No Follow-Up". 3. Make sure users can toggle the "No Follow-Up" setting on the invoice level when opening the "Overdue Invoices" view from the partner's "Accounting" tab. 4. Make sure all receivable/payable lines without a due date (either from a manual miscellaneous entry or a PoS entry) are put under the "Due" section is the Follow-Up Report instead of the "Overdue" section. Since there is no due date, they can't be overdue. [1]: https://github.com/odoo/odoo/commit/67dc71588751c9f115e09959d774686c2207a1f9 [task-4632300](https://www.odoo.com/odoo/project.task/4632300) Related to https://github.com/odoo/odoo/pull/203329
Audit report PDFs now include the styling needed to display edited content more consistently and professionally. Layouts, checklists, icons, tables, and common formatting options render more clearly, making reports easier to read and present.
Original PR description
This commit embeds the required Bootstrap assets into the HTML pages used for generating audit report PDFs. By leveraging Bootstrap's styles, the reports now have a cleaner, more professional appearance, and many of the blocks from the HTML editor are rendered with consistent, high-quality formatting. The column layout (`/column`), the checklists (`/checklist`), the icons (`/image`), etc will be displayed properly on the PDF. In addition to that, the tables will span over the entire page width making them more readable and some of the Bootstrap utility class will now also be supported (such as `bg-100`). Note: `wkhtmltopdf` does not support CSS variables, which prevents some Bootstrap rules from applying as intended. To address this, `bootstrap_review_report.scss` includes targeted workarounds to replace certain variable-based properties, ensuring the styles remain consistent in the PDF output. Task-4989809