Public Holidays

This window allows you to define Public Holidays. This enables the automatic posting of Public Holiday Payments to employees paid by the Auto Pay facility.

Prerequisites

• Hours Type Codes with a Classification of P
• Level Codes 1 (Company) as a minimum

Rules and Guidelines

• When setting up Public Holidays for Labour Day, a separate record is created for each state, where Labour Day falls on a different date for each state.
• Each Public Holiday is defined with a date containing the day, month, and year.
• Public Holidays must be defined each year.

• When the employee applies for a leave via ESS My Leave (desktop version and mobile version), My Leave (desktop version and mobile version), the system works out how many hours of that leave application should be Public Holiday hours. When the date is set to be a partial public holiday, the proportion will be applied to the employee's scheduled hours to work out the Public Holiday hours.

• If Public Holiday details are defined an Hours Type with 'P', Hours Classification must be setup. The system always uses the first P classification code it finds when outputting the hours, so even if multiple Classification P codes are set up, the system only ever uses the first one it finds.

• When referenced in TIME rules, TIME module works out how to interpret employee's time recording.

• Records can be cloned.

• When saving any change made to the Days field, or deleting a Public Holiday record, a Warning Message will pop up on this screen alerting you of the possible impact to retrospective entries for employee records containing the corresponding Public Holiday.

  Since modifying or deleting a Public Holiday record may unintentionally affect retrospective calculations, this Warning Message validates what you intend to do, whether to:

  1. Continue with the change via ticking declaration tick-box. This confirms that you understand that the configurations you made will be used for past, present, and future transactions that may trigger retrospective entries to be generated for employees having the corresponding Public Holiday record; or
  2. Cancel the change/ deletion.
• The same date can be setup with different Costing structures as Public Holidays. When this happens, the product picks up Public Holidays in below logic:

  • In Leave Application, find the exact match in Costing structure:

    • first, if found, use this PH;

    • if not found, use the PH matching the greatest Costing Level and whose smaller Costing Levels either match or left blank;

  • In auto-pay calculation, all PH matching the Costing structure are used, including those non-exact match, i.e. with some Cost Levels left blank.

    Examples:

    • Public Holiday setup in the product:

    Date	Days	Costing Level 1	Costing Level 2	Costing Level 3
    24/12/2021	0.10	A1
    24/12/2021	0.20	A1	A2
    24/12/2021	0.30	A1		A3
    24/12/2021	0.40	A1	A2	A3
    24/12/2021	0.50	A1	B2

     

    • Public Holiday picked up per employee:

    Employee ID	Costing Level 1	Costing Level 2	Costing Level 3	PH Picked up in Leave Application	PH picked up in Auto Pay
    100000	A1	A2	A3	0.40	0.10, 0.20, 0.30, 0.40
    100001	A1	A2	B3	0.20	0.10, 0.20
    100002	A1		A3	0.30	0.10, 0.30
    100003	A1	A2		0.20	0.10, 0.20
    100004	A1	B2		0.50	0.10, 0.50
    100005	A1			0.10	0.10

     

Field Information