Describing Key SAP SuccessFactors Time Management 1H 2026 Features and Enhancements

The Accrual Recalculation Posting Method Classic will reach the End of Development On November 12, 2027 and will reach the End of Maintenance and be Deleted on May 12, 2028.

Future dates are subject to change.

We are making this change because No Recalculation Postings has these advantages over the Classic accrual recalculation posting method:

• Less data volume, especially for daily accruals.
• There are no longer any issues if you have duplicate accruals. If you use the No Recalculation Postings method, duplicate accrual postings are cleaned up automatically.
• If the accrual posting method is changed during recalculation, the date change is considered as well. The Classic method only considers quantity changes.

The Accrual Recalculation Posting Method Classic will be removed from the Time Account Type with the 2H 2027 release and all Time Account Types will be migrated to No Recalculation Postings.

A validation check is added with the 1H 2023 release to block saving a Time Account Type with the Accrual Recalculation Posting Method 'Classic'.

Employees can now view and confirm attestation agreements in Mobile Time Sheet during time sheet submission, with content based on time recording profiles.

When submitting a time sheet in their mobile app, employees are now shown an attestation agreement that is dynamically determined based on their time recording profile. Customers can configure the attestation text in the Web application to maintain their own required statements. Employees can read the agreement before submitting their time sheet.

The feature ensures that employees provide legally required electronic consent during time sheet submission and helps us achieve feature parity with the Web application.

Ensure that attestation is enabled and attestation texts are maintained in the Web application.

In the current version, employees see an attestation agreement when submitting a time sheet.

In the previous version, no attestation agreement was displayed during time sheet submission.

The Family Medical Leave Act (FMLA) is a labor law that allows covered employers to provide employees with unpaid leave for certain medical and family reasons. This feature is designed to integrate with third-party providers to automatically generate FMLA-related absences and access them using a new FMLA dashboard. You can now record half-day absences or any specific time period for clock time-based intermittent absences.

When an FMLA request is received from the provider, the system checks internal configurations to determine which absences to create based on the FMLA reason and the employee. The system then generates the relevant absences automatically, complying with predefined configurations. We now have a dashboard that lists FMLA requests. You can filter by the employee name, request status, and absences processing status. You can also view the request period for FMLA requests. This feature was already released for general availability in the 2H 2025 release and we have now enhanced this feature.

We enhanced this functionality to allow half-day absences as well as any specific time period to be recorded for clock time-based intermittent absences.

• You must be using SAP SuccessFactors Time Off.
• You must have configured the API authorization using the Identity Authentication Service tenant tool. For more information, refer to Configure API Authentication Using Identity Authentication.
• You've created an API user in the SAP SuccessFactors system.

You have the relevant FMLA permissions under User Permissions→Miscellaneous Permissions and under User Permissions→Time Management Object Permissions. Under Administrator Permissions, you must also assign the Manage Family and Medical Leave Act permissions to have access to the dashboard.

You can now select First Half of Day or Second Half of Day for the Absence Duration. It is also possible to record any specific period of time.

When you modify the standard SAP SuccessFactors labels using the Manage Languages feature, the labels are now automatically updated for the Temporary Time Information To-Do cards on the Home Page.

The labels on the Temporary Time Information to-do cards are now automatically updated if you customize the standard SAP SuccessFactors labels. You can create custom translations for existing labels using either of the following ways:

• Using the Manage Languages feature, you can upload a CSV file which has the message keys to be translated and the locale information
• You can search for the relevant message key or label from the available list and modify its translation.

The custom labels are available automatically to the user without having to do any manual steps. Previously, administrators had to manually run a job to update these labels, which often led to customer incidents. This enhancement aligns Temporary Time Information To-Do cards with the automated label refresh already available for Attendance and Time Off To-Do cards.

Previously, when the labels were changed for Temporary Time Information workflow to-do cards, the labels weren't automatically refreshed. It required a task definition job to refresh the cache and display the new customized labels. To perform this task definition job, you had to contact Technical Support.

Ensure that you have the Administrator→Manage System Properties→Text Replacement permission to access the Manage Languages feature.

