<meta name="robots" content="noindex,nofollow" />
<link rel="shortcut icon" type="image/x-icon" href="/knowledge/images/favicon.ico" />
<link rel="icon" type="image/x-icon" href="/knowledge/images/favicon.ico" />

<pre>
[{TableOfContents }]
!!!DEFINE PAY COMPONENTS 

[Pay Components|PAY COMPONENTS] are any identifiable components of a pay, or any item that requires the ability to be stored or totaled. Pay components are used to store all the data calculated by the pay calculation.

You may define and maintain [pay components|PAY COMPONENTS] through the Define Pay Components (IPPC) form.


[Pay Component|PAY COMPONENTS] Data is stored in the [P2K_PR_PAY_COMPONENTS], [P2K_PR_PC_RULES] and [P2K_PR_PC_DETAILS] tables.


;[PC Code|PC_CODE]:A PC code is a unique number code from 1 to 9,999 assigned to uniquely identify the [pay component|PAY COMPONENTS] within the system. PC_Code is a 4-character numeric mandatory field that you must manually enter.
;[Abbr.|PC_ABBREVIATION]:This field holds the short alpha description of the [pay component|PAY COMPONENTS] used for printing on check and deposit statements, lists and pay registers. Although this field accepts 30 characters, you should keep your abbreviation as short as possible. PC_Abbreviation is a 30-character alphanumeric mandatory field that you must manually enter.
;[Desc|DESCRIPTION]: This field displays a longer description of the [pay component|PAY COMPONENTS] than may be entered in the abbreviation. Description is a 50 character alphanumeric mandatory field that you must manually enter.
;[PC Usage|PC_USAGE_CODE]:This field is used to categorize when and how the [pay component|PAY COMPONENTS] is to be used during the pay calculation. For example, the Usages of Net Pay indicates that this will be the Pay Component used to store the net Pay amount that is calculated through [UPCALC] (Payroll Calculation). PC_Usage_Code from [P2K_PR_PC_USAGES] is a numeric value that you may manually enter or use the LOV (F9).
;[Usage Desc|DESCRIPTION]: This field gives a short description of the usage, specifically when and how the [pay component|PAY COMPONENTS] is to be used during the pay calculation. For example, the Usages of Net Pay indicates that this will be the [pay component|PAY COMPONENTS] used to store the net Pay amount that is calculated through [UPCALC] (Payroll Calculation). PC_Usage_Description from [P2K_PR_PC_USAGES] is an alphanumeric value that defaults from the usage.
;[Store Results|STORE_RESULTS]: If this toggle is checked, the value(s) of the [pay component|PAY COMPONENTS] amount will be stored in detail in the PC Amount table and accumulated in the to-date PC Amount table. This option would be used for all Pay Register amounts. If the toggle is not checked, the [pay component|PAY COMPONENTS] amount will not be stored or accumulated. This option is used for items such as rates used in calculations, or indicators used to trigger special processing. Store Results toggle must be checked in order for a Statistical [pay component|PAY COMPONENTS] (usage 14) to work correctly. If this toggle is not checked, information will not be stored in the statistic attached to the [pay component|PAY COMPONENTS]. Store_Results is an optional toggle field.
;[Assoc. PC|PC_CODE]: Associated [pay components|PAY COMPONENTS] are used to store the number of another [pay component|PAY COMPONENTS] that may be associated with this PC. For example, if the PC being defined were a Time PC then the Earnings PC would be its Assoc. PC. This field may need to be left blank until all of your [pay components|PAY COMPONENTS] are completed. PC_Code is an optional 4 digit numeric field that you may manually enter or use the LOV (F9).
;[Statistic|STAT_CODE]: This field holds the employee payroll statistics. The result of this PC will be stored in the To Dates table as well as being sent to the Statistics table if the PC Usage is 14 and a statistic code is indicated in this field. Stat_Code from [P2K_CM_STATISTIC_COMPONENTS] is an optional 16 character alphanumeric field that you must manually enter or use the LOV (F9) to choose an option.
;[Element|ELEMENT_CODE]: If the [pay component|PAY COMPONENTS] is to hold the result of a [pay element|PAY ELEMENTS] it needs to be indicated here. If (PPE) appears in the usage, the PC should be associated to an [element|PAY ELEMENTS]. This field can be filled in after the [pay elements|PAY ELEMENTS] are completed. Element_Code from [P2K_PR_ELEMENTS] is 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Action|PC_ACTION]: The PC Action determines whether a transaction item entered under this [pay component|PAY COMPONENTS] will be:
*Accumulated to the total value of the [pay component|PAY COMPONENTS]
*Replace a prior transaction item
*Trigger a user calculation
*Suppress a user calculation.
;:PC_Action is a mandatory fixed lexicon ([X_PC_ACTION]) that you may use to look up the value.
;[Entity|ENTITY_CODE]:A [pay component|PAY COMPONENTS] may need to vary its rules or detail by entity. Entity_Code from [P2K_CM_ENTITIES] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Unit|UNIT_CODE]: A [pay component|PAY COMPONENTS] may need to vary its rules or detail by unit within entity. Unit_Code from [P2K_CM_UNITS] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Group|GROUP_CODE]: A [pay component|PAY COMPONENTS] may need to vary its rules or detail by group within unit within entity. Group_Code from [P2K_CM_GROUPS] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Basis|TIME_BASIS]:If the [pay component|PAY COMPONENTS] is to store time or units, the basis needs to be indicated. (i.e. days, hours, units) in this field. While this field is optional, it is recommended that you complete it if you are going to do a retro pay. Time_Basis is an optional fixed lexicon ([X_TIME_BASIS]) that you may use to look up the value.
;[Pay Point|PAY_POINT_TYPE]: From the pay point set previously set up, this field will indicate when this [pay component|PAY COMPONENTS] needs to be picked up for processing during the pay calculation. Pay_Point_Type is an optional fixed lexicon ([X_PAY_POINT_TYPE]) that you may use to choose an option.
;[Assignment Type|ASSIGNMENT_TYPE]: The assignment type categorizes the assignment record. Each employment record has a corresponding assignment, with an assignment type of 'primary'. Optionally, there may be additional assignments of different types. This ‘type’ is considered when determining if a given assignment is to be considered during the ‘matching assignment’ wage rate calculation. Assign_Type is a fixed lexicon ([X_ASSIGN_TYPE]) that you may use to look up the value.
;[Time Code|TIME_CODE]: User defined time code that uniquely identifies a type of time. Time codes are easy to use data entry codes chosen by the user. They are used to link the time codes used in front end time, attendance and time scheduling applications with High Line’s payroll application. i.e. PC 110 Sick Time would be associated to a Time Code called SICK HRS for Attendance purposes. Time_Code from [P2K_CM_TIME_CODES] is an optional 16-character alphanumeric field that you may manually enter or use the LOV (F9)
\\
----
!!Define Pay Components (IPPC) - PC Rules
This section indicates where and what can be entered in the Pay Line when a PC is chosen for data entry.
;[Enter Sundry|ENTER_SUNDRY_LINES]: If the Enter Sundry toggle is ON, the [pay component|PAY COMPONENTS] may be entered on a sundry line (i.e.a recurring type of transaction). If the toggle is OFF, the [pay component|PAY COMPONENTS] may not be entered on sundry lines. Enter_Sundry_Line is an optional toggle field.
;[Enter Pay Lines|ENTER_PAY_LINES]: If the Enter Pay Lines toggle is ON the [pay component|PAY COMPONENTS] may be entered on a pay line (i.e. a one-time type of transaction). If the toggle is OFF, the [pay component|PAY COMPONENTS] may not be entered on pay lines. Enter_Pay_Lines is an optional toggle field.
;[Generate Details|GENERATE_DETAILS]: If the Generate Details toggle is ON, this [pay component|PAY COMPONENTS] has associated [pay component|PAY COMPONENTS] detail records. If the toggle is OFF, there are no related PC details. Generate_Details is an option toggle field.
;[Enter Position|ENTER_POSITION]: If the Enter Position toggle is ON, you may override the position code on the pay line. If the toggle is OFF, it may not be entered. Enter_Position is an optional toggle field.
;[Default Position|DEFAULT_THE_POSITION]: If the foundation structure is set up with positions then this toggle must be ON to allow the position indicated on the employee’s assignment file to be defaulted for this [pay component|PAY COMPONENTS]. If the foundation structure was set up with only jobs then this toggle does not need to be marked. This toggle only needs to be marked for [pay components|PAY COMPONENTS] that need to be related to the rate of pay and/or distribution code. Default_The_Position is an option toggle field.
;[Enter Job|ENTER_JOB]: If this toggle is ON, you may override the job code on the pay line. If the toggle is OFF, it may not be entered. Enter_Job is an optional toggle field.
;[Default Job|DEFAULT_THE_JOB]: If the Foundation structure is set up with jobs then this toggle must be ON to allow the job indicated on the employees assignment file to be defaulted for this pay component. This toggle only needs to be marked for [pay components|PAY COMPONENTS] that need to be related to the Rate of pay and/or Distribution code. Default_The_Job is an optional toggle field.
;[Sundry Asgn Match|SUNDRY_BY_ASSIGNMENT]: This toggle is used for sundries which apply only to an employee’s specific assignment (e.g. primary or secondary assignment). Sundry_By_Assignment is an optional toggle field.
;[Enter Date|ENTER_DATE]: If the Enter Date toggle is ON, you may enter the transaction date on the pay line. If the toggle is OFF, the date may not be entered. Enter_Date is an optional toggle field.
;[Enter Value|ENTER_TIME]: If the Enter Value toggle is ON, you may enter the time on the pay line. If the toggle is OFF, it may not be entered. Enter_Time is an optional toggle field.
;[Enter Wage Rate|ENTER_WAGE_RATE]: If the Enter Wage Rate toggle is ON you may override the wage rate on the pay line. If the toggle is OFF, it may not be entered. Enter_Wage_Rate is an optional toggle field.
;[Enter Rate Basis|ENTER_WAGE_RATE_BASIS]:If the Enter Rate Basis toggle is ON, you may override the rate basis on the pay line. If the toggle is OFF, it may not be entered. Enter_Wage_Rate_Basis is an optional toggle field.
;[Reference|ENTER_DESCRIPTION]: The Reference field is used on the pay lines of either the [IPPH] (Pay Header) or [IPSN] (Sundry) forms. It allows you to enter a reference or description of the pay line or sundry to indicate how they will be used. This reference information may be either anecdotal or more structured (e.g. Union Code or Court Number). You may select either:
*Enter Vendor Code - For pay components that will be used for Accounts Payable.
*Enter Description - You will be able to enter up to 200 characters as reference on the pay lines. This entry will not be checked against values within any lexicon.
;:Enter_Description is a fixed lexicon ([X_ENTER_DESCRIPTION]) that you may use to look up the value.
;[User Calc|USER_CALC_CODE]: UserCalcs will be discussed further during UserCalc training. 
;[Enter Premiums|ENTER_PREMIUMS]: If the Enter Premiums toggle is ON, you may enter premiums on the pay line. If the toggle is OFF, it may not be entered. Enter_Premiums is an optional toggle field.
;[Enter Work Jurisdiction|ENTER_WORK_GEO]: If the Enter Work Jurisdiction toggle is ON, you may override the work  jurisdiction on the pay line. If the toggle is OFF, it may not be entered. Enter_Work_Geo if the Pay Point toggle is ON, you may override the pay point on the pay line. If the toggle is OFF, it may not be entered. Enter_Pay_Point is an optional toggle field.
;[Enter Pay Point Type|ENTER_PAY_POINT]: If the Enter Pay Point Type toggle is ON, you may enter the pay point type. If the toggle is OFF, it may not be entered. Enter_Pay_Point_Type is an optional toggle field.
;[Enter Pay Point Sequence|ENTER_PAY_POINT_SEQUENCE]: If the Enter Pay Point Sequence toggle is ON, you may enter the sequence of the task on the pay line. If the toggle is OFF, it may not be entered. Enter_Pay_Point_Sequence is an optional toggle field.
;[Enter User Calc|ENTER_USER_CALC]: If the Enter UserCalc toggle is ON, you may enter a UserCalc on the pay line. If the toggle is OFF, it may not be entered. Enter_User_Calc is an optional toggle field. 
;[Enter Detail Action|ENTER_ACTION]: If the Enter Detail Action toggle is ON, you may override the PC action on the pay line. If the toggle is OFF, it may not be entered. Enter_Action is an optional toggle field.
\\
----
!!Define Pay Components (IPPC) - PC Detail Rules
This section indicates what will be generated in the Pay Line Details when a PC is chosen for data entry.

