The function has two purposes:
The UPRLU reads IMCT 'UPRLU MAPPING' to generate the Misc. Tax Parameters on IPRLUS with the default set up.
IMCT ‘UPRLU MAPPING’ contains the list of Tax Parameters at the employee level only, therefore if the IPUTP Tax Parameter does not exist on IMCT, this IPUTP tax parameter will not be inserted on IPRLUS, this means the IPUTP tax parameter is for UPCALC internal use only
If the UPRLU is run with 'Exception Level: 0-Exception Level', UPRLU displays the report with Statistics only
If the UPRLU is run with 'Exception Level: 1-User Trace', UPRLU displays the report with Tax Parameters
During testing of the UPRLU, the user may wish to re-run the UPRLU to re-test.
Report Parameters | |
---|---|
As of Date | Mandatory, Date LOV available This field indicates the date from which information is to be collected. You must provide a date for the system to select which assignment and personal records to review for work and resident state. |
Create File | Optional, Yes or No lexicon available If <Yes> is selected UPRLU will create a flat file showing the original information in the Vertex columns and the new value in the Misc Tax Parameters. If NO, the report will be run without creating an interface file (normally for testing purposes). |
Update Method | Mandatory, X_UPRLU_METHOD lexicon available You must select which update option the UPRLU must perform. |
Directory Name | Optional, allows the user to specify a valid directory known to the database server. This is used when the Create File parameter is set to <Yes>. |
File Name | Optional, Text This field displays the file name of the data being uploaded. The file extension must be .xls, this is the only supported file format for UPRLU. |
Trial | Mandatory, Yes or No lexicon available You may choose to run the report in a trial mode to see results <Yes> or in update mode <No>. If this toggle is set to <No>, the miscellaneous tax parameters will be inserted in IPRLU. If this toggle is set to <Yes>, the report will indicate which records could potentially be updated. If the Create File toggle is also set to <Yes>, the flat file will still be created. |
Exception Level | Mandatory, Exception Level lexicon available This field defines the exception level (report messages) required. Report should be run with Exception Level 0 If issues are encountered re-run UPRLU with Exception Level = 9 for one employee. |
User Comments | Optional, Text This field holds the user-supplied comment which will appear in the header of all pages of the report. This is useful during testing phases to identify similar reports from each other. |
The report filters may be used to filter the employee records by the selected options, for example only run for Employment Status = Active.
Report Filters | |
---|---|
People List | Optional, LOV Available This will limit the report to the people list selected. |
Person | Optional, Multiple Selection Available, LOV Available This will limit the report to the persons selected. |
Entity | Optional, Multiple Selection Available, LOV Available This will limit the report to the entities selected. |
Location | Optional, Multiple Selection Available, LOV Available This will limit the report to the locations selected. |
Auth Area | Optional, Multiple Selection Available, LOV Available This will limit the report to the authorization areas selected. |
Department | Optional, Multiple Selection Available, LOV Available This will limit the report to the departments selected. |
Org Level Type | Optional, X_ORG_LEVEL_TYPE lexicon available This will limit the report to the org level type selected. |
Org Level Code | Optional, Multiple Selection Available, LOV Available This will limit the report to the organizational levels selected. |
Unit | Optional, Multiple Selection Available, LOV Available This will limit the report to the units selected. |
Group | Optional, Multiple Selection Available, LOV Available This will limit the report to the groups selected. |
Payroll | Optional, Multiple Selection Available, LOV Available This will limit the report to the payrolls selected. |
Job | Optional, Multiple Selection Available, LOV Available This will limit the report to the jobs selected. |
Position | Optional, Multiple Selection Available, LOV Available This will limit the report to the positions selected. |
Employment Status | Optional, Multiple Selection Available, LOV Available This will limit the report to the employment statuses selected. |
Employment Type | Optional, X_EMPLOYMENT_TYPE lexicon available This will limit the report to the employment types selected. |
Assignment Type | Optional, X_ASSIGN_TYPE lexicon available This will limit the report to the assignment types selected. |
Pay Type | Optional, X_PAY_TYPE lexicon available This will limit the report to the pay types selected. |
The UPRLU is a dual purpose function.
The UPRLU will insert and populate the appropriate tax parameters for any state the employee lives and works in. The function will use the data in the original Vertex fields in IPRLU to populate the new tax parameters.
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.
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.
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.
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.
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’.
If the employee does not have an IPRLU record and the ‘DFLT PAYRULE’ site preference has not been defined, the UPRLU will not create a default IPRLU record for the employee.
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:
In order for UPRLU to convert the Vertex information to the Symmetry Tax Parameters, mapping had to be laid out for each individual state.
The mapping has been provided in the custom table ‘UPRLU Mapping’ within the IMCT screen.
In IMCT, the Custom Key field holds the state code and the state’s Misc Tax parameter.
Custom Subkey displays the IPRLU field UPRLU will read in order to retrieve the data. This data will be printed in the output file.
The Custom Data holds the necessary coding and mapping for that Custom Key. This field tells UPRLU how to decode the lexicon fields to match the values supported for the tax parameter.
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'.
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).
If clients need to edit the mapping or add Internal tax parameters we advise you to request Client Services for assistance.
The internally provided Tax Parameters may be manually added to an employee’s IPRLU record, or added to IMCT and the UPRLU run for those few employees.
If you have employees who live and/or work in the following states please review these and determine if they are required for your employees. The document PR_US_State_Tax_Calc.doc provides more details on the parameters.
If it is determined these parameters are needed for some employees they may be manually added to the employee’s IPRLU record. Alternatively the parameters may be manually added to the IMCT using valid values as determined by the client, and the UPRLU run for the specific employees these parameters are valid for.
Nebraska
Oregon
TBD – the UPRLU has not yet been programmed for this purpose.
The UPRLU function provides the option of creating an output file. This output file displays what IPRLU records the UPRLU has updated. The file also shows what the values were in the Vertex fields as well as the new values inserted in the Tax Parameters.
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation