https://runbot.odoo.com/odoo/error/163099

This issue became visible as part of the change to test ACLs (removal of demo data, possibly change to groups too) as well as running the "single app tests" on *every module*, not just the apps.

The issue is that `self.Requests.user` and `self.employee_user` are unrelated (the amazingly named `self.employee_user` doesn't even have a user). On leave creation, this triggers the rule `hr_leave_rule_employee_update` which checks if:

- The current user is the employee's, which is not the case because the employee doesn't have a user.
- Or the current user is the employee's leave manager, which is also not the case because the employee does not have a leaves manager.

As a result the creation of the leaves fails immediately.

Fix in 17.4 as the test was introduced in #53940 which was merged in (what would become) 17.3, even though the test setup means it might not be possible to trigger there because of all the demo messing with groups.

Forward-Port-Of: odoo/enterprise#83427

**Steps to reproduce:**
- Install Accounting and l10n_pe_edi
- Switch to a Peruvian company (e.g. PE Company)
- Go to "Settings / Technical / Database Structure / Decimal Accuracy"
- Set 4 digits for "Product Price"
- Create a product with a lower price than 0.01 (e.g. 0.0045)
- Create an invoice:
  * Customer: [a Peruvian customer] (e.g. Comercial Constructora los Patitos S.A.)
  * Product: [the created product]
  * Quantity: 100
- Confirm the invoice
- Process the invoice by the E-invoicing service

**Issue:**
An error is triggered because "PriceTypeCode" is set to "02", which is the code used to declare that it is free.
But in this case, it is not free.

**Cause:**
"PriceTypeCode" is computed by using "is_zero" method of the currency on the unit price.
As the decimal accuracy of the currency is set to 2 and the unit price is 0.0045, "is_zero" is returning True.

**Solution:**
Compute "PriceTypeCode" from the line subtotal instead of the unit price.
This is not perfect as it can also be lower than 0.01, but it's less probable.

opw-4608671

Forward-Port-Of: odoo/enterprise#83401
Forward-Port-Of: odoo/enterprise#82019

Commits fc49984a and 2644a63b introduced changes to:
- Prevent rejections for invoices older than 72 hours (error 301).
- Use the correct partner/branch timezone when generating the CFDI.

However, these changes also cause each re-stamping attempt to use the current timestamp, resulting in duplicates on the SAT if the first attempt times out or is lost (e.g., due to a disconnection). The PAC sees each request as a distinct CFDI if there is even a slight difference in the timestamp.

This fix ensures that the same emission timestamp (stored in `l10n_mx_edi_post_time`) is reused for subsequent stamping attempts, producing an identical XML and preventing duplicates on the SAT.

Steps to reproduce the original issue:
1. Create and confirm an invoice.
2. Stamp the invoice.
3. Manually set the EDI status to “to_send”: ```python record.edi_document_ids.write({"state": "to_send"}) ```
4. Stamp again without persisting the emission timestamp => a new CFDI is generated.

Expected result after the fix:
- The system reuses the same emission timestamp (l10n_mx_edi_post_time) for each attempt, preventing duplicate CFDIs on the SAT.

According to the [SAT
documentation](http://omawww.sat.gob.mx/tramitesyservicios/Paginas/documentos/Anexo_20_Guia_de_llenado_CFDI.pdf)
the attribute `Fecha` must be the expedition date.

Forward-Port-Of: odoo/enterprise#83319
Forward-Port-Of: odoo/enterprise#81882

Currently, when settling customer's account using the mexican localization, the session crashes after selecting the payment method.

Steps to reproduce:
-------------------
* Install the mexican localization and switch to one of the company
* Create a new contact of type "Company"
* Create an invoice for that contact so that he has a due amount set
* Open session
* Select the customer and settle due amount
* Select any payment method
> Observation: Blank screen

Why the fix:
------------
Same issue addressed here but at a different place: https://github.com/odoo/enterprise/commit/e1e1abdd23cead2bcd7b8170da28161c3f5b2e15

Cause by the fact that when a customer of type "company" is selected we automatically invoice orders.
https://github.com/odoo/odoo/commit/270779c8250272920d759fbe7b6cfc889e2f5969

Instead of going in the same direction of the first fix, we never set `to_invoice` to true when we are settling customer accounts. It's pointless to set invoice to true when settling accounts as it's impossible to create an invoice without any product. This should also benefit localizations that invoice by default every order by bypassing the invoice in that case.

opw-4685842

Forward-Port-Of: odoo/enterprise#83172
Forward-Port-Of: odoo/enterprise#82785