3664856 - Restrictions and Designs of Geofencing for Clock Time

This KBA lists some of the known restrictions and designs in regards of Geofencing for Clock Time, which was delivered with 2H 2025 release.

1. Is Geofencing supported by SAP SuccessFactors web application?
2. What are the maps supported by Geofencing for rendering the maps ?
3. Is Geofencing supported for all the countries and regions ?
4. Is Precise Location mandatory to utilize Geofencing on SAP SF mobile application ?
5. Location is inaccurate on iPhone when using Geofencing for Clocking Time.
6. Is it possible to include Geofence information when creating manual time events ?
7. Is it possible to report Geofence information with time events ?

SAP SuccessFactors Time Tracking - Clock In Clock Out

1. Is Geofencing supported by SAP SuccessFactors web application?
   No.
   Currently, geofencing for clock time is only supported on SAP SuccessFactors mobile application. 
   Please make sure to upgrade your SAP SuccessFactors mobile app to the latest version to fully utilize the geofencing functionality.
   To sum up, geofencing is not considered if you clock from SAP SuccessFactors web application, even when you are accessing this SAP SuccessFactors web application from browser on your mobile device.
2. What are the maps supported by Geofencing for rendering the maps ?
   Currently only Google Maps is supported by geofencing.
3. Is Geofencing supported for all the countries and regions ?
   No.
   As currently Google Maps is the only one used for rendering maps in the application, geofencing is only supported in the countries and regions where Google Maps can be used.
   NOTE: The geofencing feature is deactivated for DC30.
4. Is Precise Location mandatory to utilize Geofencing on SAP SF mobile application ?
   Yes. Precise Location is mandatorily requested by geofencing.
5. Location is inaccurate on iPhone when using Geofencing for Clocking Time.
   Location identification in Geofencing for Clocking Time is not done by SAP SF Mobile App, instead SAP SF Mobile App only gets returned location from Google Maps, which is currently the only supported map. So in case of inaccuracy in location identification, it usually comes from the inaccurate location returned by the mobile device based on the used map.
   With iPhone, there is a known iPhone issue which would lead to inaccuracy in Geofencing in Clocking Time on iPhone.
   Please follow the steps in KBA 3691370 to adapt the settings on your iPhone mobile device so as to get more accurate location returned to Geofencing for Clocking Time.
6. Is it possible to include Geofence information when creating manual time events ?
   Yes.
   As of 1H 2026 release, it is now possible to enable Geofence field when creating manual time event from Time Sheet UI, after you have enabled Geofence Field under Settings tab in Configure Clock In Clock Out tool.
   Geofence Enhancements With Reporting Capabilities can be checked for more details. 
7. Is it possible to report Geofence information with time events ?
   Geofence information can be reported with time events in Story Report as of 1H 2026 release. 
   Geofence Enhancements With Reporting Capabilities and Geofence Data Available in Story Reports for Clock In Clock Out Time Events can be checked for more details. 

KBA 3669448 - Defined thresholds of Geofencing in Clocking Time
KBA 2090228 - How to submit enhancement ideas for SAP SuccessFactors Products
KBA 3735336 - SAP SuccessFactors Time Tracking and SAP SuccessFactors EC Time Sheet Release FAQ - First Half 2026 (1H 2026)

geofencing, geo, fence, fencing, punch, clock, time, event, in, out, cico, location, area, geofence, mobile, web, app, prevent, prevention, within, near, desired, expected, boundary, circular, polygonal, shape, iPhone, iOS, inaccurate, inaccuracy, accurate, accuracy, location, capture, inside, outside , KBA , LOD-SF-TTR-CIO , Clock In/ Clock Out , LOD-SF-TTR , Time Tracking , LOD-SF-EC-TMS , Time Sheet , LOD-SF-EC-TMS-MOB , Mobile , Problem