For example, if a time PC Users will want [{$applicationname}] to generate the earnings that would be
associated to that time.
;[PC|PC_CODE]: This field indicates the [pay component|PAY COMPONENTS] number if Time or Amount is being used PC_Code is a 4-digit numeric mandatory field that you must manually enter.
;[Abbreviation|PC_ABBREVIATION]: This field is automatically populated when the [pay component|PAY COMPONENTS] number is entered. PC_Abbreviation is a 30-character alphanumeric mandatory field whose value will be filled once the pay component is selected.
;[Type|PC_DETAIL_TYPE]: This field is used to determine the nature of the' Pay Line Details' that will eventually be created. The two main types are 'Entered Value', and 'Computed Value'. The other types are maximums and declining balance, which are not as common. 
;:''The 'Entered Value' is populated (during save) with the value entered on the Pay Line.
;:''The ‘Computed Values’ are calculated based on the 'Calculation Method'. Only one ‘Computed Value’ is allowed per [pay component|PAY COMPONENTS]detail.
;:PC_Detail_Type is a fixed lexicon ([X_PC_DETAIL_TYPE]) that you may use to look up the value.
;[Calculation Method|PC_CALC_METHOD]: Indicates the method by which an amount is calculated.
*If the Method refers to a rate then the Rate Source field must be completed.
*If the Method refers to an element (Elem) then the element field must be completed.
*If the Method refers to a user variable (Uvar) then the variable field must be completed.
;:PC_Calc_Method is a fixed lexicon ([X_PC_CALC_METHOD]) that you may use to look up the value.
;[Rate Source|PC_RATE_SOURCE]: This field indicates from where the wage rate used to determine the value of the [pay component|PAY COMPONENTS] detail is derived. Rate_Source is a fixed lexicon ([X_PC_RATE_SOURCE]) that you may use to look up the value.
;[Assignment Rate|HIGHER_OF_RATE]:The Assignment Rate applies the rate based on the assignment rate. Higher_of_Rate is a fixed lexicon ([X_HIGHER_OF_RATE]) that you may use to look up the value.
----
!Override Field Entry
;[Rate|ENTER_RATE]:If the Override Rate toggle is ON, you may override the wage rate on the Pay Line Details. If the toggle is OFF, the wage rate may not be overridden. Enter_Rate is an optional toggle field.
;[Value|ENTER_VALUE]: If the Override Value toggle is ON, you may override the value on the Pay Line Details. If the toggle is OFF, the value may not be overridden. Enter_Value is an optional toggle field.
;[User Variable|ENTER_USER_VARIABLE]: If the Override User Variable toggle is ON, you may key the user variable on the pay line details. If the toggle is OFF, you variable may not be overridden. Enter_User_Variable is an optional toggle field.
;[Distributions|ENTER_DISTRIBUTION]: If the Enter Distribution toggle is ON, you may enter the distribution on the Pay Line Details. If the toggle is OFF, the distribution may not be entered. Enter_Distribution is an optional toggle field.
;[Element|ENTER_ELEMENT]: If the Override Element toggle is ON, you may override the element on the Pay Line Details. If the toggle is OFF, the element may not be overridden. Enter_Element is an optional toggle field.
----
!Calculations
;[Highest Rate of the Day|HIGHEST_RATE_OF_DAY]: This field applies the higher of the wage rates derived from either the ‘Rate Source’ chosen, or from the Employee Prime Assignment Rate.  The ‘Highest Rate of the Day’ logic is invoked independently and at a later point in time. It compares the ‘Wage Rate’ stamped on the Pay Line Detail, to the highest ‘Wage Rate’ on all Pay Line Details. After choosing the higher, the calculation rule is applied and the individual amounts generated. Highest_Rate_of_the_Day is a fixed lexicon ([X_HIGHEST_RATE_OF_DAY]) that you may use to look up the value.
;[Salary Rate Method|SALARY_RATE_METHOD]: For salaried employees, there are multiple ways the system can derived a salary or wage value for the pay line. This field indicates the method to calculate this rate. 
;[Custom Rate Logic|CUSTOM_RATE_LOGIC]: Custom rate logic is logic defined by High Line, based on client specification.
----
!Variables
;[Element Code|ELEMENT_CODE]: If a pay element (Elem) is indicated in the calculation method then it needs to be completed here. [Pay elements|PAY ELEMENTS] are maintained through the [IPPE] (Element) form. Element_Code from [P2K_PR_ELEMENTS] is 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[User Variable|USER_VARIABLE_CODE]: If a user variable (UVAR) is indicated in the calculation method then it needs to be completed here. Maintained through the [IMVR] (Maintain user variables) form. User_Variable_Code from [P2K_AM_USER_VARIABLES] is an optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Statistic|STAT_CODE]: If the calc method used requires a statistic, this field can be used to compute the detailed amount. Stat_Code from [P2K_CM_STATISTIC_COMPONENTS] is an optional numeric field that you may either manually enter or use the LOV (F9).
----
!!Define Pay Components (IPPC) - Acct/Arrears
Review the [DEDUCTIONS AND ARREARS] page for additional details on the logic of the following fields.
;[Insufficient Earnings|POSITIVE_DEDUCTION]: Indicates the method by which a deduction should be made from gross pay. 
*‘All Or None’ ignores the deduction if there is insufficient gross. Typically used for items such as savings, bonds, charitable donations, United Way, credit union, etc.
*‘As Much As Possible’ takes a partial deduction when there is insufficient gross. Typically used for items such as loan repayments, parking, union dues, etc. It is recommended that the Create Arrears toggle also be turned on with this setting, in order to generate an arrears transaction for any balance that could not be taken.
*'Full With Advance' takes a full deduction and advances the employee any shortfall. Used for items such as insurance coverage. It is recommended that the Create Arrears toggle be turned on if an arrears transaction must be generated to recover the amount advanced to the employee on a subsequent pay.
;:Dedn_Positive_Rule is an optional fixed lexicon ([X_DEDN_POSITIVE_RULE]) that you may use to look up the value.
;[Create Arrears|POSITIVE_ARREARS]: If the Positive Arrears toggle is ON, whenever there are insufficient earnings to cover the deduction, an arrears transaction for the deduction is generated for the purpose of recovering the amount on a subsequent pay. If the toggle is OFF, in an insufficient earnings situation, no arrears are generated and the deduction is forgotten. Positive_Arrears is an optional toggle field.
;[Negative Deduction|NEGATIVE_DEDUCTION]: The negative deduction rule determines how a negative deduction (i.e. a refund or 'credit' to the employee) will be processed.
*__'Add Back To Gross'__ returns the deduction to the employee by adding it back to the Employee's gross pay, enabling it to be used to cover other deductions.
*__‘Add Back To Net'__ returns the deduction to the employee, but does not enable it to cover any other deductions (e.g. strict refund). This option tends to be used for items that are not normally part of the gross to net calculation, such as allowances or expense reimbursements. When a recoverable advance is set up as a negative deduction, the Collect Back toggle must be turned on in order to generate an arrears transaction to recover the amount advanced on a subsequent pay.
;:Negative_Deduction is an optional fixed lexicon ([X_DEDN_NEGATIVE_RULE]) that you may use to look up the value.
;[Collect Back|NEGATIVE_ARREARS]: This toggle is only ever 'ON' for one [pay component|PAY COMPONENTS] - Advance Recovery. If this toggle is ON, the negative deduction is considered to be a recoverable advance, and an arrears transaction is generated for the purpose of recovering the advance on a subsequent pay. If the toggle is OFF, the negative deduction is treated as a refund or reimbursement to the employee, for which no recovery is required.
;:Negative deductions occur when we have to pay the employee back for taking too much money from their pay for whatever reason (e.g. they were listed as Family deduction and should only have been Single for some Benefit plan).
;:''For Example:
;:''If the Collect Back toggle is Off
;:''Gross 1000
;:''Deduction -20
;:''Net = 1020 (Correct – because the company owed the employee)
;:''Next Pay: Nothing happens (correct)
\\
;:''If the Collect Back toggle is ON
;:''Gross 1000
;:''Deduction -20
;:''Net = 1020 (Correct) Arrears created (20)
;:''Next Pay:
;:''Gross 1000
;:''Arrears 20
;:''Net = 980 (If ‘Collect Back’ toggle is ON, it will result in the deduction being recovered on the next pay)
;:Negative_Arrears is an optional toggle field.
;:Collect Back toggle is only set ON for [pay component usage|PAY COMPONENT USAGES] of 5 - ‘Advance Recovered’. If Collect Back is set ON for deductions this will result in an incorrect calculation during the next pay as arrears will be generated and the gross amount reduced.
;[Arrears Recovery|DEDUCTION_RECOVERY]: The Deduction Recovery rule defines how deductions that are in arrears will be recovered.
*__'Only One Per Pay’__ recovers the deduction on a single transaction basis, for example, when an employee is three deductions in arrears for the same [pay component|PAY COMPONENTS], the pay calculation process attempts to recover only the oldest arrears transaction for that [pay component|PAY COMPONENTS]. If there are insufficient earnings to collect the whole amount of the arrears transaction, the uncollected balance is generated as a new arrears transaction.