In the current version, label changes made using Manage Language are automatically reflected on Temporary Time Information To-Do cards without requiring a manual job run. For example, in the following temporary holiday calendar, the label is changed from Holiday Calendar to Public Holiday Schedule after automatic update.

In the previous version, administrators had to manually run a job to refresh the labels on Temporary Time Information To-Do cards after making changes using Manage Language. For example, in the following temporary holiday calendar, the label Holiday Calendar remains unchanged until a task definition job was manually run.

The OData V2 APIs for Time Account Payout and Time Account Summary are now available in Integration Center, enabling integration with third-party payroll systems.

You can now access the Time Account Payout and Time Account Summary APIs directly in Integration Center. The Time Account Payout API allows you to send payout information, such as one-time payments, directly to payroll. Meanwhile, the Time Account Summary API provides up-to-date details on accruals and balances for each time account, making it easy to transfer comprehensive time account data for payroll processing. These APIs are publicly available and can be used to automate and streamline data exchange between SAP SuccessFactors Employee Central Time Off and external payroll systems.

Administrators benefit from simplified and accurate integration of time account and payout data with third-party payroll systems, reducing manual effort and improving data consistency.

You have the following permissions:

• Administrator Permission→Metadata Framework→Admin access to MDF OData API

Furthermore, if the generic object is secured, you must have the following permissions:

• User Permissions→Miscellaneous Permissions→Time Account Payout (View or Edit)
• User Permissions→Miscellaneous Permissions→Time Account (View)

You can now set up custom workflow notifications for Time Off, Time Sheet and Single Record Approvals using the Document Generation framework. This framework supports additional tokens, which helps you to provide more contextual and dynamic e-mail notifications.

Previously, the Direct Mapping type supported only HRIS entities, such as Job Information or Employment Information. You can now use tokens in your Document Generation templates to derive data from user-based MDF objects available in the Base Object dropdown, such as Employee Time Off, Employee Time Sheet, and Time Recording. With this enhancement, you can create custom workflow notifications for Time Off, Time Sheets, and Single Record Approvals which can include:

• Employee name
• Time type recorded by the employee
• Start Time/Start Date and End Time/End Date of the absence or attendance request

Ensure you've enabled Document Generation and configured the relevant workflow notification templates.

You must have the relevant permissions to use the Document Generation feature.

In the current version, you can set up custom workflow notifications for Time Off, Time Sheet, and Single Record Approvals using the Document Generation framework that supports additional tokens.

In the previous version, custom workflow notifications weren't supported for Time Off, Time Sheet, and Single Record Approvals.

You can now create absence counting rules that differentiate between holidays that fall on scheduled working days and holidays on non-working days.

Absence counting rules now include the Planned Hours Excluding Holidays parameter. This parameter helps ensure that absences on holidays that are also working days can be counted correctly, while holidays on non-working days are not considered for deduction. Temporary schedule changes are also reflected in the parameter, further improving accuracy.

For example, an employee is scheduled to work from Monday to Thursday. The employee takes leave for the entire week. The holiday on Thursday is otherwise a routine working day for the employee. Therefore, the absence counts as 1 day. Friday is a holiday and a non-working day for the employee. Therefore, the absence does not count. The detailed calculation is as follows:

• Monday to Wednesday. Count = 1 day each.
• Thursday: Holiday on a working day. Count = 1 day.
• Friday: Holiday on a non-working day. Count = 0 days.
• Saturday and Sunday: Non-working days. Count = 0 days.

In the absence counting rule, you update the rule logic to reference Planned Hours Excluding Holidays in addition to or instead of the planned hours (number of hours from Employee Time) parameter, which also includes holidays.

A new use case and several enhancements to existing use cases are now available in Joule.

Below are the details of the new transactional use case:

Besides, on iPhone and iPad devices, you can now ask Siri in multiple languages to launch Joule. Previously, only English was supported. For details about the supported languages, refer to Using Siri to Launch Joule.

We've also made enhancements to the following use cases.

We made these enhancements to optimize your experience with Joule, making your HR processes more efficient, flexible, and user-friendly.

• You've enabled Joule in SAP SuccessFactors.
• Use cases in Joule follow the same configurations and permissions as those on the Web. See Related Information for details on how to obtain required access for each use case.
• You've refreshed CDM contents. For more information, refer to KBA 3612244.

