Question about Feature 10EET and what is sent to BSI in the EPC EP parameter

[khigby]

We recently discovered that feature 10EET was misconfigured in our environment - we had it returning just the number (as in "1") rather than the full string "EETYID 1" and thus the "EP:" Employment Type parameter was missing altogether in the BSI interface for all employees.

We resolved the issue so it now correctly returns "EETYID 1" for nonresident workers and BSI receives "EP: 1" on the program-to-program interface, thus correctly withholding the De Minimis taxes.

However, in our implementation of feature 10EET we are returning "0" (an invalid value) for all other employees, causing the "EP:" parameter to be excluded from those employees. Is there any harm in configuring it this way, or should we be returning "EETYID 0" for employees that don't require a special designation?

In my testing, there was no difference when they were sent with "EP: 0" vs an absent "EP:" field.

For reference, these are the valid values for the "EP:" Employment Type parameter:

0 - Regular Active Employee (Tax as if a regular active employee.)

1 - Mobile Workforce Employee (Use non-resident minimums.)

2 - Terminated Employee

4 - Deceased - Private Sector (Tax using deceased rules for the Private Sector.)

5 - Deceased - Railroad Employee (non ICC-eligible) (Tax using deceased rules for a Railroad Employee.)

6 - Deceased - Public Sector (Tax using deceased rules for the Public Sector.)

7 - Active ICC-eligible Railroad Employee

8 - Deceased ICC-eligible Railroad Employee

9 - Flight Crew Employee

[greg_zifchock · Accepted solution]

Kevin,

For the most part we default to EETYID 0. We tie EETYID 4 to Action / Reason Codes for Deceased employees.

Greg

[khigby · Accepted solution]

Thank you! We also reached out to BSI directly and they confirmed that if the "EP" parameter is not specified, it defaults to zero.