;:This rule is primarily used for deductions applied to irregular employees. If the employee has not worked enough hours to cover certain deductions for more than a few pays. The system will wait until the employee has enough earnings, it doesn’t recover all arrears at one time and leave the employee with very little net pay. Therefore, recover the arrears one deduction at a time.

;:This rule is used for larger amount deductions where it is unlikely that there will be sufficient earnings to cover more than the regular deduction plus a single arrears transaction.
*__'Recover All At Once’__ recovers all arrears amount for this pay component regardless the number of times this deduction was in arrears.

;:This rule recovers arrears on a multiple transaction basis, for example when an employee is three deductions in arrears for the same [pay component|PAY COMPONENTS], the pay calculation process attempts to recover each of these three deductions on the next pay.

;:If there are insufficient earnings to collect the whole amount of the arrears transaction, the uncollected balance is generated as a new arrears transaction. This rule is used for deductions that are small enough for there to be a strong possibility of recovering more than one from the same pay.
;:Deduction_Recovery is a fixed lexicon ([X_DEDN_RECOVERY_RULE]) that you may use to look up the value.
\\


For more information on how the following fields work with the General Ledger please see the page [GENERAL LEDGER ACCOUNTS].
;[DR G/L Account|DGA_ID_DEBIT]: This is an optional 10 digit numeric field which allows the user to select the appropriate Debit Account Code for this pay component.
;[DR Suffix |GL_SUFFIX_TYPE_DR]:This is an optional field which allows the user to select the Debit GL Suffix Type from the  [X_GL_SUFFIX_TYPE] lexicon.
;[CR G/L Account|DGA_ID_CREDIT]: This is an optional 10 digit numeric field which allows the user to select the appropriate Credit Account Code for this pay component.
;[CR Suffix|GL_SUFFIX_TYPE_CR]:This is an optional field which allows the user to select the Credit GL Suffix Type from the  [X_GL_SUFFIX_TYPE] lexicon.
;[AP Vendor |AP_VENDOR]: This is an optional 16 alphanumeric field which allows the user to select a vendor from the [X_AP_VENDORS] lexicon. 


----
!!Define Pay Components (IPPC) - Premiums
Premium type usages provide the ability to specify the list of the premium type(s), if any, which are applicable to a [pay component|PAY COMPONENTS].

If a premium type usage is not defined, premiums of this type may not be used with the [pay component|PAY COMPONENTS].
;[Premium Type|PREMIUM_TYPE_CODE]:User defined premium type code e.g. 'shift' or 'night'. Premium_Type_Code from [P2K_SA_PREMIUM_TYPES] is a 16-character alphanumeric mandatory field that you must complete with a value from the LOV (F9) provided.
;[Distribution Rule|USE_PC_DISTRIBUTION]: This option enables the premium expenses either to be costed the same way as the pay component it’s attached to, or to be costed in conjunction with the Pay Line GL mask.
;:''Use Prem PC GL Mask (no Pay Line Distr override)
;:''Use Prem+PL GL Mask (no Pay Line Distr override) (Default Rule)
;:''Use PL PC GL Mask (no Pay Line Distr override)
;:''Use PL PC+PL GL Mask (no Pay Line Distr override)
;:Use_PC_Distribution is an optional lexicon [X_USE_PC_DISTRIBUTION].
\\
----
!!Define Pay Components (IPPC) - Retro Pay
If you wish retro pay to be calculated on the earnings of this [pay component|PAY COMPONENTS], you must use the retro pay tab. 

The Retro PC and the Retro Evaluation Method fields are mandatory; the Retro User Calc is an optional field.
;[Retro PC|PPC_ID_RETRO]:This field holds the [pay component|PAY COMPONENTS] into which retro earnings will be stored. This may be the original earnings [pay component|PAY COMPONENTS]. Retro_PC is an optional numeric field that you may either manually enter or use the LOV (F9).
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the retro [pay component|PAY COMPONENTS]. PC_Abbreviation is defaulted based on the Retro PC used.
;[Retro Method|RETRO_METHOD]:This field indicates how the retro pay will be evaluated, either by [pay component|PAY COMPONENTS] or by pay line. Retro_Method is a mandatory field you may fill with the fixed lexicon ([X_RETRO_METHOD]) provided.
;[Retro User Calc|MUC_ID_RETRO]:This field provides any User Calcs associated with this retro pay. User Calcs are ‘only’ used for retro on ‘non-earnings’ [pay components|PAY COMPONENTS] such as Benefits or an increase in a deduction. This feature is rarely used and UPRETRO is more commonly used to compute an increase in ‘Earnings’ into the past. Retro_User_Calc is an optional field you may fill manually or choose from the LOV (F9).
</pre>