Users have the User Permissions→General User Permission→Access to Joule permission.

A new rule function, Get Completed Months of Time for a Time Type, is now available in SAP SuccessFactors Employee Central Time Off. This function helps identify the number of full months an employee is continuously absent.

The Get Completed Months of Time for a Time Type function determines the number of full time months an employee is continuously absent for a selected absence time type. It uses flexible time month definitions, such as May 14 to June 13, to automate the reduction or prorating of accruals like vacation entitlements. This function supports compliance with country/region-specific or industry-specific collective labor agreements.

Administrators benefit from this enhancement as it automates compliance with collective agreement regulations, ensuring accurate identification of full time months for employee absences.

You have Employee Central Time Off enabled. You can use the rule function in an accrual rule.

In the current version, the Get Completed Months of Time for a Time Type function is available to determine full time months for employee absences.

In the previous version, there was no rule function to automatically identify full time months for employee absences.

As an employee, you can now create and delete temporary work schedules directly from the mobile app to accommodate your flexibility needs.

This feature is available in My Calendar. To create a temporary work schedule, select the start and end dates on the calendar. The system validates whether any temporary work schedules already exist for the selected dates. When workflows are configured, managers can review and approve the temporary work schedules.

This enhancement gives employees more flexibility to manage schedules on the go and brings mobile in line with the web experience.

You must have the same role-based permissions as required in the web application to create and delete temporary holiday calendars. For details, see the linked references.

You can now create and delete temporary work schedules in your mobile app.

You can now include geofence information in Story reports when analyzing employee time events recorded through the Clock In Clock Out feature.

When building Story reports for Clock In Clock Out time events, you can include geofence fields such as the geofence name and geofence code. These fields link time event records with the geofence where the time event was recorded. Clock In Clock Out (CICO) uses geofences to support time event tracking, and this information is now available for reporting. Geofence information is available through Clock In Clock Out time event data and related geofence data when building Story reports.

We've made this enhancement so that administrators can better analyze mobile time recording activity by linking time events with geofence details in Story reports.

You use Story reports in Report Center and have reporting data available for Clock In Clock Out time events.

You have the Administrator Permissions→Reports Permission→Create Story permission. Select Geofence if you want to include geofence data when creating Story reports.

In the current version, geofence information is available when building Story reports based on Clock In Clock Out time event data. You can include geofence fields together with time event details to analyze employee time events and their geofence locations.

In the previous version, geofence information wasn't available in Story reports. Administrators couldn't include geofence data when analyzing Clock In Clock Out time events.

Geofence Enhancements With Reporting Capabilities

When creating or reviewing manual time events on the SAP SuccessFactors mobile application, employees can now select and view geofence details based on the configuration.

When Enable Geofence Field is enabled using Configure Clock In Clock Out, employees who are geofence users can see the geofence name and the code on the SAP SuccessFactors Mobile application. The geofence name and code are displayed in the list of geofences along with the distance. Employees have clear visibility of geofence boundaries and details, which assists in creating accurate manual time events.

Administrators and employees benefit from improved accuracy and transparency in time event management, making it easier for approvers to verify time events and for employees to select the correct geofence when recording manual time events.

In Configure Clock In Clock Out→Settings→Time Events Creation, enable Geofence Field to show the Geofence field in manual time events.

In the current version, employees can view the geofence details when clocking their time. The geofence name and geofence code details are visible on the map in the mobile application.

The distance from the nearest geofence boundary is visible on the mobile application.

When Geofencing is enabled, you can provide the geofence details when creating manual time events using the mobile application.

In the previous version, geofence details were not available for selection or display in the mobile application.

As an employee, manager, or administrator, you can now access the time statement generation page directly from the Time Sheet and Time Sheet Approval Center UI for selected time sheet periods.

You can generate a time statement by choosing the Time Statement link from the Time Sheet UI or from the Time Sheet Approval Center UI. The time statement opens for the same time period as the selected time sheet in a separate tab. The option to generate a time statement is available for time sheets with the statuses Approved, To Be Approved, To be Submitted, and Declined. When you generate a time statement, you are redirected to the Generate Time Forms page, where the aggregation is based on the selected time sheet period. The Generate Time Forms page is also enhanced with the Include non-approved time sheets option and when selected the time statement is also generated for the non-approved time sheets.

