EPY: TAX109 Request to run for employees paid in a Calendar Year for W2 validation (Doc ID 1274874.1)

Last updated on DECEMBER 18, 2015

Applies to:

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

Symptoms

There are two Internet verification options you can use to verify that your employees' names and Social Security numbers match Social Security's records.

You can:

Verify up to 10 names and SSNs (per screen) online and receive immediate results. This option is ideal to verify new hires.
Upload overnight files of up to 250,000 names and SSNs and usually receive results the next government business day. This option is ideal if you want to verify an entire payroll database or if you hire a large number of workers at a time.

While the service is available to all employers and third-party submitters, it can only be used to verify current or former employees and only for wage reporting (Form W-2) purposes

The benefits are
Correct names and SSNs on W-2 wage reports are the keys to the successful processing of your annual wage report submission.
It's faster and easier to use than submitting your requests paper listings or using Social Security's telephone verification option.
Results in more accurate wage reports.
Saves you processing costs and reduces the number of W-2cs.
Allows Social Security to properly credit your employees' earnings record, which will be important information in determining their Social Security benefits in the future.

Customers can run TAX109 to create a file for verifying the data. However, improvements are needed to make is more user friendly.

Changes

Issue #1:
The option on the Run Control is to run this report for a Date Range. It looks for HIRE_DT status and if an employee was previously hired and the date falls within that range as was the issue with Ice 1704790000 then the employee would appear on the report. If their original Hire Date is not within the range of the Report then the employee is excluded. If LAST_HIRE_DT status was included in the selection criteria then there would be no worry about whether the original Hire Date is outside the range of the report.

Issue #2:
We need a new option on the run control that allows the TAX109 to be run against the year-end tables. We need the ability to specify the year on the run control for this new option. This would ensure the employee's data is accurate for the employees' year-end reporting. As is works now, the TAX109 reads the entire database, and includes terminated employees if part of the run control criteria. We should only validate the data if the terminated employees has year end data for the specified year. We need the ability to specify the year on the run control.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms