Fields list

The Action Clauses tab | Fields list includes the following options:

• Merge Remainder's CostCentreCode
• Costing Remainder according to rank.

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:

1. You must use a Remainder to action clause before using Merge Remainder's CostCentreCode or no action will occur.
2. If you use Costing Remainder according to rank, then the Allowances | T&A/RS (i) | Cost Centre calculation field must be "Calculated".
3. The Costing Remainder according to rank action clause:
   • Does not implement proportional costing.
   • Implements only the Allowance rank on the Company Settings | CostCentre - Timeband Rank tab because the Remainder record is not connected to timebands.

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:

• Allowance table | CostCentreCode
• CurrentActualAllowance or CurrentRosterAllowance table | CostCentreCode.

In the merge process, Allowance.CostCentreCode has a high priority than Transaction.CostCentreCode.

This action clause ignores the following:

1. Any costing set up in Company Settings.
2. Allowance table | Cost Centre Calculation, unless Allowance table | 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:

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:

1. It will not implement proportional costing.
2. It implements only the Allowance rank on the Company Settings | CostCentre - Timeband Rank tab because the Remainder record is not connected to timebands.
3. The Allowances | T&A/RS (i) | Cost Centre calculation field must be "Calculated".

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

Topic: 31379