This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

US AUDIT PAY RULES#

Overview#

This page describes the UPRLU process.

The function has two purposes:

1. To convert the Vertex U.S pay rule data to the Symmetry tax parameters
2. To audit the U.S pay rules to ensure there are no missing tax parameters.

UPRLU – Selection Criteria#

UPRLU – Audit US Tax Filing Information#

US_Audit_Pay_Rules_01.JPG

UPRLU Processing#

Purpose#

The UPRLU is a dual purpose function.

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 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>.
   
   
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 employee records are kept up to date with new tax parameters etc.

IPRLU Tax Filing Conversion#

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.

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

IMCT – Custom Table#

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.

US_Audit_Pay_Rules_02.JPG

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.

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 High Line has created ie: 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.

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.

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  NONRESPERCENTAGE

Oregon  TRANSIT_CANBY_TAX  TRANSIT_LANE_TAX  TRANSIT_TRIMET_EXCISE_TAX  TRANSIT_SANDY_TAX  TRANSIT_WILSONVILLE_TAX  TRANSIT_SOUTH_CLACKAMAS_TAX

UPRLU - Audit Tax Filing Information#

TBD – the UPRLU has not yet been programmed for this purpose.

Output File#

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.

---

Notes #

Click to create a new notes page