Setting Up Overrides

This chapter provides an overview of overrides and discusses how to:

• Define pay entity overrides.

• Define pay group overrides.

• Define payee overrides.

• Define pay calendar overrides.

• Define overrides through elements.

• Define element definition overrides.

• Define overrides with positive input.

• Manage interactions between element definitions, positive input entries, and element assignment overrides.

• Generate complementary rules instances.

• Resolve overrides in batch processing.

Understanding Overrides

This section lists common elements used in this chapter and discusses:

• Override levels.

• Overrides available for primary elements.

• Overrides available for supporting elements.

• Begin and end date logic for overrides.

• Element overrides and segmentation.

Use overrides to control the values the system uses to resolve an element for a specified time period. When you run the payroll or absence process, the system retrieves the rule definition for the element and applies any override instructions that you've entered.

Common Elements Used in This Chapter

Override Levels

Before entering instructions to override an element, you must specify the types of overrides allowed for that element by selecting the appropriate check boxes in the Override Levels group box on the Element Name page.

When you enable overrides for a supporting element, deselect the Always Recalculate check box on the Element Name page. Otherwise the system uses the value of the element according to the element definition, not the override value.

Note. An additional level, payee calendar overrides, exist for supporting elements through the Off-Cycle Requests component. This level is available for off-cycle requests only and does not extend to on-cycle calendars. Before entering supporting element overrides on the Payee Calendar SOVR page, you must select the Payee and the Calendar check boxes in the Override Levels group box on the Element Name page for the supporting element.

See Making Additional Payments.

See Also

Defining Element Names

Overrides Available for Primary Elements

Several override levels enable you to control the value of earning, deduction, absence take, and absence entitlement elements, which the system applies in this order:

1. Payee overrides.

   At the payee level, assign or disable an earning, deduction, or absence element or override the definition of an earning, deduction, or absence element.

2. Pay calendar overrides.

3. Via element overrides.

4. Positive input overrides.

Overrides Available for Supporting Elements

Eight override levels enable you to control the values of brackets, dates, duration, formulas, and variables:

• Pay entity overrides.

• Pay group overrides.

• Payee overrides: Override the value of a bracket, date, duration, formula, or variable element whenever it's resolved for the payee.

• Payee/Element overrides. Overrides the value of a variable used by a specific earning or deduction assigned to a payee.

• Pay calendar overrides.

• Via element overrides.

• Element definition overrides.

• Positive input overrides.

When the system encounters multiple overrides for a supporting element, it applies the overrides in the sequence illustrated below, beginning with pay entity overrides.

Element override hierarchy

Note. A payee/element override refers to the override of a variable element associated with a particular earning or deduction for a payee. Enter such overrides on the Element Detail page, linked to the Payee Assignment By Element and Element Assignment By Payee pages. A payee override is the override of a bracket, date, duration, formula, or variable associated with a payee. Enter such overrides on the Payee Supporting Element Overrides page.

Example

VARIABLE1 has the following values:

• 30 according to the rule definition.

• 20 according to a pay entity override.

• 10 according to a pay group override.

In this case, VARIABLE1 resolves to 10, because pay group overrides take precedence over pay entity overrides.

Begin and End Date Logic for Overrides

When entering override instructions, you must specify a begin date.

The begin date tells the system when to start applying the override instructions. The current date is the default.

In most cases, end dates are optional. They specify when the override instructions become inactive. They are required only when you enter multiple rows of instructions for the same element.

The processing rules for begin and end dates vary, depending on the type of override being processed.

Payee Overrides and Segmentation

This section discusses:

• Payee overrides and segmentation.

• Segmentation caused by payee overrides

• Proration and segmentation in the case of payee overrides.

Payee Overrides and Segmentation

You can set up your Global Payroll system to slice or segment pay periods due to changes in Human Resource or other data, including:

• Changes in job status or title that occur in mid period.

• Departmental transfers that occur in mid period.

• Changes in compensation rate that occur in mid period.

If there is a payee override in a sliced or segmented period, the system applies the override to the different slices/segments based on the segment/slice end dates as well as the override's end date.

The system follows these rules to determine the slices or segments to which to apply an override:

• If an override is to apply to a segment, the end date of the override must equal or be greater (or blank) than the end date of the segment.

• An override can apply to more than one segment if the end date of the override is greater than one segment's end date and greater than or equal to the subsequent segment's end date (or blank).

• If the end date of the override is less than the end date of the segment, the override doesn't apply to that segment.

• Payee overrides must be Active as of the segment end date.

Pay entity, pay group, and element definition overrides are unaffected by segmentation. The system retrieves the definition of the element and the override only once every period, regardless of period or element segmentation.

Note. We discuss the rules for applying overrides to slices/segments in a period in greater detail in the chapter on segmentation.

See Setting Up Segmentation.

Element Segmentation Caused by Payee Overrides

As noted previously, you can set up your Global Payroll system to slice or segment pay periods due to changes in Human Resources or other data. However, you can also configure the system to initiate segmentation and proration directly in response to an override—in the absence of any other data changes. That is, you can configure the system so that overrides are themselves treated as data changes that trigger segmentation. Then, when you assign or override the value of an element, the system slices the assigned element and any other elements included in the segmentation element list based on the begin and end dates of the override.

For example, assume that you set up the system to trigger element segmentation when you assign or override earning element E1, and that you assign E1 to a payee on the Element Assignment by Payee (GP_ED_PYE) component with begin and end dates of 10 and 20 June respectively (assume a monthly pay period). Based on the assignment/override begin and end dates, the system will slice the element into three segments and process (and prorate) the element in the second slice:

