US Tax Screens
Back to current versionRestore this version

US TAX SCREENS#

Overview#

This page describes the screens that are used for US Taxation in the Payroll Calculation Process.

Geographic Screens#

UDGNIS process loads in the "US Geographic Names Information System (GNIS)" information from the Symmetry Tax Server into the Wiki system. The process will load in all Counties, Cities, Schools, Municipalities, and Zip Codes for each state selected in the parameters. Please refer to the document PR_US_Load_GNIS page for more detailed information as to how the UDGNIS function works.

The following describes the geographic screens that are updated by the UDGNIS function.

IDCO - Define Countries#

US_Tax_Screens_2.1.JPG(info)

IDSP - Define States and Provinces#

US_Tax_Screens_2.2.JPG(info)

IDCN - Define Counties#

US_Tax_Screens_2.3.JPG(info)

IDCI - Define Cities#

US_Tax_Screens_2.4.JPG(info)

IDSD - Define School Districts#

US_Tax_Screens_2.5.JPG(info)

IDMN - Define Municipalities#

US_Tax_Screens_2.6.JPG(info)

IDZR - Maintain ZIP Ranges#

IDZR - COUNTY_ZIP RANGES Tab - Used by Symmetry Taxation

US_Tax_Screens_2.7.1.JPG(info)

IDZR - JURISDICTION ZIP RANGES Tab - Used by Vertex Taxation Only

US_Tax_Screens_2.7.2.JPG(info)

Tax Jurisdiction Feature#

IDTX - Tax Jurisdiction Concepts#

SSState FIPS Numeric Code2 digits
CCCCounty Code3 digits
FFFFFFFCity Feature IDVariable Length, 4 to 7 digits

IDTX - Tax Jurisdiction Screen Layout#

US_Tax_Screens_3.2.1.JPG(info)

Option (1)

US_Tax_Screens_3.2.2.JPG(info)

Option (2)

US_Tax_Screens_3.2.3.JPG(info)

Manually Converting Tax Jurisdictions

There may be cases where the UDGNIS could not convert a tax jurisdiction. This could be a result of a spelling error or the jurisdiction is not classified as a real city by the US Postal Service and therefore the UDGNIS could not find the correct GNIS code to use.

To manually change a Vertex GEO Code to the Symmetry GNIS format follow the steps below:

  1. Copy the GEO CODE into the Alt Geo Code field. This is needed so that when UPCALC is run using Vertex, UPCALC knows which Vertex GEO Code to use.
  2. Using the fields on the right hand side, select the correct County and City. This will create the appropriate GNIS Geo Code. The name defined in the Jurisdiction field will be replaced with the City name.

Tax Jurisdiction Editor Utility#

IDTX - Tax Jurisdiction Dialog Box#

When IDTX, IDLN, IEPI, IEAS, IPTR, IPPH screen requires a Jurisdiction code, the user can click the icon beside the GEO Code field which will pop up the Tax Jurisdiction Editor Utility dialog box.

US_Tax_Screens_4.1.JPG(info)

In the Tax Jurisdiction Editor Dialog there are 2 sections to enter information, the user can enter information in either one:

1. Enter Selection or Jurisdiction Details

GEO Code
ZIP Code
Location

After the selection of GEO Code, ZIP Code or Location Code is specified, the user can modify the Jurisdiction Details if these combinations are not correct or click OK.

2) Jurisdiction Details

State
County
City
Municipality
School

When doing lookup for County, City, Municipality or School, if the user does not know the code of the County or City, the user may use ‘%’ to lookup the column, e.g. %Ph will display the list that contains ‘Ph’

The Message Box will display the DTX_00001 to DTX_00007 messages, depending on the selections made above.

The Return GEO Code will display the generated GEO Code/GNIS Code based on the selections made above.

List of Screens that use Tax Jurisdiction Dialog Box#

The following is a list of screens that contain the tax jurisdiction:

Definition Screens#

IDGV - Maintain Government Registrations#

US_Tax_Screens_5.1.JPG(info)

IPUTR - Maintain US Tax Rates#

US_Tax_Screens_5.2.JPG(info)

IPUTR - Override Tax Rates#