• Ensure that a time statement is configured for the relevant time recording profile.
• Ensure that SAP SuccessFactors Time Tracking is enabled.

You have the User→Time Management User Permissions→Generate Time Forms permission.

In the current version, time statement can be generated for all time sheet statuses excluding Cancelled and Inactive. Also, you can generate a time statement directly from the Time Sheet UI or the Time Sheet Approval Center UI for eligible time sheet periods and statuses, and the statement opens for the selected time period.

The time statement button can be selected to open the Generate Time Forms page for the selected time sheet period.

You can generate a time statement using the options menu.

The generate time forms page using which you can generate the time statement.

In the previous version, the time statement generation was available only for the approved time sheets. Also, the time statements were accessible from the Admin workbench or People Profile→Time Forms section.

Employees can now use an attendance quota to work additional hours when required with prior approval.

An attendance quota represents an employee's authorized entitlement to work specific types of hours, such as overtime, within a set period based on prior approval. An attendance quota can be defined along with the following parameters:

• Time Period (mandatory)
• Working day restriction
• Weekday restriction
• Time restrictions
• Quota limit

In Time Management, an attendance quota can be created, modified, and deleted in some scenarios. Employees create an attendance quota when they wish to work overtime, covering higher duties, working outside of flexible hours, and so on. This request requires a prior approval from a manager. On approval from the manager, the employee now works during the quota period. The associated configuration in time valuations is considered and employees are paid according to their time recordings.

As a time administrator, I can configure the Attendance Quota parameters to be shown based on the following scenarios:

• Overtime: This request may have a limit and can be defined to show for the employee in the Attendance Quotas page.
• Work from home request/higher duties: This request may have no limit but should just be worked during the Quota Period. Hence, Quota Required can be set to No in Attendance Quota Type object definition, and then the quota limit field won't show when requesting attendance quota.
• Working outside of flex bandwidth: This may request restrictions on time segments, working days or non-working days, and weekdays. The filters of time restriction, working day restriction, and allowed weekdays can be enabled.

For example, consider a scenario where an employee has an attendance quota created for working outside of flex bandwidth. The employee creates an attendance quota with a time period from 1st March 2026 to 10th March 2026, with a time restriction from 8 PM to 10 PM on working days only, with a quota of 7 hours. When the employee now works on 2nd March 2026 from 9 PM to 10 PM that day being a workday, the recorded time will be considered in time valuation and paid accordingly based on configuration. Any hours worked outside the attendance quota period won't be considered for payout.

Administrators or Managers can define a configuration for the template of attendance quota using the Attendance Quota Type object. Overtime may require a quota limit whereas work from home may not require a quota limit. The visibility of the parameters defined earlier in this topic can be controlled by the configurations in Attendance Quota Type, except for the Time Period parameter (as it is mandatory).

Administrators or Managers expect that for any additional work like overtime, call for higher duty, and so on, an attendance quota can be created and approved beforehand for employees. This allows them to plan the payroll accordingly.

• The administrator can configure the Attendance Quota Type based on the scenario, whether the Attendance Quota limit should be defined or not. The start and end dates are mandatory for any attendance quota.
• You've set up separate time valuation chains for unlimited and limited quota scenarios. No time account is created for unlimited quota types.

