How do I enable Geofencing in hh2 Remote Payroll?

Learn how to enable Geofencing in hh2 Remote Payroll, set job site boundaries, and enforce location-based punches for employees using the Punch Clock feature.

Enabling Geofencing

In order to use Geofencing, it must first be enabled at a system and payroll group level.

1. Logged in as an RP Admin

2. RP

3. System Settings

4. Punch Clock tab

5. Add a geofence radius in feet within the setting Job Geofence

6. Note: Capture GPS must also be enabled in order to use Geofencing. This setting is automatically enabled upon entering a geofence radius.

 

Now that Geofencing has been turned on at the system level, we must enable it within individual payroll groups. This allows for admins to dictate which groups of employees will use Geofencing (ex. field employees vs office employees).

1. Logged in as an RP Admin

2. RP

3. Payroll Groups

4. select a group that will use geofencing

5. Settings tab

6. make sure Punch Clock is enabled

7. enable the setting Enforce Geofencing

 

 

Adding Latitude and Longitude to the Job

In order to use Geofencing on the job, it must have a latitude and longitude present so that the employee’s location can be validated against the job site’s location. The latitude and longitude is automatically filled out as long as the job has an address either manually entered or synced from the ERP.

To view a job’s address and/or latitude and longitude:

1. Logged in as an RP Admin

2. RP

3. Jobs

4. select a job

5. Address tab

The latitude and longitude fields will auto populate when a new address is entered for the job (either directly within hh2 or synced from the ERP) or when the address is updated (either directly within hh2 or synced from the ERP).

From this page, admins call also update the geofence radius for this specific job by entering the job specific radius within the Geofence Radius field.

To prevent the latitude and longitude fields from updating, the admin can click the lock icon within the Lock Lat & Long field. This will ensure if the admin is manually entering the latitude and longitude, it is not updated by the hh2 system.

 

 

Punching In and Out

Note: Only employee created punch records will be geofenced. This includes punches created by the employee within their own Mobile Remote Payroll app via the Punch Clock menu or employees using Kiosk Mode within the Punch Clock menu.

*This change is to be released in build 452.

Managers who have the approval path permission (PC) Punch for Others or (PC) Add Manual Punches will not be geofenced when creating punches for employees. This includes punches created manually within the Time Sheet or live punches created via Crew Punch Clock.

 

Within the Remote Payroll Mobile app, employees must select a job when Punching In/Out to validate whether they are inside or outside the selected job boundaries.

1. Open the Remote Payroll app

2. Punch Clock menu

3. Punch In

4. Select a Job and any other required coding

5. click the Submit Coding button

6. If the user is outside the selected job’s geofence boundaries, they will receive an error message stating the punch will be saved as invalid due to being outside the job’s geofence radius. The employee must punch again once they are within the job site in order to create a valid punch that will be used for calculating the employee’s total punched in time.

Once an employee has punched in/out, managers can view the employee’s punch records within the Employee’s Time Sheet.

1. Logged into the web

2. RP

3. Time Sheet

4. select the Payroll Group and Employee

5. click the icon located beneath the date

6. Any Punches that were captured outside the job geofence radius will have a red warning symbol next to the Punch. Punches inside the job geofence radius will not show the warning symbol.

Note: An employee must have a valid geofenced Punch In and Punch Out record in order to calculate their total punched in time for the day.

Managers can also click the GPS icon within the Edit Punches page to view where the employee punched in/out in location to the job.

 

Upcoming Releases:

1. Build 452: Manager punches will not be geofenced. In this first iteration of geofencing the focus was around ensuring employee's who punch outside the job radius for themselves will be caught and reported to the manager. So if the employee's punch is created by the manager via Crew Punch or manually created it will not be geofenced. 

2. Build 452: (Web) Enabling Geofencing will trigger the auto population of latitude and longitude for all existing jobs. In the meantime during testing they will want to go into the Homepage > Jobs & Job Cost Data > select a job > Address tab > enter/update the address to trigger the population of lat and long. 

3. (Mobile iOS) Geofencing can be used with limited connectivity (location can still be found).

4. (Mobile iOS) Job will be a required coding field when using geofencing.

5. (Mobile iOS) When the user is completely offline, last known location will be used for Geofencing with a warning being presented to the user about the possible inaccuracy of the “current” location.

6. (Mobile Android) Geofencing can be used with limited connectivity (location can still be found).

7. (Mobile Android) Geofencing can be used online.

8. (Mobile Android) Job will be a required coding field when using geofencing.

9. (Mobile Android) When the user is completely offline, last known location will be used for Geofencing with a warning being presented to the user about the possible inaccuracy of the “current” location.