Time Details

• For Effective Dating, the values are attached to a unique period of time to create a unique costing effective dated record.

• An "Effective Date" or "as of date" is the date when something is considered to take effect. This may be different from the date upon which the event actually occurred or has been recorded.

• The Effective Date field on the Toolbar allows you to view and select effective dated records available.

• Clicking Change on the Toolbar allows you to update/ edit the information on this screen, with the current values being displayed.

• A second level of Toolbar will be made available once Change has been selected. The From and To fields allow you to setup the new effective dated record via Date Picker. Setup the start date of the effective record using From while determine the date the record will become inactive using To. You may identify the reason of updating the effective dated record via Change Reason.

• To create a new record, click Change, and the second level Toolbar will be displayed with the From date field automatically populated with the date the system first had the Time Details setup in Preceda for the employee (this may not be the actual date that the employee has been on the record) and the To date field with '31/12/9999' (or if future records exist, next record From date - 1 day) displayed as read-only (Effective Dating 1). If the record being looked at is a past or future record, it will default to that record set From and To dates.

• You may create a new future effective record by modifying the date in the From date picker to a date in the future, and changing the information in the form (Effective Dating 2).

• It is not possible to create a new effective dated record prior to the employee Hire Date.

• All fields on the this screen will become active and apply at the Start Date; however, the pay period rule that is effective at the pay period's End Date will be applied to the whole pay period (i.e. in relation to the Pay Period Rule which cannot be pro-rated).
  Example:

  If the pay period is from '14/03/2016' to '27/03/2016' and new Daily and Pay Period rules had been added with a from date of '18/03/2016', the Daily Rule will be applied to daily transactions from the 18th but the Pay Period rule that became active on the 18th will be applied to the whole pay period ('14th' to '27/03/2016'). This will be the same for both the current pay period and any retrospective calculations.

  When a Daily Rule is retrospectively applied to the current pay period (e.g. Pay Period is '14/03/2016' to '27/03/2016' and the change to the Daily Rule was made on the 20th but dated '14/03/2016'), any transactions already interpreted would be automatically re-interpreted with the new Daily Rule.

• If any data was changed part way through a period, and has a from date where data has already been entered by any means (e.g. Time Editor, ESS, etc), then this will be applied to the data already in Preceda.
  Example:

  If the pay period is from '14/03/2016' to '27/03/2016' and new Daily and Pay Period rules had been added with a from date of '14/03/2016' was keyed in on the 18th, then the rules already in Preceda from the 14th to the 17th would be re-interpreted when the next lot of data was entered or if the Pay Period Recalculation process is run for the current period.

• Where existing files have Effective Dating added, the Effective Date will not be Mandatory in the Mapper Upload. This is to allow existing customers, with interfaces already in place, to continue to use the system without having to make changes to their interfaces.

• Click Effective Dating for more information on the effective dating functionality.

This displays the standard pay Period Rule to apply to this employee. To change an item in this field:

• Set the End Date of the current record.
• Click the 'Clone' option.
• Make the adjustments and then 'Save' the record.

 

This displays the standard Daily Rule to apply to this employee. To change an item in this field:

• Set the End Date of the current record.
• Click the 'Clone' option.
• Make the adjustments and then 'Save' the record.

 

This defines if the employee usually punches in and out for meals and breaks, or only at the beginning and end of a shift.

Code	Description
Y	The employee will punch in and out for meals and breaks. Do not automatically deduct time for meals or breaks.
N	Automatic meal and break deductions are used as specified in the Daily Rules.

• If the employee punches for meals and breaks, the Daily Rule determines if a meal or bread deduction is made.

 

This displays the employee's badge number.

• If using badges, each current employee must have a unique badge number (i.e. this is a numeric only field).
• The time clocks use this number to link an employee to their punches, so if an employee is clocking but not using badge numbers, this field should be the employee's ID Number.
• This field becomes mandatory if the Using Badges field is set to Y on the Configuration screen.

 

This displays the schedule to be applied to this employee.

• The Schedule, Pay Period Rules and Daily Rule together determine methods of rounding and grace periods for the employee.

 

This is an optional feature that may be used to prevent employees from punching at unauthorised times.

• The restriction record controls how Preceda processes each punch, whether it accepts the punch and to which roster to apply it against.

 

This defines if the defined schedule is rolled forward during the Pay Period Processing.

Code	Description
N	Do not roll any primary roster information forward
T	Roll Roster Transfers IN ADDITION to the primary roster
Y	Roll ONLY the primary roster forward

 

This displays the number of days to roll schedules forward.

• The number of days must be equal to or greater than, the number of days in the employee's pay period.

 

This displays the group that is to be the default Group for the employee.

• The Group Code may be used as a criterion or various other processes within Preceda Time, e.g. to be used to select which employees to be passed to Payroll etc.

 

This displays the Shift Code required.

• e.g. Can be used for reporting or interface purposes.
• This code can be used as an extra means of categorising employees for reports and other processes in Preceda Time.

 

The Default Elapsed Hours Start Time will populate the "Start Time" field on the Elapsed Time Entry window when using that function. It may be left blank as it is not a mandatory field. If left blank, when using the Elapsed Time Entry window you will need to enter a Start Time.

This displays the time zone in which the employee is located.

This field is used by the Scheduled Not Clocked in report.

Code	Description
21	Western Australia, Northern Territory and South Australia
22	Queensland, New South Wales, Victoria, ACT and Tasmania
23	New Zealand

 

This links the employee to a Time Monitor Rule.

• These rules are used to assist in the monitoring of the number of hours an employee works over a specified number of pay periods and measure the results against a given number of base hours.
• When the Time Monitor Update or the Time Monitor option in Daily Processing is run, reports are produced to assist with the scheduling of work hours for employees.

 

This holds the date on which the first day of the employee's Time Monitor or Rule cycle is based.

• When the Time Monitor Update process is run, this date is used to locate the date on which the employee's pay cycle started.
• If this date does not coincide with the start date of a pay period, the first period is calculated on the date the cycle falls.
• Reports will include the hours for the whole pay cycle.

 

Identify the Time Clocks that the employee is allowed to use to punch times.

There are up to 10 Time Clocks that the employee is allowed to punch times.

• Wild Cards can be used to extend the number of clocks that an employee can punch times.
• An asterisk (*) is used as the wild card.
  Example:

  If CL* is entered, the employee can punch times at any clock that has been identified as starting with CL.

  If *123 is entered, the employee can punch times at any clock that has been identified as ending with 123.

  If * is entered, the employee is assigned to all possible clocks.