Entry via Single Screen

This is one of the most frequently used screens in Preceda, primarily for data entry before a payrun.

To enter data for an employee or review pay calculation for this employee via Pay Enquiry drilldown, we must set up the Payrun Header first so that there is a valid Period End Date AND the payrun group and pay frequency included in the Payrun Header matches the setting per the employee.

Prerequisites

Rules and Guidelines

  • When an employee record is selected to enter data for the first time, the system automatically allocates the entry to the Standard Pay Slip ID.
  • When keying in negatives, the negative sign must be entered first.
  • The window is divided into two sections, Hours/Leave and Allowances/Deductions.
  • If the payrun is in progress, Pay Enquiry may appear without any entries depending on whether the Calculate Payrun or Update Payrun process has been completed.
  • The Pay Journal Enquiry wizard can be used to view an online payment after the payrun has commenced and if the Calculate Payrun or Update Payrun has been completed.
  • Note that Pay Enquiry does not invoke any retrospective calculation.
  • A warning will be provided if an A/D code is entered into Entry via Single screen and the:
    • A/D code start date is after the current Period Start Date, or
    • A/D code end date is before the current Period Start Date.
  • When Position 23 of Program Control PAY29 is set to Y, the Time Card Entry of fortnightly employees who are under 18 years of age (U18) will be calculated on a weekly basis. The fortnightly U18 employee will have a Pay Frequency of F and will be attached to an SGC Rules Code.
  • Hours worked for fortnightly U18s will be keyed into Entry Via Single Screen for each week separately or through batch upload.
  • Costing override entered on Entry via Single Screen will be applied regardless of any other settings.
  • For time-sheet transactions:
    • If the Costing Date is entered on Entry via Single Screen, this will be the Costing Date.
    • If the Costing Date is NOT entered on Entry via Single Screen, the Costing Date will be the last day of the pay period.
    • If the employee is terminated and the Costing Date is after the termination date, it will use the costing effective as the termination date. However, if the employee is terminated, it will use the termination date.
  • The Costing Date may be used to identify payments that relate to a period previously paid.

  • For Retrospective Payments due to Rate increases, the Retrospective Pay process transactions generated on this screen will have the Costing Date set to the Effective Date of the Pay Period they relate to.

  • For Retrospective Payments due to Hours or Allowances/ Deductions missed from a prior period, the Costing Date needs to be manually entered on this screen to reflect this. Note that in this scenario, the Costing Date could be any date in a prior period. The relevant period ending date will need to be determined by looking at the employee's Earnings History records to see which period the date fits into.
    • If the Costing Date is an exact match with a Period End Date found against any existing Earnings History record, this is the date displayed on the Pay slip.

    • If the Costing Date does not match a Period End Date found against any existing Earnings History records, the first Period End Date found after this date is displayed on the Pay slip.

  • Hours Type Codes only allow a maximum entry of '99999.9999' value in the Rate field so multiple Units are required.
  • Since there are no Base Hours per employee role, Auto Pay is not applicable for employee roles. To pay an employee against roles, enter the transaction with the Role specified so that the corresponding role salary rate and role costing information can be used for pay calculation.

    • If no employee role salary rate is found effective as at the Period End, pay calculation will use the employee's non-role salary rate.

    • If no employee role costing is found effective as at the Period End, pay calculation will use the employee's non-role costing structure.

    • If there is a Costing Date provided per the transaction, Costing Date will be used to find the effective (role) salary rate and (role) costing for pay calculation.

  • In the Hours/Leave browselist, when a Leave Hours Type Code is selected, the transaction must have a Date From and a Date To.

Field Information

 

Hours/ Leave Browselist

When modifying or deleting a record on the drill-down window, a Warning Message will pop up. You can either continue to save your changes via ticking the declaration box, or cancel the update and create a new Code instead. For more information and a list of areas to consider when creating a new Code, see this Page.

 

Allowances/ Deductions Browselist

When modifying or deleting a record on the drill-down window, a Warning Message will pop up. You can either continue to save your changes via ticking the declaration box, or cancel the update and create a new Code instead. For more information and a list of areas to consider when creating a new Code, see this Page.