Action Types and Processing Rules

When you manually enter an instance of positive input, you select an action type that tells the system how to process the instance. You can select from the following action types:

  • Override

  • Add

  • Do Not Process

  • Resolve to Zero

A brief explanation of each action type follows.

Override

When you enter positive input with the action type of Override, you can enter an amount that overrides the calculation rule for the instance of the element or enter a value for components of the element's calculation rule: rate, unit, percent, or base. (If the calculation rule is defined as amount, you can enter only an amount.)

Suppose that you define an earning code as a flat amount of 100 EUR. You want to give the payee 90 EUR instead. You enter the amount of 90 EUR on the Positive Input page, specifying the action type as Override. The system overrides the definition amount of 100 EUR that is resolved, and the payee receives 90 EUR.

Add

When you enter positive input with the action type of Add, the system processes the normal resolution of the element based on the element definition or instructions entered on the Element Assignment By Payee page or the Payee Assignments by Element page, if any. In addition, it processes the element again based on the values that you enter in positive input, resulting in multiple occurrences.

Suppose that you define an earning code as a flat amount of 100 EUR. You want to give the payee an extra 50 EUR. From a data entry standpoint, the administrator enters the additional 50 EUR on the Positive Input page, specifying the action type as Add. The system processes the definition amount of 100 EUR and then resolves the additional amount of 50 EUR, so that the payee receives 150 EUR.

Do Not Process

When you enter positive input with the action type of Do Not Process, you prevent the system from processing this element for the payee when calculating the calendar. No result is written to the result table.

Do Not Process instructions apply to all instances of positive input for the element—manual or system-generated—in all segments and slices of the calendar, unless you enter an end date (on the Other Data page), which enables you to limit the instructions to instances that fall in the same slice or segment.

Suppose that instance 1 has an action type of Do Not Process, and that instance 2, for the same element, has an action type of Override. If you don't enter an end date for instance 1, the Do Not Process instructions apply to both instances and neither is processed.

Resolve to Zero

When you enter positive input with the action type of Resolve to Zero, the system resolves the instance of the earning or deduction with a value of 0.

Unlike Do Not Process , Resolve to Zero writes an amount of 0 to the results table, making a zero amount on the payslip possible. Also, Resolve to Zero instructions do not affect any other instances.

Rules for Mixed Action Types

The following rules apply when positive input occurs with mixed action types within a segment:

  • Where positive input entries are a combination of Add and Override action types, the system does not resolve the element definition because of the presence of the override entry.

    Instead, the system processes all positive input entries with action types of Override and Add in this order (hierarchically): first the entry with an action type of Override, then the entry with an action type of Add.

    Suppose that E3 is a flat amount of 100 USD. You create two positive input entries, one (instance #1) with an Add action type for 30 USD and one (instance #2) with an Override action type for 200 USD.

    Despite the presence of what could be considered conflicting action types, the system processes both entries, regardless of the order in which you enter them. The system processes the entry with an action type of Override first and creates a row for 200 USD on the earning/deduction result table. Then the system processes the entry with an action type of Add and creates a row for 30 USD on the earning/deduction result table.

    The result is that the payee receives 230 USD for E3 with two rows on the earning/deduction result table. The system does not resolve the element based on its rule definition.

  • Regardless of the combination of action types, the presence of an entry with an action type of Do Not Process always overrides any other positive input entries for that segment.

    In other words, the system processes nothing for the element. The Do Not Process value supersedes all action types.

  • The action type Resolve to Zero affects only the current positive input instance.

    Where the action types of Override, Add, and Resolve to Zero are combined, the system processes all entries.

    Suppose that E4 is a flat amount of 500 USD. You create three positive input entries with the following attributes:

    • Action type of Override for 700 USD.

    • Action type of Resolve to Zero.

    • Action type of Add for 300 USD.

      The end result is that the system processes all three positive input entries and the payee receives 1000 USD for E4 with three rows (instances) in the earning/deduction result table. The system does not resolve the element through its definition. Also, the system creates a row with a result amount of 0.

Related Topics