This page (revision-89) was last changed on 26-Nov-2021 10:22 by Karen Parrott

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

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
89 26-Nov-2021 10:22 43 KB Karen Parrott to previous
88 26-Nov-2021 10:22 42 KB mmcfarland to previous | to last
87 26-Nov-2021 10:22 42 KB kparrott to previous | to last
86 26-Nov-2021 10:22 42 KB kparrott to previous | to last
85 26-Nov-2021 10:22 42 KB kparrott to previous | to last
84 26-Nov-2021 10:22 41 KB jescott to previous | to last
83 26-Nov-2021 10:22 41 KB jescott to previous | to last
82 26-Nov-2021 10:22 41 KB jescott to previous | to last
81 26-Nov-2021 10:22 41 KB jescott to previous | to last

Page References

Incoming links Outgoing links
IPPH
IPPH

Version management

Difference between version and

At line 3 changed one line
Through the Maintain Employee Pays (IPPH) form, you may create and maintain employee pays.
Users can create and maintain employee pays on the Maintain Employee Pays (IPPH) form.
At line 5 changed one line
In addition, through this form:
In addition:
At line 7 changed 2 lines
*Field access and rules for [pay component|PAY COMPONENTS] values are defined by the Pay Component Rules ([IPPC]) form.
*Position, Job, Rate and/or Distribution code may be overridden.
*Position, Job, Rate and/or Distribution codes can be overridden.
At line 10 added one line
Field access and rules for [pay component|PAY COMPONENTS] values are defined on the Pay Component Rules ([IPPC]) form.
At line 12 changed 3 lines
\\
\\
;[Pay #|PAY_NUMBER]:This field shows the unique pay number assigned to each pay header that is created for a person.
\\ \\
At line 15 added 8 lines
NOTE: As of the 5.05.00 release, the Tax Jurisdiction editor fields on this form will be in view only. To have the Tax Jurisdiction button available in the Admin UI (no restriction in the Browser UI) you have to setup the following:
*Site preference US TAX SERIES set to 1
*Logging in as 'MASTER', on IMLN for Lexicon Name=X_TABLES_NO_SITE, the DTX entry must be deleted.
\\ \\
;[Pay #|PAY_NUMBER]:This field shows the unique pay number assigned to each pay header that is created for an employee.
At line 18 changed one line
;[Payroll|PAYROLL_CODE]:This field shows the payroll associated to the group indicated.
;[Payroll|PAYROLL_CODE]:This field shows the payroll associated to the group defined.
At line 20 changed one line
;[Group|GROUP_CODE]:This is the group derived from the pay header assignment work rule. From the assignment of this pay header, it specifies a work rule on [IEAS] form. Then on [IDWR] for the Assignment Work Rule, it points to the Pay Header creation ‘Group Source’.
;[Group|GROUP_CODE]:This is the group derived from the pay header assignment work rule. From the assignment of this pay header, it defines a work rule on the [IEAS] form. Then on [IDWR] for the Assignment Work Rule, it points to the Pay Header creation ‘Group Source’.
At line 22 changed one line
*Posn/Prime Assignment - Group code for this assignment will first check if this assignment is associated with a position, then use the Posn Group Code, otherwise use employee’s prime assignment.
*Posn/Prime Assignment - Group code for this assignment will first check if this assignment is associated with a position, then use the Posn Group Code. Otherwise the employee’s prime assignment is used.
At line 24 changed one line
;:Group_Code will be defaulted from the Group Source tab located in IDWR.
;:Group_Code will be defaulted from IDWR, 'Group Source' tab.
At line 26 changed one line
;[Unit|UNIT_CODE]:This is the unit to which the group indicated belongs.
;[Unit|UNIT_CODE]:The unit the defined group belongs to.
At line 28 changed one line
;[Stage|PAY_HEADER_STAGE]:This field indicates the status of a pay header.
;[Stage|PAY_HEADER_STAGE]: Defines the status of a pay header.
At line 30 changed one line
;[Seq #|DRV_PAY_RUN_SEQUENCE_NUMBER]: This field denotes the order that the pay header was processed within the pay run. This field will be displayed as ‘N/A’ if this pay headers is not attached to a pay run. Pay_Run_Number will be system populated if this pay is calculated.
;[Seq #|DRV_PAY_RUN_SEQUENCE_NUMBER]: This field denotes the order that the pay header was processed within the pay run. This field will be displayed as ‘N/A’ if the pay headers are not attached to a pay run. The Pay_Run_Number will be populated by the system if this pay is calculated.
At line 32 changed one line
;[Source|PAY_HEADER_SOURCE]:Indicates the process that created the pay header.
;[Source|PAY_HEADER_SOURCE]:Defines the process that created the pay header.
At line 40 changed one line
Pay headers are associated with a specific pay period, pay category and batch. They may be created by manual entry, or generated through several automated processes, such as the transaction generator and the transaction loader.
Pay headers are associated with a specific pay period, pay category and batch. They can be created by manual entry, or generated through several automated processes, such as the transaction generator and the transaction loader.
At line 46 changed one line
;[Assignment|ASSIGNMENT_CODE]:This field will display the assignment for which this pay is generated. This assignment is also established by [UPTR] or [UPTL] when loading transactions in bulk. During that process, multiple pays per period may be created for multiple assignments. Assignment_Code will default to the employee’s prime assignment and can be manually entered or use the LOV (F9).
;[Assignment|ASSIGNMENT_CODE]:This field displays the assignment this pay is generated for. This assignment is also established by [UPTR] or [UPTL] when loading transactions in bulk. During that process, multiple pays per period may be created for multiple assignments. The Assignment_Code will default to the employee’s prime assignment and can be manually entered or select from the LOV (F9).
At line 48 changed one line
;[Batch #|BATCH_NUMBER]: This field shows the batch to which this pay is attached.
;[Batch #|BATCH_NUMBER]: This field shows the batch this pay is attached to.
At line 50 changed one line
;[Pay Period|PAY_PERIOD]:This field identifies the pay period for which this pay is being generated. Pay periods are numbered by the year, followed by the period of the year. Pay_Periods from [P2K_PR_PAY_PERIODS] will default from the batch entered but you may manually enter or use the LOV (F9).
;[Pay Period|PAY_PERIOD]:This field defines the pay period this pay is being generated for. Pay periods are numbered by the year, followed by the period of the year. Pay_Periods from [P2K_PR_PAY_PERIODS] will default from the batch entered, but users can enter this manually or select from the LOV (F9).
At line 52 changed one line
;[Starting|PAY_PERIOD_START_DATE]:Period start is the date of the first day of the pay period. Pay_Period_Start_Date will default from the pay period entered.
;[Starting|PAY_PERIOD_START_DATE]:Defines the first day of the pay period. Pay_Period_Start_Date will default from the pay period entered.
At line 54 changed one line
;[Ending|PAY_PERIOD_END_DATE]:Period end is the date of the last day of the pay period. Pay_Period_End_Date will default from the pay period entered.
;[Ending|PAY_PERIOD_END_DATE]:Defines the last day of the pay period. Pay_Period_End_Date will default from the pay period entered.
At line 56 changed one line
;[Category|PAY_CATEGORY_CODE]:This field shows the user-assigned code that uniquely identifies the pay category. Pay_Category_Code will default from the batch entered but you may manually enter or use the LOV (F9).
;[Category|PAY_CATEGORY_CODE]:This field defines the user-assigned code that uniquely identifies the pay category. Pay_Category_Code will default from the batch entered but users can enter this manually or select from the LOV (F9).
At line 58 changed one line
;[Pay Point Set|PAY_POINT_SET_CODE]:This field defines the set of tasks that will be used when calculating the pay. Pay_Point_Set_Code will default from the pay category but you may manually enter or use the LOV (F9).
;[Pay Point Set|PAY_POINT_SET_CODE]:This field defines the set of tasks that will be used when calculating the pay. Pay_Point_Set_Code will default from the pay category but users can enter this manually or select from the LOV (F9).
At line 60 changed one line
;[Trace Level|TRACE_LEVEL]:When performing a trial calculation, you may specify the level of message that the calculation report should display. This field is used for troubleshooting purposes.
;[Trace Level|TRACE_LEVEL]:When performing a trial calculation, users can define the level of messages that the calculation report should display. This field is used for troubleshooting purposes.\\The Trace Level can also be used to override the Trace level during [UPCALC]. Normally [UPCALC] is executed at the 'Exceptions' level. If a particular pay has issues of some kind, users can the pay run at 'Utility Level' by changing this field value.
At line 62 changed one line
;[First Pay in Period|FIRST_PAY_IN_PERIOD]: This field is populated during the [UPAUDT] process and is used to qualify processing frequencies. If the First Pay In Period toggle is ON, this is a regular pay category header, and the first time the employee has been paid in this pay period. If the toggle is OFF, the employee has already been paid in the pay period. First_Pay_In_Period is system updated during UPAUDT.
;[First Pay in Period|FIRST_PAY_IN_PERIOD]: This field is populated during the [UPAUDT] process and is used to qualify processing frequencies. If the 'First Pay In Period' toggle is set to ON, this is a regular pay category header, and the first time the employee has been paid in this pay period. If the toggle is set to OFF, the employee has already been paid in the pay period. First_Pay_In_Period is updated by the system during UPAUDT.
At line 64 changed one line
;[1st Pay in Month|FIRST_PAY_IN_MONTH]: This field is populated during the UPAUDT process and is used to qualify processing frequencies. If the First Pay In Month toggle is ON, the pay header is for the first time the employee has been paid in the calendar month for a regular pay. If the toggle is OFF, there has already been a regular pay created or paid for this (or a prior) period in the month. First_Pay_In_Month is system updated.
;[1st Pay in Month|FIRST_PAY_IN_MONTH]: This field is populated during the UPAUDT process and is used to qualify processing frequencies. If the 'First Pay In Month' toggle is ON, the pay header is for the first time the employee has been paid in the calendar month for a regular pay. If the toggle is OFF, there has already been a regular pay created or paid for this period (or a prior) in the month. First_Pay_In_Month is updated by the system.
At line 66 changed one line
;[Audited|AUDITED]:This field is populated during the UPAUDT process. If the Audited toggle is ON, the pay header has passed all the validation checks of the audit process (UPAUDT) and is ready to be processed through pay calculation. If the toggle is OFF, either the pay header has not yet been audited, or it has failed to pass the transaction audit. The Audited toggle on the pay header is not set unless all of the individual pay lines associated with that header have also passed the transaction audit. Audited is system updated.
;[Audited|AUDITED]:This field is populated during the UPAUDT process. If the 'Audited' toggle is ON, the pay header has passed all the validation checks of the audit process (UPAUDT) and is ready to be processed through pay calculation. If the toggle is OFF, either the pay header has not yet been audited, or it has failed to pass the transaction audit. The Audited toggle on the pay header is not set unless all of the individual pay lines associated with that header have also passed the transaction audit. Audited is updated by the system.
At line 68 changed one line
;[Sundry Attached|SUNDRY_ATTACHED]: This field is populated during the UPAUDT process. If the Prepared toggle is ON, the time sheet has been successfully processed by UPAUDT. To prepare this time sheet to be paid, UPAUDT has pulled together all related information (e.g. user calculations, sundry items, benefits, etc.) for this pay header from the Pay Point set (as defined in [IPPP]). If you are changing any ‘Pay Point Set’ information on [IPPP] form, you will need to run [UPUNPREP] and then run UPAUDT again to prepare. Sundry_Attached is system updated.
;[Sundry Attached|SUNDRY_ATTACHED]: This field is populated during the UPAUDT process. If the Prepared toggle is ON, the time sheet has been successfully processed by UPAUDT. To prepare this time sheet to be paid, UPAUDT has pulled together all related information (such as user calculations, sundry items, benefits, etc.) for this pay header from the Pay Point set (as defined in [IPPP]). If a user is changing any ‘Pay Point Set’ information on the [IPPP] form, users should run [UPUNPREP] and then run UPAUDT again to prepare. Sundry_Attached is system updated.
At line 70 changed one line
;[Journalized|JOURNALIZED]:This field is populated during the [UPGL] process. The UPGL uses the ‘Journalized’ toggle on the pay header to determine if the pays have been posted or not.\\
;[Journalized|JOURNALIZED]:This field is populated during the [UPGL] process. UPGL uses the ‘Journalized’ toggle on the pay header to determine if the pays have been posted or not.\\
At line 74 changed one line
;[Journalized Fund|JOURNALIZED_FUND]: This field is populated during the UPGL process. If the Journalized Fund toggle is ON, that segment of the GL Distribution can be used as a 'Fund'. Journalized_Fund is system updated.
;[Journalized Fund|JOURNALIZED_FUND]: This field is populated during the UPGL process. If the 'Journalized Fund' toggle is ON, that segment of the GL Distribution can be used as a 'Fund'. Journalized_Fund is system updated.
At line 76 changed one line
;[Time Sheet Returned|TIMESHEET_RETURNED]:This field indicates to the system that the employee has returned the time sheet. If the Time sheet Required toggle on [IDWR] - Status Rules tab is ON, then a physical time sheet for the employee must be received at data entry time. You must physically turn the Time Sheet Returned toggle on, otherwise this time sheet will not pass the UPAUDT process.
;[Time Sheet Returned|TIMESHEET_RETURNED]:This field indicates that the employee has returned the time sheet. If the 'Time Sheet Required' toggle on [IDWR] - Status Rules tab is ON, then a physical time sheet for the employee must be received at data entry time. Users must manually set the Time Sheet Returned toggle to ON, otherwise the time sheet will not pass the UPAUDT process.
At line 78 changed one line
;[Posted Retirement|POSTED_RETIREMENT]:This field indicates to the system that the [UPCAPERSXML] process has been run and this pay header has been processed. If the toggle is ON, then the [UPCAPERSXML] has been run with the Test Report parameter set to 'NO'. If the toggle is OFF, then the [UPCAPERSXML] has been run with the Test Report parameter set to 'YES'.
;[Posted Retirement|POSTED_RETIREMENT]:This field indicates that the [UPCAPERSXML] process has been run and this pay header has been processed. If this toggle is ON, then [UPCAPERSXML] has been run with the Test Report parameter set to 'NO'. If the toggle is OFF, then [UPCAPERSXML] has been run with the Test Report parameter set to 'YES'.
At line 80 changed one line
;[Trial Pay|ACT_LAUNCH_TRIAL]: This button allows you to calculate one pay header in non-update mode. This field is very useful for trial runs and for testing.
;[Trial Pay|ACT_LAUNCH_TRIAL]: This button allows users to calculate one pay header in non-update mode. This field is very useful for trial runs and for testing.
At line 82 changed one line
;[Cancel Pay|ACT_CANCEL_PAY_HEADER]: This button allows you to mark a pay header as cancelled which in turn will be physically removed by the audit process.
;[Cancel Pay|ACT_CANCEL_PAY_HEADER]: This button allows users to mark a pay header as cancelled, which in turn will be physically removed by the audit process.
At line 84 changed one line
;[Revert Pay|ACT_REVERT_PAY_HEADER]:This button allows you to revert a pay. It will undo the pay, unprepare the pay and re-prepare the pay. When this is done, all the [IPSN] Declining Balance amounts will be reverted back to their original values.
;[Revert Pay|ACT_REVERT_PAY_HEADER]:This button allows users to revert a pay. It will undo the pay, unprepare the pay and re-prepare the pay. When this is done, all the [IPSN] Declining Balance amounts will be reverted back to their original values.
At line 93 added one line
At line 87 changed one line
;[Pay By|PAY_BY_CHECK]:This field indicates whether the payment will be overridden by check or prime deposit. If this field is left blank, the pay method rules as defined in [IPPM] will be used for this pay.
;[Pay By|PAY_BY_CHECK]:This field defines whether the payment will be overridden by a check or prime deposit. If this field is left blank, the pay method rules defined on [IPPM] will be used for this pay.
At line 89 changed one line
;[Check Amount|CHECK_AMOUNT]:This field shows the amount of the check associated with the pay, only if it is a ‘[hand check|HAND CHECK]’.
;[Check Amount|CHECK_AMOUNT]:This field shows the amount of the 'hand written check' only ([hand check|HAND CHECK]) associated with the pay.
At line 91 changed one line
;[Pay Issue Date|PAY_ISSUE_DATE]: The Pay Issue Date is the date that payment is issued for the time sheet. Pay_Issue_Date will default from the pay period chosen, but may be overridden.
;[Pay Issue Date|PAY_ISSUE_DATE]: Defines the date the payment is issued for the time sheet. Pay_Issue_Date will default from the pay period chosen, but can be overridden.
At line 93 changed one line
;[Check #|CHECK_NUMBER]:The check number is assigned by you from the manual check range for the organization’s bank from [IPBA]. This field is only used for manually issued checks. Check_Number is system updated.
;[Check #|CHECK_NUMBER]:The check number is assigned by the user from the manual check range for the organization’s bank from [IPBA]. This field is used only for manually issued checks. Check_Number is system updated.
At line 104 added 2 lines
At line 97 changed one line
In the US, jurisdictions are defined by the Vertex GEO code.
In the US, jurisdictions are defined by the Symmetry GEO code.
At line 99 changed one line
In Canada, jurisdictions are supplied with [{$applicationname}].
In Canada, jurisdictions are provided with Personality software.
At line 101 changed one line
If an employee works in an area that is not in the province where they are required to pay taxes, you will identify their work area under the Work Province tab and the province to which they are paying taxes under the Work Jurisdiction tab.
If an employee works in an area that is not in the Province where they are required to pay taxes, users will identify their work area under the Work Province tab and the Province they are paying taxes to under the Work Jurisdiction tab.
At line 103 changed one line
For example, an Ontario employee works in Zimbabwe but is required to be taxed according to Ontario legislation. For this employee, you will then enter ‘Zimbabwe’ as their work province and ‘Ontario‘as their work jurisdiction.
Example: An Ontario employee works in Zimbabwe but is required to be taxed according to Ontario legislation. For this employee, users should then enter ‘Zimbabwe’ as their Work Province and ‘Ontario‘ as their Work Jurisdiction.
At line 105 changed one line
;[Work State/Prov|DSP_ID_WORK]:This field shows the State or Province code standard abbreviation where the employee works. State_Province from [P2K_CM_STATE_PROVINCES] will default from the employee’s Assignment form but you may manually enter or use the LOV (F9).
;[Work State/Prov|DSP_ID_WORK]:This field shows the State or Province code standard abbreviation where the employee works. State_Province from [P2K_CM_STATE_PROVINCES] will default from the employee’s Assignment form, but users can enter this manually or select from the LOV (F9).
At line 107 changed one line
;[Work Jurisdiction|DTX_ID_WORK]:This field holds the Geo code of the employee’s work tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] will default from the employee’s Assignment form however, you may manually enter or use the LOV (F9).
;[Work Jurisdiction|DTX_ID_WORK]:This field holds the Geo code of the employee’s work tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] will default from the employee’s Assignment form, but users can enter this manually or select from the LOV (F9). \\See NOTE above for functionality of this field as of the 5.05 release
At line 109 changed one line
;[Home State/Prov|DSP_ID_HOME]: This field holds the state or province where the employee resides. State_Province will default from the employee’s Personal form but you may manually enter or use the LOV (F9).
;[Home State/Prov|DSP_ID_HOME]: This field holds the State or Province where the employee resides. State_Province will default from the employee’s Personal form, but users can enter this manually or select from the LOV (F9).
At line 111 changed one line
;[Home Jurisdiction|DTX_ID_HOME]:This field holds the Geo code of the employee’s residence tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] will default from the employee’s Personal form but you may manually enter or use the LOV (F9).
;[Home Jurisdiction|DTX_ID_HOME]:This field holds the Geo code of the employee’s residence tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] will default from the employee’s Personal form, but users can enter this manually or select from the LOV (F9). \\See NOTE above for functionality of this field as of the 5.05 release
At line 113 changed one line
;[School District|SCHOOL_DISTRICT_CODE]: For U.S. installations only: This field shows the school district to which the employee pays taxes. School_District will default from the employee’s personal form but you may manually enter or use the LOV (F9).
;[School District|SCHOOL_DISTRICT_CODE]: For U.S. installations only: This field shows the School District the employee pays taxes to. School_District will default from the employee’s personal form, but users can enter this manually or select from the LOV (F9).
At line 115 changed one line
;[Final Pay Method|FINAL_PAY_METHOD]:The final pay method indicates whether or not a pay is considered to be an employee's final pay. The final pay method is set to 'final pay' automatically when this pay header’s employment has a termination date within the pay period and a termination reason defined as final pay on [IDTR]. When 'final pay' is set, certain events or processes may be triggered to happen automatically, such as the paying out of leave policy balances from attendance. Final_Pay_Method will default based on the employee’s termination date falling within the pay period specified or you may use to look up the value.
;[Final Pay Method|FINAL_PAY_METHOD]:Defines whether or not a pay is considered to be an employee's final pay. The final pay method is set to 'final pay' automatically when this pay header’s employment has a termination date within the pay period and a termination reason defined as 'final pay' on [IDTR]. When 'final pay' is set, certain events or processes can be triggered to happen automatically, such as the paying out of leave policy balances from attendance. Final_Pay_Method will default based on the employee’s termination date falling within the pay period defines or users can look up the value.
At line 117 changed one line
;[Tax Weeks|TAX_WEEKS]:This field shows the number of tax weeks associated with this pay for this pay frequency. The Tax Weeks field enables you to override the default number of pay weeks associated with a pay period. Changing the tax weeks changes the calculation of the normal period taxation that will be applied to that employee. For example, this is used when an employee who is on a biweekly payroll cycle is only receiving pay for working one of the two weeks in the biweekly pay period. Tax_Weeks will default from the pay weeks indicated on the pay calendar of the pay period specified, but may be overridden.
;[Tax Weeks|TAX_WEEKS]:This field shows the number of tax weeks associated with this pay, for this pay frequency. The Tax Weeks field enables users to override the default number of pay weeks associated with a pay period. Changing the tax weeks value changes the calculation of the normal period taxation that will be applied to the employee. Example: This is used when an employee who is on a biweekly payroll cycle is only receiving pay for working one of the two weeks in the biweekly pay period. Tax_Weeks will default from the pay weeks defined on the pay calendar of the defined pay period, but can be overridden.
At line 119 changed one line
;[Reversal #|PAY_NUMBER]:If the category indicated is a [reversal|PAY REVERSAL], then the pay that is to be reversed must be indicated in this field. The original pay # to be reversed must be disbursed (through [UPDISB]) before it can be reversed. Pay_Number is a mandatory field if the category is reversal.
;[Reversal #|PAY_NUMBER]:If the category defined is a [reversal|PAY REVERSAL], the pay that is to be reversed must be defined in this field. The original pay # to be reversed must be disbursed (through [UPDISB]) before it can be reversed. Pay_Number is a mandatory field if the category is reversal.
At line 123 changed one line
Pay Lines are the individual pay transactions. They are created in a number of different ways. They may be entered manually by you through data entry forms, they may be generated by the transaction generator, or loaded into the system through the transaction loader. Pay lines loaded into system may originate from the Time Scheduling application, or come from an external source such as another system. (e.g. a time clock or PC application such as Excel®).
Pay Lines are the individual pay transactions and are created in a number of different ways. They can be entered manually by a user through data entry forms, can be generated by the transaction generator, or loaded into the system through the transaction loader. Pay lines loaded into system can originate from the Time Scheduling application, or can come from an external source, such as another system (a time clock or PC application such as Excel®).
At line 125 changed one line
The information entered for the pay lines is used to generate the Pay Line Details. The pay calculation process ([UPCALC]) uses the data from the Pay Line Details for amounts and reference back to Pay Lines.
The information entered for the pay lines is used to generate the Pay Line Details. The pay calculation process ([UPCALC]) uses the data from the Pay Line Details for amounts and to reference back to Pay Lines.
At line 127 changed one line
;[Assign|ASSIGNMENT_CODE]:This field identifies the assignment by the assignment code defined on the employee’s assignment screen ([IEAS]).
;[Assign|ASSIGNMENT_CODE]:This field defines the assignment, from the assignment code defined on the employee’s assignment form ([IEAS]).
At line 129 changed one line
;[Starting|START_DATE]:This field shows the start date of the pay line. Start_Date will default as the pay period start date but may be overridden.
;[Starting|START_DATE]:This field defines the start date of the pay line. Start_Date will default as the pay period start date, but can be overridden.
At line 131 changed one line
;[PC|PC_CODE]:A pay component code is a unique number code from 1 to 9,999 assigned to uniquely identify the pay component. Only pay component with the toggle ‘Enter Pay Lines’ turned on will be accessible. Data may only be entered in the fields that have had their toggle turned ON in the Pay Component form’s PC Rules tab.
;[PC|PC_CODE]:A pay component code is a unique number code from 1 to 9,999 assigned to uniquely identify the pay component. Only pay components with the toggle ‘Enter Pay Lines’ set to ON will be accessible. Data can only be entered in the fields that have the toggle set to ON, in the Pay Component form, PC Rules tab.
At line 133 changed one line
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the pay component which will be printed on check and deposit statements, lists and pay registers. PC_Abbreviation will default from the pay component chosen.
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the pay component that will be printed on check and deposit statements, lists and pay registers. PC_Abbreviation will default from the defined pay component.
At line 135 changed one line
;[Value|TIME_ENTERED]:This field shows the amount or time entered for the pay component indicated.
;[Value|TIME_ENTERED]:This field shows the amount or time entered for the defined pay component.
At line 137 changed one line
;[Per|TIME_BASIS]:The basis is the unit of measure that the associated value is being stored or displayed in. Time_Basis will default from the pay component set up but may be overridden.
;[Per|TIME_BASIS]: Defines the unit of measure that the associated value is being stored or displayed in. Time_Basis will default from the pay component set up, but can be overridden.
At line 139 changed one line
;[Position|POSITION_CODE]:This field displays the position code from the pay line’s assignment. Position_Code will default from the play line’s assignment but may be overridden.
;[Position|POSITION_CODE]:This field displays the position code from the pay line’s assignment. Position_Code will default from the play line’s assignment, but can be overridden.
At line 141 changed one line
;[Job|JOB_CODE]:This field shows the job code from the play line’s assignment. Job_Code will default from the employee’s assignment but may be overridden.
;[Job|JOB_CODE]:This field shows the job code from the play line’s assignment. Job_Code will default from the employee’s assignment, but can be overridden.
At line 143 changed one line
;[Rate|STD_WAGE_RATE]:This is the standard wage rate from the assignment. STD_Wage_Rate will default from the pay line’s assignment and may be overridden.
;[Rate|STD_WAGE_RATE]:This is the standard wage rate from the assignment. STD_Wage_Rate will default from the pay line’s assignment, but can be overridden.
At line 145 changed one line
;[Per|STD_WAGE_RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in.
;[Per|STD_WAGE_RATE_BASIS]:Defines the unit of measure that the associated rate is being stored or displayed in.
At line 147 changed one line
;[Audit Text|AUDIT_TEXT]:This field will display audit text generated for this line. Click on the right hand side of the text block to open the editor window. Audit_Text will be updated by the system.
;[Audit Text|AUDIT_TEXT]:This field displays the audit text generated for this line. Click on the right hand side of the text block to open the editor window. Audit_Text is updated by the system.
At line 149 changed one line
;[Distribution|DISTRIBUTION_MASK]:This field holds the overridden distribution mask for this pay line that is applicable to all its pay line details for DR and CR journal entry postings. You may use the Distribution Editor button to enter the distribution.
;[Distribution|DISTRIBUTION_MASK]:This field holds the overridden distribution mask for this pay line that is applicable to all the pay line details for DR and CR journal entry postings. Users can use the Distribution Editor button to enter the distribution.
At line 151 changed 2 lines
;[Reference|REFERENCE_INFO]:This field displays a user-defined reference or note determined by the pay component set up in the reference field in [IPPC] (either ‘Enter Description’ or ‘Enter Vendor Code’). This reference information may be either anecdotal or more structured (e.g. Union Code or Court Number).
;:You can enter the text __''HL SUPPORT''__ into this field to get debug information on premium logic. In this case, there will be a new VMEX entry created with tracing information regarding the processing of premiums.
;[Reference|REFERENCE_INFO]:This field displays a user-defined reference or note determined by the pay component set up in the reference field on [IPPC] (either ‘Enter Description’ or ‘Enter Vendor Code’). This reference information can be either anecdotal or more structured, such as a Union Code or Court Number.
;:Users can enter the text __''HL SUPPORT''__ into this field to get debugging information on the premium logic. In this case, there will be a new VMEX entry created with tracing information regarding the processing of premiums.
At line 154 changed one line
;[Department|DEPARTMENT_CODE]:This is the department defined from the pay line assignment. Department_Code will default from the assignment type indicated but you may manually enter or retrieve from the LOV(F9).
;[Department|DEPARTMENT_CODE]:This is the defined department from the pay line assignment. Department_Code will default from the defined assignment type, but users can enter this manually or select from the LOV(F9).
At line 156 changed one line
;[WCB Class|WCB_CLASS]:This field shows the Workers’ Compensation class from the assignment indicated for the pay line. WCB_Class will default from the assignment type indicated and may be overridden.
;[WCB Class|WCB_CLASS]:This field shows the Workers’ Compensation class from the defined assignment for the pay line. WCB_Class will default from the defined assignment type and can be overridden.
At line 158 changed one line
;[Work Order|WORK_ORDER]:Work Order is used to define work orders attached to a specific pay line. The Work Order Validation is defined on the ‘Define G/L Company’ ([IDGC]) form. The work order on each pay line can be unedited (no validation) or validated from an external system that has been pre-programmed.
;[Work Order|WORK_ORDER]: This field defines work orders attached to a specific pay line. The Work Order Validation is defined on the ‘Define G/L Company’ ([IDGC]) form. The work order on each pay line can be unedited (no validation) or validated from an external system that has been pre-programmed.
At line 160 changed one line
;[Cost Center|COST_CENTER_CODE]:Cost Center is used to define a short cut for cost center information attached to a specific pay line.
;[Cost Center|COST_CENTER_CODE]: Defines a short cut for cost center information attached to a specific pay line.
At line 162 changed one line
;[User Calc|USER_CALC_CODE]:This field holds the UserCalc that may be attached to the pay component chosen or manually entered.
;[User Calc|USER_CALC_CODE]:This field holds the UserCalc that can be attached to the defined pay component, or it can be manually entered.
At line 164 changed one line
;[Benefit Plan|PLAN_CODE]:If this pay line is for a benefit, then the benefit plan is indicated in this field.
;[Benefit Plan|PLAN_CODE]:If this pay line is for a benefit, the benefit plan is defined in this field.
At line 166 changed one line
;[Pay Point|PAY_POINT_TYPE]:This field indicates when this pay component needs to be picked up for processing during the pay calculation. Pay_Point_Type will default from the pay component chosen for this pay line.
;[Pay Point|PAY_POINT_TYPE]:This field defines when this pay component needs to be picked up for processing during the pay calculation. Pay_Point_Type will default from the defined pay component for this pay line.
At line 168 changed one line
;[Sequence|PAY_POINT_SEQUENCE]: This field shows the unique sequence number assigned to each item processed in a pay point and determines the order of processing within a ‘Pay Point Type’. Pay_Point_Sequence will default from the pay component chosen for this pay line.
;[Sequence|PAY_POINT_SEQUENCE]: This field shows the unique sequence number assigned to each item processed in a pay point and determines the order of processing within a ‘Pay Point Type’. Pay_Point_Sequence will default from the defined pay component for this pay line.
At line 170 changed one line
;[Task|PAY_POINT_TASK]:The pay point task identifies the kind of process within the pay point.
;[Task|PAY_POINT_TASK]:The pay point task defines the kind of process within the pay point.
At line 172 changed one line
;[Status|PAY_LINE_STATUS]:This field indicates if the pay lines is ‘Active’ or ‘To be deleted’. You have the option of deleting the line or marking it for deletion. When you delete a pay line through the ‘delete and commit record’ button in the horizontal toolbar, it is temporarily removed from the screen and will be physically removed by [UPAUDT]. If you choose to mark a pay line ‘to be deleted’ in the status field, it will be removed from immediate view but is still in the database; the line will then be physically removed from the database by the audit process ([UPAUDT]).
;[Status|PAY_LINE_STATUS]:This field defines if the pay line is ‘Active’ or ‘To be deleted’. Users have the option of deleting the line or marking it for deletion. When a user deletes a pay line through the ‘delete and commit record’ button, it is immediately removed from view and will be physically removed by [UPAUDT]. If a user chooses to mark a pay line ‘to be deleted’, it will be removed from immediate view and will be physically removed from the database by the audit process ([UPAUDT]).
At line 174 changed one line
;[Leave Type|LEAVE_TYPE_CODE]:If this is an attendance line then the leave type for that line is indicated in this field.
;[Leave Type|LEAVE_TYPE_CODE]:If this is an attendance pay line, the leave type for the line is defined in this field.
At line 176 changed one line
;[End Date|END_DATE]:This field shows the end date of the pay line. End_Date will initially default to the pay period end date but will change to the start date once the pay component is entered. It can be overridden.
;[End Date|END_DATE]:Defines the end date of the pay line. End_Date will initially default to the pay period end date, but will change to the start date once the pay component is entered. This field can be overridden.
At line 184 changed 3 lines
;[Journalized|JOURNALIZED]:If this toggle is ON, the pay line has been processed through the journalizing process ([UPLG], [UPGL]). If the toggle is OFF, the pay line has not yet been journalized, or is not an item that requires journalizing.
;:Items may be journalized for costing and/or general ledger purposes, and may be statistical items such as hours, or financial items such as earnings, benefits and deductions.
;:The ‘Journalized’ toggle on the pay lines is only turned on when the UPLG is run.
;[Journalized|JOURNALIZED]:If this toggle is ON, the pay line has been processed through the journalizing process ([UPLG] or [UPGL]). If this toggle is OFF, the pay line has not yet been journalized, or is not an item that requires journalizing.
;:Items can be journalized for costing and/or general ledger purposes, and can be statistical items such as hours, or financial items such as earnings, benefits and deductions.
;:The ‘Journalized’ toggle on the pay lines is only turned on when UPLG is run.
At line 188 changed 4 lines
;[Work in Progress|WORK_IN_PROCESS]:If the Work in Progress toggle is ON, this pay line is considered a WIP transaction, which will be journalized to the Work in Progress account of the general ledger, instead of the GL accounts defined on the [IPPC] form. If the toggle is OFF, the pay line is a not journalized as work in progress. Work_In_Progress is system updated but you may manually adjust.
;[Arrears Collected|ARREARS_COLLECTED]: This pay line is created by [UPAUDT] from the Sundry Arrears transaction and this toggle indicates this pay line is from Arrears and will be collected by [UPCALC]. If the Arrears Collected toggle is OFF, then this pay line is not an arrears. Arrears_Collected is system updated but you may manually adjust.
;[Override Rate|RATE_OVERRIDDEN]:If the Override Rate toggle is ON, this pay line has had the defaulting rate altered. If the toggle is OFF, the pay line will display the original defaulting rate. Rate_Overridden is system updated but you may manually adjust.
;[Highest Rate Info|ACT_HIGHEST_RATE_INFO]: 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.
;[Work in Progress|WORK_IN_PROCESS]:If the Work in Progress toggle is ON, the pay line is considered a Work In Progress (WIP) transaction, which will be journalized to the Work in Progress account of the general ledger, instead of the GL accounts defined on the [IPPC] form. If this toggle is OFF, the pay line is not journalized as work in progress. Work_In_Progress is system updated, but users can manually adjust the value.
;[Arrears Collected|ARREARS_COLLECTED]: The pay line was created by [UPAUDT] from the Sundry Arrears transaction and this toggle indicates this pay line is from Arrears and will be picked up by [UPCALC]. If the Arrears Collected toggle is OFF, then the pay line is not an arrear. Arrears_Collected is system updated, but users can manually adjust the value.
;[Override Rate|RATE_OVERRIDDEN]:If the Override Rate toggle is ON, the pay line has had the defaulting rate altered. If the toggle is OFF, the pay line will display the original defaulting rate. Rate_Overridden is system updated but users can manually adjust the value.
;[Highest Rate Info|ACT_HIGHEST_RATE_INFO]: This field applies the higher of the wage rates derived from either the defined 'Rate Source', 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 rate, the calculation rule is applied and the individual amounts are generated.
At line 197 changed one line
Data may only be entered in the fields that have had their toggle turned ON in the pay component form’s PC Detail Rules tab.
Data can only be entered in the fields that have had the toggle turned ON, on the pay component form, PC Detail Rules tab.
At line 199 changed one line
;[PC|PC_CODE]:The details pay component code(s) that default from the pay line pay component code entered. For example, if a Time pay component is entered on the pay line, then the Time and Earnings pay component may be generated on the pay detail line.
;[PC|PC_CODE]:Defines the details pay component code(s) that default from the pay line pay component code entered. Example: If a Time pay component is entered on the pay line, then the Time and Earnings pay component can be generated on the pay detail line.
At line 201 changed one line
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the pay component used for printing on check and deposit statements, lists and pay registers. PC_Abbreviation will default from the pay component chosen.
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the pay component used for printing on check and deposit statements, lists and pay registers. PC_Abbreviation will default from the defined pay component.
At line 205 changed one line
;[Rate|WAGE_RATE_OVERRIDE]:This field is the wage rate derived from the pay line rate and displayed in the basis of the pay component. Wage_Rate_Override is system calculated based on the Time Basis indicated.
;[Rate|WAGE_RATE_OVERRIDE]:This field is the wage rate derived from the pay line rate and displayed in the basis of the pay component. Wage_Rate_Override is system calculated based on the defined Time Basis.
At line 207 changed one line
;[Per|RATE_BASIS_OVERRIDE]:The rate basis is the unit of measure that the associated rate is being stored or displayed in. Rate_Basis_Override will be derived from the time basis indicated but may be overridden.
;[Per|RATE_BASIS_OVERRIDE]:Defines the unit of measure that the associated rate is being stored or displayed in. Rate_Basis_Override will be derived from the defined time basis, but can be overridden.
At line 209 changed one line
;[Type|PC_DETAIL_TYPE]:'PC Detail Type' 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 detail.
;[Type|PC_DETAIL_TYPE]:'PC Detail Type' 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 detail.
At line 211 changed one line
;[Calc. Method|PC_CALC_METHOD]:This field indicates the method by which an amount is calculated. PC_Calc_Method will default from the pay component but may be overridden.
;[Calc. Method|PC_CALC_METHOD]:This field defines the method that an amount is calculated. PC_Calc_Method will default from the pay component, but can be overridden.
At line 213 changed one line
;[Description|DESCRIPTION]:This field provides detailed information on the Calc Method used. Description default from the Calc Method.
;[Description|DESCRIPTION]:This field provides detailed information on the Calc Method used. Description will default from the Calc Method.
At line 215 changed one line
;[Rate Source|PC_RATE_SOURCE]:This field indicates from where the wage rate is derived. PC_Rate_Source will default from the pay component.
;[Rate Source|PC_RATE_SOURCE]:This field defines from where the wage rate is derived. PC_Rate_Source will default from the pay component.
At line 217 changed one line
;[O/R User Variable|USER_VARIABLE_OVERRIDE]:You may wish to manually enter the user variable amount.For example, the user variable field may indicate a rate or 1.5 but for this particular transaction you may wish to enter 1.55.
;[O/R User Variable|USER_VARIABLE_OVERRIDE]:Users can manually enter the user variable amount. Example: The user variable field can define a rate or 1.5, but users can enter 1.55, if required.
At line 219 changed one line
;[User Variable|USER_VARIABLE_CODE]:This field shows the user variable that may be used according to the pay component details set up. User_Variable_Code will default from the pay component but may be overridden.
;[User Variable|USER_VARIABLE_CODE]:This field defines the user variable that can be used according to the pay component details set up. User_Variable_Code will default from the pay component, but can be overridden.
At line 221 changed one line
;[Element|ELEMENT_CODE]:The element that is to be used according to the pay component details set up is shown in this field. Element_Code will default from the pay component but may be overridden.
;[Element|ELEMENT_CODE]:Defines the element to be used according to the pay component details set up. Element_Code will default from the pay component, but can be overridden.
At line 223 changed one line
;[Premium|PREMIUM_CODE]:If this pay line detail is a premium, it will contain the premium code. Premium_Code from
;[Premium|PREMIUM_CODE]:If this pay line detail is a Premium, it will contain the premium code. Premium_Code will default from the pay component, but can be overridden.
At line 225 changed one line
;[Audit Info|AUDIT_TEXT]:This fields will display the audit text generated for this line. This text is derived from the Audit Text field on the Pay Lines tab. Audit_Text will be updated by the system.
;[Audit Info|AUDIT_TEXT]:This field displays the audit text generated for this line. This text is derived from the 'Audit Text' field on the Pay Lines tab. Audit_Text is system updated.
At line 227 changed one line
;[Pay Line Detail Status|PAY_LINE_DETAIL_STATUS]: This field indicates if the pay line is ’Active’ or ‘To be deleted’. You have the option of deleting the line or marking it for deletion. When you delete a pay line through the ‘delete and commit record’ button in the horizontal toolbar, it is temporarily removed from the screen and will be physically removed by [UPAUDT]. If you chooses to mark a pay line detail ‘to be deleted’ in the status field, it will be removed from your immediate view but is still in the database; the line will then be physically removed from the database by the audit process ([UPAUDT]).
;[Pay Line Detail Status|PAY_LINE_DETAIL_STATUS]: This field defines if the pay line is ‘Active’ or ‘To be deleted’. Users have the option of deleting the line or marking it for deletion. When a user deletes a pay line through the ‘delete and commit record’ button, it is immediately removed from view and will be physically removed by [UPAUDT]. If a user chooses to mark a pay line ‘to be deleted’, it will be removed from immediate view and will be physically removed from the database by the audit process ([UPAUDT]).
At line 229 changed one line
;[Action|PC_ACTION]:The PC Action determines whether a transaction item entered under this pay component will be accumulated to the total value of the pay component, replace a prior transaction item, trigger a user calculation, or suppress a User calculation. PC_Action will default from the pay component and may be overridden.
;[Action|PC_ACTION]:The PC Action defines whether a transaction item entered under this pay component will be accumulated to the total value of the pay component, replace a prior transaction item, trigger a user calculation, or suppress a user calculation. PC_Action will default from the pay component, but can be overridden.
At line 231 changed one line
;[Amount Processed|AMOUNT_PROCESSED]:This field shows the amount actually processed by the pay calculation process, after performing 'gross to net' assessment. The original transaction amount may be modified by the system based on the pay component rules. For example, if there are insufficient earnings to take a deduction amount, the rule may indicate to take as much as possible with an arrears transaction being created to recover the balance at a later date. The amount processed would be the modified 'as much as possible' value. Amount_Processed is system maintained.
;[Amount Processed|AMOUNT_PROCESSED]:This field shows the amount actually processed by the pay calculation process, after performing the 'gross to net' assessment. The original transaction amount may be modified by the system based on the pay component rules. Example: If there are insufficient earnings to take a deduction amount, the rule may indicate to take as much as possible with an arrears transaction being created to recover the balance at a later date. The amount processed would be the modified 'as much as possible' value. Amount_Processed is system maintained.
At line 233 changed one line
;[Distribution CR Mask|DISTRIBUTION_CR_MASK]:Distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the credit GL code of the pay component.
;[Distribution CR Mask|DISTRIBUTION_CR_MASK]:Contains the distribution derived from the assignment, position or job, overlaid by the distribution mask based on the credit GL code of the pay component.
At line 235 changed one line
;[Distribution DR Mask|DISTRIBUTION_DR_MASK]:Distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the debit GL code of the pay component.
;[Distribution DR Mask|DISTRIBUTION_DR_MASK]:Contains the distribution derived from the assignment, position or job, overlaid by the distribution mask based on the debit GL code of the pay component.
At line 239 changed one line
Premiums are usually system generated as defined for the pay component on the [IPPC] form. However users may enter additional premiums for a pay line on the Premium tab of IPPH.
Premiums are usually system generated as defined for the pay component on the [IPPC] form. However users can enter additional premiums for a pay line on the Premium tab of IPPH.
At line 241 changed one line
This tab is only used when a premium is to be manually attached to a pay line. These premiums are picked up during [UPAUDT] and turned into Pay Line Details for [UPCALC].
This tab is used only when a premium will be manually attached to a pay line. These premiums are picked up during [UPAUDT] and turned into Pay Line Details for [UPCALC].
At line 245 changed one line
;[Premium|PREMIUM_CODE]:This field provides a user defined premium code that uniquely identifies this premium within the organization.
;[Premium|PREMIUM_CODE]:This field provides a user defined premium code that uniquely identifies the premium within the organization.
At line 249 changed one line
;[Basis|DRV_SPMD_RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual.
;[Basis|DRV_SPMD_RATE_BASIS]:Defines the unit of measure that the associated rate is being stored or displayed in, such as hourly, weekly, biweekly, semi-monthly, monthly or annually.
At line 251 changed one line
;[O/R Rate|PREMIUM_RATE]:This field holds the Premium Override rate you entered, which will be used in the premium calculation.
;[O/R Rate|PREMIUM_RATE]:Defines the Premium Override rate entered, which will be used in the premium calculation.
At line 253 changed one line
;[O/R Basis|RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual.
;[O/R Basis|RATE_BASIS]:Defines the unit of measure that the associated rate is being stored or displayed in, such as hourly, weekly, biweekly, semi-monthly, monthly or annually.
At line 256 changed 2 lines
!!Pay Amounts tab
Pay Amounts store the pay component totals resulting from the pay calculation process. The pay amounts tab will show the results for all pay component that have the ‘Store Results’ toggle turned on the pay component form and all legislated amounts from taxation. Amounts are displayed in pay component order.
!!Pay Amounts Tab
Pay Amounts store the pay component totals resulting from the pay calculation process. The pay amounts tab will show the results for all pay component that have the ‘Store Results’ toggle turned ON on the pay component form and all legislated amounts from taxation. Amounts are displayed in the pay component order.
At line 259 changed one line
This tab will only be displayed after the pay is calculated through [UPCALC] or the Trial Calc <Trial Pay> button on the Pay Header.
This tab will be displayed only after the pay is calculated through [UPCALC] or through the Trial Calc <Trial Pay> button on the Pay Header.
At line 264 changed 7 lines
!!Journalized tab
This tab will only be displayed if any pay line has been journalized by the Labor GL ([UPLG]) process prior to Payroll calculation or if this Pay has been paid and closed by [UPCLOZ] and has been run by the Payroll GL process ([UPGL]). The pay can be distributed
through [UPGL] or [UPLG] in trial or update mode. This is a view only screen.
;[Fiscal|CALENDAR_PERIOD]:This field indicates the fiscal period for which the transaction will be journalized.
;[Distribution|DISTRIBUTION_CODE]:This field holds the distribution code for the pay component displayed.
;[GL Date|GL_EFFECTIVE_DATE]:This field displays the date that the journal entry is effective.
;[GL Account|GL_ACCOUNT_CODE]:This field displays the general ledger account for the journal entry.
!!Journalized Tab
This tab will be displayed only if any pay line has been journalized by the Labor GL ([UPLG]) process prior to Payroll calculation, or if this Pay has been paid and closed by [UPCLOZ] and has been run by the Payroll GL process ([UPGL]). The pay can be distributed through [UPGL] or [UPLG] in trial or update mode. This is a view only tab.
;[Fiscal|CALENDAR_PERIOD]:Defines the fiscal period for the transaction will be journalized for.
;[Distribution|DISTRIBUTION_CODE]:This field holds the distribution code for the displayed pay component.
;[GL Date|GL_EFFECTIVE_DATE]:Defines the date the journal entry is effective.
;[GL Account|GL_ACCOUNT_CODE]:Defines the general ledger account for the journal entry.
At line 274 changed 11 lines
;[Journalized Source|JOURNAL_SOURCE]:This field will display the process used to create the journalized record. e.g. [UPGL], Trial Pay Line
;[Fiscal End Date|CALENDAR_END_DATE]:This field displays the last date of the fiscal period for the transaction.
;[Created by mex id|MEX_ID]:This field will contain the execution id of the journal source listed. This field will be populated by either [UPLG] or [UPGL] when the journal entries are being generated.
;[Interface mex id|MEX_ID]:This field holds the execution id of the GL interface.
;[Costed by mex id|MEX_ID_COSTED]:If a detail costing file needs to be generated to the general ledger, you must turn on the 'Affects Costing' toggle within the [IDGA] screen. When [UPGLF] is run, you may enter an interface file for the costing. If [UPGLF] is run in update mode, this field will contain the mex id of that [UPGLF] run.
;[Trial Journal|TRIAL_JOURNAL]:If this toggle is checked, the Journal Entry is a trial journal after either the [UPLG] or [UPGL] is run.
;[G/L Post Number|GLPOST_NUMBER]:This is a customized field not used for most clients.
;[G/L Post Seq #|GLPOST_SEQUENCE]:UPGLF automatically assigns a GL Post Sequence on change of distribution code. This GL Post Sequence is updated to [P2K_PR_JOURNAL_ENTRIES].
;[G/L Pointer|GL_POINTER]:This is a customized field not used for most clients.
;[Work Order|WORK_ORDER]:This is a customized field not used for most clients.
;[G/L Fund Code|GL_FUND_CODE]: If using Fund Accounting, you need to define G/L Fund code on [IDGF] screen attached to each distribution mask. When [UPLG] and [UPGL] generates Journal Entries, the G/L Fund code is also attached to each journal entry.
;[Journalized Source|JOURNAL_SOURCE]:This field defines the process used to create the journalized record, such as [UPGL], Trial Pay Line
;[Fiscal End Date|CALENDAR_END_DATE]:This field defines the last date of the fiscal period for the transaction.
;[Created by mex id|MEX_ID]:This field defines the execution id of the journal source listed. This field will be populated by either [UPLG] or [UPGL] when the journal entries are being generated.
;[Interface mex id|MEX_ID]:This field defines the execution id of the GL interface.
;[Costed by mex id|MEX_ID_COSTED]:If a detail costing file needs to be generated to the general ledger, users must turn the 'Affects Costing' toggle to ON, on the [IDGA] form. When [UPGLF] is run, users can enter an interface file for the costing. If [UPGLF] is run in update mode, this field will contain the mex id of that [UPGLF] run.
;[Trial Journal|TRIAL_JOURNAL]:If this toggle is set to ON, defines the Journal Entry as a trial journal after either the [UPLG] or [UPGL] is run.
;[G/L Post Number|GLPOST_NUMBER]:This is a customized field not used by most clients.
;[G/L Post Seq #|GLPOST_SEQUENCE]:UPGLF automatically assigns a GL Post Sequence on the change of a distribution code. This GL Post Sequence is updated to [P2K_PR_JOURNAL_ENTRIES].
;[G/L Pointer|GL_POINTER]:This is a customized field not used by most clients.
;[Work Order|WORK_ORDER]:This is a customized field not used by most clients.
;[G/L Fund Code|GL_FUND_CODE]: If using Fund Accounting, users need to define the G/L Fund code on [IDGF] attached to each distribution mask. When [UPLG] and [UPGL] generates Journal Entries, the G/L Fund code is also attached to each journal entry.
At line 287 changed one line
!!Pay Audit tab
!!Pay Audit Tab
At line 289 changed 2 lines
;[PC|PC_CODE]:This field shows the pay component for this pay amount.
;[Abrv|PC_ABBREVIATION]:This field shows the abbreviation for the pay component.
;[PC|PC_CODE]:This field defines the pay component for this pay amount.
;[Abrv|PC_ABBREVIATION]:This field defines the abbreviation for the pay component.
At line 292 changed 2 lines
;[Origin|DRV_PAY_AUDIT_SOURCE]:This field displays the source of the pay component and value. i.e. Sundry, Benefit Plan, Taxation Legislation
;[Pay Point Type|PAY_POINT_TYPE]:This field shows the pay point type at which this pay component was evaluated.
;[Origin|DRV_PAY_AUDIT_SOURCE]:This field defines the source of the pay component and value, such as Sundry, Benefit Plan, Taxation Legislation
;[Pay Point Type|PAY_POINT_TYPE]:This field shows the pay point type when this pay component was evaluated.
At line 296 changed one line
!!Pay Jurisdiction tab
!!Pay Jurisdiction Tab
At line 298 changed one line
This tab is used to display tax results for those who run U.S. payroll with Symmetry.
This tab is used to display tax results for organizations who run U.S. payroll with Symmetry.
At line 300 changed one line
If the Pay Stage is prior to ‘Calculated / Paid’, the Work Jurisdiction and Home Jurisdiction Area can be used to enter the Home Tax Jurisdiction and Work Tax Jurisdiction, note that these can also be entered on the PAY HEADER Tab
If the Pay Stage is prior to ‘Calculated/Paid’, the Work Jurisdiction and Home Jurisdiction Area can be used to define the Home Tax Jurisdiction and Work Tax Jurisdiction. Note: these can also be entered on the Pay Header Tab.
At line 302 changed one line
The user can click the Jurisdiction Name to look up or to pop into the ‘Tax Jurisdiction Editor Dialog’ Box to enter State, County, City, Municipality and School
Users can click the Jurisdiction Name to look up or to go to the ‘Tax Jurisdiction Editor Dialog’ box to enter State, County, City, Municipality and School information
At line 304 changed one line
The Tax Jurisdiction is returned by look up or the ‘Tax Jurisdiction Editor Dialog’ Box and becomes the ‘Pay Jurisdiction’ of this pay.
The Tax Jurisdiction is returned by the look up or from the ‘Tax Jurisdiction Editor Dialog’ box and becomes the ‘Pay Jurisdiction’ of this pay.
At line 306 changed one line
The Jurisdiction information is passed to the Symmetry Tax Engine so it knows what type of taxes must be calculated for the employee's pay.
The Jurisdiction information is passed to the Symmetry Tax Engine to indicate what type of taxes must be calculated for the employee's pay.
At line 311 changed 7 lines
;[Work State|DSP_ID_WORK]:This field displays the employee's work state. This field is defaulted in from the employee's assignment information in [IEAS]. The employee's work state is default in from the employee's Work Location.
;[Jurisdiction Name|DTX_ID_WORK]:This field displays the name of the tax jurisdiction where the employee works. This field is defaulted in from the employee's assignment in [IEAS]. For example: Newark.
;[Work GNIS Code|GEO_CODE]: This field displays the actual GNIS code of the tax jurisdiction where the employee works. The GNIS code is defined in [IDTX]. The GNIS is made up of State, County and City. For example: 34-013-878762
;[Work County|DCN_ID]: This field displays the name and code of the County where the employee works. This information partially makes up GNIS Code / tax jurisdiction. For example: 34-013, Essex
;[Work City|DCI_ID]: This field displays the name and code of the City where the employee works. This information partially makes up the GNIS Code / tax jurisdiction. For example: 878762, Newark
;[Work Municipality|DMN_ID]: This field displays the municipality code associated to the work tax jurisdiction. This field is only populated for Pennsylvania tax jurisdictions. The municipality is tied to the tax jurisdiction in [IDTX], this information will default in when the Tax Jurisdiction is populated above.
;[Work School|DSD_ID]: This field displays the school district code associated to the employee's work tax jurisdiction. This field is only populated for Ohio and Pennsylvania tax jurisdictions. The school code is tied to the tax jurisdiction in [IDTX], this information will default in when the Tax Jurisdiction is populated above.
;[Work State|DSP_ID_WORK]:This field defines the employee's work state. This field is defaulted in from the employee's assignment information in [IEAS]. The employee's work state is defaulted in from the employee's Work Location.
;[Jurisdiction Name|DTX_ID_WORK]:This field defines the name of the tax jurisdiction where the employee works. This field is defaulted in from the employee's assignment in [IEAS]. Example: Newark.
;[Work GNIS Code|GEO_CODE]: This field defines the actual GNIS code of the tax jurisdiction where the employee works. The GNIS code is defined on [IDTX]. The GNIS code is made up of State, County and City codes. Example: 34-013-878762
;[Work County|DCN_ID]: This field defines the name and code of the County where the employee works. This information partially makes up GNIS Code/Tax jurisdiction. Example: 34-013, Essex
;[Work City|DCI_ID]: This field defines the name and code of the City where the employee works. This information partially makes up the GNIS Code/Tax jurisdiction. Example: 878762, Newark
;[Work Municipality|DMN_ID]: This field is only populated for Pennsylvania tax jurisdictions and defines the municipality code associated to the work tax jurisdiction. The municipality code is tied to the tax jurisdiction on [IDTX]. This information will default in when the Tax Jurisdiction is defined (above).
;[Work School|DSD_ID]: This field is only populated for Ohio and Pennsylvania tax jurisdictions and will be populated with the school district code associated to the employee's work tax jurisdiction. The school code is tied to the tax jurisdiction on [IDTX]. This information will default in when the Tax Jurisdiction is defined (above).
At line 320 changed 7 lines
;[Home State|DSP_ID_HOME]: This field displays the employee's resident state. This field is defaulted in from the employee's personal information in [IEPI].
;[Jurisdiction Name|DTX_ID_HOME]: This field displays the name of the employee's resident tax jurisdiction. This field is defaulted in from the employee's personal information in [IEPI]. For example: Newark.
;[Home GNIS Code|GEO_CODE]: This field displays the actual GNIS code of the employee's resident tax jurisdiction. The GNIS code is defined in [IDTX]. The GNIS is made up of State, County and City. For example: 34-013-878762
;[Home County|DCN_ID]: This field displays the name and code of the employee's resident County. This information partially makes up the employee's tax jurisdiction listed above in the Home GNIS Code field. For example: 34-013, Essex
;[Home City|DCI_ID]: This field displays the name and code of the employee's resident City. This information partially makes up the employee's tax jurisdiction. For example: 878762, Newark
;[Home Municipality|DMN_ID]: This field displays the municipality code associated to the employee's resident tax jurisdiction. This field is only populated for Pennsylvania tax jurisdictions. The municipality is tied to the tax jurisdiction in [IDTX], this information will default in when the Tax Jurisdiction is populated above.
;[Home School|DSD_ID]: This field displays the school district code associated to the employee's resident tax jurisdiction. This field is only populated for Ohio and Pennsylvania tax jurisdictions. The school code is tied to the tax jurisdiction in [IDTX], this information will default in when the Tax Jurisdiction is populated above.
;[Home State|DSP_ID_HOME]: This field defines the employee's resident state. This field is defaulted in from the employee's personal information on [IEPI].
;[Jurisdiction Name|DTX_ID_HOME]: This field defines the name of the employee's resident tax jurisdiction. This field is defaulted in from the employee's personal information on [IEPI]. Example: Newark.
;[Home GNIS Code|GEO_CODE]: This field defines the actual GNIS code of the employee's resident tax jurisdiction. The GNIS code is defined on [IDTX]. The GNIS code is made up of State, County and City codes. Example: 34-013-878762
;[Home County|DCN_ID]: This field defines the name and code of the employee's resident County. This information partially makes up the employee's tax jurisdiction listed above in the Home GNIS Code field. Example: 34-013, Essex
;[Home City|DCI_ID]: This field defines the name and code of the employee's resident City. This information partially makes up the employee's tax jurisdiction. Example: 878762, Newark
;[Home Municipality|DMN_ID]: This field is only populated for Pennsylvania tax jurisdictions and defines the municipality code associated to the employee's resident tax jurisdiction. The municipality code is tied to the tax jurisdiction on [IDTX]. This information will default in when the Tax Jurisdiction is defined (above).
;[Home School|DSD_ID]: This field is only populated for Ohio and Pennsylvania tax jurisdictions and will display the school district code associated to the employee's resident tax jurisdiction. The school code is tied to the tax jurisdiction in [IDTX], this information will default in when the Tax Jurisdiction is defined (above).
At line 329 changed 4 lines
;[Jurisdiction|DTX_ID]: This field displays the Jurisdiction of the tax calculations below.
;[Jurisdiction Name|JURISDICTION_NAME]: The full Jurisdiction name is displayed in this field.
;[School|SCHOOL_DISTRICT_NAME]: If the Jurisdiction contains a school code, the school code will display here.
;[Municipality|MUNICIPALITY_NAME]: If the Jurisdiction contains a municipality code, the municipality code will display here.
;[Jurisdiction|DTX_ID]: This field displays the GNIS Code and Jurisdiction Name of the tax calculations below. This information is based on the Work and Resident locations defined above. Example: 34-013-878762, Newark
;[Jurisdiction Name|JURISDICTION_NAME]: The full Jurisdiction name is displayed in this field. The name of the jurisdiction is defined on [IDTX]. Example: Newark.
;[School|SCHOOL_DISTRICT_NAME]: This field is only populated for Ohio and Pennsylvania tax jurisdictions. If the Jurisdiction contains a school code, the school code is displayed here.
;[Municipality|MUNICIPALITY_NAME]: This field is only populated for Pennsylvania tax jurisdictions. If the Jurisdiction contains a municipality code, the municipality code is displayed here.
At line 335 changed 7 lines
;[Tax Identifier|TAX_IDENTIFIER]: The identifier of the tax calculated by the STE (Symmetry Tax Engine) will display in this field, i.e 01-000-0000_SUTA_ER. The Tax Identifiers that are calculated are determined by the employee's Home and Work Jurisdictions. A list of Tax Identifiers can be found by state in the [IPUTR] form. The Tax Identifier is made up of the state or local GNIS code as well as the tax type.
;[Description|DESCRIPTION]: A brief description of the tax identifier is displayed. This description comes from the Tax Engine and also indicates the State Code. An example: State Withholding - CA
;[Tax PC Code|PPC_ID_TAX]: The Pay Component Code of where the tax is calculated and stored in will display. UPCALC uses the [pc usage|PC_USAGE_CODE] to determine which PC Code to store the tax. For example, UPCALC knows that [PC Usage 6621|U.S. STATE LEVEL PAY COMPONENT USAGES] is used for State Res Income tax and therefore will store the State Resident Income Tax in the Pay Component tied to the usage 6621.
;[Tax PC Desc|PC_ABBREVIATION]: The description of the pay component will display here. The description provides meaning and usage of the pay component, for example SUI ER. The description is populated based on the Description in [IPPC].
;[Tax Amount|TAX_AMOUNT]: The amount of tax calculated by the Tax Engine will display in this field.
;[Tax Stored|TAX_STORED]: This field will display the amount of tax that is stored in the pay component above. The amount of tax stored may differ than the amount of tax calculated by the Tax Engine, this may be a result of user calcs adjusting the results or reciprocity rules defined to override the state or local tax results.
;[Tax Pay Type|TAX_PAYTYPE]: This field states the type of tax calculated. For example, Regular, Supplemental, Combined Reg + Sup, Derived Amount.Derived Amount is used when the amount of wages is based on a [pay element|PAY_ELEMENT]. Derived Exemption is used when the amount of the pay component is derived from a benefit exemption [pay element|PAY_ELEMENT] such as Pre-State 125 Exemption.
;[Tax Identifier|TAX_IDENTIFIER]: Defines the identifier of the tax calculated by the STE (Symmetry Tax Engine). The Tax Identifiers are pre-defined by Symmetry and define the Location code and Tax Type. These provide a mechanism to allocate a tax rate/tax amount to a specific tax jurisdiction. The first two digits in the Tax Identifier indicates the FIPS code of the State. The second segment indicates the County, if the tax rate is specific to a county. The third segment indicates the City's Feature ID, if the tax rate is specific to a City. Otherwise it will be filled with zeros. The fourth segment indicates the type of tax, such as SIT for State Income Tax or ER_SUTA for Employer State Unemployment Tax. A list of Tax Identifiers can be found by state on the [IPUTR] form. Example: 34-000-0000-SIT-000-Res-Reg
;[Description|DESCRIPTION]: A brief description of the tax identifier is displayed. This description comes from the Symmetry Tax Engine and also indicates the State Code. Example: State Withholding - CA
;[Tax PC Code|PPC_ID_TAX]: Displays the Pay Component Code of where the tax is calculated and stored in. UPCALC uses the [PC Usage|PC_USAGE_CODE] to determine which PC Code to store the tax. Example: UPCALC knows that [PC Usage 6621|U.S. STATE LEVEL PAY COMPONENT USAGES] is used for State Res Income tax and therefore will store the State Resident Income Tax in the Pay Component tied to the 6621 usage.
;[Tax PC Desc|PC_ABBREVIATION]: Displays the description of the pay component. The description defines the meaning and usage of the pay component, such as SUI ER. The description is populated from the Description field on [IPPC].
;[Tax Amount|TAX_AMOUNT]: Displays the amount of tax calculated by the Symmetry Tax Engine.
;[Tax Stored|TAX_STORED]: Displays the amount of tax that is stored in the pay component above. The amount of tax stored may differ from the amount of tax calculated by the Tax Engine. This could be due to user calcs adjusting the results or reciprocity rules defined to override the State or Local tax results.
;[Tax Pay Type|TAX_PAYTYPE]: This field defines the type of tax calculated. Example: Regular, Supplemental, Combined Reg + Sup, Derived Amount. \\ *The Derived Amount is used when the amount of wages is based on a [pay element|PAY_ELEMENT]. \\* The Derived Exemption is used when the amount of the pay component is derived from a benefit exemption [pay element|PAY_ELEMENT] such as Pre-State 125 Exemption.
At line 343 changed 6 lines
;[Wage PC Code|PPC_ID_WAGES]: This field will display the pay component code the wages were stored in. Like the Tax PC Code, UPCALC will use the PC Usage to determine which PC Code to store the wages.
;[Wage PC Description|PC_ABBREVIATION]:This field will display the description of the pay component the wages were stored in. The description is populated based on the Description defined in [IPPC]
;[Subject Wages|SUBJECT_WAGES]:This field will display the wages that are subject to the tax, i.e taxable wages. The subject wages are the pre-tax wages (derived from the pay element tied to the Pre-Tax Pay Component for the particular tax) minus any benefits which are exempt from the particular tax. The STE keeps track of which types of benefits are exempt by state and local jurisdictions and subtracts them from the gross wages yielding the subject wages. If the tax has a wage base limit, i.e. State Unemployment Tax, these subject wages will reflect the enforced wage base limit if the employee is close to reaching the maximum limit.
;[Gross Wages|GROSS_WAGES]:This field will display the pre-tax wages used to calculate the tax. The Pre-Tax wages are determined by the pay element associated to the Pre-Tax Wages Pay Component in [IPPC] for the particular tax type. There are Pre-Tax Wage pay components used for most of the tax identifiers, for example for the 06-000-0000-SIT-000-Res-Reg tax identifier UPCALC will derive the wages from PC Usage 6651 Pre-State Earnings - Reg Tax Table Method (PPE).
;[Gross Subject Wages|GROSS_SUBJECT_WAGES]: This field will display the wages that are subject to the tax, similar to the Subject Wages described above however the maximum wage base limit is not applied to these wages. Therefore, these are the wages subject to the tax regardless of how much year to date wages the employee has.
;[Wages Stored|WAGES_STORED]: This field will display the actual wages stored in the Pay Component by UPCALC.
;[Wage PC Code|PPC_ID_WAGES]: Displays the pay component code the wages were stored in. Like the Tax PC Code, UPCALC will use the PC Usage to determine which PC Code to store the wages in.
;[Wage PC Description|PC_ABBREVIATION]:Displays the description of the PC Code the wages were stored in. The description is populated from the Description field on [IPPC].
;[Subject Wages|SUBJECT_WAGES]:Displays the wages that are subject to the tax, such as taxable wages. The subject wages are the pre-tax wages (derived from the pay element tied to the Pre-Tax Pay Component for the particular tax) minus any benefits which are exempt from the particular tax. The STE keeps track of which types of benefits are exempt by State and Local jurisdictions and subtracts them from the gross wages yielding the subject wages. If the tax has a wage base limit, such as State Unemployment Tax, these subject wages will reflect the enforced wage base limit, if the employee is close to reaching the maximum limit.
;[Gross Wages|GROSS_WAGES]:Displays the pre-tax wages used to calculate the tax. The Pre-Tax wages are determined by the pay element associated to the Pre-Tax Wages Pay Component on [IPPC] for the particular tax type. There are Pre-Tax Wage pay components used for most of the tax identifiers. Example: For the 06-000-0000-SIT-000-Res-Reg tax identifier, UPCALC will derive the wages from PC Usage 6651 Pre-State Earnings - Reg Tax Table Method (PPE).
;[Gross Subject Wages|GROSS_SUBJECT_WAGES]: Displays the wages that are subject to the tax, similar to the Subject Wages described above. However, the maximum wage base limit is not applied to these wages, therefore these are the wages subject to the tax regardless of how much year to date wages an employee has accumulated.
;[Wages Stored|WAGES_STORED]: Displays the actual wages stored in the Pay Component by UPCALC.
At line 359 added one line
It should be noted that when adjustment pay lines or user calcs are used to adjust tax amounts, only the [Tax Stored Amount|TAX_STORED] and the [Wage Stored Amount|WAGES_STORED] fields are updated. The other amounts that are returned from the Symmetry Tax Engine will not be changed, such as Tax Amount, Subject Wages, Gross Wages, Gross Subject Wages. These amounts must remain as the original calculated amounts from Symmetry, for when the employee's Federal and State Tax Method is defined to use the PTD method.
At line 351 changed one line
It should be noted that when adjustment pay lines or user calcs are used to adjust tax amounts only the [Tax Stored Amount|TAX_STORED] and the [Wage Stored Amount|WAGES_STORED] are updated. The other amounts that are returned from the Symmetry Tax Engine will not be changed (i.e. Tax Amount, Subject Wages, Gross Wages, Gross Subject Wages). These amounts are needed to remain the original calculated amounts from Symmetry for when the employee's Federal and State Tax Method is defined to use the PTD method.
----
!Net Pay Split
This tab will show the disbursements for this pay. The details will only be available if the pay is at a stage of ‘Calculated/Paid’ or ‘Closed’.
At line 365 added one line
;[Split Sequence|SPLIT_SEQUENCE]: This field defines the sequence number controlling the order in which this payment rule detail was processed according to the setup on the Payment Method [IPPM] form.
At line 367 added 9 lines
;[Pay Type|PAYMENT_RULE_TYPE]: This field indicates whether the payment was made by check or deposit.
;[Amount $|Amount]: This field displays the dollar amount of the deposit or check.
;[Bank Transit|BANK_TRANSIT_CODE]:Defines the transit number of the bank where the deposit was sent to.
;[Bank Account|BANK_ACCOUNT]:Defines the employee-supplied bank account number the deposit was sent to.
\\
This page (revision-89) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop