Organisation | Entitlements | Allowances | Action Clauses tab
Summary |
PayGlobal can perform additional actions when an allowance code is processed. For example, a warning message could appear whenever an allowance is used. Award rule action clauses are evaluated before allowance action clauses. In Daily View, if you use Process Actuals to generate an allowance based on allowance action clauses, then the generated allowance does not use the rate in the original allowance. The rate in the generated allowance is based on the standard PayGlobal hierarchy, so the allowance uses the rate code and rate amount. If the allowance does not have a rate code or rate amount, then it uses the employee's default rate and rate amount. |
"applying to" parameter |
The "applying to" parameter allows you to determine whether PayGlobal applies transactions to the start of the day or to the end of the day. It appears when you use the following fields in an action clause:
The "applying to" parameter contains the following options:
You can use these clauses to allocate the following values to a transaction:
|
Fields |
The Action Clauses tab | Fields list includes the following options:
These options allow you to customise the costing process in the allowance action clauses. PayGlobal uses these action clauses for Roster or Actuals processing with the following conditions:
Example - "Remainer to"PayGlobal uses rules when it processes Rosters or Actuals. You can define award rules in the award, but allowance rules are defined in the allowances attached to the award. An allowance rule defines actions for transactions that are based on the allowance. In this example, the Z.001 40 D allowance contains the following action clauses: Daily maximum of 7 applying at the start of the day Remainder to "Z.002WCA" These action clauses check all Z.001.40D allowance records. If the employee's total Quantity values is greater than the daily maximum of "7", then processing creates a Z.002WCA transaction for the remainder. For example, if the Quantity total was "10", then processing would create a Z.002WCA transaction with Quantity = "3".
Example - "Merge Remainder's CostCentreCode"The Merge Remainder's CostCentreCode action clause merges the following values:
In the merge process, Allowance.CostCentreCode has a high priority than Transaction.CostCentreCode. This action clause ignores the following:
For example:
In this example, the Z.001 40 D allowance contains a Remainder to action clause so you can add a Merge Remainder's CostCentreCode action clause: Daily maximum of 7 applying at the start of the day Remainder to "Z.002WCA" Merge Remainder's CostCentreCode
Example - "Costing Remainder according to rank"The Costing Remainder according to rank action clause uses the costing set up in Company Settings. However, this action clause has the following limitations:
In this example, the Z.001 40 D allowance would have the following action clauses: Daily maximum of 7 applying at the start of the day Remainder to "Z.002WCA" Costing Remainder according to rank |
See also |