• You have the view and edit permissions for User→Time Management Object Permissions→Attendance Quota.
• You have the view and edit permissions for User→Time Management Object Permissions→Attendance Quota Type.
• You have the view and edit permissions for User→Time Management Object Permissions→Attendance Quota Type.Time Account Types.
• You have the view and edit permissions for User→Time Management Object Permissions→Time Valuation Employee Variable Value.Allowed Weekdays (Time Valuation Employee Variable Allowed Weekdays).
• You have the view and edit permissions for User→Time Management Object Permissions→Time Valuation Employee Variable Value.Time Segments (Time Valuation Employee Variable Time Segment Filter).
• You have the view and edit permissions for User→Time Management Object Permissions→Time Valuation Employee Variable Value.
• You have the view and edit permissions for User→Time Management Object Permissions→Time Valuation Global Variable Value.Allowed Weekdays (Time Valuation Global Variable Allowed Weekdays).
• You have the view and edit permissions for User→Time Management Object Permissions→Time Valuation Global Variable Value.Time Segments (Time Valuation Global Variable Time Segment Filter).
• You have the view and edit permissions for User→Time Management Object Permissions→Time Valuation Global Variable Value.
• You have the view and edit permissions for User→Time Management Object Permissions→Time Records Filter.Time Records Variable Filter (TimeRecordsFilterVariable).
• You have the view and edit permissions for User→Time Management Object Permissions→Time Valuation.Time Segment Variable Filter (TimeSegmentVariableFilter).

In the current version, administrators can configure a template for attendance quota for pre-approvals. Employees can request for pre-approval to perform overtime, higher duties, and so on, based on quota assignment.

Attendance Quotas provides the details of all the Attendance Quota Types and you can view the details of each entry and also its status.

In this example, an attendance quota type Work from Home is recorded on a working day without any quota limit and for a specific time period.

In this example, an attendance quota type Overtime is recorded on a working day with a quota limit.

In the previous version, there was no option to configure attendance quotas.

You can now configure how the system manages overlaps between absences and attendances, allowing accurate time tracking even when the records collide.

Managing employee time accurately is essential for operational efficiency and compliance. In previous releases, customers reported issues when absences (such as sick leave or vacation) overlapped with attendance records (such as on-call shifts or clock-ins). The new Collision Handling between Absences and Attendances feature provides robust and configurable options to resolve such overlaps, ensuring your time tracking records reflect real-world scenarios and policies. With this enhancement, you can now configure how the system behaves when absences and attendances overlap.

We've made this enhancement for the following reasons:

• Attendances with Overlapping Absences - Previously, overlaps between Clock In Clock Out records and absences would block time recording or require intervention to resolve conflicts. Now, the system supports importing or entering time punches even during absence periods. This enables seamless and automated time sheet management, even when external time data might overlap with existing leave records.
• Attendance or On-call Hours Outside Absences hours - With the new collision handling, employees can log work outside the absence hours. For example, on-call duties or overtime hours on days that are otherwise marked as full-day absences. The system intelligently handles the physical times check for full-day absences without blocking the on-calls/overtime recordings.

• SAP SuccessFactors Time Tracking is enabled.
• You've defined the Time Type Collision Grouping and assigned them to the relevant Time Types in Manage Data.
• You've defined the Incoming Grouping, Existing Grouping, Collision Resolution Action, and Collision Resolution Message. Also, under Manage Data, you've defined Time Management Collision Resolution→Absence and Attendance Collision Resolution.

In the current version, when an employee's attendance slightly overlaps with an absence (for example, a late clock out during a partial-day absence), the system processes the record without a collision error. Let us consider a scenario where an employee has a vacation for the second-half of the day but clocks out of work 15 minutes late. For example, the clock in is at 8:00 AM and clock out is at 12:30 PM. Absence starts from 12:15 PM to 5:00 PM (second half). There's no more a collision error rather a warning is displayed to the employee that a collision between absence and attendance has been resolved.

In the previous version, any overlap between attendance and absence records resulted in a collision error, blocking time recording and requiring manual resolution. Let's consider a scenario where an employee has a vacation in the second-half of the day but clocks out of work 15 minutes late. For example, Clock In is at 8:00 AM and Clock Out at 12:30 PM. Absence is from 12:15 PM - 5:00 PM (second-half). Before this new implementation, this overlap resulted in a collision error.

Collision Resolution Between Absences and Attendances

Time Management Collision Resolution

As an administrator, you can now configure how partial day absences are treated in dynamic break deduction to prevent double deduction of breaks when an employee has both working time and a partial absence on the same day.

For each absence time type, you can decide whether it should be considered as working time or as a break for automatic (dynamic) break calculation. For example, if an employee has a doctor's appointment in the middle of a workday or takes vacation in the first or second half of the day, you can configure the system to treat these partial absences appropriately. By default, existing configurations and calculations remain unchanged.