Note. The only type of segmentation that can be triggered by an element assignment or override is element segmentation.

To set up the system to trigger segmentation in response to an element assignment:

1. Select the Active Anytime Within Segment option on the Countries (GP_COUNTRY) component .

   When you do this, the system processes all element assignments/overrides that fall within a period—even those with end dates that are less than the pay period end date.

   See Defining Installation Settings.

2. If you want the element you are assigning to be prorated, associate the element with a proration rule on the earning or deduction definition pages.

   See Defining Rounding and Proration Options for an Earning Element.

3. Set up segmentation triggers for the begin and end-dated earning and deduction assignment record (GP_PYE_OVRD), and list the earnings and deductions that should trigger element segmentation when the assignment begin date comes after the pay period begin date, and/or the assignment end date comes before the period end date.

   See Setting Up Segmentation Triggers for The Begin and End-Dated Earning and Deduction Assignment Record (GP_PYE_OVRD).

Proration and Segmentation in the Case of Payee Level Overrides

Proration of payee level, primary element overrides occurs under the following conditions:

Note. Primary element overrides include earnings and deductions. Supporting element overrides include elements such as variables, formulas, arrays, and brackets.

• When period or element segmentation is triggered by data changes not directly related to an element override or assignment.

  • If there is period segmentation in the period to which an earning or deduction assignment applies (that is, all elements are segmented), the system prorates the assigned element based on the segment begin and end dates if the element is defined to be prorated. If not, the entire value of that element is applied to each of the targeted segments.

  • If there is element segmentation in the period to which an earning or deduction assignment applies, the assigned element is included in the list of elements to be sliced, and that element is defined to be prorated, the system prorates the element based on the slice dates. If not, the entire value of the element is applied to each of the targeted slices.

• When you configure your system so that primary element overrides or assignments directly trigger element segmentation.

  In this case, the system slices the assigned element (and any elements associated with that element on the element list) based on the begin and end dates of the assignment as long as that element is defined to be prorated. There does not have to be slicing or segmentation for any other reason. If the element is not defined to be prorated, the full value of the element is processed within the slice defined by the assignment begin and end dates.

  Note. You can set up the system to slice an element within a pay period based on the begin and end dates of the overrides assigned to a payee on the Element Assignment by Payee (GP_ED_PYE) and Payee Assignment by Element components (GP_ED_ELEM). We discuss how to do this in the chapter on trigger definitions.

  See Setting Up Segmentation Triggers for The Begin and End-Dated Earning and Deduction Assignment Record (GP_PYE_OVRD).

Note. Primary element overrides are prorated if the element is defined to be prorated and there is either period segmentation (all elements are segmented), or there is element segmentation and the element being assigned is on the list of elements to be sliced.

In the case of supporting element overrides, the supporting element is prorated if it is a component of an element that is defined to be prorated and that element is segmented/sliced.

Defining Pay Entity Overrides

This section provides an overview of processing rules for pay entity overrides and discusses how to override the value of supporting elements that are associated with a pay entity.

Understanding Processing Rules for Pay Entity Overrides

During processing, the system refers to the begin and end dates (if any) and the Definition as of Date (Use Defn As Of) that were defined for the element on the Element Name page.

For the override instructions to take effect:

• The begin date must be before or equal to element's Definition as of Date.

• The end date must be greater than or equal to the Definition as of Date.

Example

VARIABLE1 is defined as follows:

• Definition as of Date = Calendar Period Begin Date.

• Value = 100.

• Pay Period = January 01, 2004 - January 31, 2004.

The following pay entity override exists:

• Begin Date = January 16, 2004 (no End Date).

• Value = 200.

Payee 1 has segmentation on January 10, 2004. Payee 2 has no segmentation.

Both payees have the same value for VARIABLE1. Payee 1's segmentation doesn't alter the value of VARIABLE1.

In the diagram, the pay entity supporting element override is not applicable to either payee, because it wasn't applicable as of the VARIABLE1 Definition as of Date (Calendar Period Begin Date), resulting in a value of 100 for both payees.

If the Definition as of Date for VARIABLE1 is Pay Period End Date, both payees use the pay entity override value 200.

Processing rules for pay entity overrides example

Page Used to Define Pay Entity Overrides

Overriding the Value of Elements That Are Associated with a Pay Entity

Access the Pay Entities - Supporting Element Overrides page (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Framework, Organizational, Pay Entities, Supporting Element Overrides).

To define a pay entity override on the Pay Entities - Supporting Element Overrides page:

1. Select the type and name of the supporting element for which you want to enter override instructions.

2. Enter the override begin and end dates.

3. Enter the override value on the Values tab.

Defining Pay Group Overrides

This section provides an overview of pay group overrides and lists the page used to define pay group override.

Understanding Pay Group Overrides

To override the value of supporting elements that are associated with payees in a specific pay group, you use the Pay Groups - Supporting Element Overrides page. This page is similar to the Pay Entities - Supporting Element Overrides page, as are the processing rules.

Page Used to Define Pay Group Overrides

See Also

Overriding the Value of Elements That Are Associated with a Pay Entity

Defining Payee Overrides

This section provides an overview of payee overrides and processing rules for payee overrides, and discusses how to:

• Assign and disable earnings and deductions by payee.

• Assign and disable earnings and deductions by element.

• Override component values, generation control, frequency, arrears, and variables for a payee.

