3800631 - Clock time uses device timezone rather than user profile timezone in cico

• Clock In/Out events recorded via the web quick action reflect the client device/workstation timezone, not the timezone configured for the user in the application.
• Changing the device timezone before punching changes the recorded time accordingly.
• No error message is displayed.

• Product: SAP SuccessFactors Employee Central
• Clock In/ Clock Out

1. Ensure the user has a specific timezone configured in the application (for example, UTC-6).
2. Change the client device/workstation timezone to a different timezone.
3. Open the application and use the Clock/Record My Time quick action to perform a Clock In.
4. Observe that the recorded time reflects the device timezone instead of the user’s configured timezone.

Working as designed: Clock In/Out uses the client device’s timezone to determine the recorded timestamp; the employee profile timezone is not considered, and the timezone offset is captured for reporting.

1. This is expected Standard behavior: Clock In/Out records time based on the device timezone, not the user profile timezone.
   Same applies to for Mobile application also.
2. Before recording time, verify the device timezone and system clock are correct.
3. Use time event reporting to include and review the recorded timezone offset to identify punches made from a different timezone than expected.

• Refer to: Clock My Time behavior and server-time validation (release information)
• Refer to: SAP Note 3726826 - Server Time Synchronization in SuccessFactors
• Refer to: SAP Note 2079939 - Public profile displays the employee’s local time incorrectly

time tracking, cico, clock time, clock in, clock out, device timezone, workstation timezone, user timezone, employee profile timezone, server time, timezone offset, quick action, record my time, timestamp, expected behavior , KBA , LOD-SF-TTR-CIO , Clock In/ Clock Out , Problem