Organisation | Common Reasons | Reasons | Details (ii) tab
Procedure |
These settings are not compulsory. You may customise them according to your needs but they are provided as a general guide. The following table gives the standard settings for the fields on this page for general use and for if you want to create a Break Reason code.
|
Reasons used in Award Rules |
If the following fields are set to Yes, PayGlobal uses the flags as Timeband clauses in the Award Rules:
The 'Payroll type' is also used in the Award Rule Timeband clauses. |
Displaying the reason code in Actuals |
If the following fields are set to Yes, PayGlobal displays the Reason code in employee Actuals:
|
Using Reasons in PayGlobal Rostering |
If the following fields are set to Yes, PayGlobal uses the Reason code when processing rostering requirements:
|
Include hrs for break calc |
This field is used in conjunction with the Relative Breaks.
|
Payroll type |
This field allows you to group timebands in Time & Attendance.
You can use these payroll types to group leave. For example, you could use "Extra" to group long service leave and overtime. Important: Pay attention to how you group timebands. This will affect the total in a customised column in Daily View that you have set up to total transactions based on payroll types. |
Flag Absent Clock Result |
This field determines the timebands that come through to Actuals when running results. It is used when you have a roster, but no Actuals. PayGlobal marks only those timebands with an 'AB' clock result code if there is either no Reason code for the day or a Reason code has 'Flag Absent Clock Result' as Yes. |
Is available |
This field is used when determining the suggested placements for a Requirement. It is generally set to No. If set to Yes, employees with timebands with this Reason code are included in the suggested placements for a Requirement. For example, if an employee has the following timeband: Start 0800 End 1700 Reason ONCALL Clients would usually want this employee to show as a suitable candidate for a shift requirement and would set the 'Is available' field to Yes for the ONCALL reason code. Note that the 'On-call Y/N' does not impact on whether the employee is displayed in suggested placements. |
Include in allocation |
This field is used to determine which employees are viewed when you double click Allocated in Allocation View. It is generally set to No. This field would be set to Yes if you use reason codes for timebands that are still working time, and you want to include these timebands in the list of Allocated employees. For example, if an employee has the following timeband: Start 0815 End 1700 Reason LATE and 'Include in allocation' was set to Yes, then this employee would show as Allocated to a requirement, even though they were late. Additional uses This field is also useful if you want to display employees when a user double- clicks Allocated, but you not want to have them included in the number actually allocated to a requirement. For example, if an employee is sick. If you double-click Allocated, you can see the employees that are allocated as per normal. By setting the 'Include in allocation' to Yes on the SICK reason code, when you double-click Allocated, Daily View will display employees who are working the requirement and are on sick leave. The total allocated employees will still be just those that are working. The number will not include those that are on sick leave. |
See also |