This page (revision-17) 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
17 26-Nov-2021 10:22 13 KB mmcfarland to previous
16 26-Nov-2021 10:22 13 KB jescott to previous | to last
15 26-Nov-2021 10:22 13 KB jmyers to previous | to last
14 26-Nov-2021 10:22 13 KB jmyers to previous | to last
13 26-Nov-2021 10:22 13 KB jmyers to previous | to last
12 26-Nov-2021 10:22 13 KB jmyers to previous | to last
11 26-Nov-2021 10:22 13 KB jmyers to previous | to last
10 26-Nov-2021 10:22 13 KB jmyers to previous | to last
9 26-Nov-2021 10:22 13 KB jmyers to previous | to last
8 26-Nov-2021 10:22 13 KB jmyers to previous | to last
7 26-Nov-2021 10:22 13 KB jmyers to previous | to last
6 26-Nov-2021 10:22 12 KB jmyers to previous | to last
5 26-Nov-2021 10:22 12 KB jmyers to previous | to last
4 26-Nov-2021 10:22 12 KB jmyers to previous | to last
3 26-Nov-2021 10:22 11 KB jmyers to previous | to last
2 26-Nov-2021 10:22 11 KB jmyers to previous | to last
1 26-Nov-2021 10:22 11 KB jmyers to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 11 changed one line
When employees live in a different state than the one where they work, or an employee performs services in more than one state, the withholding rules can become quite complicated. There are reciprocal withholding agreements between States which must be considered and in the absence of those agreements, the "Nexus" or business connection between the company and the State where the employee resides must also be factored into the equation. \\ \\
When employees live in a different state than the one where they work or if someone performs services in more than one state, the withholding rules can become quite complicated. There are reciprocal withholding agreements between states which must be considered and in the absence of those agreements, the "Nexus" or business connection between the company and the state where the employee resides must also be factored into the equation.
At line 13 changed one line
The Symmetry Tax Engine maintains a list of all the reciprocal agreements between the States, using the Nexus method. This provides a list of the Nexus relationships for the employer. Based upon the residency of the employee, the locations where the employee worked, the Nexus relationships of the employer, and the status of the employee having filed a Certificate of Non-Residency, the STE will determine the correct locations where taxes should be withheld.\\ \\
Symmetry Tax Engine maintains a list of all the reciprocal agreements between the states. Using the setNexus method, this will provide a list of the nexus relationships for the employer. Based upon the residency of the employee, the locations where the employee worked, the nexus relationships of the employer, and the status of the employee having filed a Certificate of Non-Residency, the STE will determine the correct locations where taxes should be withheld.
At line 15 changed 2 lines
In addition, a State may decide to withhold taxes on a resident employee who works in a different State, if that State does not have a State withholding tax, or does not require withholding for non-residents, such as the District of Columbia. Also, States may require that tax be withheld on employees working in a different (non-resident) State. In this situation, a State may allow a credit for the tax which is withheld in the non-resident work State. The non-resident work State tax would be subtracted from the tax computed for the resident state. \\ \\
The default value for all Nexus settings is false. In order to define the Nexus relationship of the employer to an individual state, the Nexus for each State must be set.
In addition, a state may decide to withhold taxes on a resident employee who works in a different state if that state does not have a state withholding tax or does not require withholding on nonresidents (e.g. District of Columbia). Also, states may require that tax be withheld on employees working in a different (nonresident) state. In this situation, a state may allow credit for the tax which is withheld in the nonresident work state. The nonresident work state tax would be subtracted from the tax computed for the resident state. The default value for all nexus settings is false. In order to indicate the nexus relationship of the employer to an individual state, the Nexus for each State must be set.
At line 18 changed one line
The STE uses the flow chart on the following pages to determine which taxes to withhold in a multi-state scenario. The STE begins by identifying the Resident State of the employee. STE then loops through all the Non-Resident States to determine how withholding will occur. There are 5 possibilities:
The STE uses the flow chart on the following pages to determine which taxes to withhold in a multi-state scenario. STE begins by identifying the Resident State of the employee. STE then loops through all the Non-Resident States to determine how withholding will occur. There are 5 possibilities:
At line 20 changed 5 lines
#Withhold only in the resident State
#Withhold only in the non-resident State
#No withholding in either the resident or non-resident State
#Withhold the full amounts in both the resident and non-resident State
#Withhold the full amount in the non-resident State. If the calculated tax in the resident State on the same wages is greater than the calculated tax in the non-resident State, withhold the difference in the resident State.
#Withhold only in the resident state
#Withhold only in the nonresident state
#No withholding in either the resident or nonresident state
#Withhold the full amounts in both the resident and nonresident state
#Withhold the full amount in the nonresident state. If the calculated tax in the resident state on the same wages is greater than the calculated tax in the nonresident state, withhold the difference in the resident state.
At line 26 changed one line
In situations where the withholding occurs in the Resident State, the STE will take the wages and benefits assigned to the non-resident State and add them to the Resident State totals in order to perform the calculation.
In situations where the withholding occurs in the Resident State, STE will take the wages and benefits assigned to the Non-Resident state and add them to the Resident State totals in order to perform the calculation.
At line 28 changed one line
The flow chart on next page refers to some specific data for each State under consideration. These factors are presented in a table following the flow chart. The factors are:
The flow chart on next page refers to some specific data for each state under consideration. These factors are presented in a table following the flow chart. The factors are:
At line 30 changed 6 lines
*Does the State have a reciprocal agreement in place with other States?
*Does the State have a tax?
*Does the State withhold on non-residents?
*Does the State withhold on residents working outside of the State?
*Does the State withhold if the non-resident State does not require withholding?
*Does the State allow credits for non-resident State withholding?
*Does the state have a reciprocal agreement in place with other states?
*Does the state have a tax?
*Does the state withhold on nonresidents?
*Does the state withhold on residents working outside the state?
*Does the state withhold if the nonresident state does not require withholding?
*Does the state allow credit for nonresident state withholding?
At line 41 changed one line
Symmetry uses this flow chart to determine which taxes are to be withheld in a multi-State scenario.
Symmetry uses this flow chart to determine which taxes are to be withheld in a multi-state scenario.
At line 43 changed 3 lines
[US_State_Reciprocity_01.JPG]
----
[US_State_Reciprocity_02.JPG]
[US_Audit_Pay_Rules_01.JPG]
At line 44 added 2 lines
[US_Audit_Pay_Rules_02.JPG]
At line 51 changed one line
The following table (as of January 2011) shows the values used by the STE for the multi-State withholding algorithm.
The following table (as of January 2011) shows the values used by STE for the multi-state withholding algorithm.
At line 111 changed one line
!!Nexus Relationship Set Up
!Nexus Relationship Set up
At line 114 removed one line
When [UPUTR] is run, the STATE_NEXUS Miscellaneous Identifier will be generated with the value of DEFAULT for the selected States.
At line 126 added one line
When UPUTR is run, the Miscellaneous Identifier STATE_NEXUS will be generated with the value of DEFAULT for the selected States.
At line 117 removed 3 lines
||Value||Description
|STATE_NEXUS| Defines if the State Nexus Relationship exists for the state.
|DEFAULT VALUE|Options are: \\Default: The Default Nexus Relationship is used. \\YES: Nexus Relationship exists \\NO: Nexus Relationship does not exist
At line 121 changed one line
This [IPUTP] STATE_NEXUS Miscellaneous Identifier is applicable for the entire Company for the State defined.
At line 123 removed one line
If an organization has no specific requirement for a Nexus Relationship at the State or Local level, there is no more set up required for Nexus Relationship.
At line 125 changed one line
If an organization has multiple Entities or State Registrations that require to set up different State Nexus Relationships, users must set up [IDGV] by State Registration. __NOTE:__ The IDGV State Nexus set up overrides the IPUTP set up.
STATE_NEXUS - indicates if the State Nexus Relationship exist for the State
At line 127 changed one line
If an organization has multiple Local Registrations that require to set up different Local Nexus Relationships, users must set up IDGV by Local Registration. __NOTE:__ The IDGV Local Nexus set up overrides the State Nexus set up.
DEFAULT -The Default Nexus Relationship is used
YES -Nexus Relationship exists
NO -Nexus Relationship does not exist
At line 138 added 11 lines
This IPUTP STATE_NEXUS Miscellaneous Identifier is applicable for the entire Company for the State defined.
If the Company has no specific requirement for Nexus Relationship at the State or Local level, there is no more set up required for Nexus Relationship.
If the Company has multiple Entities or State Registrations that require to set up different State Nexus Relationship, user must set up IDGV by State Registration. The IDGV State Nexus set up overrides the IPUTP set up.
If the Company has multiple Local Registrations that require to set up different Local Nexus Relationship, user must set up IDGV by Local Registration. The IDGV Local Nexus set up overrides the State Nexus set up.
At line 131 removed one line
If an organization has multiple Entities or State Registrations that require to set up different State Nexus Relationships, users must set up the IDGV form. __NOTE:__ This setup overrides the IPUTP STATE_NEXUS set up. If IDGV is not set up, the IPUTP setup is used.
At line 133 changed 7 lines
__IDGV Form Values__\\
||Field||Description
|Reg. Type|Users must enter one of: ‘US State Regist 1’ or ‘US State Regist 2’ up to ‘US State Regist 9’\\The last digit of ‘US State Regist’ must match the last digit of the State Regist Type defined on IDGR.
|Govt Rate Type|Users must enter the lexicon value of ‘US State Nexus Relationship’. \\This is from lexicon [X_GOVT_RATE_TYPE] 024003 - US State Nexus Relationship.
|Effective/Expiry|Enter the applicable Effective/Expiry dates.
|Amount|This defines if the State Nexus Relationship exists for the State Registration.\\ \\Enter one of the following applicable Nexus Relationship values:\\0 – Use IPUTP STATE_NEXUS set up\\1 – YES: Nexus Relationship exists for the State Registration\\99 – NO: Nexus Relationship does not exist for the State Registration
\\
At line 154 added 20 lines
If the Company has multiple Entities or State Registrations that require to set up different State Nexus Relationship, user must set up on IDGV screen, this set up overrides the IPUTP STATE_NEXUS set up. If IDGV is not set up, the IPUTP set up is used.
Registration Type - must enter one of ‘US State Regist 1’ or ‘US State Regist 2’ up to ‘US State Regist 9’
- the last digit of ‘US State Regist n’ matches the last digit of IDGR State Regist Type.
Govt Rate Type - must enter lexicon value of ‘US State Nexus Relationship’
- from lexicon X_GOVT_RATE_TYPE 024003 - US State Nexus Relationship
Effective / Expiry - enter applicable Effective / Expiry dates
Amount - indicates if the State Nexus Relationship exist for the State Registration
- enter one of the following applicable Nexus Relationship values:
0 – Use IPUTP STATE_NEXUS set up
1 – means YES, Nexus Relationship exists for the State Registration
99 – means NO, Nexus Relationship does not exist for the State Registration
At line 142 removed one line
If an organization has multiple Entities or Local Registrations that require setting up different Local Nexus Relationships, users must set up the IDGV form. __NOTE:__ This setup overrides the IDGV State Nexus and the IPUTP STATE_NEXUS setup. If IDGV Local Nexus is not set up, the IDGV State Nexus setup is used.
At line 144 removed 7 lines
__IDGV Form Values__\\
||Field||Description
|Reg. Type|Users must enter one of: ‘US State Regist 1’ or ‘US State Regist 2’ up to ‘US State Regist 9’\\The last digit of ‘US State Regist’ must match the last digit of the State Regist Type defined on IDGR.
|Govt Rate Type|Users must enter the lexicon value of ‘US State Nexus Relationship’. \\This is from lexicon [X_GOVT_RATE_TYPE] 024003 - US State Nexus Relationship.
|Effective/Expiry|Enter the applicable Effective/Expiry dates.
|Amount|This defines if the State Nexus Relationship exists for the State Registration.\\ \\Enter one of the following applicable Nexus Relationship values:\\0 – Use IPUTP STATE_NEXUS set up\\1 – YES: Nexus Relationship exists for the State Registration\\99 – NO: Nexus Relationship does not exist for the State Registration
\\
At line 152 changed one line
!IPRLUS – State Reciprocity Agreement
At line 154 removed one line
On the [IPRLUS] 'State' tab, an employee should set up the ‘Reciprocity Agreement’, if applicable.
At line 156 changed 7 lines
__IPRLUS Reciprocity Field Values__\\
From the lexicon [X_UST_RECIPROCATION]\\
|00|Default (PPH Work/Res GEO)\\*Pay Line Earnings are allocated according to the Pay Header’s Work and Home Jurisdiction \\*If the Pay Line’s Tax Jurisdiction is the same as Pay Header’s Home Jurisdiction, the Pay Line’s earnings are allocated to the Pay Header’s Home Jurisdiction \\*If the Pay Line’s Tax Jurisdiction is NOT the same as the Pay Header’s Home Jurisdiction, the Pay Line’s earnings are allocated to the Pay Header’s Work Jurisdiction \\*If a Pay Line does not specify a Tax Jurisdiction, the Pay Line’s Earnings are allocated to the Pay Header’s Work Jurisdiction \\*The NonResCertificate = False when it is passed to Symmetry \\*The NEXUS is set according to the IDGV or the IPUTP set up
|01|NR Certificate Filed\\*Pay Line Earnings are allocated the same way as 00 – Default \\*The NonResCertificate = True when it is passed to Symmetry \\*The NEXUS is set according to the IDGV or the IPUTP set up
|02|Calc WORK Tax (PPH Work GEO)\\*All Pay Line Earnings are allocated according to Pay Header’s WORK Jurisdiction \\*The NonResCertificate = False when it is passed to Symmetry \\*The NEXUS value will be set to YES for the WORK GEO, otherwise the NEXUS value will be set to NO
|03|Calc RES Tax (PPH Home GEO)\\*All Pay Line Earnings are allocated according to Pay Header’s HOME Jurisdiction \\*the NonResCertificate = False when pass to Symmetry \\*the NEXUS value will be set to YES for the HOME GEO, otherwise the NEXUS value will be set to NO
|04|Calc WORK / RES (PPH 2 States)\\*same as 00 – Default (PPH Work/Res GEO)
If the Company has multiple Entities or Local Registrations that require to set up different Local Nexus Relationship, user must set up on IDGV screen, this set up overrides the IDGV State Nexus and IPUTP STATE_NEXUS set up. If IDGV Local Nexus is not set up, the IDGV State Nexus set up is used.
At line 164 changed 2 lines
*If the IPRLUS ‘Reciprocity Agreement’ is not set up, the [IMST] Site Preference US TAX RECIP will be used.
*The IMST Site Preference ‘US TAX RECIP’ has the same values from the lexicon [X_UST_RECIPROCATION], as above.
Registration Type - must enter one of ‘US Local Regist 1’ or ‘US Local Regist 2’ up to ‘US Local Regist 9’
- the last digit of ‘US Local Regist n’ matches the last digit of IDGR Local Regist Type.
At line 185 added 2 lines
Govt Rate Type - must enter lexicon value of ‘US Local Nexus Relationship’
- from lexicon X_GOVT_RATE_TYPE 027014 - US Local Nexus Relationship
At line 188 added 62 lines
Effective / Expiry - enter applicable Effective / Expiry dates
Amount - indicates if the Local Nexus Relationship exist for the Local Registration
- enter one of the following applicable Nexus Relationship values:
0 – Use IDGR State Nexus or IPUTP STATE_NEXUS set up
1 – means YES, Nexus Relationship exists for this Local
99 – means NO, Nexus Relationship does not exist for this Local
!IPRLU – State Reciprocity Agreement
On IPRLU STATE Tab, an employee should set up the ‘Reciprocity Agreement’ if applicable.
From Lexicon X_UST_RECIPROCATION
00 – Default (PPH Work/Res GEO)
01 – NR Certificate Filed
02 – Calc WORK Tax (PPH Work GEO)
03 – Calc RES Tax (PPH Home GEO)
04 – Calc WORK / RES (PPH 2 States)
- If IPRLU ‘Reciprocity Agreement’ is not set up, the IMST Site Preference US TAX RECIP will be used.
- IMST Site Preference ‘US TAX RECIP’ has the same values from lexicon X_UST_RECIPROCATION as above.
1) 00 – Default (PPH Work/Res GEO)
- Pay Lines Earnings are allocated according to Pay Header’s Work and Home Jurisdiction
- if the Pay Line’s Tax Jurisdiction is the same as Pay Header’s Home Jurisdiction, this Pay Line’s earnings is allocated to Pay Header’s Home Jurisdiction
- if the Pay Line’s Tax Jurisdiction is NOT the same as Pay Header’s Home Jurisdiction, this Pay Line’s earnings is allocated to Pay Header’s Work Jurisdiction
- if a Pay Line does not specify a Tax Jurisdiction, this Pay Line’s Earnings will be allocated to Pay Header’s Work Jurisdiction
- the NonResCertificate = False when pass to Symmetry
- the NEXUS is set according to IDGV or IPUTP set up
2) 01 – NR Certificate Filed
- Pay Line Earnings are allocated the same way as 00 –Default
- the NonResCertificate = True when pass to Symmetry
- the NEXUS is set according to IDGV or IPUTP set up
3) 02 – Calc WORK Tax (PPH Work GEO)
- All Pay Line Earnings are allocated according to Pay Header’s WORK Jurisdiction
- the NonResCertificate = False when pass to Symmetry
- the NEXUS will be set to YES for the WORK GEO, otherwise NEXUS will be set to NO
4) 03 – Calc RES Tax (PPH Home GEO)
- All Pay Line Earnings are allocated according to Pay Header’s HOME Jurisdiction
- the NonResCertificate = False when pass to Symmetry
- the NEXUS will be set to YES for the HOME GEO, otherwise NEXUS will be set to NO
5) 04 – Calc WORK / RES (PPH 2 States)
- same as 00 – Default (PPH Work/Res GEO)
At line 251 added 2 lines
At line 170 removed one line
For an employee with a residence in a Michigan city, which withholds tax, the STE checks to insure the organization has a Nexus relationship with the City before withholding the tax. \\The STE automatically sets the Nexus value to TRUE when wages are earned for the residence location. However, if the employee does not have wages in the residence location, the organization needs to define the presence of a Nexus relationship. If the Nexus relationship is not set, then no withholding will occur in the Michigan resident location. \\For a Michigan City, users can set up the Nexus Relationship by each city on [IDGV]. If the Local Nexus Relationship is not set up for a city, then the State Nexus Relationship will be used.
At line 172 changed 5 lines
|IPRLUS STATE Tab|Reciprocity Agreement:|- Null, default to IMST, which uses the Default Reciprocity
|IPUTP Michigan State|STATE_NEXUS|- DEFAULT
|IPUTP OHIO State|STATE_NEXUS|- DEFAULT
|IDGV ‘US State Regist 1’|Govt Rate Type|- ‘US State Nexus Relationship’ is not set up
|IDGV ‘US Local Regist 1’|Govt Rate Type|- ‘US Local Nexus Relationship’ is not set up
For employee with a residence in Michigan city which withholds tax, STE checks to insure the company has a Nexus relationship with the city before withholding the tax. STE automatically sets the nexus to TRUE when the wages are earned for the residence location. However, if the employee does not have wages in the residence location, the company needs to indicate the presence of a nexus relationship. If the nexus relationship is not set, then no withholding will occur in the Michigan resident location. For Michigan City, user can set up Nexus Relationship by each City on IDGV, if Local Nexus Relationship is not set up for that City, then the State Nexus Relationship will be used.
At line 178 removed 2 lines
|WORK:|OH 39-049-1080996|Columbus, Franklin, OH
|RES:|MI 26-107-1619197|Big Rapids, MI
At line 181 changed 4 lines
|IPPH|PAY LINES |Jurisdiction - 39-049-1080996 Columbus, Franklin, OH|- All Earnings
| | |Jurisdiction - 26-107-1619197 Big Rapids, MI|- No Earnings
[US_State_Reciprocity_06.JPG]\\
In this example, since the IDGV State and Local Nexus are not set up, then IPUTP STATE_NEXUS for Michigan will be used. The IPUTP for Michigan is set to DEFAULT Nexus Relationship. This means the Default Nexus will be passed to Symmetry with the Nexus Relationship value set to YES, therefore the Michigan Residence Earnings and Taxes are returned.
IPRLU STATE Tab Reciprocity Agreement: - Null, default to IMST, which uses Default Reciprocity
IPUTP Michigan State STATE_NEXUS - DEFAULT
IPUTP OHIO State STATE_NEXUS - DEFAULT
IDGV ‘US State Regist 1’ Govt Rate Type - ‘US State Nexus Relationship’ is not set up
IDGV ‘US Local Regist 1’ Govt Rate Type - ‘US Local Nexus Relationship’ is not set up
At line 186 changed 4 lines
|PC 8130 RCITY Earn|2564.10
|PC 8131 RCITY SupEarn|1000.00
|PC 6951 Res CITY Reg Tax|25.64
|PC 6953 Res CITY Sup Tax|10.00
WORK: OH 39-049-1080996 Columbus, Franklin, OH
RES: MI 26-107-1619197 Big Rapids, MI
At line 267 added 13 lines
IPPH PAY LINES Jurisdiction - 39-049-1080996 Columbus, Franklin, OH - All Earnings
Jurisdiction - 26-107-1619197 Big Rapids, MI - NO Earnings
In this test, since IDGV State and Local Nexus are not set up, then IPUTP STATE_NEXUS for Michigan will be used. IPUTP for Michigan is set to DEFAULT Nexus Relationship, this means the Default Nexus will be passed to Symmetry with the Nexus Relationship = YES, therefore the Michigan Residence Earnings and Taxes are returned.
PC 8130 RCITY Earn 2564.10
PC 8131 RCITY SupEarn 1000.00
PC 6951 Res CITY Reg Tax 25.64
PC 6953 Res CITY Sup Tax 10.00
At line 193 changed 4 lines
|IDGV MI ‘US State Regist 1’|Govt Rate Type|- ‘US State Nexus Relationship’ is set up with Amount = 99
| | |- this means Nexus Relationship does not exist
[US_State_Reciprocity_07.JPG]\\
[US_State_Reciprocity_08.JPG]\\
IDGV MI ‘US State Regist 1’ Govt Rate Type - ‘US State Nexus Relationship’ is set up with Amount = 99
- this means Nexus Relationship does not exist
At line 198 changed 2 lines
In this example, the Nexus Relationship is set to NO for Michigan, therefore the Michigan Residence Earnings and Taxes are NOT returned.\\ \\
Users can optionally set the IDGV Local Nexus Relationship value to NO for Big Rapids City and the Michigan Residence Earnings and Taxes are NOT returned.
At line 201 changed 4 lines
|PC 8130 RCITY Earn|0
|PC 8131 RCITY SupEarn|0
|PC 6951 Res CITY Reg Tax|0
|PC 6953 Res CITY Sup Tax|0
At line 289 added 18 lines
The Nexus Relationship is set to NO for Michigan, therefore the Michigan Residence Earnings and Taxes are NOT returned.
User may optionally set up the IDGV Local Nexus Relationship to NO for Big Rapids City, the Michigan Residence Earnings and Taxes are NOT returned.
PC 8130 RCITY Earn 0
PC 8131 RCITY SupEarn 0
PC 6951 Res CITY Reg Tax 0
PC 6953 Res CITY Sup Tax 0