Businesses can now set a cutoff date so older invoices and payments from the Invoicing app are ignored when moving to full Accounting. This makes migration simpler by letting teams cancel legacy records and reimport opening balances without duplicating accounting impact.

This is done by introducing a new threshold setting, allowing choosing a date before which all invoices and payments have to be ignored by the accounting. Once this is done, all the balances can be reimported directly, easing the migration to Odoo Accounting a lot.

account.move objects having to be ignored because of this are cancelled, and receive the new 'from_invoicing' payment state. account.payment objects are moved to the new 'from_invoicing' state and their related account.move is cancelled and marked as from invoicing as well.

Task:  2092377

Manufacturing users can now adjust component quantities and add new components to confirmed manufacturing orders when the bill of materials allows flexible consumption. The update also lets teams choose the work order where new components are consumed and improves availability and lot-tracking checks for more reliable production handling.

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

Ribbon labels in the web interface now better handle longer text by adjusting the display and allowing multiple lines. This makes status or context labels easier to read, and optional tooltips can provide extra explanation without cluttering the screen.

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

List view sidebar actions now receive a clear indicator when users selected all records using the header checkbox instead of choosing individual records. This helps business actions, especially accounting workflows, correctly understand whether they should apply to a full filtered set or only selected visible records.

In a list view, select some records (either by selecting them one
by one, or by clicking on the header to select all records), then
click on an action (except for the special case of 'Export) in the
sidebar. Some information about the selection is put into the
context:
 - active_ids: the ids of the selected records (only those of the
   current page)
 - active_domain: the current domain

However, before this commit, there were no way to determine whether
the user checked the header checkbox (i.e. all records), or some of
them individually.

This commit adds the information, with a 'select_all' key in the
context.

Note that this is a quick solution, as we need it right now for an
accounting usecase. A more elaborate solution, which will allow the
user to choose whether he wants to apply the action on the selected
ids or on the whole domain, will be developped soon.

Part of Task 2146469

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 accounting general ledger now includes a default cumulative balance view, making it easier to follow how account balances evolve line by line. Users can also use a simple balance field for grouping and selected-line totals, while journal views keep it hidden by default to avoid clutter.

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 Point of Sale customer list now shows only customers linked to the company currently being used. This helps staff choose the right customer records and reduces confusion in multi-company environments.

**Task**: https://www.odoo.com/web#id=2145607&model=project.task&menu_id=4720
**Pad**: https://pad.odoo.com/p/r.7168a8e8210fa7cc810cdf56eb92dc19

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

Avatar images shown on kanban cards now appear round instead of square. This provides a cleaner, more consistent visual presentation for users browsing records in kanban views.

Change the style of avatar images in kanban cards to make them round.

Task 2179548

Companies can now set a cutoff date so older invoices and payments from the Invoicing app are ignored during accounting setup. This helps teams migrate to Odoo Accounting more smoothly by allowing balances to be reimported without old transactions disrupting the books.

This is done by introducing a new threshold setting, allowing choosing a date before which all invoices and payments have to be ignored by the accounting. Once this is done, all the balances can be reimported directly, easing the migration to Odoo Accounting a lot.

account.move objects having to be ignored because of this are cancelled, and receive the new 'from_invoicing' payment state. account.payment objects are moved to the new 'from_invoicing' state and their related account.move is cancelled and marked as from invoicing as well.

Task:  2092377

Manufacturing users can now add extra components directly to a specific work order when the bill of materials allows flexible consumption. The update also helps ensure products tracked by lot or serial number keep the required link between consumed and finished lots, improving traceability.

Consuming product tracked by lot (or serial number ) to produce product
also tracked must ensure the link between the two lots (consumed and produced)
is always set. This test is not done in community version while there is
one in the enterprise conterpart (mrp_workorder module). This commit
move this test to the mrp module to have it everywhere

Quality rules can now cover multiple products and operations, reducing duplicate setup for teams managing inspections. The update also improves quality check visibility, supplier traceability, team-specific stages, and issue notes so managers can track quality outcomes more effectively.

Users can now delete default IP ranges from the IoT scanning list when they know their IoT Box is not there. This helps reduce unnecessary scanning time and lowers network load during device discovery.

A few weeks ago, we've added default IP ranges to scan. When you know
that the IoT Box is not in those ranges, you might want to delete the
range from the list in order to save some time and load on the network.

TaskID: 2151455