My Oracle Support Banner

EPY: Bug 35997796 Did Not Fix "Not Applicable" Issue With Indiana Tax Form WH-4 (Doc ID 3023203.1)

Last updated on MAY 19, 2024

Applies to:

PeopleSoft Enterprise HCM Payroll for North America - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Bug 35997796 did not fix "Not Applicable" issue with Indiana Tax Form WH-4 that was delivered in PI48.

WH-4, "Not Applicable" must be a possible selection for "Indiana County of Residence as of January 1" and "Indiana County of Principal Employment as of January 1," as described in the form instructions. Instead, only "None" or an Indiana County are available. "Not Applicable" needs to be added." "Not Applicable" has been added as a selection choice.

Bug 35997796 applied to our development environment did not achieve the expected results.  The Employee Self-Service Indiana state tax form (WH-4) when submitted with Not Applicable for both Indiana County of Residence as of January 1 and Indiana County of Principal Employment as of January 1 for a rehire, the action changes marital status and creates a new effective-dated row that pulls forward old information. So, for instance, if the person previously worked and lived in Marion County, then the new row has Marion County for both county of residence and employment, and therefore not correct. The re-hired employees, who did not live and\or work in Indiana at the beginning of the year, would have an Indiana county on their tax data page from when they were previously hired even though they selected Not Applicable when rehired. 


The issue can be reproduced with the following steps:

1. State Tax Data for "IN" had a tax status of "M"
2. Local Tax Data had a local
3. Made a change on the updateable form PDF to indicate "Not Applicable" and submitted
4. Went back to Employee Tax Data and expected the Local Tax Data to be blank since it is no longer N/A and was not. It just changed the Tax Status to “N” and left the local on that page.
5. Click on the State Tax Data, the system changed the tax status from "M" to "N" which should not have changed the tax status since it is based on county

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.