User's Guide

Chapter 1 Overview
16
When the default transaction for a home employee’s badge swipe is a punch, you
can assign a different default transaction for a badge ID entry. For example, if a
group of home employees routinely change job assignments when they start a
shift, you can set the default transaction to a Job Transfer for a start-of-shift badge
read.
The types of default transactions are:
• Home employee default
• Home employee shift start
• Home employee IN during shift
• Home employee shift end
• Non-home employee default
Transaction persistence
An administrator can configure the host application to repeatedly apply an
employee’s paycode edits and transfers to the employee’s record, for each
scheduled work day. The transaction persists until the employee or manager (on
the employee’s behalf) performs a punch, edit, or transfer—at the device or using
the host application. The repeating transaction generates amounts (for paycode
edits) or punches (for transfers), based on the employee’s daily schedule.
A paycode edit is persistent when both of the following are true:
• The employee is assigned to a schedule.
• The host application is configured to repeat the paycode edit on days that the
employee works.
A labor category transfer or work rule transfer is persistent when both of the
following are true:
• The employee is assigned to a schedule.
• The employee’s assigned pay rule is configured to repeat labor category
transfers or work rule transfers on days that the employee works.