Daily updates from Odoo
Thursday, July 2, 2026
27 changes
2 changes
Enhancements to existing features
This change removes technical e-reporting fields from the main invoice screen to reduce clutter for regular users. Important e-reporting status updates and blocking issues are still recorded in the invoice chatter, with a direct link to the related flow for easier follow-up.
Original PR description
E-reporting technical fields were displayed directly on invoices, adding noise for regular invoicing users. Hide the e-reporting status columns and technical block from the standard invoice views. Log the relevant e-reporting flow, status and blocking errors in the invoice chatter instead, with a link to the related flow. Also avoid reporting address validation errors on B2C invoices, as they are not required for Flux 10 e-reporting. Task-6273226 Forward-Port-Of: odoo/odoo#271865
This update strengthens the process of exporting the French Liasse Fiscale report by implementing crucial data checks. Specifically, it verifies that key information about the writer, debtor, and associated partners is complete and accurate before the report is generated. This improves data reliability and reduces potential errors in financial reporting.
Original PR description
while exporting liasse fiscale, no chceks were done before the export and there were no account returns checks before sending it, this commit add account return checks to the liasse fiscale: -writer and debtor have the necessary informations on their record -partners mentionned in the reports have the necessary fields completed on their records -for some line, we have to choose between some values task-6127270 Forward-Port-Of: odoo/enterprise#115812
1 change
Enhancements to existing features
This change removes technical e-reporting fields from the standard invoice screen to make invoicing simpler and less cluttered for users. The relevant status, flow, and blocking error information is now available in the invoice chatter, with a direct link to the related flow, and address validation warnings are no longer shown for B2C invoices when they are not needed.
Original PR description
E-reporting technical fields were displayed directly on invoices, adding noise for regular invoicing users. Hide the e-reporting status columns and technical block from the standard invoice views. Log the relevant e-reporting flow, status and blocking errors in the invoice chatter instead, with a link to the related flow. Also avoid reporting address validation errors on B2C invoices, as they are not required for Flux 10 e-reporting. Task-6273226 Forward-Port-Of: odoo/odoo#271865
3 changes
Enhancements to existing features
The Expense dashboard now follows the same filtering rules as the list view for the 'To Submit', 'Waiting Approval', and 'Waiting Reimbursement' states. This makes dashboard totals more accurate, for example allowing managers to see the amounts for the employees they supervise.
Original PR description
For the expense dashboard with the states 'To Submit', 'Waiting Approval' and 'Waiting Reimbursement', make these states compliants with the current filters of the list view. It means, for example, that a manager can see the total amounts of the people he manages. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#273302 Forward-Port-Of: odoo/odoo#270234
This change removes technical e-reporting fields from standard invoice screens so everyday users see a cleaner, less confusing form. The same information is still available in the invoice chatter, where related flow, status, and blocking errors are recorded with a direct link to the e-reporting process. It also avoids unnecessary address validation errors on B2C invoices when they are not needed for this reporting flow.
Original PR description
E-reporting technical fields were displayed directly on invoices, adding noise for regular invoicing users. Hide the e-reporting status columns and technical block from the standard invoice views. Log the relevant e-reporting flow, status and blocking errors in the invoice chatter instead, with a link to the related flow. Also avoid reporting address validation errors on B2C invoices, as they are not required for Flux 10 e-reporting. Task-6273226 Forward-Port-Of: odoo/odoo#271865
The log viewer has been improved to stay responsive with very large log files by showing only the most recent entries. It also now keeps new messages in view only when you are already at the bottom, and removes extra noise such as color-code artifacts and self-generated log request entries.
Original PR description
This commit makes the following pages to the log viewing page: - Only the last 10000 lines of logs are shown. This stops the page from freezing/performing badly when the logfile is very large. - When the view is at the bottom of the page, new logs are automatically scrolled into view. Otherwise the view stays still so the user can inspect the logs without them scrolling away. - The ANSI color codes are now stripped from the logs as they were just displayed as garbage characters. - The requests to fetch logs are now removed from the output, as otherwise you would be spammed with requests that only happen as a result of the logging page being open. task-6330996 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
2 changes
Enhancements to existing features
This change removes technical e-reporting details from the main invoice view to reduce clutter for regular users. The same information is still recorded in the invoice chatter, where users can follow the e-reporting flow, status, and any blocking issues through a link to the related record.
Original PR description
E-reporting technical fields were displayed directly on invoices, adding noise for regular invoicing users. Hide the e-reporting status columns and technical block from the standard invoice views. Log the relevant e-reporting flow, status and blocking errors in the invoice chatter instead, with a link to the related flow. Also avoid reporting address validation errors on B2C invoices, as they are not required for Flux 10 e-reporting. Task-6273226 Forward-Port-Of: odoo/odoo#271865
This update simplifies the website forum editor by removing unnecessary toolbar options and making the editing experience more consistent. It also fixes a crash in the table menu and prevents overlay styling issues, improving reliability for forum users and editors.
Original PR description
Description of the feature this PR addresses: - Remove unwanted toolbar features (heading, font_family, powerbuttons, undo/redo buttons) - Update toolbar styles in website_forum to keep them consistent - Fix table menu traceback by passing missing `localOverlayContainers` in `website_forum_wysiwyg` config task-6123698 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263326
2 changes
Enhancements to existing features
This change removes technical e-reporting fields from standard invoice views, making invoices easier to read for regular users. The key e-reporting details and blocking issues are now shown in the chatter with a link to the related flow, and unnecessary address validation warnings are no longer shown on B2C invoices.
Original PR description
E-reporting technical fields were displayed directly on invoices, adding noise for regular invoicing users. Hide the e-reporting status columns and technical block from the standard invoice views. Log the relevant e-reporting flow, status and blocking errors in the invoice chatter instead, with a link to the related flow. Also avoid reporting address validation errors on B2C invoices, as they are not required for Flux 10 e-reporting. Task-6273226 Forward-Port-Of: odoo/odoo#271865
Backorder creation when validating very large receipts is now much faster and more reliable. The change reduces unnecessary processing and avoids database memory issues, helping large warehouse operations finish without timeouts.
Original PR description
## The Problem Validating receipts with a large number of operations by creating a backorder was timing out due to $O(N*M)$ filtering inside `_get_qty_received_without_self`, where N is the number of…
## The Problem Validating receipts with a large number of operations by creating a backorder was timing out due to $O(N*M)$ filtering inside `_get_qty_received_without_self`, where N is the number of moves in the picking, and M is the number of moves being processed for valuation. This happened while computing price units for moves one by one: each move filtered all picking moves to find the ones with the same `product_id`. Another issue was a PostgreSQL `"memory exhausted"` error caused by generating a large number of OR'ed conditions, equal to the number of processed moves. ## The Solution The massive filtering was fixed by filtering moves of the `purchase_line` instead of the `picking`, which is typically associated with only a few moves. This is still correct as the loop just after already ignores moves that don't have the same `purchase_line_id` of `self` anyways. The PostgreSQL error was fixed by grouping moves by `location_dest_id` and generating one condition per location using an `in` clause, which is typically much smaller than generating one condition per move. ## Benchmark Benchmark on a customer database, validating a receipt with 10k+ operations by creating a backorder: ```text Time: timeout -> 6 min ``` OPW-6272667 Forward-Port-Of: odoo/odoo#272603 Forward-Port-Of: odoo/odoo#269350
14 changes
Enhancements to existing features
The button previously labeled “Revert” is now labeled “Mark as Unpaid” in payroll run screens. This makes the action easier to understand and better reflects what actually happens when a paid run is changed back to unpaid.
Original PR description
Problem: Reverting a pay run simply removes the "Paid" status to put back all payslips as "Done". This is not consistent with the payslips and does not reflect the behavior. Solution: Changed the label of the "Revert" action button to "Mark as Unpaid". Task-6352441
Peruvian electronic delivery slips now display a clearer title so they are easier to identify. They also include additional required transport information for both public and private shipments, helping ensure compliance with local delivery guide rules.
Original PR description
Peruvian transport guidelines specifies that the delivery guide should be explicitly and easily identifiable and should display mandatory transport information. This commit targets to achieve this: - Sent peruvian electronic delivery slips now explicit what they are on the doc title - added new mandatory transport data for public and private transports task-5866397
The DMFA form now includes a read-only XML file field so users can download the original XML directly from the record. The action buttons were also rearranged to make the declaration step easier to find and the preview action more clearly secondary.
Original PR description
Add a read-only "XML File" field on the DMFA form view, allowing the user to download the original XML. Also reorder the header buttons so "Post ONSS Declaration" is positioned first and the "Preview" button is positioned last. Task: 6333142
When users compare report lines against selected lines, the comparison is always shown as a percentage. This update hides the amount/percent selector in that case, so the report settings only show options that are actually useful. This makes the interface clearer and avoids confusion.
Original PR description
In [^1] support for comparison against user selected lines was added. This is always in percentages, as such, the "Comparison In" option that was added in [^2] is not useful as we would never set it to Amount. In this PR we hide "Comparison In" if the report line is selected. task-6322616 [^1]: odoo/enterprise#116721 [^2]: odoo/enterprise#116480 Forward-Port-Of: odoo/enterprise#121526
When a user manually sets allocated hours on a task, those values are now preserved even if the task dates change later. This prevents the system from overwriting user input and helps keep planning and time estimates consistent.
Original PR description
Before this commit, updating the planned start date or deadline recomputed the allocated hours automatically, even when the user had manually set a custom allocated hours value. In this commit ensures that once the allocated hours is manually updated by the user, the system marks the value as manually defined and prevents further automatic recomputation based on task scheduling changes.
The AI-related Discuss client action now uses a reactive signal for its action state instead of a plain property. This makes the interface update more reliably when the action changes, improving responsiveness and reducing the chance of stale behavior for users.
Original PR description
Pr community: https://github.com/odoo/odoo/pull/273286
A new “Daily Rates” smart button is added to rental pricelists, opening a calendar view of dated pricing rules. This makes it easier to review seasonal rates at a glance and create pricing periods by selecting dates directly on the calendar.
Original PR description
Seasonal rental prices are set through pricelist rules with validity dates. This commit adds a "Daily Rates" smart button on the pricelist that opens a month calendar of its dated rules, where selecting a period creates a single rule spanning it. task-4968689
The paid time off allocation process now automatically suggests postponed leave entries for employees who were absent during the relevant periods, reducing manual work during payroll runs. The interface also makes it easier to see which leaves are lost, postponed, or already allocated, improving clarity for payroll users.
Original PR description
Improve the paid time off allocation wizard by automatically suggesting postponed leaves for employees who were not working during the relevant periods and by enhancing the visibility of allocation information. - If an employee is absent in December, we prefill postpone N-1. - If an employee is absent the whole year, we prefill postpone N-2. - Improve the UI to better highlight lost leaves, postponed leaves, and already allocated leaves. - Remove the wizard form view, as the wizard is only used from the payrun flow and all form fields are hidden. Task: 6279404
The DMFA Occupation report no longer uses a fixed joint committee code. It now pulls the code from the payroll version’s own joint committee, which makes the reporting more accurate across different cases and reduces manual inconsistencies.
Original PR description
Prior to this commit, the JC code on DMFA Occupation was hardcoded to 200. This commit makes it dynamic by fetching the JC code from the version's joint committee. task-6352493
The Time & Attendance step is now hidden in Belgian payroll runs for all payroll structures except the Monthly Pay structure. This makes the process clearer and avoids showing a step that does not affect payslip calculations for those other payrun types.
Original PR description
Hide the Time & Attendance step in Belgian payruns for all payroll structures except the Monthly Pay structure, since attendance data does not affect payslip computation for the other structures. task: 6346664
This update enhances the payroll journal report by automatically filtering payruns, grouping data by salary rules and year, and displaying the salary rule name for clarity. It also includes a new employer cost measure and sorts the report by sequence number, improving data organization and reporting accuracy.
Original PR description
[IMP] hr_payroll: payroll journal improvement . Selected payrun is filtered by default in searchbar. . Default group_by for salary rule. . Code is added to display name of the salary rule for only payroll journal report. . The list is sorted by sequence number. task - 6311017
This update aligns Odoo with Belgian tax law, providing a withholding tax exemption (10% or 20%) for new businesses (start-ups and micro-enterprises) during their initial 48 months of operation. The changes update reporting and calculations to accurately reflect these exemptions, ensuring compliance with Belgian regulations. This improves the accuracy of tax reporting for businesses operating in Belgium.
Original PR description
Belgian law grants a withholding tax exemption (10% for start-ups, 20% for micro-enterprises) during their first 48 months of activity. This updates the settings and the 274.XX wizard to compute these exemptions, update the Summary and Excel reports, and enforce the 48-month limit. Task-6328760
This update adds 'Today' and 'Tomorrow' labels to the preparation display cards used in point-of-sale orders. This clarifies the expected timeframe for order fulfillment, improving communication and accuracy for staff and potentially customers.
Original PR description
Introduce "Today" and "Tomorrow" labels for preset times on the preparation display cards. Task-6279720
This update adjusts the location of the attachment list menu within the Odoo interface. This change enhances the user experience by streamlining access to attachments and improving overall usability. The update was implemented to address a minor visual inconsistency.
Original PR description
PR community: https://github.com/odoo/odoo/pull/273380
2 changes
Enhancements to existing features
Odoo can now use the Central Bank of Azerbaijan as a source for daily currency rates. This helps companies with multi-currency accounting and taxable transactions convert amounts into Azerbaijani manat (AZN) using the official rate for the transaction day.
Original PR description
This commit adds the Central Bank of Azerbaijan (CBA) as a supported service provider for automatic currency rate updates. Purpose: To ensure multi-currency accounting entries and taxable transactions are accurately translated into the national currency (AZN) using the official exchange rate defined by the CBA for the transaction day. Functionality: -Enables fetching official daily exchange rates directly from CBA via XML. -Automatically handles rates defined for different nominal quantities (e.g., rates quoted per 100 units instead of 1 unit). Related Community PR: https://github.com/odoo/odoo/pull/262471 Related Upgrade PR: https://github.com/odoo/upgrade/pull/10107 task-6112867
This update adds Russian translations to the Uzbekistan reporting documents. It helps businesses in Uzbekistan use these reports more easily, supporting adoption in a market where Russian is commonly used alongside Uzbek.
Original PR description
Uzbekistan's business environment requires Russian in addition to the official Uzbek language to ensure adoption. While localizations typically activate only statutory languages, Central Asian market realities justify this exception. task-6229114 -- I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr)
1 change
Enhancements to existing features
The shipping setting previously called “Batch Shipping” has been renamed to “Multicollo” in Sendcloud. This makes the wording match Sendcloud’s own terminology and reduces confusion for users configuring delivery options.
Original PR description
In order to avoid confusion for the customer, "Use Batch Shipping" was renamed to "Use Multicollo".This way it is consistent with the terminology used by Sendcloud. task-6048477