This update improves the wording of a message in the Accounting app to make it easier to understand. It is a small grammar-focused change that helps users read the interface more clearly without changing how the system works.

The update clarifies guidance for developers working with Odoo settings so they avoid a risky customization point during module installation or removal. This helps reduce the chance of system instability or database issues caused by configuration changes being applied at the wrong time.

Execute shouldn't really be overriden because it handles a very touchy
case: module (un)installs, if it is poorly overriden it can create
registry inconsistencies and can make databases crash in really dumb
ways, since the module operations *need* to be performed at the end of
the transaction (last).

Most of the time, an override of set_values() does the same job and is
much safer.

This commit updates the `res.config.settings.execute()` documentation to
reflect this.

Linked to https://github.com/odoo/enterprise/pull/12470

German invoice reports now better follow DIN formatting expectations by adding the company address above the recipient address and including the country in the address block. The visual styling of these reports was also refined to improve layout consistency and document presentation.

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 now gives a more explicit error when a calculated read-only field is left without a value during processing. This helps developers and support teams identify configuration or coding mistakes faster, reducing troubleshooting time for affected business workflows.

Non-stored readonly computed fields must be assigned when compute is called.

The accounting tax screens and related records now use the clearer term “distribution” instead of “repartition.” This makes tax configuration language more familiar and easier for business users to understand, without changing the underlying tax behavior.

The latter is more usual.

Sales managers can now update SMS templates linked to sales orders. This keeps sales communication templates easier to maintain by the people responsible for sales operations, matching permissions already available for similar templates.

Purpose
 
Could be great that sales managers
can update templates linked to SO,
like they already do for partner/
opportunity templates.

Specifications 
sales managers should be able to 
update templates linked to SO.

PR #56257
task-id: 2319841


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

Check payment stubs now always show the check number, making printed check records easier to identify and reconcile. The check header still only shows the number when manual sequencing is used, preserving the existing behavior for automatically managed check numbers.

Task [2005940](https://www.odoo.com/web#id=2005940&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720)

Always display check number on the stub, but only when manual sequencing
on the header

This change reduces the risk of database instability when administrators change system settings. It moves sensitive module installation and removal handling away from risky custom overrides, making configuration changes safer and more reliable.

Execute shouldn't really be overriden because it handles a very touchy
case: module (un)installs, if it is poorly overriden it can create
registry inconsistencies and can make databases crash in really dumb
ways, since the module operations *need* to be performed at the end of
the transaction (last).

Most of the time, an override of set_values() does the same job and is
much safer.

Linked to https://github.com/odoo/odoo/pull/56032