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.
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.
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.
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:
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.
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:
Symmetry uses this flow chart to determine which taxes are to be withheld in a multi-State scenario.
The following table (as of January 2011) shows the values used by the STE for the multi-State withholding algorithm.
State | Has State Tax | Withhold on Nonresidents | Withhold on Residents Working Out of State | Withhold if Nonresident State Does Not Require Withholding | Allow Credit for Nonresident State Withholding | Reciprocal States |
---|---|---|---|---|---|---|
AL | TRUE | TRUE | FALSE | TRUE | FALSE | |
AK | FALSE | FALSE | FALSE | FALSE | FALSE | |
AR | TRUE | TRUE | FALSE | TRUE | FALSE | |
AS | FALSE | FALSE | FALSE | FALSE | FALSE | |
AZ | TRUE | TRUE | FALSE | FALSE | FALSE | |
CA | TRUE | TRUE | TRUE | TRUE | TRUE | |
CO | TRUE | TRUE | FALSE | TRUE | FALSE | |
CT | TRUE | TRUE | TRUE | TRUE | TRUE | |
DC | TRUE | FALSE | TRUE | TRUE | FALSE | MD, VA |
DE | TRUE | TRUE | TRUE | TRUE | TRUE | |
FL | FALSE | FALSE | FALSE | FALSE | FALSE | |
GA | TRUE | TRUE | FALSE | TRUE | FALSE | |
GU | FALSE | FALSE | FALSE | FALSE | FALSE | |
HI | TRUE | TRUE | TRUE | TRUE | FALSE | |
IA | TRUE | TRUE | TRUE | TRUE | FALSE | IL |
ID | TRUE | TRUE | FALSE | FALSE | FALSE | |
IL | TRUE | TRUE | FALSE | TRUE | FALSE | IA,KY,MI,WI |
IN | TRUE | TRUE | TRUE | TRUE | FALSE | KY,OH,PA,WI |
KS | TRUE | TRUE | TRUE | TRUE | TRUE | |
KY | TRUE | TRUE | TRUE | TRUE | FALSE | IL,IN,MI,OH,WV,WI,VA |
LA | TRUE | TRUE | FALSE | TRUE | FALSE | |
MA | TRUE | TRUE | TRUE | TRUE | TRUE | |
MD | TRUE | TRUE | TRUE | TRUE | FALSE | DC,PA,VA,WV |
ME | TRUE | TRUE | TRUE | TRUE | FALSE | |
MI | TRUE | TRUE | TRUE | TRUE | FALSE | IL,IN,KY,MN,OH,WI |
MN | TRUE | TRUE | TRUE | TRUE | TRUE | MI,ND |
MO | TRUE | TRUE | FALSE | TRUE | FALSE | |
MP | FALSE | FALSE | FALSE | FALSE | FALSE | |
MS | TRUE | TRUE | FALSE | TRUE | FALSE | |
MT | TRUE | TRUE | TRUE | TRUE | FALSE | ND |
NC | TRUE | TRUE | FALSE | TRUE | FALSE | |
ND | TRUE | TRUE | FALSE | TRUE | FALSE | |
NE | TRUE | TRUE | TRUE | TRUE | TRUE | |
NH | FALSE | FALSE | FALSE | FALSE | FALSE | |
NJ | TRUE | TRUE | TRUE | TRUE | TRUE | PA |
NM | TRUE | TRUE | TRUE | TRUE | FALSE | |
NV | FALSE | FALSE | FALSE | FALSE | FALSE | |
NY | TRUE | TRUE | TRUE | TRUE | TRUE | |
OH | TRUE | TRUE | TRUE | TRUE | FALSE | IN,KY,MI,PA,WV |
OK | TRUE | TRUE | TRUE | TRUE | FALSE | |
OR | TRUE | TRUE | TRUE | TRUE | FALSE | |
PA | TRUE | TRUE | FALSE | TRUE | FALSE | IN,MD,NJ,OH,VA,WV |
PR | TRUE | TRUE | TRUE | TRUE | FALSE | |
RI | TRUE | TRUE | TRUE | TRUE | FALSE | |
SC | TRUE | TRUE | FALSE | TRUE | FALSE | |
SD | FALSE | FALSE | FALSE | FALSE | FALSE | |
TN | FALSE | FALSE | FALSE | FALSE | FALSE | |
TX | FALSE | FALSE | FALSE | FALSE | FALSE | |
UT | TRUE | TRUE | TRUE | TRUE | TRUE | |
VA | TRUE | TRUE | TRUE | TRUE | TRUE | DC,KY,MD,PA,WV |
VI | FALSE | FALSE | FALSE | FALSE | FALSE | |
VT | TRUE | TRUE | TRUE | TRUE | TRUE | |
WA | FALSE | FALSE | FALSE | FALSE | FALSE | |
WI | TRUE | TRUE | TRUE | TRUE | FALSE | IL,IN,KY |
WV | TRUE | TRUE | TRUE | FALSE | TRUE | KY,MD,OH,PA,VA |
WY | FALSE | FALSE | FALSE | FALSE | FALSE |
When UPUTR is run, the STATE_NEXUS Miscellaneous Identifier will be generated with the value of DEFAULT for the selected States.
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 |
This IPUTP STATE_NEXUS Miscellaneous Identifier is applicable for the entire Company for the State defined.
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.
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.
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.
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.
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 |
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 |
On the IPRLUS 'State' tab, an employee should set up the ‘Reciprocity Agreement’, if applicable.
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) |
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 |
WORK: | OH 39-049-1080996 | Columbus, Franklin, OH |
RES: | MI 26-107-1619197 | Big Rapids, MI |
IPPH | PAY LINES | Jurisdiction - 39-049-1080996 Columbus, Franklin, OH | - All Earnings |
Jurisdiction - 26-107-1619197 Big Rapids, MI | - No Earnings |
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 |
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 |
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.
PC 8130 RCITY Earn | 0 |
PC 8131 RCITY SupEarn | 0 |
PC 6951 Res CITY Reg Tax | 0 |
PC 6953 Res CITY Sup Tax | 0 |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation