_
## Short functional explanation of the error
When an employee enters multiple attendances for a single day, the company tolerance time isn't computed correctly.

## Reproduction Steps
1. Go to attendances.
2. Click on configuration and scroll down to the Extra Hours section. Set a Tolerance Time in Favor of Company of 15 minutes.
3. Create 2 attendances for the same employee: one attendance from 8 to 15 for example, and a second one from 16 to 18:12.

### Expected behavior
As the overtime entered is 12 minutes, which is inferior to the company tolerance time of 15 minutes, no extra time should be computed.

### Unexpected behavior
12 minutes of overtime are computed.

## Origin of the issue
Let's say we enter 2 different shifts for the same day. Our work day should be 8 hours, and the sum of both shifts reaches 8 hours or more. We shouldn't have any overtime. However, in the code, the overtime is negative. This is compensated by, in our case, the post-work time: in our case, our overtime duration will be equal to -1, but our post-work time will be equal to 1.2. Both cancel each other, and in the end we obtain 0.2 of overtime, which corresponds to our 10 minutes overtime. However, in this code:
https://github.com/odoo/odoo/blob/afcbd98594c9f7007f03a343ea40ea122b955459/addons/hr_attendance/models/hr_attendance.py#L374-L380 it isn't computed that way: because post-work time is 1.2, which is above our company tolerance time of 15 minutes (0.25 in the code), we will always be in the case where we exceed the tolerance time.

Hence, we have to "flatten" the overtime duration and the post-work time before reaching that piece of code.

__
opw-5136861


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

**Description of the issue/feature this PR addresses:**

The same third-party check payment method (e.g., in_third_party_checks) can currently be assigned multiple times to the same journal, either as inbound or outbound. This misconfiguration leads to unexpected behavior and runtime errors when using the payment transfer wizard.

**Current behavior before PR:**

It is possible to assign a third-party check payment method more than once to a journal.

When transferring a third-party check via the wizard (l10n_latam_payment_mass_transfer), the system may raise:

pgsql
Copy
Edit
ValueError: Expected singleton
because more than one payment method line is returned.

Functionally, allowing duplicate third-party check payment methods in the same journal does not make sense, as each method should be clearly associated with a unique payment context.

**Desired behavior after PR is merged:**

The system raises a ValidationError if a restricted third-party check payment method is added more than once to a journal.

This ensures data consistency and prevents runtime errors when using the check transfer wizard.

If a different handling is needed for a third-party check method, a new journal should be created and configured accordingly.

**Video:**
https://drive.google.com/file/d/1arbsjfA3NPG4aO2_BKxVStSTw5y4cgnM/view

**Steps to reproduce the issue:**

1.Go to Accounting > Configuration > Journals.

2.Open a cash journal that will be used as the destination journal for third-party check transfers.

3.Add the same third-party check payment method multiple times in inbound_payment_method_line_ids.

4. Create the Third-Party Check.

5.Go to Accounting > Customer > Third-Party Checks and select a check to transfer.

6.Open the mass transfer wizard and select the journal from step 2 as the destination.

7.Click to confirm the transfer → the system will raise a ValueError: Expected singleton.


Note: This issue has been observed from Odoo v15 onwards

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