This enhancement offers more accurate working time and break calculations for administrators, helping to ensure correct balances and payroll results for employees. Previously, partial absences could result in more break time being deducted than intended, impacting time accounts and payroll.

• Ensure you've enabled Time Tracking.
• Set the Time Type Specific Break Generation field to Time Type Specific in the Dynamic Break Configuration object. The default value of the Time Type Specific Break Generation field is Standard.
• Then, in the Time Type object, set the Dynamic Break Handling field to either Consider as Break or Consider as working time. The default value of the Dynamic Break Handling field is Consider as working time.

In the current version, you can configure absence time types to be considered as breaks. When an absence is considered as a break, no additional break is generated after the working time threshold is reached. For example, if an employee works for 7 hours with a partial absence, and the absence is configured as a break, the system doesn't generate an additional 30-minute break.

In the previous version, absence was considered as working time, and a 30-minute break was generated after 7 hours of work. This could result in more break time being deducted than intended, leading to double deduction of breaks and impacting time accounts and payroll accuracy.

Setting Up Dynamic Breaks

Recalculation Triggers in the Time Sheet

Configuring Dynamic Break Deduction with Partial Absences

In SAP SuccessFactors Time Tracking, you can now configure time valuation results to include start and end times, and a physical start date and physical end date.

This enhancement enables customers using SAP SuccessFactors Time Tracking with rotating shifts, night work, or Sunday and holiday work to create multiple time segments for a single time valuation. This leads to more accurate processing of payroll in line with tax regulations for example, Germany's §3b Einkommensteuergesetz (Income Tax Law). It eliminates the need for complex workarounds that previously required the configuration of time valuations. Previously it was only possible to display a specific number of hours in time valuations.

• You must be using SAP SuccessFactors Time Tracking.
• In the time type group, you've set the Pay Result Time to Split by Clock Time, the Time Category is Calculated Time, and the Time Pay Type is set to Yes.

When you configure the time type group, you can choose to split the valuation by clock time. Time valuation results now include start and end times along with both physical start and end dates.

You can now replicate attendance records in real time from SAP S/4HANA to SAP SuccessFactors Time Sheet to prevent data collisions and ensure consistency in Consolidated Time Recording.

This enhancement enables real-time replication of attendance data from SAP S/4HANA to the External Time Data in SAP SuccessFactors Time Sheet. Previously, only approved attendances were replicated, which could result in data collisions if an absence was created in SAP SuccessFactors Time Off for a period with a pending attendance in SAP S/4HANA. With this update, all attendance records, including those pending approval, are replicated in real time. This helps to prevent overlapping or conflicting entries.

Administrators benefit from improved data consistency and reduced risk of collision scenarios between SAP S/4HANA and SAP SuccessFactors Time Sheet.

• Ensure that you've SAP SuccessFactors Time Tracking enabled.
• Ensure that you've enabled Consolidated Time Recording under Admin Center→Manage Employee Central Settings.
• Go to Configure Object Definitions and set the field Time Recording Source to Editable for the Time Type object.
  Note

  The Time Recording Source field is editable only if Consolidated Time Recording is enabled.
• Go to Configure Object Definitions and set the field External Approval Status to Editable for the External Time Data object.
  Note

  The External Approval Status field is editable only if Consolidated Time Recording is enabled.
• Go to Manage Data and configure the relevant Time Type (classification Attendance, On Call, Break, and Extra) by setting the Time Recording Source field as Consolidated Time Recording.
• Assign these Consolidated Time Recording time types to a time profile.
• Assign this time profile to an employee who has an External Time Recording group assigned in Job Information.

In the current version, if you create a time type (Attendance, Extra, Break, or On-call) with Time Recording Source as Consolidated Time Recording and use this Time type to record time on the SAP S/4HANA My Time sheet for a Consolidated Time Recording user, then the time sheet records are replicated in real-time with External Approval Status as Pending to SAP SuccessFactors External Time data as soon as they're submitted using the SAP S/4HANA My Timesheet.

Later when the same time sheet record is approved using the SAP S/4HANA Approve my Timesheet, the External Approval Status of the time sheet record in External Time data is updated to Approved.

