Timekeeping Properties
These properties affect the behavior and appearance of Timekeeping screens and functions.
| Property | Description |
|---|---|
| Specifies the pay period before their vacation when operators are advanced their vacation pay. If Next Pay Period is selected, operators are advanced their vacation pay in the pay period before their vacation begins. If Two Pay Periods is selected, operators are advanced their vacation pay two pay periods before their vacation begins. | |
| Specifies the calculate pay components (segments) that are considered when determining the bid value of a Demand Response run. | |
| Specifies the calculate pay components (segments) that are considered when determining the bid value of a Fix Route run. | |
| Specifies the calculate pay components (segments) that are considered when determining the bid value of a Holiday Bid Run Source. | |
| Specifies the calculate pay components (segments) that are considered when determining the bid value of a Duty Segment. | |
| If selected, the Designated value is applied for Max Time To Deduct when costing Absence Pay Rules that are set to check eligible balance through an Accrual Hierarchy configuration. | |
| If selected, automatically process FLSA on the weekly processing date. | |
Specifies the banking order:
Default is no order. |
|
| Specifies the Working Status group used for custom BidValue. | |
| Specifies a bi-weekly processing date (pay ending date). The value can be agency dependent. | |
Specifies the time that the Employee Bank Time Election Max Time represents:
|
|
| Specifies the clawback straight-time processing order. | |
| If selected, get BidValue considers the run piece column. | |
| If selected, FX run platform time is costed by segment type (No, Line, or Zone). | |
| If selected, manual adjustments can be made after running daily timekeeping rules. On the first run, only daily rules are processed. On the second pass, weekly and bi-weekly rules are processed. | |
| If selected, for absences that are merged with work when determining the costing sequence, absence and work will be costed in the order of sequence, then time order. | |
|
This changes the work absence cost order. Absence first. The absence pay is not reduced by overlapping work hours. This is the default setting. Work first. The absence pay is reduced by the overlapping work hours. Note that hours are not reduced by partial bid work performed after the absence/overlapping work. |
|
| If selected, PassWork will not always cost first and work order can be configurable. | |
| If selected, complete work is costed before any incomplete work. | |
| Specifies the order in which work is costed. | |
| Specifies the work cost order. | |
| If selected, extra pay is costed in the same level of work instead of always after regular work. Default is false. | |
| Specifies the costing order for timekeeping calculations. Available values are SignOn Time, Bid Work then SignOn Time, and Published Work then SignOn Time. | |
| If selected, exception combinations specified in Bid Day Exception Template ancillary data are considered in timekeeping. If not selected, exception combinations from FX are used. Exception combinations are sets of trips that operate only on specific days. | |
| Specifies the pay code group used for custom timekeeping logic. | |
| Specifies whether pay time can be adjusted before posting. | |
| Specifies the work cost order. | |
| If selected, Extra Pay Types that require approval must be approved when considered by costing. | |
| If selected, Reference Details are added as a Summarize By option on the Weekly Timekeeping Summary Context. | |
| If selected, when a user manually changes a timekeeping entry for an employee, the employee's timekeeping records for that pay period are frozen. They are protected from costing. | |
| If selected, if any transactions are frozen for an employee/date, costing for that employee/date is skipped. Otherwise, the records will be unfrozen and costed. | |
| If selected, if any transactions are frozen for an employee/date, prior pay costing for that employee/date is skipped. Otherwise, the records will be unfrozen and costed. | |
| Addresses the setting of the Employee Day Type for February 29 during non-leap years. You can choose from two options as to which date the Birthday Holiday is applied on a non-leap year: Day Before and Day After (default). If you select Day Before, the date is February 28, and if you select Day After, the date is March 1. | |
| If selected, there would be no hierarchy processing when determining the absences that will be costed. | |
| If selected, operators performing hold downs inherit the bid units of the operators they are relieving. | |
| If selected, operators performing vacation relief inherit the bid units of the operators they are relieving. | |
| If selected, Vacation Relief operators added to the Extraboard list will assume the Extraboard Bid Unit associated with the list for timekeeping calculations. | |
| If selected, the system loads work for all divisions when costing. | |
| If selected, if the holiday bid status is EB and there is no bid work for the holiday. the bid status will be reset to no bid. | |
| If selected, the EB employee bid status s determined using bidding information. | |
| If selected, if the holiday bid status is H-D and there is no bid work for the holiday, the bid status will be reset to no bid. | |
| Selecting this property prevents duplicate timekeeping entries when costing multiple days with split PASS runs. | |
| If selected, absences are ignored when processing Piece Intervening Rules.
The property is unselected by default. |
|
| Specifies the piece intervening rule. When costing, specifies whether to treat the piece as Piece One or Piece Two. | |
| Specifies the costing order for timekeeping calculations. Available values are SignOn Time, Bid Work then SignOn Time, and Published Work then SignOn Time. | |
| If selected, if an employee's absence records have changed, the employee is flagged for recosting. | |
| If selected, if an employee's accrual balance records have changed, the employee is flagged for recosting. | |
| If selected, if an employee's bidlinework has changed, the employee is flagged for recosting. | |
| If selected, if an employee's bid unit has changed, the employee is flagged for recosting. | |
| If selected, if an employee's day off has changed, the employee is flagged for recosting. | |
| If selected, if an employee's relief work has changed, the employee is flagged for recosting. | |
| If selected, if an employee's status has changed, the employee is flagged for recosting. | |
| If selected, if an employee's demand response work has changed, the employee is flagged for recosting. | |
| If selected, if an employee's extra pay has changed, the employee is flagged for recosting. | |
| If selected, if an employee's pay grid has changed, the employee is flagged for recosting. | |
| If selected, if the employee timekeeping attribute has changed, the employee is flagged for recosting. | |
| If selected, if an employee's fixed route work has changed, the employee is flagged for recosting. | |
| Only employees who belong to this division group will be considered by the Prior Pay Adjustment Agent. If no division group is specified, employees from any division will be considered. | |
| If selected, Prior Adjustment logic will be invoked. | |
| If selected, when the agent flags a pay period as a Prior Pay candidate, the agent will also flag any subsequent pay periods as well (for that employee). | |
| If selected, the prior pay calculation will include any days already costed within the current pay period. This is only true if is also enabled. | |
| Specifies the time interval between logging potential adjustment records. | |
| This is the maximum number of prior pay weeks that will be considered when identifying prior timekeeping adjustments. | |
| This value represents the number of prior days (from today) that will not be considered by the Prior Pay Adjustment Agent. | |
| If selected, when selecting a record and clicking Reverse Transaction a new record is created with the same pay code, employee and date information as the original record. The new record will have a PriorPayAdj of 1 and a PayTime that is the negative of the original record's PayTime value. The SourceID of the new record is the PayID of the original record. | |
| If selected, the Absence time is split between the Max eligible balance and the remainder time when costing Absence Pay Rules that are set to check eligible balance through an Accrual Hierarchy configuration. | |
| Specifies the rounding method used after each biweekly rule is calculated. | |
| Specifies the rounding method used after each daily rule is calculated. | |
| Specifies the pay code group used for final rounding exclusions. | |
| If selected, timekeeping records will not be rounded to the nearest minute when persisted during calculate timekeeping. | |
| Specifies the rounding method used after each piece rule is calculated. | |
| Specifies the rounding method used after each weekly rule is calculated. | |
| Specifies whether timekeeping records are filtered by pay codes or payroll codes. | |
| Specifies a weekly processing date (week ending date). The value can be agency dependent. | |
| If selected, a two-week grid appears in the Weekly Timekeeping Summary screen. | |
|
If selected, pay week information is shown for employees with a matching bid unit on any day in the pay summary period. If cleared, pay information is shown for employees whose bid unit matches on the Start Date defined in the screen Context. This property is used for the Weekly Timekeeping Summary and Weekly Timekeeping Activity Summary screens. |
|
| If selected, Pay Amount Only Pay will be displayed separately in the Weekly Timekeeping Summary screen. | |
| If selected, a period adjustment column appears in the Weekly Timekeeping Summary screen. |