• Override supporting element values for payees.

Understanding Payee Overrides

Payee overrides enable you to control how an earning or deduction element is resolved for a specific payee.

Payee Override Uses

Using payee overrides, you can:

• Assign or disable an earning or deduction element for a payee.

• Override the component values defined for an earning or deduction element assigned to a payee, or override the defined frequency, generation control, payback type, or arrears payback amount.

• Override variable elements used by a specific earning/deduction assigned to a payee.

• Override a variable for all elements that use the variable (not just one earning or deduction assigned to a payee).

• Override supporting elements associated with a payee.

Payee Override Methods

There are two ways to enter overrides for a specific earning or deduction assigned to a payee:

• By assigning, disabling, and overriding elements by payee.

  To do this, you select a payee, and then assign the earning or deduction, or enter overrides for the payee's existing element assignments.

• By defining payee overrides by element.

  To do this, you select an element, and then assign it to a payee, or enter overrides for existing assignments of the element.

Using Payee Overrides to Trigger Multiple Resolutions

You can trigger multiple resolutions of an element at the payee level by entering multiple overrides with overlapping assignment dates for the same earning or deduction.

See Managing Multiple Resolutions of an Earning or Deduction.

Batch Updates to End Dates of Assigned Earnings and Deductions

Batch updates to the end dates of assigned earnings and deductions are governed by two system elements: SET ED END DATE and UNSET ED END DATE. The process by which the system updates end dates involves the following steps:

• For each earning and deduction assignment, the system checks the Allow Batch Update of End Date check box. If it is selected, the system checks the associated system elements.

• If the SET ED END DATE system element is on:

  • The system updates the Previous End Date field with the current value of the End Date field.

  • The system updates the End Date field with the date of the slice or segment that initiated the end date change.

  • The system updates the Updated in Payroll Run field with the ID and description of the calendar group that initiated the end date change.

• If the UNSET ED END DATE system element is on:

  • The system updates the Previous End Date field with the current value of the End Date field.

  • The system deletes the current value of the End Date field, leaving it blank.

  • The system updates the Updated in Payroll Run field with the ID and description of the calendar group that initiated the end date change.

These system elements work only within the context of the current earning or deduction being processed. Furthermore, PeopleSoft does not deliver a method to turn the SET ED END DATE and UNSET ED END DATE system elements on. Therefore, you should create a formula that turns these system elements on and attach it as a post-process formula to the earnings and deductions for which you want to update the end date. By defining the formula yourself, you can choose how your system determines the criteria for turning the system elements on.

For example, assume that you have a loan deduction that you want stopped when they payee to which it is assigned pays off the loan amount. In addition, you want the system to update the end date of the loan deduction to reflect the stoppage of repayment. To accomplish this you create a formula with the following parameters:

• Name of deduction: GXDDED01.

• Variable: GXVRED01. This value stores the loan amount (amount to be repaid).

• Variable: GXVRED02. This is a temporary variable that is used to store a temporary value during the processing of the formula.

• Accumulator: GXDDED01_CUS. This custom period accumulator stores the amount paid, to date, toward the loan amount.

Using these parameters, you create a formula with the following parts:

1. If the amount paid to date plus the current amount is less than the loan amount then exit. This part of the formula is expressed as:

   If (ac) GXDDED01_CUS + (sy) CURR AMT VAL < (vr) GXVRED01
   THEN
   EXIT
   

2. If the amount paid to date plus the current amount is equal to or greater than the loan amount, however, the system takes the amount paid to date plus the current amount and subtracts the loan amount. This is the amount that the system subtracts from the current amount to determine the amount to deduct. This part of the formula is expressed as:

   ELSE
   (ac) GXDDED01_CUS + (sy) CURR AMT VAL 
   – (vr) GXVRED01 >> (vr) GXVRED02
   (sy) CURR AMT VAL – (vr) GXVRED02 >> (sy) OVRD CURR AMT VAL
   (sy) OVRD CURR AMT VAL >> (formula name)
   1 >> (sy) SET CURR AMT VAL
   

3. Finally, because the condition was met, the system sets the end date:

   1 >> (sy) SET ED END DATE

Note. Setting or unsetting the end date occurs only during current periods and not during retro periods.

Warning! It is recommended that you not update end dates in batch if you manually maintain the end dates for a payees or elements. Using this feature overrides any manually entered values that are not available to the formula.

See Also

Overriding Component Values, Generation Control, Frequency, Arrears, and Variables for a Payee

Pages Used to Define Payee Overrides

See Also

Pages Used to Adjust Entitlements

Assigning and Disabling Earnings and Deductions by Payee

Access the Element Assignment By Payee page (Global Payroll & Absence Mgmt, Payee Data, Assign Earnings and Deductions, Element Assignment By Payee).

When you first access this page, the system displays all existing assignments for the payee in the Assignments grid. Use the fields in the Selection Criteria group box to select and display a subset of the earnings and deductions retrieved for the payee.

Elements

Access the Elements tab.

Use the fields on the Elements tab to update or disable element assignments.

To update an earning or deduction element for a payee:

1. Click the Element Name hyper link.

2. Modify the process order.

3. Modify the end date.

To disable an earning or deduction assignment:

1. Choose the assignment to disable.

2. Deselect the Apply check box or manually enter an end date for the assignment.

Note. When you assign an element to an element group, you indicate that the element should be calculated automatically for each payee whose eligibility group contains that element group, or that the element should be calculated only when it's assigned to a payee.

