End Date Behavior in IFS Cloud Prevents Time Clocking on Employee's Last Working Day

Hello,

We have noticed what appears to be a challenge with employee termination dates and Time Clocking in IFS Cloud.

In Finland, an employee's last working day is typically the day when the employment is still active and the employee is expected to work and clock in. The employment relationship ends only after that day.

However, when an employee's employment is ended in IFS Cloud with a specific end date, the employee is unable to clock in via Time Clocking on that same date.

Example:

• Fixed-term employment ends on 31-Aug-2026.
• The employee should still be able to work and clock in on 31-Aug-2026.
• In IFS Cloud, the employee cannot clock in on that date because the employment appears to be considered inactive immediately on the end date.

This creates a gap between local business/legal expectations and the system behavior.

Questions:

1. Is this the expected standard behavior in IFS Cloud?
2. Is there a configuration setting that allows employees to remain active throughout the end date and become inactive only on the following day?
3. How are other customers handling this scenario, especially in countries where the employment end date is considered the employee's final active working day?

Any recommendations or best practices would be greatly appreciated.

Thank you!