This page (revision-77) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by KateN

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
77 26-Nov-2021 10:22 25 KB Kevin Higgs to previous
76 26-Nov-2021 10:22 24 KB Meg McFarland to previous | to last
75 26-Nov-2021 10:22 24 KB mmcfarland to previous | to last
74 26-Nov-2021 10:22 24 KB kparrott to previous | to last
73 26-Nov-2021 10:22 24 KB kparrott to previous | to last
72 26-Nov-2021 10:22 24 KB kparrott to previous | to last
71 26-Nov-2021 10:22 23 KB jescott to previous | to last
70 26-Nov-2021 10:22 23 KB rforbes to previous | to last
69 26-Nov-2021 10:22 23 KB jmyers to previous | to last
68 26-Nov-2021 10:22 23 KB jmyers to previous | to last
67 26-Nov-2021 10:22 22 KB jmyers to previous | to last
66 26-Nov-2021 10:22 22 KB jmyers to previous | to last
65 26-Nov-2021 10:22 22 KB jmyers to previous | to last
64 26-Nov-2021 10:22 22 KB jmyers to previous | to last
63 26-Nov-2021 10:22 22 KB jmyers to previous | to last
62 26-Nov-2021 10:22 22 KB jmyers to previous | to last
61 26-Nov-2021 10:22 22 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
IPPC
IPPC

Version management

Difference between version and

At line 1 removed 2 lines
IPPC
At line 6 changed one line
[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.
__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.
At line 8 changed one line
Pay Components are defined and maintained on the Define Pay Components (IPPC) form.
You may define and maintain pay components through the Define Pay Components (IPPC) form.
At line 10 changed one line
[Pay Component|PAY COMPONENTS] Data is stored in the [P2K_PR_PAY_COMPONENTS], [P2K_PR_PC_RULES] and [P2K_PR_PC_DETAILS] tables.
You may access this feature under the Screen/Form menu: __Payroll > Setup and Definitions > Define Pay Components__
At line 12 changed one line
;[PC Code|PC_CODE]:A PC code is a unique number code from 1 to 9,999 assigned to uniquely identify the pay component within the system.
Pay Component Data is stored in the [P2K_PR_PAY_COMPONENTS], [P2K_PR_PC_RULES] and [P2K_PR_PC_DETAILS] tables.
At line 14 removed one line
;[Abbr.|PC_ABBREVIATION]:This field holds the short alpha description of the pay component used for printing on check and deposit statements, lists and pay registers. Although this field accepts 30 characters, users should keep the abbreviation as short as possible.
At line 16 changed 6 lines
;[Desc|DESCRIPTION]: This field displays a longer description of the pay component than can be entered in the abbreviation field.
;[PC Usage|PC_USAGE_CODE]:This field is used to categorize when and how the pay component 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). [Pay Components Usages|PAY COMPONENT USAGES] are provided with the application.
;[Usage Desc|DESCRIPTION]: This field gives a short description of the [usage|PAY COMPONENT USAGES], specifically when and how the pay component 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 Code|PC_CODE]:A PC code is a unique number code from 1 to 9,999 assigned to uniquely identify the paycomponent 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 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 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 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 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_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 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 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 (usage 14) to work correctly. If this toggle is not checked, information will not be stored in the statistic attached to the pay component. Store_Results is an optional toggle field.
;[Assoc. PC|PC_CODE]: Associated pay components are used to store the number of another pay component 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 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 is to hold the result of a pay element it needs to be indicated here. If (PPE) appears in the usage, the PC should be associated to an element. This field can be filled in after the 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.
At line 26 changed 13 lines
*Suppress a user calculation
;%%info The PC ACTION does not impact how the values are stored on the YTD tables. Setting the value to REPLACE will not result in the YTD being replaced each pay. IPVT will display a cumlative amount regardless of this set up.__
;[Store Results|STORE_RESULTS]: If this toggle is set to ON, the value(s) of the pay component 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 set to NO, the pay component 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. The Store Results toggle must be set to ON in order for a Statistical pay component (usage 14) to work correctly. If this toggle is set to NO, information will not be stored in the statistic attached to the pay component.
;[Assoc. PC|PC_CODE]: Associated pay components are used to store the number of another pay component that may be associated with this PC. For example, if the PC being defined is a Time PC, then the Earnings PC would be its Associated PC. This field may need to be left blank until all of your pay components are completed.  All Earnings PC that have time associated to them must have the Associated PC for check/deposit form printing.   Example - Regular Earnings PC must have Regular Hours PC in the Assoc. PC field. 
;[Assoc. Description|DESCRIPTION]:A description of the pay component is provided here.
;[Assoc. 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 defined in this field.
;[Assoc. Element|ELEMENT_CODE]: If the pay component is to hold the result of a [pay element|PAY ELEMENTS], it needs to be defined here. If (PPE) appears in the usage, the PC should be associated to a pay element. This field can be defined after the pay elements are completed.
*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 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 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 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 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 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)
At line 41 changed 5 lines
!!PC Information tab
;[ADP Tax Code|ADP_TAX_CODE]:This field is used to define the ADP tax code. These tax codes are decided between ADP and the client and must be mapped in the ADP system to ensure that the amounts collected are applied to the correct tax accounts.
;[ADP Tax Type|ADP_TAX_TYPE]:This field is used to define the ADP tax code and indicates whether the amount is considered a Deduction, a Contribution, a subject amount or a taxable amount.
;[ADP Tax Resident|ADP_TAX_RESIDENT]:When this toggle is set to ON, indicates that the tax is a resident tax, not work tax.
;[Third Party to Disburse|THIRD_PARTY_TO_DISBURSE]:This field is used for reporting purposes.
!!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|????]: If the Enter Sundry toggle is ON, the pay component may be entered on a sundry line (i.e.a recurring type of transaction). If the toggle is OFF, the pay component may not be entered on sundry lines. Enter_Sundry_Line is an optional toggle field.
;[Enter Pay Lines|???]: If the Enter Pay Lines toggle is ON the pay component may be entered on a pay line (i.e. a one-time type of transaction). If the toggle is OFF, the pay component may not be entered on pay lines. Enter_Pay_Lines is an optional toggle field.
;[Generate Details|??]: If the Generate Details toggle is ON, this pay component has associated pay component detail records.
If the toggle is OFF, there are no related PC details. Generate_Details is an option toggle field.
;[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|??]: 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. 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 that need to be related to the rate of pay and/or distribution code. Default_The_Position is an option toggle field.
;[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|???]: 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 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|???]: 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|??]: 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|???]: 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\??]: 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|???]: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|??]: 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|????]: 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|???]: 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|???]: 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|??]: 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|??]: 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|??]: 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.
At line 48 changed 20 lines
!!Elements Used In tab
;[Element|ELEMENT_CODE]:This field holds the element code assigned to uniquely identify the element. Elements are groups of pay components that need to be tallied together to perform a specific calculation such as Taxes, UserCalcs, Benefits, etc.
;[Basic|BASIC_ELEMENT]: When this toggle is set to ON, the element is made up by a list of [pay components|PAY COMPONENTS] only and is considered a basic [element|PAY ELEMENTS].
;[Description|DESCRIPTION]:A short description of the element is provided here.
;[Seq #|ELEMENT_PC_SEQUENCE]:This field will determine the sequential order (1 to 99999) in which pay components are processed and displayed within the element.
;[Operator|ELEMENT_OPERATOR]:This field identifies the mathematical operator (Add or Subtract) that defines how the pay components will be processed.
\\
----
;[Entity|ENTITY_CODE]:A pay component may need to vary its rules or detail by entity.
;[Unit|UNIT_CODE]: A pay component may need to vary its rules or detail by unit, within an entity.
;[Group|GROUP_CODE]: A pay component may need to vary its rules or detail by group, within a unit, within an entity.
;[Basis|TIME_BASIS]:If the pay component is to store time or units, the basis needs to be defined, such as days, hours, units, in this field. While this field is optional, it is recommended that users define it if a retro pay will be processed.
;[Pay Point|PAY_POINT_TYPE]: From the pay point set previously set up, this field defines when this pay component needs to be picked up for processing during the pay calculation.
;[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 can 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.
;[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 the front end of the Time, Attendance and Time Scheduling applications with Personality’s payroll application. Example: PC 110 Sick Time would be associated to a Time Code called SICK HRS for Attendance purposes.
\\
----
!!PC Rules tab
This section defines 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 set to ON, the pay component can be entered on a sundry line, such as a recurring type of transaction. If the toggle is set to OFF, the pay component can not be entered on sundry lines.
!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.
At line 69 changed 177 lines
;[Enter Pay Lines|ENTER_PAY_LINES]: If the Enter Pay Lines toggle is set to ON, the pay component can be entered on a pay line, such as a one-time type of transaction. If the toggle is set to OFF, the pay component can not be entered on pay lines.
;[Generate Details|GENERATE_DETAILS]: If the Generate Details toggle is set to ON, this pay component has associated pay component detail records. If the toggle is set to OFF, there are no related PC details.
;[Enter Position|ENTER_POSITION]: If the Enter Position toggle is set to ON, users can override the position code on the pay line. If the toggle is set to OFF, it can not be entered.
;[Default Position|DEFAULT_THE_POSITION]: If the foundation structure is set up with Positions, then this toggle must be set to ON to allow the position defined on the employee’s assignment file to be defaulted for this pay component. If the foundation structure was set up with only Jobs, then this toggle does not need to be set to ON. This toggle only needs to be set to ON for pay components that need to be related to the rate of pay and/or distribution code.
;[Enter Job|ENTER_JOB]: If this toggle is set to ON, users can may override the job code on the pay line. If the toggle is set to OFF, it can not be entered.
;[Default Job|DEFAULT_THE_JOB]: If the Foundation structure is set up with Jobs, then this toggle must be set to ON to allow the Job defined on the employees assignment file to be defaulted for this pay component. This toggle only needs to be set to ON for pay components that need to be related to the Rate of pay and/or Distribution code.
;[Sundry Assgn Match|SUNDRY_BY_ASSIGNMENT]: This toggle is used for sundries which apply only to an employee’s specific assignment, such as primary or secondary assignment.
;[Enter Date|ENTER_DATE]: If the Enter Date toggle is set to ON, users can enter the transaction date on the pay line. If the toggle is set to OFF, the date can not be entered.
;[Enter Value|ENTER_TIME]: If the Enter Value toggle is set to ON, users can enter the time on the pay line. If the toggle is set to OFF, it can not be entered.
;[Enter Wage Rate|ENTER_WAGE_RATE]: If the Enter Wage Rate toggle is set to ON, users can override the wage rate on the pay line. If the toggle is set to OFF, it can not be entered.
;[Enter Rate Basis|ENTER_WAGE_RATE_BASIS]:If the Enter Rate Basis toggle is set to ON, users can override the rate basis on the pay line. If the toggle is set to OFF, it can not be entered.
;[Reference|ENTER_DESCRIPTION]: The Reference field is used on the pay lines of either the [IPPH] (Pay Header) or [IPSN] (Sundry) forms. It allows users to enter a reference or description of the pay line or the sundry to define how they will be used. This reference information can be either anecdotal or more structured, such as a Union Code or Court Number. Users can select either:
*Enter Vendor Code - For pay components that will be used for [Accounts Payable|ACCOUNTS PAYABLE - UPVEND].
*Enter Description - Users can enter up to 200 characters as reference on the pay lines. This entry will not be checked against values within any lexicon.
;[UserCalc|USER_CALC_CODE]:This field provides the name of the UserCalc associated with the PC Rule.
;[Enter Premiums|ENTER_PREMIUMS]: If the Enter Premiums toggle is set to ON, users can enter premiums on the pay line. If the toggle is set to OFF, it can not be entered.
;[Enter Work Jurisdiction|ENTER_WORK_GEO]: If the Enter Work Jurisdiction toggle is set to ON, users can override the work jurisdiction on the pay line. If the toggle is set to OFF, it can not be entered. Enter_Work_Geo if the Pay Point toggle is set to ON, users can override the pay point on the pay line. If the toggle is set to OFF, it can not be entered.
;[Enter Pay Point Type|ENTER_PAY_POINT]: If the Enter Pay Point Type toggle is set to ON, users can enter the pay point type. If the toggle is set to OFF, it can not be entered.
;[Enter Pay Point Sequence|ENTER_PAY_POINT_SEQUENCE]: If the Enter Pay Point Sequence toggle is set to ON, users can enter the sequence of the task on the pay line. If the toggle is set to OFF, it can not be entered.
;[Enter User Calc|ENTER_USER_CALC]: If the Enter UserCalc toggle is set to ON, users can enter a UserCalc on the pay line. If the toggle is set to OFF, it can not be entered.
;[Enter Detail Action|ENTER_ACTION]: If the Enter Detail Action toggle is set to ON, users can override the PC action on the pay line. If the toggle is set to OFF, it can not be entered.
\\
----
!!PC Detail Rules tab
This section defines what will be generated in the Pay Line Details when a PC is chosen for data entry.
Example: If a time PC, users will want to generate the earnings that would be associated to that time.
;[PC|PC_CODE]: This field defines the pay component number, if Time or Amount is being used.
;[Abbreviation|PC_ABBREVIATION]: This field is automatically populated when the pay component number is entered.
;[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 balances, 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 detail.
;[Calculation Method|PC_CALC_METHOD]: Defines the method 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.
;[Rate Source|PC_RATE_SOURCE]: This field defines from where the wage rate is derived and used to determine the value of the pay component detail.
;[Assignment Rate|HIGHER_OF_RATE]:The Assignment Rate applies the rate based on the assignment rate.
!Override Field Entry
;[Rate|ENTER_RATE]:If the Override Rate toggle is set to ON, users can override the wage rate on the Pay Line Details. If the toggle is set to OFF, the wage rate can not be overridden.
;[Value|ENTER_VALUE]: If the Override Value toggle is set to ON, users can override the value on the Pay Line Details. If the toggle is set to OFF, the value can not be overridden.
;[User Variable|ENTER_USER_VARIABLE]: If the Override User Variable toggle is set to ON, users can enter the user variable on the pay line details. If the toggle is set to OFF, the variable can not be overridden.
;[Distributions|ENTER_DISTRIBUTION]: If the Enter Distribution toggle is set to ON, users can enter the distribution on the Pay Line Details. If the toggle is set to OFF, the distribution can not be entered.
;[Element|ENTER_ELEMENT]: If the Override Element toggle is set to ON, users can override the element on the Pay Line Details. If the toggle is set to OFF, the element can not be overridden.
!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's 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 are generated.
;[Salary Rate Method|SALARY_RATE_METHOD]: For salaried employees, there are multiple ways the system can derive a salary or wage value for the pay line. This field defines the method to calculate this rate. For more information see the page [Using Salary Rate Methods|USING SALARY RATE METHODS].
;[Custom Rate Logic|CUSTOM_RATE_LOGIC]: Custom rate logic is logic preprogrammed into [{$applicationname}], based on client specifications.
!Variables
;[Element Code|ELEMENT_CODE]: If a pay element (Elem) is defined in the calculation method, it needs to be defined here. Pay elements are maintained on the [IPPE] (Element) form.
;[User Variable|USER_VARIABLE_CODE]: If a user variable (UVAR) is defined in the calculation method, it needs to be defined here. User Variables are maintained on the [IMVR] (Maintain User Variables) form.
;[Statistic|STAT_CODE]: If the calculation method used requires a statistic, this field can be used to compute the detailed amount.
----
!!Acct Arrears tab
Review the [DEDUCTIONS AND ARREARS] page for additional details on the logic of the following fields.
;[Insufficient Earnings|POSITIVE_DEDUCTION]: Defines the method 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|POSITIVE_ARREARS] toggle also be set to ON with this setting, in order to generate an arrears transaction for any balance that could not be taken.
*'Full With Advance' takes the full deduction and advances the employee any shortfall. Used for items such as insurance coverage. It is recommended that the [Create Arrears|POSITIVE_ARREARS] toggle be set to ON if an arrears transaction must be generated to recover the amount advanced to the employee on a subsequent pay.
*When there is Insufficient Earnings and the rule is to take the deduction ‘Full with Advance’, this will advance an amount to cover the deduction that could not be taken for this pay component. \\ \\ To create arrears for the deduction portion that is not taken (the Advance amount in this case), the 'Create Arrears' toggle must be set to ON. Once set to ON, users can optionally set up the Arrears PC. When the Arrears PC is set up, the arrears will be generated under this pay component (such as PC 3369). Otherwise the arrears will be generated under the original deduction pay component (such as PC 3368). \\ \\When the deduction (such as PC 3368) is a Negative Deduction amount, and the rule is to ‘Add to Gross’, the 'Collect Back' must be set to ON. Once set to ON, the negative deduction will be set up as an arrear under the Recoverable Advance pay component for recovery in the next pay. \\ \\After arrears are generated, users must define the:\\*Arrears Recovery rule to recover the arrears. Options are Only One Per Pay or Recover All at Once. \\*CR G/L Account field should be set up for the deduction pay component to generate journal entries.
;[Create Arrears|POSITIVE_ARREARS]: If the Create Arrears toggle is set to 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 set to OFF, no arrears are generated for the insufficient earnings, and the deduction is forgotten.
;[Arrears PC|]:
;[Abbreviation|]:
;[Negative Deduction|NEGATIVE_DEDUCTION]: The negative deduction rule determines how a negative deduction, such as 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 (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|NEGATIVE_ARREARS] toggle must be set to ON to generate an arrears transaction to recover the amount advanced on a subsequent pay.
;[Collect Back|NEGATIVE_ARREARS]: This toggle is only set to ON for one pay component - Advance Recovery. If this toggle is set to 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 set to 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).
;:''Example:
;:''If the Collect Back toggle is set to OFF:
;:''Gross 1000
;:''Deduction - 20
;:''Net = 1020 (Correct – because the company owed the employee)
;:''Next Pay: Nothing happens
\\
;:''If the Collect Back toggle is set to ON:
;:''Gross 1000
;:''Deduction - 20
;:''Net = 1020 (Correct) Arrears created (20)
;:''Next Pay:
;:''Gross 1000
;:''Arrears - 20
;:''Net = 980 (If ‘Collect Back’ toggle is set to ON, it will result in the deduction being recovered on the next pay)
;:Negative_Arrears is an optional toggle field.
;:The 'Collect Back' toggle is only set ON for [pay component usage|PAY COMPONENT USAGES] of 5 - ‘Advance Recovered’. If the 'Collect Back' is set to 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. Example: When an employee is three deductions in arrears for the same pay component, the pay calculation process attempts to recover only the oldest arrears transaction for that pay component. 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 does not 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 arrear amounts for this pay component, regardless of the number of times this deduction was in arrears.
;:This rule recovers arrears on a multiple transaction basis. Example: When an employee is three deductions in arrears for the same pay component, 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.
\\
For more information on how the following fields work with the General Ledger, please see the [GENERAL LEDGER ACCOUNTS] page.
\\
;[DR G/L Account|DGA_ID_DEBIT]: This field allows users to define the appropriate Debit Account Code for this pay component.
;[DR Suffix |GL_SUFFIX_TYPE_DR]:This field allows users to define the Debit GL Suffix Type.
;[CR G/L Account|DGA_ID_CREDIT]: This field allows users to define the appropriate Credit Account Code for this pay component.
;[CR Suffix|GL_SUFFIX_TYPE_CR]:This field allows users to define the Credit GL Suffix Type.
;[AP Vendor |AP_VENDOR]:This field allows users to define a vendor.
\\
----
!!Premiums tab
Premium type usages provide the ability to define the list of the premium type(s), if any, which are applicable to a pay component.
If a premium type usage is not defined, premiums of this type can not be used with the pay component.
;[Premium Type|PREMIUM_TYPE_CODE]:User defined premium type code, such as 'shift' or 'night'.
;[Distribution Rule|USE_PC_DISTRIBUTION]: This option enables the premium expenses to be costed either 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)
\\
----
!!Retro Pay tab
If a users wants retro pay to be calculated on the earnings of this pay component, the retro pay tab must be defined.
The Retro PC and the Retro Evaluation Method fields are mandatory; the Retro UserCalc is an optional field.
;[Retro PC|PPC_ID_RETRO]:This field holds the pay component the retro earnings will be stored. This can be the original earnings pay component.
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the retro pay component. PC_Abbreviation is defaulted based on the Retro PC defined.
;[Retro Method|RETRO_METHOD]:This field defines how the retro pay will be evaluated, either by pay component or by pay line.
;[Retro User Calc|MUC_ID_RETRO]:This field defines any [UserCalcs|USERCALC] associated with this retro pay. UserCalcs are ‘only’ used for retro on ‘non-earnings’ 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.
----
![Notes|Edit:Internal.IPPC]
[{InsertPage page='Internal.IPPC' default='Click to create a new notes page'}]
For example, if a time PC Users will want ePersonality to generate the earnings that would be
associated to that time.
This page (revision-77) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop