Wiki: IPPH

MAINTAIN EMPLOYEE PAYS
Pay Header tab
Checks
Location
Pay Lines tab
Pay Line Details
Premiums
Pay Amounts Tab
Journalized Tab
Pay Audit Tab
Pay Jurisdiction Tab
Work Jurisdiction
Home Jurisdiction
Net Pay Split
Notes

MAINTAIN EMPLOYEE PAYS#

Users can create and maintain employee pays on the Maintain Employee Pays (IPPH) form.

In addition:

Users can override normal deposit information for an employee and pay by check for a single pay.
Position, Job, Rate and/or Distribution codes can be overridden.

Field access and rules for pay component values are defined on the Pay Component Rules (IPPC) form.

Employee Pay data is stored on the P2K_PR_PAY_HEADERS, P2K_PR_PAY_LINES, and P2K_PR_PAY_LINE_DETAILS tables.

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 #: This field shows the unique pay number assigned to each pay header that is created for an employee.

Period: Pay periods are numbered by the year, followed by the period of the year.

Payroll: This field shows the payroll associated to the group defined.

Group: 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’.

Prime Assignment - Group code for this assignment is always from the 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.
Job Only - Group code for this assignment is always from this assignment’s job code to look up the group code for this job.

: Group_Code will be defaulted from IDWR, 'Group Source' tab.

Unit: The unit the defined group belongs to.

Stage: Defines the status of a pay header.

Seq #: 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.

Source: Defines the process that created the pay header.

Pay Header tab#

A Pay Header is created to indicate that an employee must be processed through a pay cycle.

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.

An employee can have multiple pay headers (time sheets) per period.

Each pay header for an employee should have a unique pay period and pay category combination.

Assignment: 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).

Batch #: This field shows the batch this pay is attached to.

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).

Starting: Defines the first day of the pay period. Pay_Period_Start_Date will default from the pay period entered.

Ending: Defines the last day of the pay period. Pay_Period_End_Date will default from the pay period entered.

Category: 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).

Pay Point Set: 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).

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.

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.

1st 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.

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.

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.

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.

: If the Journalized toggle is ON, all of the pay lines and pay amounts for this header have been processed through the journalizing process.

: If the toggle is OFF, all or some of the pay lines have not yet been journalized. Journalized is system updated.

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.

Time Sheet 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.

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'.

Trial Pay: This button allows users to calculate one pay header in non-update mode. This field is very useful for trial runs and for testing.

Cancel Pay: This button allows users to mark a pay header as cancelled, which in turn will be physically removed by the audit process.

Revert Pay: 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.

Checks#

Pay By: 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.

Check Amount: This field shows the amount of the 'hand written check' only (hand check) associated with the pay.

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.

Check #: 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.

Hand Check: If the Hand Check toggle is ON, the pay header is for a pay which includes a hand written check that needs to be recorded in the system. If the toggle is OFF, this is a normal computer generated payment.

Location#

In the US, jurisdictions are defined by the Symmetry GEO code.

In Canada, jurisdictions are provided with Personality software.

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.

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.

Work State/Prov: 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).

Work Jurisdiction: 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

Home State/Prov: 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).

Home Jurisdiction: 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

School District: 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).

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.

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.

Reversal #: If the category defined is a 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.

Pay Lines tab#

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®).

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.

Assign: This field defines the assignment, from the assignment code defined on the employee’s assignment form (IEAS).

Starting: This field defines the start date of the pay line. Start_Date will default as the pay period start date, but can be overridden.

PC: 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.

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.

Value: This field shows the amount or time entered for the defined pay component.

Per: 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.

Position: 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.

Job: 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.

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.

Per: Defines the unit of measure that the associated rate is being stored or displayed in.

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.

Distribution: 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.

Reference: 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.

Department: 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).

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.

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.

Cost Center: Defines a short cut for cost center information attached to a specific pay line.

User Calc: This field holds the UserCalc that can be attached to the defined pay component, or it can be manually entered.

Benefit Plan: If this pay line is for a benefit, the benefit plan is defined in this field.

Pay Point: 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.

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.

Task: The pay point task defines the kind of process within the pay point.

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).

Leave Type: If this is an attendance pay line, the leave type for the line is defined in this field.

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.

Audited: If the Audited toggle is ON, the pay line 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 line has not yet been audited, or it has failed to pass the transaction audit. Audited is system updated.

Detail Generated: If this toggle is ON, pay line detail has been generated for this pay line through ‘Save’, UPTR or UPTL. If this toggle is OFF, no pay line detail has been generated. Detail_Generated is system updated.

Posted Experience: If the Posted Experience toggle is ON, the pay line has been updated to the experience application through the track experience process (USEP). If the toggle is OFF, the experience application has not been updated. Posted_Experience is system updated.

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.

Work in Progress: 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: 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: 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: 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.

Pay Line Details#

Pay Line Details contain the results of applying the PC rules of the pay component to derive all of the required values associated with a pay line.

Data can only be entered in the fields that have had the toggle turned ON, on the pay component form, PC Detail Rules tab.

PC: 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.

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.

Amount: This field shows the amount calculated as a result of applying the PC Calc Method. Amount_Override will be populated by the system based on the pay component rules.

Rate: 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.

Per: 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.

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.

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.

Description: This field provides detailed information on the Calc Method used. Description will default from the Calc Method.

Rate Source: This field defines from where the wage rate is derived. PC_Rate_Source will default from the pay component.

O/R User Variable: 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.

User Variable: 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.

Element: 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.

Premium: 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.

Audit Info: 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.

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).

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.

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.

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.

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.

Premiums#

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.

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.

All other premiums are system generated and displayed in the Pay Line Details tab.

Premium: This field provides a user defined premium code that uniquely identifies the premium within the organization.

Rate: This field shows the premium rate that is used in the premium calculation.

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.

O/R Rate: Defines the Premium Override rate entered, which will be used in the premium calculation.

O/R 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.

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.

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.

This is a view only tab.

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: Defines the fiscal period for the transaction will be journalized for.

Distribution: This field holds the distribution code for the displayed pay component.

GL Date: Defines the date the journal entry is effective.

GL Account: Defines the general ledger account for the journal entry.

PC: This field displays the pay component code attached to the GL account code for the journal entry.

Abbrev: This field displays the description abbreviation of the pay component for the journal entry.

G/L Amount: This field displays the amount of the journal entry.

Journalized Source: This field defines the process used to create the journalized record, such as UPGL, Trial Pay Line

Fiscal End Date: This field defines the last date of the fiscal period for the transaction.

Created by 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: This field defines the execution id of the GL interface.

Costed by mex id: 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: 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: This is a customized field not used by most clients.

G/L Post Seq #: 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: This is a customized field not used by most clients.

Work Order: This is a customized field not used by most clients.

G/L 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.

Pay Audit Tab#

There will be no information in this tab until a Pay Line has been entered. All other information is displayed after the Pay is prepared during UPAUDT. This is a view only tab.

PC: This field defines the pay component for this pay amount.

Abrv: This field defines the abbreviation for the pay component.

Amount: This field displays the entered or calculated value of the pay component.

Origin: This field defines the source of the pay component and value, such as Sundry, Benefit Plan, Taxation Legislation

Pay Point Type: This field shows the pay point type when this pay component was evaluated.

Description: This field describes the calculation method for the pay component.

Pay Jurisdiction Tab#

This tab is used to display tax results for organizations who run U.S. payroll with Symmetry.

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.

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

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.

The Jurisdiction information is passed to the Symmetry Tax Engine to indicate what type of taxes must be calculated for the employee's pay.

Once the Pay is calculated by Trial Calc or UPCALC, the results as calculated by the Symmetry Tax Engine will display in the Tax Audit Information section for the Jurisdictions applicable to the pay header.

Work Jurisdiction#

Work State: 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: 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: 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: 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: 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: 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: 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).

Home Jurisdiction#

Home State: This field defines the employee's resident state. This field is defaulted in from the employee's personal information on IEPI.

Jurisdiction Name: 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: 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: 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: 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: 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: 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).

Jurisdiction: 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: The full Jurisdiction name is displayed in this field. The name of the jurisdiction is defined on IDTX. Example: Newark.

School: 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: This field is only populated for Pennsylvania tax jurisdictions. If the Jurisdiction contains a municipality code, the municipality code is displayed here.

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: 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: Displays the Pay Component Code of where the tax is calculated and stored in. UPCALC uses the PC Usage to determine which PC Code to store the tax. Example: UPCALC knows that PC Usage 6621 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: 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: Displays the amount of tax calculated by the Symmetry Tax Engine.

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: 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.
* The Derived Exemption is used when the amount of the pay component is derived from a benefit exemption pay element such as Pre-State 125 Exemption.

Wage PC Code: 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: Displays the description of the PC Code the wages were stored in. The description is populated from the Description field on IPPC.

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: 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: 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: Displays the actual wages stored in the Pay Component by UPCALC.

It should be noted that when adjustment pay lines or user calcs are used to adjust tax amounts, only the Tax Stored Amount and the Wage Stored Amount 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.

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’.

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.

Pay Type: This field indicates whether the payment was made by check or deposit.

Amount $: This field displays the dollar amount of the deposit or check.

Bank Transit: Defines the transit number of the bank where the deposit was sent to.

Bank Account: Defines the employee-supplied bank account number the deposit was sent to.

Notes #

Click to create a new notes page

Table of Contents