This update improves everyday accounting screens by making labels clearer, dates match the user's language settings, and dashboard links behave more consistently. It also streamlines some customer actions and updates German accounting module names to use English wording for better clarity.

Description of the issue/feature this PR addresses:

Task: https://www.odoo.com/web?#id=46188&view_type=form&model=project.task&action=327&menu_id=4720
Pad: https://pad.odoo.com/p/r.0cd0553ba1131341a7b0d36117d1c693

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

Manufacturing users are now blocked from changing a bill of materials when it is already used by an unfinished manufacturing order. This helps prevent production inconsistencies and keeps ongoing work aligned with the recipe that was planned.

Task : https://www.odoo.com/web?#id=1855566&action=327&model=project.task&view_type=form&menu_id=4720

Pad : https://pad.odoo.com/p/r.e590f2ae64f17789a9ac0c3eb99ccf06

This update improves the onboarding experience by making payment setup clearer and ensuring related sales settings are activated when needed. It also makes sample document emails work as intended, improves wording and layout, and better guides users through payment and signing options.

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

This update aligns several Odoo Enterprise apps with a change that makes the administrator account a technical user. It adjusts access rules, demo data, and tests so features like Accounting, Helpdesk, Studio, Website, and other apps continue to work correctly without unnecessary permission errors.

Accounting dashboards now include all vendor bills in graph data, making results easier to understand and less misleading. The update also improves TaxCloud settings help and standardizes the German reports label from “Deutschland” to “Germany”.

Task: https://www.odoo.com/web?#id=46188&view_type=form&model=project.task&action=327&menu_id=4720
Pad: https://pad.odoo.com/p/r.0cd0553ba1131341a7b0d36117d1c693

This fix ensures reference units must always use a conversion factor of 1, including when records are imported in bulk. It prevents incorrect quantity calculations that could affect stock movements and other product measurements.

Hi @bst-odoo @nim-odoo  I don't find the fix for https://github.com/odoo/odoo/pull/22025 in master. Please find this following PR.

**Description of the issue/feature this PR addresses:**
There no constrains to force factor = 1 if it is a reference unit (there is only an onchange). It can be result some wrong compute with `_compute_quantity`.

Especially for the field `product_qty` in `stock.move`, which is a compute field from `product_uom_qty`. If there are an factor on a Reference unit, the compute will be wrong.

Because `_compute_quantity` doesn't check if it is a reference or no, and use anyway the stored factor.

https://github.com/odoo/odoo/blob/11.0/addons/product/models/product_uom.py#L92.

**Current behavior before PR:**
- import by CSV an unit with : factor= 11, uom_type = 'reference'
- no error

**Desired behavior after PR is merged:**
- import by CSV an unit with : factor= 11, uom_type = 'reference' --> Raise
![image](https://user-images.githubusercontent.com/16716992/34578751-6aab5812-f186-11e7-8b4c-1b8855ca1145.png)




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