This page (revision-14) was last changed on 26-Nov-2021 10:22 by jmyers

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

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
14 26-Nov-2021 10:22 7 KB jmyers to previous
13 26-Nov-2021 10:22 7 KB jmyers to previous | to last
12 26-Nov-2021 10:22 7 KB jmyers to previous | to last
11 26-Nov-2021 10:22 7 KB jmyers to previous | to last
10 26-Nov-2021 10:22 7 KB jmyers to previous | to last
9 26-Nov-2021 10:22 7 KB jmyers to previous | to last
8 26-Nov-2021 10:22 7 KB jmyers to previous | to last
7 26-Nov-2021 10:22 7 KB jmyers to previous | to last
6 26-Nov-2021 10:22 7 KB jmyers to previous | to last
5 26-Nov-2021 10:22 9 KB jmyers to previous | to last
4 26-Nov-2021 10:22 8 KB jmyers to previous | to last
3 26-Nov-2021 10:22 8 KB jmyers to previous | to last
2 26-Nov-2021 10:22 9 KB jmyers to previous | to last
1 26-Nov-2021 10:22 9 KB jmyers to last

Page References

Incoming links Outgoing links
US Audit Pay Rules
US Audit Pay Rules

Version management

Difference between version and

At line 27 changed 4 lines
1) Vertex to Symmetry Conversion
The initial purpose of the UPRLU function is to populate the state’s Miscellaneous Tax Parameters in IPRLU based on the fields used by Vertex. The UPRLU will read the custom table ‘UPRLU Mapping’ in the IMCT screen to determine which field in IPRLU should be used to populate the Misc Tax Parameter. For example, the UPRLU will take the value stored in Filing Status (UST_FILING_STATUS column) and will populate the Tax Parameter FILINGSTATUS.
The vertex mapping would only occur when the parameter Vertex Conversion = Yes.
#Vertex to Symmetry Conversion\\ \\The initial purpose of the UPRLU function is to populate the state’s Miscellaneous Tax parameters in [IPRLU] based on the fields used by Vertex. The UPRLU will read the custom table ‘UPRLU Mapping’ in the [IMCT] screen to determine which field in IPRLU should be used to populate the Miscellaneous Tax parameter.\\ \\For example, the UPRLU will take the value stored in Filing Status (UST_FILING_STATUS column) and will populate the Tax parameter FILINGSTATUS.\\ \\The vertex mapping would only occur when the parameter Vertex Conversion is set to <Yes>.\\ \\
#Audit IPRLU Data\\ \\TBD - UPRLU has not been programmed for this as of yet.\\ \\The intent on this second purpose is to audit the date in IPRLU on a regular basis to ensure that employee records are kept up to date with new tax parameters etc.
At line 32 removed 8 lines
2) Audit IPRLU Data
TBD - UPRLU has not been programmed for this as of yet.
The intent on this second purpose is to audit the date in IPRLU on a regular basis to ensure that employees records are kept up to date with new tax parameters etc.
At line 31 added one line
In order for [UPCALC] to calculate state tax correctly using the Symmetry Tax Engine (STE), the IPRLU state information (tax parameters) must be set up for each applicable state the employee lives and works in.
At line 42 removed 3 lines
In order for UPCALC to calculate State tax correctly using the Symmetry Tax Engine, the IPRLU state information (tax parameters) must be set up for each applicable state the employee lives and works in.
At line 47 changed one line
Using the As Of Date provided in the report parameters, UPRLU will read IEAS and IEPI effective records where this date falls between the effective start and end dates. Any records whose effective start date is greater than the As Of Date used will also be read, this is so that the UPRLU picks up any future changes in work or res locations.
Using the As Of date provided in the report parameters, UPRLU will read [IEAS] and [IEPI] effective records where this date falls between the effective start and end dates. Any records whose effective start date is greater than the As Of date used will also be read, this is so that the UPRLU picks up any future changes in work or residence locations.
At line 49 changed one line
The Work State is retrieved from IEAS using the field Jurisdiction Code. If there is no Jurisdiction defined then the UPRLU will look at the Works in Location field in IEAS to retrieve the Jurisdiction defined for the location.
The Work State is retrieved from IEAS using the Jurisdiction field. If there is no Jurisdiction defined then the UPRLU will look at the Works in Location field in IEAS to retrieve the Jurisdiction defined for the location.
At line 51 changed one line
Since Symmetry calculates taxes based on Residence state the UPRLU will create Misc Tax Parameters for the HOME state if the home state differs from the state defined in the IEAS Jurisdiction Code field. The Home state is retrieved from the employee’s personal information defined in IEPI.
Since Symmetry calculates taxes based on Residence state the UPRLU will create Misc Tax Parameters for the home state if the home state differs from the state defined in the IEAS Jurisdiction field. The home state is retrieved from the employee’s personal information defined in IEPI.
At line 53 changed one line
Once UPRLU has determined an employee’s work and resident state, it will then read IMCT ‘UPRLU Mapping’ to retrieve the necessary Misc Tax Parameters for the employee’s states. UPRLU will then populate the employee’s IPRLU with the appropriate Tax Parameters. Using the mapping indicated in IMCT, UPRLU will retrieve the data stored in the fields used by Vertex to populate the values for the Tax Parameters.
Once UPRLU has determined an employee’s work and resident state, it will then read [IMCT] ‘UPRLU Mapping’ to retrieve the necessary Misc Tax parameters for the employee’s states. UPRLU will then populate the employee’s IPRLU with the appropriate tax parameters. Using the mapping indicated in IMCT, UPRLU will retrieve the data stored in the fields used by Vertex to populate the values for the tax parameters.
At line 55 changed one line
If the employee does not have an IPRLU record and a Default Pay Rule has defined in the site preference ‘DFLT PAYRULE’, then UPRLU will create a default IPRLU record. The default record will be populated with the Misc Tax Parameters from the employee’s prime assignment ‘Jurisdiction Code’
If the employee does not have an IPRLU record and a Default Pay Rule has been defined in the site preference ‘DFLT PAYRULE’, then UPRLU will create a default IPRLU record. The default record will be populated with the Misc Tax parameters from the employee’s prime assignment ‘Jurisdiction Code’.
At line 59 changed one line
If there are multiple Effective records in IPRLU the UPRLU will insert the appropriate Tax Parameters for these records with the information that was effective within those records. If there are effective records in IPRLU that are greater than the date the UPRLU is run, these will also be updated. For example
If there are multiple effective records in IPRLU, the UPRLU will insert the appropriate tax parameters for these records with the information that was effective within those records. If there are effective records in IPRLU that are greater than the date the UPRLU is run, these will also be updated. For example:
At line 61 changed 4 lines
In IPRLU an employee has 3 effective records:
01 Jan 0000 – 31 Dec 1999 (no information as EE was hired Jan 1 2000)
01 Jan 2000 – 31 Jan 2010, EE claimed Single, 1 exemption
01 Feb 2010 – 31 Dec 3999, EE claimed Married, 2 exemptions
;In IPRLU an employee has three effective records:01 Jan 0000 – 31 Dec 1999 (no information as EE was hired Jan 1 2000)\\01 Jan 2000 – 31 Jan 2010, EE claimed Single, 1 exemption\\01 Feb 2010 – 31 Dec 3999, EE claimed Married, two exemptions\\ \\The UPRLU is run for 1 Jan 2010 – it will update the employee's 01 Jan 2000 record with the appropriate tax parameters with a Single filing status. The 01 Feb 2010 record will also be updated with the appropriate tax parameters with a Married filing status and two exemptions.
At line 66 removed 6 lines
The UPRLU is run for 1 Jan 2010 – it will update the employees 01 Jan 2000 record with the appropriate Tax Parameters with a Single filing status. The 01 Feb 2010 record will also be updated with the appropriate Tax Parameters with a Married filing status and 2 exemptions.
At line 76 changed one line
The mapping has been provided in the Custom Table ‘UPRLU Mapping’ in the IMCT screen.
The mapping has been provided in the custom table ‘UPRLU Mapping’ within the IMCT screen.
At line 57 added one line
[US_Audit_Pay_Rules_02.JPG]
At line 79 changed one line
In IMCT, the Custom Key field holds the state code and the state’s Misc Tax parameter.
At line 61 added one line
Custom Subkey displays the IPRLU field UPRLU will read in order to retrieve the data. This data will be printed in the output file.
At line 82 removed 4 lines
In IMCT, the Custom Key holds the State Code and the state’s Misc Tax Parameter.
The Custom Subkey displays the IPRLU field where the UPRLU will read from to retrieve the data. This data will be used to print in the output file.
At line 88 changed one line
In the above example the UPRLU will read the UST_FILING_STATUS field in IPRLU to populate the tax parameter ‘FILINGSTATUS’ for California. This decode statement tells UPRLU that the lexicon value of 01 is the equivalent of S for this tax parameter, a value of 02 is equal to M and a value of 03 is equal to H.
In the above example, the UPRLU will read the UST_FILING_STATUS field in IPRLU to populate the tax parameter ‘FILINGSTATUS’ for California. This decode statement tells UPRLU that the lexicon value of '01' is the equivalent of 'S' for this tax parameter, a value of '02' is equal to 'M' and a value of '03' is equal to 'H'.
At line 90 changed one line
IMCT has been defined with Tax Parameters from the Symmetry Tax Engine. It does not include Tax Parameters that High Line has created ie: those that have a Provided By = Internal or Legislative.
IMCT has been defined with Tax Parameters from the Symmetry Tax Engine. It does not include Tax Parameters that have been system created. (i.e. Those that have a Provided By = Internal or Legislative).
At line 92 changed one line
If Clients need to edit the mapping or add Internal Tax Parameters we advise you to request Client Services for assistance.
If clients need to edit the mapping or add Internal tax parameters we advise you to request Client Services for assistance.
At line 96 changed 2 lines
Symmetry Tax Parameters Not Included in IMCT
There are a number of Tax Parameters that are provided by Symmetry which were not added to IMCT. The following were not included due to High Line not being able to determine a valid value based on the information currently provided in the IPRLU.
;Symmetry Tax Parameters Not Included in IMCT
There are a number of tax parameters that are provided by Symmetry which were not added to IMCT. The following were not included as it was not able to determine a valid value based on the information currently provided in the IPRLU.
At line 104 changed one line
 NONRESPERCENTAGE
*NONRESPERCENTAGE
At line 107 changed 6 lines
 TRANSIT_CANBY_TAX
 TRANSIT_LANE_TAX
 TRANSIT_TRIMET_EXCISE_TAX
 TRANSIT_SANDY_TAX
 TRANSIT_WILSONVILLE_TAX
 TRANSIT_SOUTH_CLACKAMAS_TAX
*TRANSIT_CANBY_TAX
*TRANSIT_LANE_TAX
*TRANSIT_TRIMET_EXCISE_TAX
*TRANSIT_SANDY_TAX
*TRANSIT_WILSONVILLE_TAX
*TRANSIT_SOUTH_CLACKAMAS_TAX
At line 114 removed one line
At line 119 removed 2 lines
This page (revision-14) was last changed on 26-Nov-2021 10:22 by jmyersTop