With the second option, the element is resolved for a payee only if positive input exists for the payee or you assign the element to the payee on the Element Assignment By Payee page, the Payee Assignment By Element page, or the Entitlement/Take Assignment page.

Note. If you define a component to replace the standard element assignment interface, you can grant or deny users the ability to delete assignments, apply assignments, and update assignment begin and end dates. You cannot limit user access to these actions on the standard component shown here.

See Configuring Element Overrides.

Recipient

Select the Recipient tab.

Note. Recipient tags are specifically for use with multiple resolutions: because different assignments of the same element can each be associated with a unique recipient tag, and each tag can be tied to a different recipient ID or recipient name, the system can direct each resolution of the assigned element to a different recipient.

Note. Define recipient tags for deductions and payees on the Add Deduction Recipients page.

See Assigning Recipients to Deductions and Payees.

See Also

Begin and End Date Logic for Overrides

Defining Element Groups

Managing Multiple Resolutions of an Earning or Deduction

Assigning and Disabling Earnings and Deductions by Element

Access the Payee Assignment By Element page (Global Payroll & Absence Mgmt, Payee Data, Assign Earnings and Deductions, Payee Assignment By Element).

Note. This page is similar to the Element Assignment By Payee page. Except for page elements described below, the information about the Element Assignment By Payee page applies to this page as well.

See Assigning and Disabling Earnings and Deductions by Payee.

Use the fields in the Selection Criteria group box to specify search criteria for retrieving the payees to whom the earning or deduction shown at the top of the page is assigned.

Assignments

Select the Assignments tab.

Use the Active field on the Assignments tab to activate or disable element assignments.

Recipient

Select the Recipient tab.

This tab appears for elements that are associated with a deduction recipient.

See Defining Banking Instructions.

Pay Group

Select the Pay Group tab.

Use the fields on the Payee Details tab to view pay entity and pay group information for an employee.

Overriding Component Values, Generation Control, Frequency, Arrears, and Variables for a Payee

Access the Element Detail page (click the element name link on the Element Assignment By Payee page or the payee ID link on the Payee Assignment By Element page).

Note. You can modify the appearance of the Element Detail page using the Configuration by Element and Configuration by Category components, or designate a user-configurable component to replace this page. Depending on the option you choose, your page may appear different than the standard page shown here.

See Configuring Element Overrides.

Assignment Process Detail

Calculation Information

Use the fields in this group box to assign or override the values of the components—Unit, Rate, Base, Percent, and Amount— that constitute the calculation rule of the earning or deduction element.

For example, if the calculation rule for an element is Unit x Rate, you can enter values for the unit and rate components but not the base and percent components.

You can enter an amount regardless of the calculation rule. If you enter an amount with other component values, the system uses the amount to resolve the element. For example, if you enter an amount for an earning element that has a calculation rule of unit * rate, the system uses the amount in the calculation. If you also enter a unit and rate, the system passes these values to the results tables, but it doesn't use them to resolve the element.

To override the value of the unit, rate, base, percent, or amount component, select the type of element that returns the override value. For numeric elements, enter the appropriate number in the Value field; for other element types, enter the name of the element that retrieves the override value in the Element field.

Supporting Element Overrides

Use the fields in the Supporting Element Overrides group box to override the value of a variable used in the calculation of an earning or deduction.

When you override the value of a variable used in the calculation of an earning or deduction, the override value affects only the resolution of that earning or deduction for the specified payee. After the earning or deduction is resolved, the variable is set to its previous value. (These overrides are also called payee/element overrides.)

The supporting element override uses the same begin and end dates as the parent element. You cannot enter values with a monetary entry type.

Important! To override a variable element for all elements that use the variable—not just one earning or deduction that uses the variable—use the Payee Supporting Element Overrides page.

Note. You can configure the standard Supporting Element Overrides group box to include descriptive labels for override variables, required fields, and simple edits such as prompt table, translate value, and yes/no edits. To configure this group box for an element or a category of elements, use the Configuration by Element and Configuration by Category components. The modified group box replaces the standard one.

See Configuring Element Overrides.

Example: How the Two Variable Override Methods Differ

E1 and E2 are set up as a flat amount with the amount = V1.

V1 = 100 (from the element definition).

If V1 = 200, based on an override entered on the Payee Supporting Element Overrides page, E1 and E2 resolve to 200.

If V1 = 200, based on an override entered for E1 on the Element Assignment By Payee or Payee Assignment By Element pages, E1 resolves to 200, V1 is reset to 100, and E2 resolves to 100.

Example: Entering Variable Values for Court Orders

When a payee has a court order, you might have to define the payee's disposable earnings. Using a simplified example, say a judge indicates that E1 and E2 constitute disposable earnings but only 50 percent of E2 counts. So if E1 = 1000 and E2 = 500, disposable earnings should equal 1250 (1000 + 1/2 of 500).

When you define the disposable earnings accumulator on the Accumulators - Members page, you indicate the elements (E1 and E2) and the percentage. On this page, you could indicate the percentages (100 and 50), but to avoid setting up a unique disposable earning accumulator for each person (because the next garnished employee might have E2 with a percentage of 75), you can create two variables that default to 100 (percent). On the accumulator, you enter the variable names, not a percentage.

To enter the variable values for a payee, select the garnishment deduction element on the Element Assignment By Payee page, go to the Element Detail page, and enter the variable values (50 percent for E2 in the example).

See Defining the List of Elements That Contribute to an Accumulator.

Example: Using Variable Overrides to Calculate Garnishments

