Thursday, September 10, 2026
66 changes · master
Enhancements to existing features
The employee form has been reorganized to make key payroll information easier to find and manage. Notes now stay attached to the employee overall rather than individual employee versions, and working time calculations better reflect reference calendars.
Original PR description
[IMP] hr: employee form UI This PR adds and adapts employee UI functionalities. - Notes are now relative to the employee and not on the single versions - the notebook page Payroll has been moved at its start task-5961555 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Channel invitation search now focuses on internal users instead of including large numbers of portal customers. This improves performance for the common case of inviting coworkers, while external participants can still join through invite links.
Original PR description
The exclusion of portal users from the channel invite search was dropped in [1], letting the search match millions of portal users instead of the couple thousand internal ones. This was done to let support agents invite a customer to a videoconf when a ticket needs quick back-and-forth, but that is a corner case compared to the common case of inviting colleagues. Slowing down the common case for everyone to serve a corner case isn't worth it, and external people can still be reached through the invite link. [1]: https://github.com/odoo/odoo/pull/250988 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
Poll start and end notifications will now show a fallback message instead of appearing blank. This makes poll activity easier for users to understand when they receive notifications.
Original PR description
Before this commit, the notification of a start/end poll message was empty. We already have a fallback for empty body and attachments, we can do the same for polls. 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
Saudi e-invoices with an uncertain submission status are now resent exactly as originally signed instead of being recreated. This prevents duplicate or conflicting invoice versions in the official ZATCA chain and keeps retry actions focused on the latest submission attempt.
Original PR description
ZATCA Phase 2 E-invoicing requires each invoice to carry an Invoice Counter Value (ICV) and a Previous Invoice Hash (PIH), forming a cryptographic chain of documents per device (journal). When ZATCA…
ZATCA Phase 2 E-invoicing requires each invoice to carry an Invoice Counter Value (ICV) and a Previous Invoice Hash (PIH), forming a cryptographic chain of documents per device (journal). When ZATCA fails to respond to a submission (timeout or other exception), the document is marked unknown since its actual outcome on ZATCA's side can't be confirmed. Retrying such a document previously regenerated the XML from scratch, producing a new UUID and signature. If ZATCA had in fact processed the original submission, this risked creating a second, divergent version of the same invoice within the chain. This commit stores the signed XML at the moment a document goes unknown and reuses that exact file on every subsequent retry, rather than regenerating it: - A document that returns unknown saves its submitted, signed XML as an attachment - Retrying an unknown document resends that same attachment unchanged, so retries are idempotent and cannot fork the chain - Documents previously stuck in unknown state without a stored attachment are backfilled via a migration, bringing existing data in line with the new behavior - The now-unused chain-blocking mechanism and its supporting field are removed, since a document's own stored attachment is sufficient to guarantee a safe, consistent retry - Only the latest log per document is now actionable (Retry/Process); previously every historical log could show these buttons, letting users retry outdated attempts instead of the current one. Related PR: https://github.com/odoo/upgrade/pull/10887 taskID-5359557
Sales margin tracking will now be installed automatically with the standard sales management flow, instead of requiring users to turn it on in settings. This simplifies setup and makes margin information consistently available for sales teams.
Original PR description
Margins were gated behind a settings toggle even though sale_margin only depends on sale_management, which every quotation flow already requires. Mark sale_margin auto_install so it always installs alongside sale_management, and dropping the "Margins" setting. task-6255022 Related pr: Documentation PR:https://github.com/odoo/documentation/pull/20022 Upgrade PR:https://github.com/odoo/upgrade/pull/11293 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website builders get a broader set of decorative shapes, including blurry, line, geometric, grid, and travel map styles. The update also adds ready-made text-and-chart sections to help create richer pages for the new Eclipse theme more quickly.
Original PR description
This PR introduces: - 4 blurry shapes (to be used in new `theme_eclipse`) - 8 lines shapes inside a new section - 5 geometric shapes inside a new section - 2 grid shapes - 2 travel shapes (topographic maps) This PR also introduces `s_text_chart` and `s_chart_text` snippets to be used in new `theme_eclipse`. D-T: https://github.com/odoo/design-themes/pull/1249 task-6482496 | Examples | |--------| | <img width="100%" height="auto" alt="Home-My-Website-09-02-2026_11_15_AM" src="https://github.com/user-attachments/assets/4feab930-0953-4906-91f1-957dfb59da00" /> | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The employee form no longer includes the chat button, and the related code has been removed from the HR module because it is no longer used there. This keeps HR screens cleaner and reduces unused code, while any remaining use is expected to live in the module that still needs it.
Original PR description
The hr_employee_chat widget (component + template + styling) is no longer used in hr since the previous commit removed its only usage on the employee form. It is now only used in sale_timesheet_enterprise (edit_billable_time_target_views.xml), so move it there instead of keeping dead code in hr. task-id 6563733
The timesheet timer now uses the last task or ticket a user viewed instead of relying on recent timesheet defaults, making it more likely to start with relevant context. Users can also copy project and task details from an existing timesheet into the timer, then immediately fill in the description, reducing repetitive entry.
Original PR description
_* = helpdesk_timesheet **- Remove the default project/task values based on the user's most recent timesheets.** - Prefill the timer with the last task visited by the user, even if they are no longer working on it. - store the last visited task/ticket in local storage from the status widget to use it for timer prefill. **- Copy timesheet:** - Add a copy button below the duration of existing timesheets. - Display the copy icon in muted text and turn it green on hover. - Always display the copy button in the mobile view. - Clicking the copy icon sets the corresponding project and task in the timer. - Automatically focus the description field after copying the timesheet. task-6487738
Updates Panama localization reference data to prepare for future electronic invoicing and legal reporting needs. This helps businesses operating in Panama align their accounting setup with upcoming compliance requirements.
Original PR description
Purpose: Update the data in l10n_pa for future implementations of electronic invoicing and legal reporting in Panama. task-6382219 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Employee and payroll forms have been adjusted so wage details, notes, working hours, joint committees, and worked-code lists appear in a clearer and more consistent way. This should reduce confusion for payroll teams managing Belgian employee records and payslip-related information.
Original PR description
This PR adds and adapts base and Belgian payroll UI functionalities. As for base payroll: - Depending on the selected wage_type (monthly or hourly) the wage and hourly_wage appear accordingly - Notes are now relative to the employee and not on the single versions As for L10N_BE payroll: - Reference Working Hours is now depending on the resource.calendar and not on a hr.version - Formatted how Joint Committees are displayed in dropdown menus - Formatted Worked Code list view task-5136311
Custom fields added to Planning worksheets with Odoo Studio now show correctly in customer previews and Field Service PDF reports. The update also respects hidden-field rules and preserves side-by-side layouts, so reports better match the worksheet configured by the business.
Original PR description
Previously, - Custom fields added to a worksheet page in Planning (via Odoo Studio) were failing to display in both the **Customer Preview** and the **Field Service PDF report** From now, - Dynamic Field Extraction: Now we actively **scans** the worksheet page for any additional fields added by Studio. - Visibility Evaluation: Now we properly evaluates invisible conditions before adding fields, ensuring hidden elements remain hidden on the report. - Layout Support: Fields are now appended to formatted_properties using a `studio_columns` type. This adds full support for column views if a user arranges fields side-by-side in Studio, the report will faithfully recreate that multi-column layout. - Other Module Compatibility: These changes are seamlessly integrated, leaving the core worksheet functionality and rendering completely **unchanged** for other modules and standard users. Task - 6455812
Businesses can now manage one asset under multiple depreciation rules at the same time, such as statutory and internal book accounting. This improves reporting accuracy and reduces duplicate asset records when different ledgers require different depreciation treatment.
Original PR description
* = account_reports,l10n_{in_asset,ph_reports_asset,ro_saft} This commit enables a single asset to carry multiple depreciation configurations (variants), each targeting a different ledger. This…
* = account_reports,l10n_{in_asset,ph_reports_asset,ro_saft}
This commit enables a single asset to carry multiple depreciation
configurations (variants), each targeting a different ledger. This allows
the same asset to be depreciated under multiple accounting regimes (e.g.,
statutory vs. book) simultaneously.
Changes:
- Introduces `account.asset.variant` model: moves most depreciation
lifecycle logic (board computation, disposal, sale, modification)
from `account.asset` onto variants. A single asset owns multiple
variants, each with its own model, journal, accounts, and state.
- Renames `account.move.asset_id` to `asset_variant_id`: all depreciation
moves now link to a variant instead of an asset directly. Downstream
integrations (fleet, l10n_*, reports) are updated accordingly.
- Adds ledger account fields to `account.depreciation.model`
(`ledger_depreciation_account_id`, `ledger_expense_account_id`,
`ledger_recovery_account_id`) so a depreciation model used for a
ledger variant carries its own account mapping.
- Adds `ledger_depreciation_model_ids` on `account.account` so default
ledger depreciation models can be configured per account, enabling
automatic multi-variant asset creation from bills.
- Adds UI: asset variant list view, depreciation ledger list/form
views, ledger-specific sections on the depreciation model form,
conditional button visibility based on variant state, and a wizard
(`depreciation.ledger.wizard`) to attach a ledger-based depreciation
model to an existing asset.
- Adapts the account asset report SQL to operate at variant level:
restructures CTEs to group values by variant, avoids double-counting
asset cost values across variants, and adjusts disposal/recovery
logic for the multi-variant scenario.
- Updates `l10n_ro_saft` SA-FT asset queries and `l10n_in_asset`
computation overrides to work with `account.asset.variant`.
- Adapts existing tests and adds test file (`test_asset_ledger.py`)
covering ledger variant creation, board generation, disposal, and
report output.
task-5961309Users can now undo shifts scheduled from the planning side panel, making it easier to return to the previous schedule when shifts are split or placed across multiple dates. The planning dialog behavior is also shared more consistently between Planning and Sales Planning, improving reliability when several shifts are scheduled at once.
Original PR description
As some shifts could be split and scheduled at different dates when using the side panel drag & drop feature (happens if there are some unavailabilities in the working schedule or other planned…
As some shifts could be split and scheduled at different dates when using the side panel drag & drop feature (happens if there are some unavailabilities in the working schedule or other planned shifts at that time); In some situations, it can be tedious for the user to undo the scheduling and return to the initial state. To do that, the user would need to manually unschedule the shifts that were planned, set back the allocated hours, etc To prevent this, we introduce an "Undo" notification button that appears after scheduling a shift (i.e., event) from the side panel, allowing you to easily return to the initial state (as we do in most planning actions, like rescheduling or splitting a shift in two). We also moved the logic of the "Plan" dialog that shows up when clicking on an empty cell from sale_planning to the planning module. Thus, we adapted the undo logic to work in batch to handle multiple shifts being scheduled at once. Follow-up of this PR: https://github.com/odoo/enterprise/pull/112009 task-6303828
Belgian payroll now handles mobility budget settlements, Pillar 2 and Pillar 3 payments, year-end balances, and termination calculations more accurately. The update also adds warnings to help payroll teams spot inconsistent payments, invalid budget limits, or company car conflicts before declarations and payslips are finalized.
Original PR description
Rework the mobility budget logic according to Partena requirements. * Settle the remaining mobility budget in December or on the employee's final monthly payslip instead of in the anniversary month.…
Rework the mobility budget logic according to Partena requirements. * Settle the remaining mobility budget in December or on the employee's final monthly payslip instead of in the anniversary month. * Support Pillar 2 payments through payslip inputs even when the Expenses module is not installed. * Add dedicated salary rules for mobility budget amounts already paid, remaining balances, and Pillar 3 payments, including payments related to the previous year. * Include the mobility budget amount in termination fee computations. * Compute the yearly mobility budget as a prorated amount based on all employee versions within the calendar year, where required for payroll calculations and the 281.10 declaration. * Adapt the DMFA mobility budget declaration to report the applicable yearly mobility budget for Pillar 3 payments, including payments related to the previous year. * Add warnings when Pillar 2 or Pillar 3 payments are inconsistent with the remaining mobility budget. * Add warnings when the mobility budget falls outside the configured boundaries or exceeds 20% of the yearly wage. * Add a dashboard warning for employees with a mobility budget and a company car emitting CO₂. * Move the computation of the default mobility budget amount from l10n_be_hr_contract_salary to l10n_be_hr_payroll, so that the mobility budget amount is available without requiring the salary configurator module to be installed. Related upgrade PR:https://github.com/odoo/upgrade/pull/11241 Task: 6263962
Positive correction payslips now defer intellectual property payment increases and their withholding tax to the next monthly payroll. This keeps all intellectual property payments for a month grouped into a single 273.S declaration, reducing reporting inconsistencies and administrative follow-up.
Original PR description
Defer the intellectual-property increase introduced by a correction payslip (the amount and its movable withholding tax) to the next monthly payrun, so that all IP paid in a given month falls into a single 273.S declaration. task-6499510
Belgian payroll now calculates certain withholding tax exemptions directly on payslips, including exemptions for eligible R&D employees. This improves accuracy when exemptions depend on totals across multiple payslips and supports required Belgian reporting.
Original PR description
Some withholding tax exemptions depend on the result of other payslips tax exemptions. Tax exemptions need to be implemented as payslip rules. In order to have the result of other payslip's rules, we need to setup up "rounds of computation". For example: payslip1, payslip2 and payslip3 need to be computed with rules 1, 2 and 3 for each payslip. Rule 3 needs the result of rule 1 and 2 for all payslips. - rule 1: round_of_computation = not_defined -> default = 0 - rule 2: round_of_computation = 0 - rule 3: round_of_computation = 1 Computation will happen in the following order 1) payslip1: rule 1 and rule 2 2) payslip2: rule 1 and rule 2 3) payslip3: rule 1 and rule 2 4) payslip1: rule 3 5) payslip2: rule 3 6) payslip3: rule 3 The final goal of this task is to introduce the computation of withholding tax for R&D employees (bachelor, master and doctor/civil_engineers). task-6201363
Gantt users can now select whole rows or columns directly from their headers when creating multiple items. This makes bulk planning faster and more intuitive, with keyboard shortcuts to extend or adjust selections.
Original PR description
Before this commit, users were unable to select entire rows or columns by clicking on the Gantt chart headers. Selection was only possible by dragging or clicking individual cells inside the grid. We now introduce header-based multi-selection when multi-create mode is enabled: - Clicking a column or row header selects all cells across that column or row. - Shift+click allows extending the range of selected rows or columns from the last selected header anchor. - Ctrl+click allows toggling individual headers, as well as unfolding and selecting folded columns. task-6456200
Financial report expressions can now define selectable options with translatable labels. This lays the groundwork for more flexible reporting choices while ensuring option text can be properly localized for different users.
Original PR description
In order to allow report expressions to have selection options, we add a new field to the ``account.report.expression`` model that will store the selection options as an HTML string, using the following format:
```xml
<select>
<option value="option1">Option 1</option>
<option value="option2">Option 2</option>
<option value="option3">Option 3</option>
</select>
```
We use this format to cleanly extract the option labels for translation using ``html_translate``.
Further handling of these options is done in the related enterprise commit.
[task-6159824](https://www.odoo.com/odoo/project.task/6159824)This update improves responsiveness when using Mail-related dropdown menus in the Odoo navigation bar. It removes a slow page-style check that could cause visible lag, making menu interactions much smoother for users.
Original PR description
This :has() was itself a regression: c9466bb8f8d6 ("unify discuss menus") deleted messaging_menu_patch.scss, which had this exact rule scoped instead as ".o_web_client.o-mail-discuss-systray-menu-open .o_main_navbar" behind a plain media query - the class already toggled by useDiscussSystray()'s body-class effect for a sibling case
Step to reproduce:
1. On runbot, open "Planning" app
2. Go to "Kanban view" (https://<instance>/odoo/employees-planning?view_type=kanban&debug=assets)
3. Open the navbar menu, open a dropdown and "quick" hover the menus "Schedule" > "Maps" > "Planning" > "Reporting" > "Configuration" => You can see the "lag"
On my laptop a come from ~2098ms to ~26.44ms (-98.7%)
task-6465302
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe employee form no longer includes the chat button, and the related code has been moved out of HR because it is only needed by timesheet billing workflows. This keeps the HR module simpler while preserving the functionality where it is still used.
Original PR description
The hr_employee_chat widget (component + template + styling) is no longer used in hr since the previous commit removed its only usage on the employee form. It is now only used in sale_timesheet_enterprise (edit_billable_time_target_views.xml), so move it there instead of keeping dead code in hr. task-id 6563733
Manufacturing administrators can now reset canceled manufacturing orders to draft or move completed ones back into progress, making it easier to correct or continue production records. Canceled orders now consistently cancel all related work orders, and serial or lot numbers are reused when an order is restarted to avoid cluttering inventory records.
Original PR description
This PR allows Manufacturing Admin user to `Reset to Draft` an MO if it's canceled or `Set to In Progress` if validated. This PR also changes the behavior of canceling an MO to cancel all workorders regardless of their state. In case of producing a product tracked by serial number or lot: if the MO already generated/assigned lot_ids, then Mo is validated/canceled, then reset, then confirmed/produced again, it uses the same old lot_ids which keeps the inventory from being crowded with unused serial numbers. Related PR: https://github.com/odoo/enterprise/pull/124863 Task-6348605
Spreadsheet and accounting spreadsheet formulas now handle evaluation errors in the calculation step instead of behind-the-scenes data lookups. This should make user-facing spreadsheet errors clearer and more consistent without changing day-to-day workflows.
Original PR description
Before this commit The evaluation error was thrown in the getters of the plugin. It should be thrown in the compute of the function instead. Task: 6306250 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
Odoo’s shared icon resources are now centralized so multiple apps can reuse the same icon data and search behavior. The icon font generation process is also stored in the codebase, making icons easier to maintain and reducing duplicated frontend mappings.
Original PR description
[IMP] web, html_editor, mail: move icon metadata in `web` --- __Before commit__ All the icon logic is in `web` except for `ms_icons.py`, which contains icon codepoints and search terms. It was…
[IMP] web, html_editor, mail: move icon metadata in `web` --- __Before commit__ All the icon logic is in `web` except for `ms_icons.py`, which contains icon codepoints and search terms. It was originally put in `html_editor` because it was mainly used by the Media Dialog. However, `web_studio` also has an icon selector, `ai_website` uses it inside a model and reimplements a search method, and the codepoints are used by `mail`. __After commit__ - `ms_icons.py` is moved to the root of `web` since it can be used by controllers and models across the entire codebase. - A search method is added to it so `ai_website` doesn't have to write its own. [IMP] web, html_editor, mail: use ligature for `odoo_ui_icons` --- __Before this commit__ `odoo_ui_icons` was generated on fontello.com without ligatures. This meant that a CSS file had to map every icon name to a custom Unicode character. __After this commit__ The Fontello config is stored in the repository. Based on this config, `generate_icons.py` generates a WOFF2 font that contains icon ligatures and a WOFF1 font, which is only used in the backend and includes both ligatures and codepoints. We can therefore remove the frontend CSS mapping, centralize all icon metadata in `icons.py`, and simplify the code exclusive to Odoo UI icons.
This update improves how Odoo records inventory costs, cost of goods sold, and accruals for purchases and sales. It gives finance teams more accurate stock valuation and a clearer view of goods invoiced but not yet delivered or received.
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
Quotation templates now include a Catalog button so users can browse products and add quantities directly, instead of adding items one by one through a field. This makes building reusable sales templates quicker and more consistent with the sales order experience, with related catalog performance improvements when prices are not shown.
Original PR description
Before this commit, adding a product to a quotation template line required creating a line and picking the product from a many2one field, one product at a time. With this commit, a "Catalog" button is added next to "Add a product" in the template lines list, reusing the same product catalog kanban view already available on sale orders. Products can be browsed and added, with their quantity set directly from the catalog. task-6326792
GSTR-1 filing error messages now show the specific HSN codes responsible for failures, along with related error codes and messages. This helps users identify and correct filing issues directly from the chatter without checking separate status files, while also avoiding unhelpful empty error entries.
Original PR description
When GSTR-1 filing fails due to HSN-related errors, the error logs posted in the chatter now include the HSN codes that caused the errors, along with the corresponding error codes and error messages. Previously, the chatter only displayed the error codes and error messages, to identify the HSN codes responsible for the failure, users had to review the generated status.json file separately. By including the HSN codes responsible for errors directly in the chatter, users can quickly identify the source of the issue and resolve it more efficiently. earlier if error code and error message both were missing system still printed False-False now it will be skipped. Also made some improvements in invoices fetching and generating clickable link. task-6214114
Manufacturing orders can now be cancelled without being blocked by related work order quality checks, even when those work orders are in different states. This supports smoother recovery workflows, including future options to reset manufacturing orders back to draft or in progress.
Original PR description
This PR basically allows the deletion of checks on workorders when the MO is canceled regardless of the state of the workorders. This PR is a small part of a feature allowing the user to reset an MO to draft/in progress. Related PR: https://github.com/odoo/odoo/pull/277276 Task-6348605
HR managers in Belgian payroll now receive an activity when an employee has been on sick leave for eight weeks or more. This helps ensure timely contact with occupational medicine services to assess work capacity and support compliance with extended sick leave follow-up processes.
Original PR description
In order to inform the payroll officers to contact the occupational medicine facility to check for the sick employees capacity to their work efficiently in case of an extended sick leave, a new activity will be assigned to the employee HR manager in case any of the employees has a sick leave that has been ongoing for 8 or more weeks. Task: 6126847
Belgian payroll now stores cafeteria plan salary sacrifice and employee net contribution amounts for use in payroll. This prepares payroll processing for cafeteria plan benefits, including deductions that can reduce employer yearly cost when employees cover more of the benefit cost.
Original PR description
This PR is a first step into the cafeteria plan implementation. It creates some properties on the version: - net_contribution: which is an amount taken from the net to cover exceeding benefits costs.…
This PR is a first step into the cafeteria plan implementation. It creates some properties on the version: - net_contribution: which is an amount taken from the net to cover exceeding benefits costs. - salary sacrifice: which represents the amount that the employee willingly sacrifices from his.her gross. Both are used in the payroll process. Salary sacrifice is used because ONSS is due on that. Net contribution is a simple deduction from the net total. Those values are just stored but not computed. They're supposed to be filled after the salary config flow is complete. Updating the salary sacrifice does not trigger any recomputation. The net contribution though has an impact on the yearly_cost : if more of the benefit cost is covered by the employee, it means that the employer cost is lowered. Updating the net contribution has an impact on the yearly_cost, just as updating benefits on the employee's form has an impact on the yearly_cost (in that case, an increase). task-6313710
Spreadsheet survey formulas now handle user-facing errors at the calculation step rather than while retrieving data. This makes error messages appear in the right context and improves reliability without changing the visible survey spreadsheet features.
Original PR description
EvaluationError should be thrown in the compute of the functions instead of the getters. Task: 6306250
Products and lot information selected through the Add Products catalog are now also reflected on the related Equipment page. This helps field service teams keep equipment records aligned with the products used during service work.
Original PR description
Make the lots added in the `Add Products` catalog be added to the `Equipment` page --- task-6397373
The spreadsheet side panels have been visually refreshed to look more polished, consistent, and aligned with Odoo's design style. This improves the user experience when configuring or reviewing spreadsheet options without changing the underlying business workflows.
Original PR description
Go through all the side panels and update their style to be prettier and more modern (and more odoo like). Task: [4080127](https://www.odoo.com/web#id=4080127&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Cash on Delivery and Pay on Site orders now remain marked as unpaid until money is actually collected, while still confirming the order and showing customers a successful checkout. Delivery staff are prompted to collect the due amount during delivery, and Point of Sale can later settle these orders correctly even after goods have been delivered.
Original PR description
The calendar side panel now lets users search and select attendees with clear attendee tags instead of managing a checkbox list. Users can also show or hide their own calendar separately, and selected filters are reused as default attendees when creating new events.
Original PR description
Purpose ======= Improve the calendar side panel attendees filtering. Specification ============= Changing the regular attendee filters display consisting of checkboxes into an attendee records selector with a search input and attendee tags. Each attendee tag matching the color of the related attendee calendar events. As those are filters, they'll be reset after each reload. Also adding a "My calendar" filters so that users can choose between showing/hiding their events. When creating a calendar event, the selected attendee filters will be used as default attendees for the event. The current user will also be added in the default attendees if the "My calendar" filter is checked. Task-5946597 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Calendar views can now place extra fields before or after the popover section without triggering a validation error. This gives implementers more flexibility when configuring calendars and helps avoid unnecessary setup failures.
Original PR description
Before this PR, the validator of the calendar view does not allow a field after the popover element inside the calendar tag; a validator error occurs.
This PR makes sure the fields can be added after popover in case, we add a field like this:
```xml
<calendar>
...
<popover>...</popover>
<field name="name"/>
</calendar>
task-5999286The export data dialog is easier to use, with a cleaner layout, better field selection behavior, and editable export templates. Users can now export translated field values by language, making multilingual data exports easier to reuse and re-import.
Original PR description
This PR applies several changes to revamp the export data dialog. First commit modernizes the layout and behavior of the export dialog: Layout: - Replace the "I want to update data (import-compatible…
This PR applies several changes to revamp the export data dialog. First commit modernizes the layout and behavior of the export dialog: Layout: - Replace the "I want to update data (import-compatible export)" checkbox with a more compact "Updatable fields only" switch, placed next to the "Available fields" title it actually filters. - Replace the export format radio buttons with a select displayed below the available fields, freeing vertical space in the right panel, and name the formats "Excel Workbook (.xlsx)" and "Plain Text (.csv)" instead of bare extensions. - Add a search icon inside the search input, hidden as soon as the user starts typing. - Use caret icons and the standard emphasis hover color in the fields tree instead of the brand color overlay, and drop the special styling of expanded items. Behavior: - Toggling "Updatable fields only" now only refreshes the available fields and keeps the export list untouched, instead of resetting it to the default/template list. - Hide the "add" icon of fields already selected instead of rendering it in a disabled state. - Ignore the trash icon in the draggable hook so removing a field cannot accidentally start a drag sequence, and give it a pointer cursor. Second commit adds translation support to export: since https://github.com/odoo/odoo/pull/224997, the import supports translated fields through the `field@lang` header convention (e.g. `name@fr_FR`). The commit adds the counterpart on the export side. Server: - `_export_rows()` now accepts field paths suffixed with `@` and a language code and exports the translation of the field in that language, mirroring the import convention (including nested paths such as `line_ids/name@fr_FR`). - `/web/export/get_fields` and `ir.exports._get_fields_info()` expose a `translate` flag so the client knows which fields are translatable. Export dialog: - Add a "Languages" input at the bottom of the "Fields to export" column, only shown when more than one language is installed. The selected languages are displayed as removable tags next to an inline autocomplete listing the remaining installed languages. - On export, each translatable field of the export list is replaced by one column per selected language, using the `field@code` syntax. An import-compatible export can thus be re-imported with its translations directly. - Languages export preferences can also be saved and loaded into/from export templates. Layout: - Rework the two-pane layout into a 2-column CSS grid so each horizontal pair (titles, search/template, field lists, format/languages) shares a row and stays vertically aligned with equal heights - in particular the Format select and the Languages input. Third commit improves export template creation/edition UX. Templates can now be renamed and have their fields/order/languages changed in-place, instead of only supporting a separate "New template" option. Changing the export list, field order or languages while a template is selected but not being edited detaches from it, keeping the current selection as an unsaved working set instead of forcing edition mode, so a new template can be built on top of an existing one without altering it. ir.exports.line gains a sequence field so the field order of a template is preserved across saves. task-6090205
This update brings Odoo's spreadsheet component up to its latest version, improving reliability in printing, charts, search and replace, clipboard handling, and dashboard spreadsheet behavior. Business users should see fewer errors and more consistent spreadsheet outputs, especially when printing dashboards or working with charts and copied data.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/2b1e397c1c [REL] 19.5.0-alpha.19 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/2b1e397c1c [REL] 19.5.0-alpha.19 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/b85fb02778 [FIX] search and replace: manage invalid range [Task: 6483222](https://www.odoo.com/odoo/2328/tasks/6483222) https://github.com/odoo/o-spreadsheet/commit/b786cb49ed [MOV] clipboard: move clipboard store to correct folder [Task: 6389205](https://www.odoo.com/odoo/2328/tasks/6389205) https://github.com/odoo/o-spreadsheet/commit/873b9b4a20 [REF] clipboard: transform the clipboard into a store [Task: 6389205](https://www.odoo.com/odoo/2328/tasks/6389205) https://github.com/odoo/o-spreadsheet/commit/e4f76b9720 [FIX] carousel: cannot add non-existing chart to carousel [Task: 6455790](https://www.odoo.com/odoo/2328/tasks/6455790) https://github.com/odoo/o-spreadsheet/commit/1fbd77fa5d [FIX] calendar chart: wrong groupBy choice filtering [Task: 5358625](https://www.odoo.com/odoo/2328/tasks/5358625) https://github.com/odoo/o-spreadsheet/commit/56dd9da741 [REF] print: use an iframe to print the spreadsheet [Task: 6466136](https://www.odoo.com/odoo/2328/tasks/6466136) https://github.com/odoo/o-spreadsheet/commit/fe65c382c5 [IMP] draw_grid: explicitly reset transform [Task: 6466136](https://www.odoo.com/odoo/2328/tasks/6466136) https://github.com/odoo/o-spreadsheet/commit/f6cc865beb [FIX] grid: hide AddRowFooter when the mainViewport is too small [Task: 6103620](https://www.odoo.com/odoo/2328/tasks/6103620) https://github.com/odoo/o-spreadsheet/commit/3418890d8e [FIX] print: always print in light mode [Task: 6432165](https://www.odoo.com/odoo/2328/tasks/6432165) https://github.com/odoo/o-spreadsheet/commit/e3f0d8100c [FIX] charts: some charts cannot be aggregated [Task: 6501177](https://www.odoo.com/odoo/2328/tasks/6501177) https://github.com/odoo/o-spreadsheet/commit/d0227ba203 [FIX] print: handle hidden headers [Task: 6332587](https://www.odoo.com/odoo/2328/tasks/6332587) https://github.com/odoo/o-spreadsheet/commit/59860bf2de [FIX] xlsx: fix geo chart xlsx export [Task: 4632983](https://www.odoo.com/odoo/2328/tasks/4632983) https://github.com/odoo/o-spreadsheet/commit/929d44602d [FIX] composer speech_bubble: move after rendering [Task: 6484405](https://www.odoo.com/odoo/2328/tasks/6484405) https://github.com/odoo/o-spreadsheet/commit/fb3300f036 [IMP] package: update owl to alpha 49 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/2c7276afad [IMP] *: set button border radius to 4px [Task: 5086089](https://www.odoo.com/odoo/2328/tasks/5086089) https://github.com/odoo/o-spreadsheet/commit/1de94c295d [IMP] formatLargeNumber: throw Error instead of EvaluationError [Task: 6306250](https://www.odoo.com/odoo/2328/tasks/6306250) https://github.com/odoo/o-spreadsheet/commit/1bcd848606 [FIX] hover_overlay: avoid useless render [Task: 6526551](https://www.odoo.com/odoo/2328/tasks/6526551) https://github.com/odoo/o-spreadsheet/commit/a177d96fd5 [FIX] carousel: increase bottom padding [Task: 6481993](https://www.odoo.com/odoo/2328/tasks/6481993) https://github.com/odoo/o-spreadsheet/commit/4b77d5f79f [FIX] ComposerHighlight: Highlight the correct sheet with `#` [Task: 6527596](https://www.odoo.com/odoo/2328/tasks/6527596) https://github.com/odoo/o-spreadsheet/commit/88fdc912e8 [FIX] clipboard: typo on copy/paste on a merge [Task: 6515850](https://www.odoo.com/odoo/2328/tasks/6515850) Co-authored-by: Florian Damhaut (flda) <flda@odoo.com> Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Ronak Mukeshbhai Bharadiya (rmbh) <rmbh@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com> Co-authored-by: Marceline Thomas (matho) <matho@odoo.com>
Snail mail letters can now report delivery status updates back into the related invoice chatter. This helps users see when a posted letter has delivery problems, reducing uncertainty and making follow-up easier.
Original PR description
Before this commit - sometimes letter got lost and undeliverable for some reason but there was no way to get the status update on that After this commit - added webhook that notify the user in invoice chatter with the status of letter IAP: https://github.com/odoo/iap-apps/pull/1148 task-4942960 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Italian e-invoices now use the customer or vendor payment method to select the correct SdI payment code automatically, reducing manual work and inconsistent invoice data. Italian invoice PDFs also show more of the legally relevant FatturaPA information, including payment method, fiscal code, and reference document details.
Original PR description
**PURPOSE** - The Italian invoice PDF should contain the relevant information available in the FatturaPA XML, such as the payment method, fiscal code, and reference document. - The SdI payment method…
**PURPOSE** - The Italian invoice PDF should contain the relevant information available in the FatturaPA XML, such as the payment method, fiscal code, and reference document. - The SdI payment method should also be derived from the customer's configured payment method instead of being manually selected or overridden during payment registration. **SPECIFICATION** - Map Odoo payment methods to their corresponding SdI payment codes. - Automatically set the SdI payment method on new customer invoices based on the customer's configured payment method. - Remove the payment-registration logic that overrides the SdI payment method based on matched or linked payments. - Use the payment method already set on the vendor bill when opening the payment registration wizard. - Improve the Italian invoice PDF to display the missing information, including payment method, fiscal code, and reference document. Task [link](https://www.odoo.com/odoo/project.task/6107170) task-6107170
The website builder can now track and wait for editing actions to finish, which helps AI-driven website editing behave more reliably. Loading feedback has also been improved so users see a continuous indication while multiple builder actions are being processed.
Original PR description
[IMP] html_builder: applyAction returns promise `BuilderActionsPlugin.applyAction` is used to execute builder actions in the builder mutex. After this commit, this method returns the promise associated with the new action pushed in the mutex. This way, if needed, the caller can keep track of the action and await for its execution. This is used in `ai_website` to make the agent await for the execution of builder actions. task-6487866 --- [IMP] html_builder: make Operation handle multiple block requests This commit refactors the `Operation` mechanism such that it can handle multiple block requests. Also `OperationPlugin` now exposes the method `addLoadingElement`. This allows to show a continous loading animation while actions are being pushed in the operation mutex. This is the case in `ai_website` (see linked Enterprise PR). task-6487866
The spreadsheet refresh action now updates Odoo-based formulas as well as charts, pivots, and lists. This helps users see current values across spreadsheets after one refresh, reducing stale financial or business data.
Original PR description
When using the `Refresh all data` menu item, every odoo function should be refreshed, not only the chart/pivot/list data sources. Task: [4823668](https://www.odoo.com/web#id=4823668&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) 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
Planning shift information is now presented more consistently across calendar, map, Gantt, and Kanban views, making it easier for users to recognize and act on shifts. Field service flows are also clearer, with simpler action labels, better handling when starting open shifts, and corrected menu behavior after uninstalling the field service feature.
Original PR description
## [FIX] web_map: allow to define field/popover in any order in map view Before this commit, it was not possible to add field below the popover element in the map view definition. It was also not…
## [FIX] web_map: allow to define field/popover in any order in map view
Before this commit, it was not possible to add field below the popover
element in the map view definition. It was also not possible to define a
field without string attribute. However, if the string attribute is not
given, the string is found thanks to the fields_get, so the string
attribute can be optional.
This commit improves the rng file for the map view to accept to add
field after the popover to be able to add a field with such xpath:
```xml
<xpath expr="//map" position="inside">
<field name="x_coucou"/>
</xpath>
```
this commit also makes string attrbitue optional for field inside the
map view definition.
## [FIX] planning: wrong order for planning manager
## [IMP] planning{_field_service}: harmonize card popover in calendar/gantt/map
This commit adds the card view in calendar/gantt/map to be able to have
the same card view in popover of those views but also in the kanban
view. This commit also refactors a bit the code to avoid having to
duplicate the code in all those views.
## [IMP] planning_field_service: rename view itinerary and sign in buttons
This commit renames `View Itinerary` into `Navigate` to reduce the size
of the button and also renames `Sign In` button into `Start` to facilitate
the understanding of the purpose of that button.
## [FIX] planning_field_service: correctly restore the menu items in planning
Before this commit, when the field service feature is uninstalled, the
menuitems in planning are not reset as they should be in planning module
and so those menuitems are no longer linked to the planning app.
This commit adds an uninstall_hook to reset the menuitems to their
expected state when only planning is installed.
## [IMP] planning_field_service: improve sign in on open shift
Before this commit, when the user signs in on an open shift, the shift
state is changed to in progress but the shift remains unassigned.
This commit assigns the current user who signs in the open shift to make
sure a resource is assigned to continue the process.
task-5999286Appointment test coverage was updated to reflect recent changes in how calendar partner filters are handled. This helps ensure appointment scheduling continues to work reliably as related calendar behavior evolves.
Original PR description
Update the existing appointment tests to use the "calendar.filters" model so that the recent changes done in to the calendar partner filters (cf COM PR) are correctly reflected. Task-5946597
Spreadsheet printing has been made more reliable by isolating print output from the surrounding page layout, reducing the chance of blank or incorrect pages. The spreadsheet clipboard behavior was also aligned with recent platform updates, helping related chart, sales, and comment tests continue to work correctly.
Original PR description
See https://github.com/odoo/odoo/pull/287546
The AI website builder can now receive direct feedback from browser-based editing tools, so it knows when requested changes succeed or fail. The builder interface stays locked during an AI response to avoid flickering and conflicting edits, and a crash during page redesigns with menu changes has been fixed.
Original PR description
[IMP] ai_website: use aiClientToolsRegistry PR [1] introduced a more convenient way to call client tools, which does not rely anymore on the bus and allow the AI agent to receive a response from the…
[IMP] ai_website: use aiClientToolsRegistry PR [1] introduced a more convenient way to call client tools, which does not rely anymore on the bus and allow the AI agent to receive a response from the tool executing in the user browser. This commit implements this new method for the tools defined in `aiWebsiteBuilderPlugin`. [1]: https://github.com/odoo/enterprise/pull/122477 task-6487866 --- [IMP] ai_website: make agent aware of failed edits Before this commit, the AI agent was not aware of failures generated in `aiWebsiteBuilder.applyActions()`. This meant that the agent was giving a positive feedback to the user edit requests, even if they failed. After this commit, `applyActions()` reports per action what the editor dropped. task-6487866 --- [IMP] ai_website, *: lock the builder UI for the whole AI turn *: ai_html_builder Before this commit, `Thread.post` in `ai_website` ran the post promise inside the builder mutex. The lock was therefore held by `post` for the whole AI turn. After this commit, the loading screen shows the loading effect and blocks the page for the whole turn, this way there won't be any flickering. task-6487866
The spreadsheet refresh action now also updates survey-related formulas, so users see current survey results when refreshing all data. This makes reports more reliable and avoids manually fixing or reopening spreadsheets to get updated survey information.
Original PR description
When using the `Refresh all data` menu item, every odoo function should be refreshed, not only the chart/pivot/list data sources. This commit maek sure the ODOO_SURVEY function is updated. Task: [4823668](https://www.odoo.com/web#id=4823668&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
Spreadsheet pivot tables can now have styles defined directly on the pivot, so users no longer need to create separate dynamic tables just to format them. This makes pivot reports easier to format consistently and supports richer styling for headers, totals, and measures.
Original PR description
### [IMP] spreadsheet: implement pivot table styles With this commit, we don't need to manually create a dynamic table to a pivot to have a style applied. Instead we can add a style in the pivot definition, and dynamic tables will automatically be created on the dynamic pivot formulas. Those new pivot styles are better than traditional tables styles because: - they are directly linked to the pivot, taking into account the number of headers, the presence of totals, etc. - they are automatically added on `=PIVOT()` formulas, without the need to create a dynamic table first. - they are more powerful than the old table styles, they can have a style for the sub-headers, the measure headers, etc. Task: [4552232](https://www.odoo.com/odoo/2328/tasks/4552232) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mobile spreadsheet dashboards now show charts and scorecards with more consistent sizing, making them easier to read on phones and tablets. The update also enables carousel-style data views to appear correctly in the mobile dashboard, improving access to spreadsheet insights on smaller screens.
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
Spreadsheet pivot tables now include an option to display row headers in a tabular layout, with each row level shown in its own column. This makes complex pivot reports easier to read, compare, and export for business analysis.
Original PR description
### [IMP] spreadsheet: add pivot tabular form This commit adds a new setting for pivot: whether to use tabular form. In tabular form, each level of row header is displayed in a separate column. Task: [4794334](https://www.odoo.com/web#id=4794334&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Charts in spreadsheets now use updated layout helpers so titles and padding appear more consistent across chart types. This creates a cleaner, more uniform visual experience when users view bar, line, and pie charts.
Original PR description
Adapt the odoo charts to use the new helpers for chart layout. Task: [4316044](https://www.odoo.com/web#id=4316044&action=333&active_id=2328&model=project.task&view_type=form&cids=1&menu_id=4720) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The spreadsheet app interface now adapts to dark mode, giving users a more comfortable viewing option in low-light environments. This also simplifies how the interface is styled, making future visual updates easier to maintain.
Original PR description
This commits implements dark mode for the user interface in o-spreadsheet. We can drop the drak mode-specific stylesheets and use CSS variables using light-dark() instead. Task: [5082659](https://www.odoo.com/web#id=5082659&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Spreadsheet pivot tables now visually indent row groupings based on their hierarchy level. This makes grouped pivot data easier to scan and understand, especially when reports contain multiple nested row categories.
Original PR description
Makde adpatation to the code: now the different groupBys of the rows of the pivots are indented depending on the level of the groupBy. Task: [3965246](https://www.odoo.com/odoo/2328/tasks/3965246) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Spreadsheet users can now duplicate charts directly from the carousel panel menu. This saves time when reusing chart layouts and keeps the related Odoo menu link information intact in the copied chart.
Original PR description
The o-spreadsheet adds a button in the cog wheel of the carousel panel to duplicate charts in the carousel. With this commit, the odoo menu id is also duplicated when duplicating a carousel chart. Task: [5081788](https://www.odoo.com/odoo/2328/tasks/5081788) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product images now include a new stored classification that prepares Odoo for clearer control over primary and secondary product images in future upgrades. This also fixes product duplication so copied products no longer receive duplicate main images or keep image links to the original product's attribute values.
Original PR description
This field will be used in subsequent PRs to: - Keep a product's primary and secondary images unchanged when upgrading to version 20.0. - Allow users to select the primary and secondary images manually, instead of relying on some obscure computation. We're doing the extra work in a separate PR because the new `type` field should be added in the same version as https://github.com/odoo/odoo/pull/242995, and we won't have the time to implement everything before the next version freeze. This PR also fixes issues related to duplicating products with images. Previously: - The main image would be duplicated in the extra images. - Extra images with attribute values would keep pointing to the attribute values of the original product, instead of the duplicate.
The module update process was optimized to reduce repeated lookups and use existing application caching more effectively. This should make system startup and module list refreshes noticeably faster, with reported gains of 30-50%.
Original PR description
30-50% gain by using the ORM directly and caches during loading of all modules. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Belgian payroll now includes activated joint committee support and related payroll configuration data, helping companies apply the right local payroll rules more consistently. The update also cleans up outdated salary rule references and improves salary configurator test coverage to reduce errors in Belgian payroll flows.
Original PR description
task-6397954
Call activities can now be linked to any relevant contact or record within the same company, not just the exact contact from the call. This makes it easier for teams to record calls against the right opportunity, ticket, project, sale, or subscription when multiple contacts belong to one customer organization.
Original PR description
…ntact *=voip_crm,voip_helpdesk,voip_project,voip_sale,voip_sale_subscription When logging a call activity, the proposed records were limited to those directly related to the call's contact (or its children). They now cover every partner sharing the same `commercial_partner_id`, i.e. the whole company. The Contact field is also unlocked: it used to be readonly when the call had a matched contact, making it impossible to log the activity on another contact of the same company. It now defaults to the call's contact and stays editable within the commercial entity. The helpdesk ticket domain previously matched the call's exact contact only; it now follows the same commercial entity rule as other models. task-6503168
Austrian companies can now see the Fiskaly cash register ID directly in the POS settings. This makes it easier to match each Fiskaly register with the correct POS register, especially for businesses operating multiple registers.
Original PR description
It is difficult to track which Fiskaly register belongs to which POS register for companies which use multiple registers. But we already track the information in the l10n_at_pos module. So this commit will also show the register as a read only field in res_settings for austrian companies (similar to how it's done in l10n_de_cert) Task-[5503862](https://www.odoo.com/odoo/project/1737/tasks/5503862)
Payroll premium pay handling is now made generic so it can be used consistently across all country localizations. This helps businesses apply premium pay categories more uniformly and reduces localization-specific setup or maintenance differences.
Original PR description
Task: 6530690
The calendar side panel filters have been redesigned to make managing visible calendars and attendees clearer and easier. This should help users find, organize, and adjust calendar views faster with a more streamlined filtering experience.
Original PR description
- to do: see if can use Many2manyTagsField instead - Many2ManyTagsFieldColorListPopover? task-5946597
Sales users can now apply the discount wizard to only some lines on a sales order instead of discounting the entire order. This gives teams more flexibility for targeted promotions, corrections, or negotiated discounts without changing unrelated items.
Original PR description
Before this commit, the discount wizard could only discount all the lines of the SO. After this commit it is possible to make the discount on a fraction of them. 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
The Vietnam accounting localization now includes dedicated accounts for recording revenue and costs from selling or liquidating investment property. This supports compliance with Circular 99/2025/TT-BTC and enables related financial reports to separate these gains or losses from regular revenue and cost accounts.
Original PR description
Circular 99/2025/TT-BTC adds a dedicated Profit & Loss line for gains/losses on the sale and liquidation of investment property, computed from dedicated sub-accounts rather than the main revenue and cost-of-goods-sold accounts. Add the two accounts to the chart of accounts: - 5117 Revenue from sale and liquidation of investment property - 6327 Cost of sale and liquidation of investment property See the paired l10n_vn_reports commit for the report changes that consume these accounts. Task-6518304 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Vietnamese Balance Sheet and Profit & Loss reports are updated to match Circular 99/2025/TT-BTC effective from FY2026. The changes rename the balance sheet, add the required investment property gain/loss line, adjust line numbering and calculations, and hide a comparison option that does not work correctly for these reports.
Original PR description
Circular 99/2025/TT-BTC (effective FY2026) replaces Circular 200/2014/TT-BTC. It renames the Balance Sheet to "Báo cáo tình hình tài chính" (Statement of Financial Position); the report's account…
Circular 99/2025/TT-BTC (effective FY2026) replaces Circular 200/2014/TT-BTC. It renames the Balance Sheet to "Báo cáo tình hình tài chính" (Statement of Financial Position); the report's account mapping is otherwise unchanged, so only the Vietnamese title needs updating. The Profit & Loss statement (Mẫu B02-DN) gains a new mandatory line, "Lãi/lỗ của hoạt động bán, thanh lý bất động sản đầu tư" (mã số 21), computed from the new 5117/6327 sub-accounts (see the paired l10n_vn commit). Financial income, financial expenses and the interest memo line shift to mã số 22/23/24 accordingly, the "Net profit from operating activities" formula is updated to include the new line, and all following line numbers/labels are renumbered to match the printed form. Also, per revised guidance: - Revenue and cost of goods sold now exclude the new investment property sub-accounts (5117/6327), so those amounts aren't double-counted between the main lines and the new gain/loss line. - Other income is now computed from the "income_other" account type instead of a hardcoded account code, matching how the chart of accounts already classifies it. - The "Percentage of" comparison option is hidden on both reports: it silently no-ops as soon as a report declares more than one column (both reports have a Code column alongside Balance), and there's no per-report way to make it work without a core account_reports change. Task-6518304 See: https://github.com/odoo/odoo/pull/287549
Point of Sale employee access levels have been renamed to clearer business roles: Restrictive, Cashier, Manager, with a new Supervised role added. POS actions are now limited according to each employee's assigned role, helping businesses better control what staff can do at checkout.
Original PR description
**= point_of_sale, pos_discount, pos_loyalty, pos_sale, pos_self_order Following this commit: ==== - Minimal Employee has been renamed to Restrictive. - Basic Employee has been renamed to Cashier. - Advanced Employee has been renamed to Manager. - Introduced the Supervised Employee role. - Restricted POS features based on the employee's assigned role. task-6317141 Ent PR : https://github.com/odoo/enterprise/pull/122275 Upgrade PR : https://github.com/odoo/upgrade/pull/10629
Point of Sale features in appointments, planning, due settlement, and delivery integrations now respect each employee's assigned role. This helps businesses limit sensitive actions to the right staff and keep daily operations aligned with internal responsibilities.
Original PR description
**= appointment, planning, settle_due, urban_piper Following this commit: ==== - Restricted POS features based on the employee's assigned role. task-6317141 Community PR : https://github.com/odoo/odoo/pull/273084 Upgrade PR : https://github.com/odoo/upgrade/pull/10629
This improves how Mexican CFDI invoices are imported, making product, partner, tax, and amount matching more accurate. Businesses should see fewer failed imports and clearer explanations when an invoice cannot be accepted, reducing manual correction work.
Original PR description
Previous this changes, the CFDI import had some limitations: - Missing description when importing Conceptos with a product that didn't exist in database and also the lookup didn't consider when a…
Previous this changes, the CFDI import had some limitations:
- Missing description when importing Conceptos with a product that didn't exist in database
and also the lookup didn't consider when a product reference is from the vendor
- Not a strong validation when importing CFDI (a different RFC, wrong journal, etc.)
- Missing information to be imported due to recent changes
- Wrong criteria to search for a partner when is a foreign Invoice or to public
- No support for local taxes
- Failed to match amounts when taxes are hidden or doesn't match database tax configuration.
- Repetitive error messages or not a complete description on what failed mainly on tax import
and when a document is not valid
After this commit, now:
- The lookup of products considers the vendor information and if no product is found,
the description of the Concepto is used instead
- Improved the validation when a CFDI is not valid and a message explaining why
- Added missing information
- Improved partner search to not search by a generic RFC but for the Registration number
- Added support for local taxes. This will be created as new invoice lines with a generic tax.
- Tax amounts are fixed by forcing the tax lines to have the values of the CFDI. For the untaxed
amounts, a rounding line will be created
Also the structure of the import workflow is changed to use the new helpers for edi import
task-4399021*: account_payment_custom, payment(_custom), pos_sale(_delivery,_stock), pos_stock, sale, website_sale_collect Since 9d01784fa998, "Cash on Delivery" and "Pay on Site" transactions were marked as…
*: account_payment_custom, payment(_custom), pos_sale(_delivery,_stock), pos_stock, sale, website_sale_collect Since 9d01784fa998, "Cash on Delivery" and "Pay on Site" transactions were marked as done as soon as the order was placed, so the order appeared fully paid: it could no longer be settled in the Point of Sale, and 1c9c1a1213ef had to patch the remaining balance to ignore those transactions. This keeps such transactions pending instead, the money genuinely hasn't been received yet, and drops that workaround. The order is still confirmed and the customer still sees a success message at checkout, but the payment stays outstanding until it is really collected: - The invoice is no longer issued at checkout, so the customer isn't invoiced for money they haven't paid; it is created when the payment comes in. - Validating a delivery for such an order pops a dialog stating the amount the delivery person has to collect, and for which orders, before the transfer goes through. - The order keeps a remaining balance, so it can be loaded and settled in the Point of Sale, including after the goods have already been delivered, which previously loaded an empty order. - Settling it in the Point of Sale takes the payment there and closes the promise of a payment on delivery. - "Pay on Delivery" is only offered for the full remaining balance: it can't be used to promise a partial payment. task-5166559