US_Tax_Screens_5.3.JPG(info)

IPUTP - Maintain US Tax Parameters#

US_Tax_Screens_5.4.JPG(info)

Internal Miscellaneous Identifiers

LevelMiscellaneous IdentifierProvided ByAllow IPRLU Override
Federal401K_CATCHUPInternalYes
StateSTATE_ROUNDINGLegislativeNo
StateSUP_PAID_WITH_REGInternalYes
StateSUP_PAID_WITHOUT_REGInternalYes
e.g. 401K_CATCHUP is used for Federal and State Level 401K calculation

IPCU - Define Pay Component Usages#

US_Tax_Screens_5.5.JPG(info)

IPPC - Define Pay Components#

US_Tax_Screens_5.6.JPG(info)

Employee Screens#

IPRLU - Miscellaneous tab#

US_Tax_Screens_6.1.JPG(info)

IPRLUS - New Tax Filing Screen#

US_Tax_Screens_6.2.JPG(info)

IPPH - Pay Jurisdiction Tab#

US_Tax_Screens_6.3.JPG(info)

• 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

• The user can click the Jurisdiction Name to lookup or to pop into the ‘Tax Jurisdiction Editor Dialog’ Box to enter State, County, City, Municipality and School

• The Tax Jurisdiction is returned by Lookup or the ‘Tax Jurisdiction Editor Dialog’ Box and becomes the ‘Pay Jurisdiction’ of this pay

• On the ‘PAY LINES’ Tab, each Pay Line Jurisdiction may specify the Work Jurisdiction of this line so that the Hours and Earnings are allocated to the specified Work Jurisdiction of this line

• After this Pay is calculated by Trial Calc or UPCALC, the Tax Audit Information will be displayed for the list of Jurisdictions, and the summary of all Pay Components are displayed on ‘PAY AMOUNTS’ Tab

IPVT – View Employee Pay Totals#

• After UPCLOZ the Pay Header’s Work Jurisdictions and Home Jurisdiction will be updated into IPVT YTD / QTD

IPGH – Manage Government Report Details#

• RPYEU will generate IPGH information by Jurisdictions

• IPGH ‘PAY JURISDICTION’ Tab allows the user to view the Jurisdiction information

Site Preference – US Taxation#

IMST – Site Preference#

• For each Database Server, the above IMST Site Preferences should be set up during the installation of US Symmetry taxation

US TAX PREFERENCES

US TAX SERIES - specifies the US Tax Series to be used in UPCALC; field size: char(1) 0, N – N/A, client is not using US Taxation, UPCALC is used for BE/AT purposes only 1 – Main US tax module, the Symmetry Tax Engine (STE) is used L – Legacy Series, the Vertex COBOL version tax module is used Q – Quantum Q Series Tax Calculation, not supported, will remove later

US TAX HOST NAME - specifies the Database Host Name of the SymmetryTaxServer that is installed

US TAX PORT NUM - specifies the Port Number of the SymmetryTaxServer that will be listening for incoming Tax Server requests, this must be the same as serverConfig.txt PORT_NUMBER

SYMMETRY PREFERENCES

US STE LOG DIR - optional, specifies the Output Directory for Symmetry Log File - this directory should be the same Output Directory that is used to generate Interface Files for the Application Server, e.g.
Tantus\output - IMPORTANT: please specify a valid Directory Name with Path Name, the Database Object for Output Files MUST NOT be used e.g. OUTPUT object cannot be used

US STE LOG LEVEL - optional, specifies the Symmetry Logging Level that will be passed in STE_LOGGING_LEVEL - user may specify one of the following LOG LEVEL: - “DEBUG”, “INFO”, “WARN”, “ERROR”, “FATAL”, “OFF”, NULL - this should be set to ‘DEBUG’ as default, when Trail Calc or UPCALC is run in Utility Trace, this Log Level will be used - when STE_LOGGING_LEVEL is passed to Symmetry, Symmetry will display information pertaining to the Level specified, e.g. if WARN, it will show only WARN info - please set to ‘DEBUG’ to see all information when running in Trace

US STE LOG FILE - optional, may specify an overridden Symmetry Log File name (future, not used yet)


Notes #

Click to create a new notes page