Module Navigation

6/2025 – Time (ExakTime) Release Notes – Default Locations and Cost Codes Employees

Enhance the time and attendance system by enabling administrators to assign default work locations and/or cost codes to employees. This feature aims to streamline the clock-in process, reduce manual input, minimize errors, and ensure accurate time tracking for payroll and job costing purposes.

When an employee has a default Location and/or Cost Code selected, and the employee logs pressing the Go (Clock In) button, they will bypass the Location and/or Cost Code selection screens.

Required ExakTime Mobile Version

The Default Location and Cost Code feature requires ExakTime Mobile version 2.101 (released on 6/13/2025) on both iOS and Android to function.

Default Assignment Configuration

A default Location and/or Cost Code can be assigned to an employee via an employee profile update.

ETC - Employee - Default Location Cost Code - 00.png

For information on setting up a default mobile location/cost code for an employee, refer to our dedicated article here.

ExakTime Mobile Settings - Employee Default Override

With the release of the employee default location and cost code, a new "Mobile Setting" has been added called “Allow employees to override default location and cost code when clocking in on Exaktime Mobile". When this setting is enabled, the employee, when clocking in, sees their assigned default location and/or cost code but has the ability to select a different location and/or cost code if needed. 

ETC - Mobile Settings - Override Default Location Cost Code - 00.png

The Default Location or Cost Code will appear at the top of the selection list under the default header.  

EM - Mobile Settings - Override Default Location Cost Code - 00.png

When groups are used, the default header will appear when a group is selected that contains the default location or cost code. If a group is selected that does not contain the default location or cost code, it will not appear.

For more information on Mobile Settings, you can refer to our dedicated article here.

Default Location and/or Cost Code Logic

As locations and cost codes can become inactive while assigned, and a mobile device may have its own assigned. The following will describe the expectations for various scenarios.

Location

  • If Employee has Active default location and Device has Active default location:
    • App to use assigned employee default
  • If Employee has Inactive default location and Device as Active default Location:
    • App to use assigned device default
  • If employee has Inactive default location and Device as Inactive or No default Location:
    • Employee will use location picker

Cost Code

  • If Employee has Active default cost code and device has Active default cost code:
    • App to use employee default
  • If Employee has Inactive default cost code and device as Active default cost code:
    • App to use assigned device default
  • If employee has Inactive default cost code and device as Inactive or No default cost code:
    • Employee will use cost code picker

Employee Default Location/Cost Code and Scheduler Clock-in

Currently if an employee is scheduled for a specific location and/or cost code and uses the Clock-into Scheduler feature, the scheduled location and cost code will take precedence and be assigned to that employee's punch.

Employees assigned default and location will follow the same rules.

  • If an employee has a schedule created with a scheduler that will have an assigned location and cost code
    • And employee uses the Scheduler Clock-In feature
      • The Scheduled Location and/or Cost Code will apply to the employee punch

Features Do Not Support Default Locations and Cost Codes

The following methods of time entry do not support Employee location and cost code defaults

  • Exaktime Mobile Clock For – Supervisors clocking in on behalf of an individual or crew will not support employee defaults
  • Connect Clock will not support employee defaults.
  • Manual time entry via Timecards or Timesheets will not support defaults.
Was this article helpful?
0 out of 0 found this helpful