Organisation | Entitlements | Allowances | Action Clauses tab
Summary |
The following options in the Action Clauses tab | Fields list 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 |
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 these examples, the Z.001 40 D allowance contains the following action clauses:
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". |
Merge Remainder's CostCentreCode |
The Merge Remainder's CostCentreCode action clause merges the following values:
In the merge process, Allowance.CostCentreCode has a higher priority than Transaction.CostCentreCode. This action clause ignores any costing set up in Company Settings, and Allowance table | Cost Centre Calculation, unless Allowance | CostCentreCode is not empty. 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. |
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:
|
See also |