Users can now register a single payment for multiple invoices from the same partner even when those invoices use different receivable or payable accounts. This removes an error that previously blocked payment processing in valid accounting setups, making invoice settlement smoother for businesses with multiple account configurations.

…bles accounts

Suppose registering a payment for several invoices for the same partner but each one
having a different receivable account:
The UserError 'entries are not of the same account' is raised.

-task: https://www.odoo.com/web#id=35202&view_type=form&model=project.task&action=333&active_id=967&menu_id=4720

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 reconciliation widget now lets users match payments directly to a sales order. Selecting a sales order can confirm it, create and validate the invoice, and offer the resulting invoice lines for reconciliation, reducing manual billing and matching work.

New feature: allow to reconcile with sale order in the reconciliation widget

This change packages translated screen templates and related translation data into existing asset bundles instead of loading them through many separate requests. Users should see faster navigation and more responsive screens after assets are built, with a possible small delay the first time bundles are generated.

Reduce the ajax request number and include in bundles the translated xml and js translation.
Allows synchronous calling and improves speed (but slower when first click when creating bundles)

To think: invalidation when changing translations

This update consolidates duplicate web data handling code that was previously split across files. It reduces maintenance complexity across several Odoo apps without changing day-to-day user workflows.

I removed the branch from 10.0 to create this one for master