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

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

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 8 added 6 lines
The amounts calculated by some benefit plans may be used to adjust employee taxable wages. The amounts stored in the benefit deduction pay components need to be passed to the SymmetryTaxEngine so the system can determine the correct taxable wage for the employee for the various taxes.
UPCALC passes the benefit amounts to Symmetry via new PC Usages for what Symmetry calls ‘Benefit Types’. The SymmetryTaxEngine will use the value passed in these Benefit Types to reduce the taxable wage. The SymmetryTaxEngine knows per state which Benefit Types are pre-tax and which are post-tax.
There are no changes required to the benefit plans themselves, nor the benefit deduction pay components. There is just a need to define new pay components and elements. This document will review the new pay components needed.
At line 10 changed one line
STE will determine the pretax status of the nine predefined benefit types for each of the taxes calculated.
The STE will determine the pretax status of the nine predefined benefit types for each of the taxes calculated.
At line 24 changed one line
Symmetry requires the current to date (CTD) value and the year to date (YTD) value to be passed to the SymmetryTaxEngine. If the benefit type has a maximum contribution limit (ie: 401ks) the tax engine will monitor the YTD to determine when the maximum contribution limit has been reached. The tax engine will NOT stop the benefit deduction from taking place, however; it will stop reducing the taxable wages if an Employee has reached the max limit.
If there are multiple benefit plans defined for the same benefit type and each have a different contribution limit, these must be separated out using the Custom benefit types. An example of this is FSA Medical and Dependent Care. The FSA Medical would be set up using the pre-determined FSA benefit type PC Usage, and the FSA Dependent Care would be set up using a custom benefit type PC Usage.
At line 92 added one line
*Dependent Care
At line 130 removed one line
For Symmetry users or converted users, if a particular Benefit type is to be used, you should set up a pay component on [IPPC] with the PC Usage as defined above.
At line 132 removed 4 lines
If the Benefit type is made up by an element, then specify the element name. (e.g. 125 Regular - proration logic here.)
On [IPPC], you can optionally turn ON the 'Store Results' toggle to store the amounts on 'Pay Amounts' tab. This pay component will be stored on IPPH 'Pay Jurisdiction' tab regardless of the 'Store Results' toggle.
At line 158 removed one line
!Benefit PC Usages - IPPC Pretax Criteria Override
At line 166 added 23 lines
!Pre-Defined Benefit Type Pay Component and Element Set Up
[IPCU] PC Usages are supplied to users with the taxation software release.
For each applicable Benefit Type PC Usage (7801 – 7979), the user must define a Pay Component in [IPPC]. On [IPPC] for the new Benefit Type Pay Components, the user must also specify an Element. The element must contain all of the appropriate taxable benefit deduction pay components for that particular benefit type. These Elements are used for all employees by [UPCALC] for all States.
The SymmetryTaxEngine will determine which of the 9 pre-defined benefit types are taxable for each level of taxation.
e.g. 401K Usage 7902 IPPC Element Name: ‘FWT 401K EXEMPT’
!Custom Benefit Type PC & Element Set Up - For All States
For the benefits that do not fall under the nine pre-defined by Symmetry clients may set up ‘custom’ benefit types. These are set up similar to the 9 pre-defined types.
On [IPPC] a new Pay Component must be defined for each ‘custom’ Benefit Type needed. The Pay Component must specify an Element with the benefit deduction pay components for the custom benefit type being created. These Element names are used for all employees by [UPCALC] for all States.
e.g. Custom Benefit Usage 7801 IPPC Element Name: ‘PFRS PERS EX’
IPPE element ‘PFRS PERS EX’ includes all of the benefit deduction pay components which could affect an employee’s taxable wages
!Custom Benefit Types - IPPC Pretax Criteria Override
At line 162 changed one line
For each applicable Benefit PC Usage 7801 to 7979, you must define a pay component on [IPPC] screen and enter the PC Usage for this pay component. You must then enter the element name that made up the Benefit amount for this Benefit Type pay component.
For each applicable Custom Benefit Type PC Usage defined, the user MUST specify the Pre-tax criteria for each tax type. This is done using User Fields in [IPPC]. [UPCALC] will pass the values of these user fields onto the SymmetryTaxEngine so the taxable wages are adjusted appropriately.
At line 166 changed one line
If the nine Pre-defined Benefit types are defined with these user-defined Pretax criteria, this PC Usage is treated as a Custom Benefit Type, this Pretax setup overrides the Pre-defined taxability of the benefit type.
For the nine pre-defined benefit types, the SymmetryTaxEngine will adjust the taxable earnings appropriately for each level of taxation. However if any of the nine Pre-defined Benefit Types are defined with these user-defined Pre-Tax Criteria, this PC Usage is treated as a Custom Benefit Type, this Pre-Tax set up overrides the Pre-defined taxability of the benefit type.
At line 170 removed 2 lines
After a pay component is defined on the [IPPC] screen for a Benefit PC Usage, you can go into the [IPCU] screen for that PC Usage to view the Pay Component setup.
At line 174 removed one line
!Benefit Element - For All States
At line 176 changed one line
On the [IPPC] screen for the pay component of each Benefit PC Usage, you must specify an element that made up the Benefit Amount.
!Custom Benefit Type Element - Varies by States
At line 178 changed 3 lines
e.g.
|401K Usage 7902|IPPC Element Name: TX-401K
|Custom Benefit Usage 7801|IPPC Element Name: TX-BEN-01
Since not all States follow the same exemption rules for the various Custom Benefit Types, users have the ability to create state specific elements which have their own pre-tax criteria defined. If the user does business in multiple states which have differing exemption rules for these ‘custom’ benefit types, an additional element is required per state. The Pre-Tax Criteria User Fields available in [IPPC] are also available in [IPPE], using these user fields the user can define the pre-tax criteria for each state.
At line 182 changed 3 lines
These element names are used for all employees by [UPCALC] for all states
!Benefit Element - Varies by States
The State specific element must be created with the same name as the generic element created in section 5.5. The name must be concatenated with a hyphen and the State code as the suffix.
At line 186 changed one line
Some states require different Benefit Amounts to be varied for some Benefit Types.
After the State specific Element is defined with the State code suffix, the user can define the Pre-Tax criteria on [IPPE] screen for this State Element using the User Fields. The [IPPE] Pre-Tax criteria set up overrides the [IPPC] Pre-tax criteria set up of each Benefit Type.
At line 188 changed one line
UPCALC provides capability to define different Benefit Element for each Benefit Type to be varied by State.
[UPCALC] will append the State Code with a hyphen to the generic Element name to retrieve the specific Element with the Pay Header ‘s Work State, if the Element does not exist for the Work State, then the [IPPC] generic Benefit Element name will be used
At line 190 changed one line
On [IPPC] screen for the Pay Component of the Benefit Usage, a generic Benefit Element name must be set up, this element is used for all states. For states that have a different Benefit amount, set up a different Benefit Element name on [IPPE] screen that is made up from the generic Element Name concatenated with a hyphen and the State code as the suffix.
e.g. Using the previous example of PFRS PERS EX shown in the previous sections for Custom Benefit, New York has different exemption rules for Pension and PERS than New Jersey thus a state specific element is needed.
At line 192 changed 6 lines
e.g.
IPPE Generic Element Name: TX-BEN-01
IPPE Specific State Element Name for New Jersey: TX-BEN-01-NJ
IPPE Specific State Element Name for New York: TX-BEN-01-NY
[UPCALC] will append the State code with a hyphen to the generic element name to retrieve the specific element with the Pay Header's Work State, if element does not exist for the Work State, then IPPC generic Benefit Element name will be used.
e.g.
IPPE Generic Element Name: ‘PFRS PERS EX’
IPPE Specific State Element Name for New York: ‘PFRS PERS EX-NY’
IPPE Specific State Element Name for New Jersey: ‘PFRS PERS EX-NJ’
At line 199 changed one line
This functionality is applicable to all Benefit types including the nine Pre-defined Benefit types and ten custom Benefit types.
!Custom Benefit Type Element – Amounts Vary by States
At line 201 changed one line
!Benefit Element - IPPE PreTax Criteria Override
Some States require different Benefit Amounts to be varied for some Benefit Types.
At line 203 changed one line
Some states require different Pre-tax taxability for some Benefit types.
[UPCALC] provides capability to define different Benefit Element for each Benefit Type to be varied by State.
At line 205 changed one line
[UPCALC] provides capability to define different Benefit Pretax criteria by state-specific elements.
On [IPPC] for the Pay Component of the Benefit Usage, a generic Benefit Element name must be set up, this Element is used for all States. For States that have a different Benefit amount, set up a different Benefit Element name on [IPPE] screen that is made up from the generic Element Name concatenated with a hyphen and the State code as the suffix
At line 207 changed one line
After the State element is defined with the State code suffix, you can define the Pretax criteria on the [IPPE] screen for this State element.
e.g.
IPPE Generic Element Name: ‘TX-BEN-01’
IPPE Specific State Element Name for New Jersey: ‘TX-BEN-01-NJ’
IPPE Specific State Element Name for New York: ‘TX-BEN-01-NY’
At line 209 changed 4 lines
e.g.
IPPE Generic Element Name: TX-BEN-01
IPPE Specific State Element Name for New Jersey: TX-BEN-01-NJ
IPPE Specific State Element Name for New York: TX-BEN-01-NY
[UPCALC] will append the State Code with a hyphen to the generic Element name to retrieve the specific Element with the Pay Header ‘s Work State, if Element does not exist for the Work State, then [IPPC] generic Benefit Element name will be used
At line 214 changed 3 lines
On the [IPPE] screen, click the 'Show User Fields' icon.
The [IPPE] Pretax criteria setup overrides the [IPPC] Pretax criteria setup of each Benefit type.
This functionality is applicable to all Benefit Types including the nine Pre-defined Benefit Types and ten custom Benefit Types.
At line 236 added one line