In the previous version, there was no option to replicate pending attendance data from the SAP S/4HANA My Timesheet solution to the SAP SuccessFactors Time Sheet.

We've introduced a few enhancements related to the Time Statement Generation feature to improve the usability.

We've made enhancements in the following areas of Time Statement Generation:

• Time Statement Supports Display of Non-approved Data: This enhancement benefits users who need to track time sheet records efficiently. It ensures that all relevant data is accessible for review and decision-making by enabling access to time statements from the time sheet approval center.
• Display of Leave of Absence details: This enhancement improves transparency and accuracy in employee time records by including Leave of Absence details, ensuring that all time-related information is visible and up to date.
• Time Sheet Period Aggregation: This enhancement enables users to view data grouped by specific time sheet periods.
• Sorting of Time Records in Time Statement: This enhancement improves the user experience by offering a consistent view of time recordings, making it easier for employees and managers to understand and manage time entries.

You can now generate reports for the geofence data, configure geofence fields for manual time events, and configure larger numbers of geofences for Clock In Clock Out.

The geofence field can now be displayed for manual time events, allowing employees to select a geofence when creating a manual entry, which helps approvers to verify the event. For example, if an employee has missed recording a time event when within the geofence boundary and now wants to create a manual time event, you now have a provision to provide the geofence information for the missed time event recording.

• Reporting capabilities are enhanced to include geofence information in Clock In Clock Out (CICO) time event reports.
• The system now supports displaying and assigning more than 200 geofences with a limit of 2000 geofences using Configure Clock In Clock Out, improving scalability for organizations with extensive geofencing needs.
• Geofence audit is now possible that allows you to track the creation, modification, and deletion of geofences. For more details, refer to the Related Information section.
• In Time Sheet Approval Center, you now have the geofence code in the Related Approvals page.

These enhancements help administrators and managers efficiently manage geofence data, generate time event reports with geofence information, and support configuration with larger number of geofences.

In Configure Clock In Clock Out→Settings→Time Events Creation, enable Geofence Field to show the Geofence field in Manual Time Events.

In the current version, you can configure the geofence field for manual time events, report on geofence information in Clock In Clock Out time events, and manage up to 2000 geofences.

You can enable or disable the Geofence Field from the Configure Clock In Clock Out page.

Selection of a geofence is possible using the dropdown list when creating manual time events.

Time event details summary page shows the Geofence name.

In the Related Approvals details, you can view the Geofence Code.

Geofence reports provide details of the Geofence name and Geofence code.

In the previous version, the geofence field wasn't available for manual time events, reporting on geofence information wasn't supported, and only up to 200 geofences could be managed.

You can now configure more periodic Time Containers in a Time Recording Profile.

The maximum number of periodic Time Containers allowed in a Time Recording Profile has been increased. By default, you can now configure up to 15 periodic Time Containers.

Administrators at large or multinational organizations benefit from this update by being able to meet advanced time valuation requirements without manual workarounds or system limitations.

In the current version, you can configure up to 15 periodic Time Containers by default.

In the previous version, you could configure up to 5 periodic Time Containers by default.

Administrators can now enable replication to third-party payroll systems using a dedicated switch in Admin Center. This feature allows for streamlined integration and management of payroll proxies and related APIs.

A new switch Time Data Replication to Third-party Payroll Systems is now available in the Manage Employee Central Settings page in Admin Center. This switch can only be enabled if you have an active SAP SuccessFactors Time Tracking subscription. This enhancement supports organizations using a mix of SAP and third-party payroll solutions, making it easier to manage payroll integrations without requiring direct access to Provisioning.

Administrators benefit from simplified enablement and management of third-party payroll replication, addressing common integration challenges for global organizations.

Ensure that SAP SuccessFactors Time Tracking is enabled.

In the current version, you can enable replication to third-party payroll systems by using a dedicated switch in the Manage Employee Central Settings UI, provided you have an active SAP SuccessFactors Time Tracking subscription.

In the previous version, there was no dedicated switch for enabling replication to third-party payroll systems, and administrators couldn't manage this integration directly from the Admin Center.