Timekeeping Punch Code Configuration

In this section, you can create and manage the punch codes employees use when clocking in and out. Punch codes help categorize time entries as paid or unpaid, assign work to specific job titles, and provide visual indicators through customizable colors. Here's how you can do it:
  1. First, go to Timekeeping and click on the Punch Codes Management tab. In this section, you will see 3 entries by default, which you can use right away.
     
  2. Next, to add a new punch code, click on the + New Punch Code button.
  3. Now, add the following information:
    • Punch Code Name - The name of the punch code employees will see during the time punching. 
    • Punch Code Type - Indicates whether the punch code record is Billable or Non-Billable.
    • Job Title - Select the job title associated with the punch code, if applicable.
    • Color - Select a color to visually distinguish the punch code throughout the system.
  4. Once done, click on "Create Punch Code".
  5. To edit the punch code, simply click on the Ellipsis menu [...], and click on the Edit option. The same window will pop up as shown in step #4 so you can edit the details of the punch code. Click on Save Changes to proceed with the process.
  6. You can also deactivate the punch code by clicking the Deactivate option. This option will take off the code from the clock in / clock out station. But the existing time card punches that have it will be kept on record.
  7. If you wish to delete the punch code, click Delete. This will permanently remove the code.
  8. Finally, once you have finished configuring the settings, navigate to the Clock In / Clock Out module so your employees can begin using their punch codes to record their work hours.
IMPORTANT NOTE:
The code marked as "Default" status only has the "Billable" option and cannot be associated with any Job Title. It only has the Edit option, and it cannot be deactivated or deleted.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.