You have an accumulator for the GARNAC1 garnishment, with these earning elements as members:

The variables are set up as follows:

Payee 8001 has two garnishments that use the same calculation rule:

GARNISH1 = Percent × Base

GARNISH2 = Percent × Base

where:

Percent = Payee Level Override

Base = GARNAC1

You set it up on the Element Detail page as follows:

• EARNING1 equals 1000.

• EARNING2 equals 500.

• EARNING3 equals 750.

When calculating GARNISH1, the system encounters GARNAC1, sees that Percent is a variable, looks for supporting element overrides, finds override values for VARIABLE1 and VARIABLE2 for Payee 8001, and calculates the value of GARNAC1 as follows:

[(1000 × 75%) + (500 × 50%) + (750 × 100%)] = 1750

where GARNAC1 is calculated as:

(EARNING1 × VARIABLE1 + EARNING2 × VARIABLE2 + EARNING3 × VARIABLE3).

Therefore, the calculation for GARNAC1 in GARNISH1 is:

1000 × 75% (using the payee-level override value of 75 for VARIABLE1)

500 × 50% (using the payee-level override value of 50 for VARIABLE2)

750 × 100% (using the default value of 100, because no payee-level override value existed for VARIABLE3).

When calculating GARNISH2, the system finds a supporting element override only for VARIABLE1 and calculates the value of GARNAC1 as:

