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

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

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 2 lines
[{TableOfContents }]
At line 9 changed 8 lines
|Remove Old Tax Rates|Optional. When set to YES, the report will remove old [IPUTR] Tax Rates that match the defined Effective date.\\ \\Users can run UPUTR to remove old tax rates without loading new rates, to clean up historical tax rates.\\ \\[Yes or No|X_YES_NO] lexicon available
|Load Tax Rates|Optional. When set to YES, the report load the IPUTR Tax Rates for the defined Effective date and the selected States.\\ \\When this toggle is set to YES, users do not need to set the 'Remove Old Tax Rates' toggle to YES. UPUTR will automatically match or create new entries with the same Effective date. This is because UPUTR needs to retain the Overridden User Rates and therefore cannot remove Old Rates with the same Effective Date before loading. \\ \\ [Yes or No|X_YES_NO] lexicon available
|Load State Misc Parms|Optional. When set to YES, the report will load the IPUTP Tax Parameters for selected States. \\ \\[Yes or No|X_YES_NO] lexicon available
|Load Tax District Type|Optional. If defined, the PSD Codes (Political Subdivision Codes) for Pennsylvania will be loaded and stored on [IDSD]. \\ \\ [District Type|X_UPUTR_DISTRICT_TYPE] lexicon available
|Trial|Optional. When set to YES, the report will be run in trial mode. \\When this toggle is set to NO, the IPMT and IPUTR forms will be updated. \\ \\[Yes or No|X_YES_NO] lexicon available
|Print Load Detail| Optional. When set to YES, the report will show the detailed dump of the Tax Rates and State Misc Tax Parameter information. \\ \\When set to YES, the report size may be quite large, therefore users should leave set this toggle to NO, unless required for tracing purposes. \\ \\[Yes or No|X_YES_NO] lexicon available
|Exception Level|Optional. This field defines the exception level (report messages) to be printed.\\ \\Users should run the report with this toggle set to 'Exceptions Only' unless reuqired for tracing. When this toggle is set to 'Utility Trace, the report could be over several hundred pages. \\ \\[Exception Level|X_TRACE_LEVEL] lexicon available.
|User Comment|Optional. Users can enter test that will be printed on the header of the report. \\This is useful during testing phases to identify similar reports from each other. Text field.
|Remove Old Tax Rates|Optional. When set to YES, the report will remove old [IPUTR] Tax Rates that match the defined Effective date.\\ \\Users can run UPUTR to remove old tax rates without loading new rates, to clean up historical tax rates.\\ [Yes or No|X_YES_NO] lexicon available
|Load Tax Rates|Optional. When set to YES, the report load the IPUTR Tax Rates for the defined Effective date and the selected States.\\ \\When this toggle is set to YES, users do not need to set the 'Remove Old Tax Rates' toggle to YES. UPUTR will automatically match or create new entries with the same Effective date. This is because UPUTR needs to retain the Overridden User Rates and therefore cannot remove Old Rates with the same Effective Date before loading. \\[Yes or No|X_YES_NO] lexicon available
|Load State Misc Parms|Optional. When set to YES, the report will load the IPUTP Tax Parameters for selected States. \\[Yes or No|X_YES_NO] lexicon available
|Load Tax District Type|Optional. If defined, the PSD Codes (Political Subdivision Codes) for Pennsylvania will be loaded and stored on [IDSD]. [District Type|X_UPUTR_DISTRICT_TYPE] lexicon available
|Trial|Optional. When set to YES, the report will be run in trial mode. \\When this toggle is set to NO, the IPMT and IPUTR forms will be updated. \\[Yes or No|X_YES_NO] lexicon available
|Print Details| Optional. When set to YES, the report will show the detailed dump of the Tax Rates and State Misc Tax Parameter information. When set to YES, the report size may be quite large, therefore users should leave set this toggle to NO, unless required for tracing purposes. \\[Yes or No|X_YES_NO] lexicon available
|Exception Level|Optional. This field defines the exception level (report messages) to be printed.\\ \\Users should run the report with this toggle set to 'Exceptions Only' unless reuqired for tracing. When this toggle is set to 'Utility Trace, the report could be over several hundred pages. \\[Exception Level|X_TRACE_LEVEL] lexicon available.
|User Comments |Optional. Users can enter test that will be printed on the header of the report. \\This is useful during testing phases to identify similar reports from each other. Text field.
At line 24 changed one line
|Load Only Jurisdiction|Optional. Users can enter a list of jurisdictions to load in the County or City rates. Example: City of Yonkers.\\ \\__Note:__ If the "Load All Jurisdiction" toggle is set to YES, this toggle will not be used.
|Load Only Jurisdiction|Optional. Users can enter a list of jurisdictions to load in the County or City rates. Example: City of Yonkers.\\ \\__Note__ If the "Load All Jurisdiction" toggle is set to YES, this toggle will not be used.
At line 58 removed 16 lines
The IPUTR US Tax Rates are for information purposes only (except for the overridden SUTA / FUTA rates). The tax rates are not passed to Symmetry for tax calculations, rather Symmetry retrieves the tax rates directly within their tax engine (Symmetry Tax Server). \\ \\
The [UPCALC] process will read IPUTR for SUTA / FUTA Overridden amounts and will pass these overridden amounts to Symmetry for the tax calculations. \\ \\
There are two options to set up Overridden Rate, Overridden Wage Base or Overridden Tax Limit:\\ \\
1. IPUTR
*Enter the rate or wage base provided by the government on the Override fields.
*These overrides are applicable for the entire organization, for the State.
*Rate overrides are only applicable for FUTA, SUTA, SUTA SC, SUI EE and SDI EE tax identifiers. Overrides entered for other tax rates will not be read.\\
2. [IDGV]
*If there is a specific rate given by the government for a different State Registration #, enter on IDGV, "Reg Type" field. This overrides the IPUTR rate.
*UPCALC retrieves the IDGV information by Government Registration, from the employee's pay header group. \\ \\
The Effective Date entry on IPUTR is not used by Symmetry. The UPUTR process will load in all tax rates, regardless of when they become effective. During the tax calculations, UPCALC will pass the pay period issue date to the Symmetry Tax Server to determine which tax rates to use for the period being paid. \\ \\
At line 75 changed one line
The Effective Date entry on IPUTR is used by the UPCALC process to determine which record to read for any overridden tax rate for the pay period being paid. \\ \\
If a users needs to add in a new effective date entry for a change to an overridden tax rate, such as new government supplied SUTA rate, users should run UPUTR for the new effective date. \\ \\
At line 77 removed 2 lines
If a user needs to add in a new effective date entry for a change to an overridden tax rate, such as new government supplied SUTA rate, users should run UPUTR for the new effective date. \\ \\
At line 86 changed 3 lines
----
![Notes|Edit:Internal.UPUNVEND]
[{InsertPage page='Internal.UPUNVEND' default='Click to create a new notes page'}]