[(1000 × 60%) + (500 × 100%) + (750 × 100%) = 1850

where GARNAC1 is:

(EARNING1 × VARIABLE1 + EARNING2 × VARIABLE2 + EARNING3 × VARIABLE3).

The calculation for GARNAC1 in GARNISH2 is as follows:

1000 × 60% (using the payee-level override of 60 for VARIABLE1)

500 × 100% (using the default value of 100, because there was no payee-level override value for VARIABLE2)

750 × 100% (using the default value of 100 because there was no payee-level override value for VARIABLE3)

Other Overrides

Use the fields in this group box to override frequencies, generation control, and arrears.

Note. You can modify the appearance of the Element Detail page using the Configuration by Element and Configuration by Category components, or designate a user-configurable component to replace this page. Depending on the option you choose, your page may appear different from the standard page shown here.

See Configuring Element Overrides.

See Also

Defining Element Names

Frequency and Generation Control Calculations

Understanding Net Pay Validation and Arrears Processing

Understanding Arrears and Retroactive Processing

Understanding Payback Processing

Overriding Supporting Element Values for Payees

Use the Supporting Elements page to override the value of a bracket, date, duration, formula, or variable element that's associated with a payee. Whenever the system resolves an element for the payee, it uses the override value that you select.

The Supporting Elements page is similar to the Pay Entities - Supporting Element Overrides page, but the processing rules differ.

See Also

Defining Pay Entity Overrides

Processing Payee Overrides

For payee overrides, the system looks at segment end dates (or period dates if there's no segmentation) for a payee to determine if a supporting element override is used. The end date must be greater than or equal to the segment end date in order for it to be processed. Unlike pay entity and pay group, the system doesn't look at the Use Defn As Of (Definition as of Date).

Example: Segmentation and Payee Supporting Element Overrides

Two payees have the same override.

• Payee 1 has no segmentation.

• Payee 2 has segmentation. Segment 1 is January 1-15. Segment 2 is January 16-31.

• The pay period is January 1-31.

• VR1, a variable element, is defined as 50.

• VR1 has a payee-level override of 100 beginning on January 16.

For Payee 1, the value of VR1 is always 100, because there's no segmentation.

For Payee 2, the value of VR1 is 50 for Segment 1 and 100 for Segment 2.

See Also

Payee Overrides and Segmentation

Defining Pay Calendar Overrides

When defining a calendar for a payroll or absence process, you can enter instructions for two types of overrides. You can:

• Specify any earning, deduction, or absence elements to exclude from processing for all payees.

  Enter these instructions on the Calendar - Excluded Elements page.

• Override the value of brackets, dates, duration, formulas, and variable elements on the Calendar - Supporting Element Overrides page.

  In this case, begin and end dates aren't used, on the assumption that the override applies to the calendar period.

See Also

Excluding Elements From a Calendar

Overriding Supporting Elements for a Calendar

Entering Calendar Override Instructions for a Payee

Defining Overrides Via Elements

The Update Via Element feature is used to control which elements can be updated by another element. You can update an element by means of another element in four places in the application:

• Arrays (through the Arrays Fields Retrieved fields on the Array Fields Retrieved page.

• Brackets (through the Return Column fields on the Bracket Search Keys/Return Columns page).

• Dates (through the Date Extract fields on the Date Extract page).

• Formulas (through the Assign To columns on the Formula Definition page).

There are two ways to override the value of an element that's updated through another element: with positive input or by entering an override on the Supporting Element Overrides page, accessible through the Earning/Deduction Assignment page.

Defining Element Definition Overrides

This section provides an overview of element definition overrides and lists the page used to define element definition overrides.

Understanding Element Definition Overrides

With element overrides, you can override certain supporting elements that are associated with a primary element. The supporting element can be part of the primary element's definition.

You use the Element Definition - Supporting Element Overrides page to override the definition of elements associated with primary elements. This page is similar to the Pay Entities - Supporting Element Overrides page.

The processing rules for (primary) element overrides are the same as those for pay entity overrides, but element overrides are resolved in the earning, deduction, or absence module of the batch process. Accordingly, the supporting element that's being overridden reverts to its prior value after being resolved.

Page Used to Define Element Definition Overrides

See Also

Defining Pay Entity Overrides

Defining Overrides with Positive Input

You can override an earning, deduction, or absence element by entering positive input on the Positive Input component. Use positive input to enter payee-related data for one pay period. For example, you can enter positive input for one time bonuses or for hours worked during a pay period.

You can also use the Supporting Element Overrides grid, accessed through the Details page of the Positive Input component, to override any system or variable element associated with an instance of positive input. Here, element values must be numeric, character, or date; they cannot be monetary.

An override applies to only one instance of positive input. After the instance is resolved, the supporting element returns to its previous value.

Processing Rules in Positive Input and Overrides

Begin and end dates exist on the positive input record, but the system uses them strictly as a means of assigning a positive input sequence (instance number) to a segment or slice. It uses the value assigned to the supporting element only for that sequence. After use, it reverts to the value that was assigned before the positive input entry.

See Also

Working with Positive Input

Defining Pay Entity Overrides

Managing Interactions Between Element Assignment Overrides, Positive Input Entries, and Element Definitions

This section discusses how the system manages competing element assignment and positive input entries for the same earnings or deductions.

Rules for Processing Competing Element Assignments and Positive Input Entries

In Global Payroll you can enter multiple element assignment and positive input rows for the same element within a single pay period slice or segment. To manage the competing instructions contained in these overrides, the system matches earning and deduction assignments with their corresponding positive input entries within the same slice or segment, and then determines which elements to resolve and which instructions to follow based on the processing rules described in this section.

Note. The system treats element assignments and positive input entries as matching if they are for the same element and occur in the same slice or segment of the pay period.

The system observes these rules when processing competing element assignments and positive input entries:

Important! Note that the rules outlined here apply per slice or segment, as element assignments interact with positive input entries only within the same slice or segment. If there is no segmentation or slicing of elements, the slice/segment begin and end dates can be viewed as equivalent to the begin and end dates of the period as a whole, and element assignments and positive input entries interact across the entire period. There is one exception to this rule, however: a Resolve to Zero entry in positive input cancels all assignments of the same element in any other segment or slice (in other words, a Resolve to Zero entry is not restricted to the segment/slice in which it occurs).

The following examples illustrate how the system resolves payee level overrides, and demonstrate interactions between element assignments and positive input entries in both segmented/sliced and unsegmented periods.

These examples are based on an earning element E1 with a calculation rule of Rate x Unit x Percent.

Note. These examples assume that there are no user field values associated with the assigned earnings or deductions. To see how the rules change when there are user fields, review the chapter on multiple resolutions.

See Managing Multiple Resolutions of an Earning or Deduction.

Example: Rule 1 (One Assignment to One or More Positive Input Overrides)

Assume that the following element assignment and positive input entries exist for earning element E1:

Applying Rule 1, the system resolve E1 as follows:

1. 10 x 75 x 150% = 1125

The system resolves the first instance of positive input and goes to either the element assignment or the rule definition for the missing component values.

2. 5 x 60 x 150% = 450

The system resolves the second instance of positive input and goes to either the element assignment or the rule definition for the missing component values.

Example: Rule 2 (Many Assignments to One or More Positive Input Overrides)

Assume that the following element assignment and positive input entries exist for earning element E1:

Applying Rule 2, the system resolve E1 as follows:

5 x 50 x 150% = 375

The system resolves the positive input entry and goes to the rule definition to obtain the missing component values, ignoring all earning/deduction assignments.

Example: Rule 2 (Many Assignments to One or More Positive Input Overrides—with Element Segmentation Due to Overrides)

Assume that the following element assignment and positive input entries exist for earning element E1, and that element segmentation occurs based on the begin and end dates of the assignments:

Note. You can set up the system to slice a pay period based on the begin and end dates of the overrides assigned to a payee on the Element Assignment by Payee (GP_ED_PYE) and Payee Assignment by Element components (GP_ED_ELEM). We discuss how to do this in the chapter on trigger definitions.

See Setting Up Segmentation Triggers for The Begin and End-Dated Earning and Deduction Assignment Record (GP_PYE_OVRD).

Note. In this example, element assignment is abbreviated Assign, positive input is abbreviated PI, and the positive input action type of override is abbreviated Over.

Applying Rule 2, the system resolves E1 as follows:

1. In slice 1 (June 1-15): 2 x 60 x 150% = 180

Applying Rule 2, the system processes the positive input entry for slice 1 (June 1 - June 15) but not the corresponding element assignment. Because positive input overrides look to the element assignment within the same slice for missing component values, the positive input uses the Rate component (60) from the assignment in slice 1, and then retrieves the percent value (150) from the rule (as the element assignment in slice 1 does not specify a percentage).

2. In slice 2 (June 16-30): 5 x 75 x 150% = 562.50

Applying Rule 2, the system processes the positive input entry for slice 2 (June 16-30) but not the corresponding element assignment. Because positive input overrides look to the element assignment within the same slice for missing component values, the positive input uses the Rate component (75) from the assignment in slice 2, and then retrieves the percent value (150) from the rule (as the element assignment in slice 2 does not specify a percentage).

Example: Rule 4 (Many Assignments to One or More Positive Input Additional Rows)

Assume that the following element assignment and positive input entries exist for earning element E1:

Note. In this example, element assignment is abbreviated Assign, positive input is abbreviated PI, and the positive input action type of additional is abbreviated Add.

Applying Rule 4, the system resolves E1 as follows:

1. 10 x 60 x 150% = 900

The system resolves the first element assignment and goes to the rule definition to obtain missing component values.

2. 10 x 75 x 150% = 1125

The system resolves the second element assignment and goes to the rule definition to obtain missing component values.

3. 2 x 50 x 150% = 150

The system resolves the first instance of positive input and goes to the rule definition to obtain missing component values.

4. 5 x 50 x 150% = 375

The system resolves the second instance of positive input and goes to the rule definition to obtain missing component values.

Example: Rule 5 (One or More Assignments and a Resolve to Zero Row in Positive Input)

Assume that the following element assignment and positive input entries exist for earning element E1:

Applying Rule 5, the system resolves E1 as follows:

E1 = 0

The system resolves only the positive input Resolve to Zero instance and not the element assignments.

Example: Rule 5 (One or More Assignments and a Resolve to Zero Row in Positive Input—with Element Segmentation Due to Overrides)

looks good

Assume that the following element assignment and positive input entries exist for earning element E1, and that element segmentation occurs based on the begin and end dates of the assignments:

Note. You can set up the system to slice a pay period based on the begin and end dates of the overrides assigned to a payee on the Element Assignment by Payee (GP_ED_PYE) and Payee Assignment by Element components (GP_ED_ELEM). We discuss how to do this in the chapter on trigger definitions.

See Setting Up Segmentation Triggers for The Begin and End-Dated Earning and Deduction Assignment Record (GP_PYE_OVRD).

Note. In this example, element assignment is abbreviated Assign, positive input is abbreviated PI, and the positive input action type of Resolve to Zero is abbreviated RTZ.

Applying Rule 5, the system resolves E1 as follows:

1. In slice 1 (June 1-15): E1 = 0

In slice 1, the system resolves only the positive input Resolve to Zero instance and not the element assignment.

2. In slice 2 (June 16-30): E1 = 0

In slice 2, the system ignores the element assignment entry for June 16-30 and processes only the resolve to zero instructions entered using positive input. This is because a positive input resolve to zero instance applies not only to elements assigned within the same segment or slice, but to all assignments of the same element in any other slice.

Example: Rule 6 (Element Assignment in Conjunction with Override and Resolve to Zero Rows in Positive Input)

Assume that the following element assignment and positive input entries exist for earning element E1:

Applying Rule 6, the system resolves E1 as follows:

1. 2 x 60 x 150% =180

The system resolves the positive input override and goes to both the element assignment and the rule definition for missing component values.

2. E1 = 0

The system resolves the positive input Resolve to Zero instance and not the element assignment.

Example: Rule 9 (Apply Check Box deselected For an Element Assignment)

Assume that the following element assignment and positive input entries exist for earning element E1:

Applying Rule 7, the system resolves E1 as follows:

2 x 50 x 150% = 150

The system resolves the positive input entry with the action type of Additional. There are no other resolutions of earning E1.

Example: Rule 10 (Apply Check Box deselected For One of Many Element Assignments)

Assume that the following element assignment and positive input entries exist for earning element E1:

Applying Rule 10, there are no resolutions of Earning E1.

Generating Complementary Rules Instances

This section discusses the conditions that trigger the creation of a complementary rule.

A complementary rule is an earning or deduction that the system resolves automatically to complement an existing element assignment when that assignment's begin and end dates do not encompass the entire pay period. For example, suppose that you assign a deduction to a payee with begin and end dates of 1 and 15 January respectively, and that you use a monthly pay period calendar. Under certain conditions, the system automatically generates an assignment for the same element with begin and end dates of 16 and 31 January—in other words, it creates an instance of the deduction in the second slice to complement the existing assignment in the first slice in the segment.

The system generates a complementary rule for an assigned element under these conditions:

1. You select the Active Anytime Within Segment option on the Countries page.

   When this is the case, the system processes all element assignments within a period, including those with end dates that come before the period end date.

   See Defining Installation Settings.

2. You set up earnings and deductions to trigger element segmentation (slicing) when they are assigned to payees on the Element Assignment by Payee (GP_ED_PYE) and Payee Assignment by Element components (GP_ED_ELEM).

   See Setting Up Triggers.

3. The assignment begin date for an earning or deduction comes after the period start date, and/or the assignment end date comes before the period end date.

4. You set the eligibility type of the assigned element to By Eligibility Group on the Element Group Members page, and you specify an override level of Payee for the element on the Earning or Deduction Name page.

   See Defining Element Groups, Override Levels.

   Note. When you select an override level of Payee on the Earning or Deduction Name page, you enable the element to be assigned at the payee level using the Element Assignment by Payee (GP_ED_PYE) and Payee Assignment by Element components (GP_ED_ELEM).

In addition, the following must be true:

Note. These rules assume that there are no user field values associated with the earning or deduction on the assignment pages or on the Earning or Deduction Definition pages. To see how the rules change when there are user fields, review the chapter on multiple resolutions.

• There can be no positive input Override for the same element in any slice in the pay period.

  A positive input Override in any slice prevents the creation of a complementary rule in all other slices.

• There can be no positive input Do Not Process entry for the same element in any slice in the pay period.

  A Do Not Process entry in any slice prevents the creation of a complementary rule in all other slices.

• There can be no positive input Resolve to Zero entry for the same element in any slice in the pay period.

  A Resolve to Zero entry in any slice prevents the creation of a complementary rule in all other slices.

Note. The system does not create complementary rule instances where there is already an element assignment for an earning or deduction. For example, if there is an existing assignment for the period 1 to 15 January, and you add an assignment for the same element with begin and end dates of 16 January and 31 January respectively, the system does not generate a complementary rule for the second slice (16-31 January).

Note. The system never generates more than a single complementary rule instance for an assigned element in any slice, even when there are multiple assignments of the same element. For instance, if you assign the same deduction five times in the first slice in a pay period, the system generates only one complementary rule instance in the second slice.

Note. Positive input additional rows in a slice do not prevent the creation of a complementary rule instance in the same or any other slice.

When all of these conditions are met, the system creates a complementary rule using definition of the unit, rate, percent, or amount components specified in the calculation rule of the earning or deduction.

Note. The calculation rule is the definition of the earning or deduction specified in the Earnings Definition (GP_EARNING) and Deductions Definition (GP_DEDUCTION) components.

The following examples illustrate how and under what circumstances the Global Payroll system generates complementary rule instances.

Example: An Earning Assignment Triggers the Creation of A Complementary Rule Instance

Assume that there is an element assignment for earning element E1 (calculation rule of Rate x Unit x Percent). Eligibility is by eligibility group and the begin and end dates of the element assignment are June 1 and June 15 respectively:

Note. In this example, element assignment is abbreviated Assign.

The system divides the calendar into two slices based on the assignment begin and end dates (slice 1 = June 1-15; slice 2 = June 16-30).

The system resolves E1 as follows:

1. In slice 1 (June 1-15): 2 x 60 x 100% x .5 (proration factor) = 60

2. In slice 2 (June 16-30): 5 x 50 x 150% x .5 (proration factor) = 125

The system creates a complementary rule instance for E1 in slice 2 (June 16-30) using the rule definition (the definition of the earning specified in the Earning Definition component).

Example: A Positive Input Override Prevents the Creation of A Complementary Rule Instance

Assume that an element assignment and positive input entry exist for earning element E1 (calculation rule of Rate x Unit x Percent). Eligibility is by eligibility group and the begin and end dates of the element assignment and the positive input entry are June 1 and June 15 respectively:

Note. In this example, element assignment is abbreviated Assign, positive input is abbreviated PI, and the positive input action type of override is abbreviated Over.

The system divides the calendar into two slices based on the assignment begin and end dates (slice 1 = June 1-15; slice 2 = June 16-30).

The system resolves E1 as follows:

1. In slice 1 (June 1-15): 2 x 60 x 150% x .5 (proration factor) = 90

In keeping with Rule 1 described in the section Managing Interactions Between Element Assignment Overrides, Positive Input Entries, and Element Definitions, the system processes the positive input entry for slice 1 (June 1-15) but not the corresponding element assignment. The system looks to the element assignment in slice 1 for the Rate component (60) that is missing from positive input, and then retrieves the percent value (150) from the rule (as the element assignment in slice 1 does not specify a percentage).

2. In slice 2 (June 16-30): The system does not create a complementary rule instance for E1 because the positive input override in the first slice blocks the creation of the complementary rule in all other slices.

Example: Complementary Rule Instance Not Created Because of Do Not Process Instructions in Positive Input

Assume that there is a positive input entry and an element assignment for earning element E1 and that eligibility is by eligibility group (the calculation rule of E1 is Rate x Unit x Percent). The begin and end dates of the positive input entry are June 1 and June 10, and the begin and end dates of the element assignment are June 11 and June 20 respectively. The positive input entry has an action type of Do Not Process:

Note. In this example, positive input is abbreviated PI and element assignment is abbreviated Assign.

The system divides the calendar into three slices based on the assignment begin and end dates (slice 1 = June 1-10; slice 2 = June 11-20; slice 3 = June 21-30).

The system resolves E1 as follows:

1. In slice 1 (June 1-10): The system does not process E1 because of the do not process instructions.

2. In slice 2 (June 11-20): The system does not process E1 because the do not process instructions in the first slice prevent processing in all other slices in the same segment.

3. In slice 3 (June 21-30): The system does not create a complementary rule instance because the do not process instructions in the first slice block the creation of the complementary rule in all other slices.

Resolving Overrides in Batch Processing

This section discusses overrides in batch processing.

The following table describes how overrides to supporting elements are resolved during batch processing.

Earning/Deduction Program Flow

Here's what happens in the Earning/Deduction Program:

1. Retrieve the earning, deduction, take, or entitlement element rule definition.

2. When a primary element override exists (that is, when there are instructions to override a supporting element that is associated with an earning, deduction, take, or entitlement), retrieve and store the current value of the supporting element.

   Set the value of each supporting element to the override value (to be in force for the duration of the earning or deduction resolution).

3. Loop per instance.

   Note. For take and entitlement elements, there is only 1 resolution of the element. For earning and deduction elements, there can be many instance resolutions.

4. When payee/element or positive input supporting element overrides exists, retrieve and store the current value for each supporting element with an override value.

5. Set the override value of each supporting element.

   When there are both payee/element and positive input overrides for the same supporting element, the positive input override is applied.

6. Apply payee/element field by field overrides to the rule.

   Apply positive input field by field overrides to the rule.

7. Calculate the earning/deduction instance.

8. Add the instance return values to the PIN Manager Return List (earning/deduction + components).

9. Reset the previous value of each supporting element that was overridden via payee/element and positive input supporting element overrides.

10. End instance loop.

11. Reset the previous value of each supporting element that was overridden via primary element overrides. This completes the restoration of the supporting elements to the values in effect prior to the earning, deduction, take, or entitlement resolution.