October 25, 2010 PeopleSoft Payroll Tax Update 10-E – Release 9

PeopleSoft Payroll for North AmericaTax Update 10-ETax Update Notes - Release 9

PeopleSoft Payroll’s Tax Update 10-E includes updates to U.S. tax and garnishment tables, COBOL program and store statement changes, and re-delivered SQRs for U.S. and Canadian payroll reporting. These tax update notes include:

  • Instructions for updating your system’s tables and a summary of the table changes
  • A list of COBOL program and store statement changes
  • A summary of the SQRs delivered with this tax update
  • An appendix of object changes delivered with this tax update

For Release 9, the tax update package also includes the following documentation files:

UPD813279_INSTALL.htm / “PeopleSoft Application Update Installation Instructions”
Resolution_813279.xls / List of object changes delivered with Tax Update 10-E
UPD813279_CODECHANGES.rtf / PS Print Project Report for Release 9


You must follow the instructions in the UPDxxxxxx_INSTALL.htm document to apply the object changes listed in the Resolution_xxxxxx.xls spreadsheet before applying the COBOL and store statement changes, running the DataMover scripts, or using the SQRs delivered in this tax update. Before applying Tax Update 10-E, you must apply all previous tax updates.
Unless otherwise indicated by a specific posting date, Report IDs referenced in these tax update notes have not been posted to MyOracle Support.

Copyright © 2010, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Updating Your Tables

Tax Update 10-E includes the following files for updating the tables in your PeopleSoft Payroll system.

File / Contents
upd813279_01.dat
upd813279_01.dms
/ U.S. tax table updates
upd813279_02.dat
upd813279_02.dms
/ Garnishment table updates
upd813279_03.dat
upd813279_03.dms
(U.S. only)
/ Tax Form Definitions Table and Tax Form Print Parameters Table
(Report IDs1934393000, 1981773000, 1929405000, 2002705000)
upd813279_04.dat
upd813279_04.dms
/ Strings table
upd813279_05.dms
/ Database stamp
(There is no .dat file associated with this .dms file.)
upd813279_06.dat
upd813279_06.dms
(U.S. only)
/ 2010 U.S. Year End Forms PDF Templates for XMLP
(Report ID 2002717000)
upd813279_07.dat
upd813279_07.dms
/ New “PAYROLL” Report Category ID for Payroll XML report definitions.
(Report ID 1975586000)

Both U.S. and Canadian customers should apply the garnishment, strings anddatabase stamp updates.

The DataMover script (.dms) files identify the input data file (.dat) as well as the output log message file. The directory where DataMover looks for the input data file and the log file is specified in your Configuration Manager.

Any new-insert DataMover entries in these tax update scripts which have key values matching rows already in your database will not be applied. This condition could occur if you have already added any of the new table entries included in this tax update script on your own, such as a tax change, which was posted to MyOracle Support.

Special Notes – North America

New “PAYROLL” Report Category ID

Currently, the “ALLUSER” Report Category ID as defined on the XML Report Definition is attached to payroll related reports and many other report definitions. As a result, all users have access to payroll-related reports when they should not.

Effective with this tax update, a new “PAYROLL” Report Category ID has been provided for payroll related XML Report Definitions. Customers can use this new report categoryto limit access to payroll information. The “PAYROLL” Report Category ID delivers assigned security roles for the Payroll Administrator, PI Administrator and Employee Self-Service. The Payroll Administrator role will be granted update access to the report definitions.

(Report ID 1975586000)

XMLP PDF Bulk File Issue with PT 8.50.10

For customers on the PeopleTools Product Patch 8.50.10 running the XMLP versions of year-end forms or slips, the generated PDF bulk file contained only the last employeein the batch; records for the remainder of the employees were missing from the file.
This issue is resolved in PeopleTools 8.50.11. For more details, please use the following link to refer to the Patch Notes for Report ID 1954857000 (Save XMLP Global Properties page to enable new psxp_pdf_optimized property).

Special Note – Preparing for U.S. Year End Reporting 2010

After you have followed the instructions in the “PeopleSoft Application Update Installation Instructions” to apply the object changes delivered in this tax update, you are ready to update your year end tables for 2010 U.S. year-end wage and tax reporting. Refer to the separate document Year End Processing 2010: U.S., Puerto Rico, and U.S. Territories delivered with this tax update for detailed instructions on year-end processing with PeopleSoft Payroll for North America.

Step 1 is for NEW PeopleSoft Payroll Users only (processing Year End in PeopleSoft Payroll for the first time in 2010)
  1. If you have not already done so, run the DataMover script upd805004_04.dms (delivered in the previous Tax Update 10-D) to add 2009 entries to the Tax Form Definition Table.
Steps 2 – 10 are for ALL PeopleSoft Payroll Users
  1. IMPORTANT: You must complete this manual step before proceeding to use Change Assistant to apply the DataMover scripts upd813279_03.dms and upd813279_06.dms delivered with Tax Update 10-E.
    Enter the Tax Form Identification W-2 and the Effective Date of 01/01/2009 on the Tax Form Definition search page and select Search. Add a new row in the table that duplicates all of the 2009 entries by selecting the Add (+) button in the “Effective Date” Group Box. Change the effective-date for this newly inserted row to 01/01/2010. Save this new entry. Then follow this same procedure for Tax Form Identifications W-2c, W-2AS, W-2GU, W-2PR, W-2VI, W-2cAS, W-2cGU, W-2cPR, and W-2cVI. Save these new entries.
  2. Update the new 2010 Tax Form Definition Table entries you have created with your specific earnings and deductions information for year-end reporting. Save your changes.
    To update the Tax Form Definition Table with a new earnings or deduction, the Effective Date of the Earnings Table or Deductions Table entry must match the Effective Date of the Tax Form Definition Table entry you are updating. For example, if you are updating a Tax Form Definition Table entry dated 01/01/2010, then the Effective Date on the Earnings Table or Deduction Table entry of the earnings or deduction being added to the Tax Form Definition Table entry must also be 01/01/2010. If necessary, in Correction mode, temporarily change the Effective Date of the Earnings Table or Deduction Table entry to match the Effective Date of the Tax Form Definition Table entry, update the Tax Form Definition Table entry with the earnings or deduction and save the change, and then, again in Correction mode, return the Effective Date of the Earnings Table or Deduction Table entry to its original date.
  3. To update your Tax Form Definition Table for 2010 Form 940 reporting, enter the Tax Form Identification 940 and the Effective Date of 01/01/2009 on the Tax Form Definition search page and select Search. Add a new row in the table by selecting the Add (+) button in the “Effective Date” Group Box and change the Effective Date for this newly inserted row to 01/01/2010. Enter information for any earnings or deductions that should be defined as FUTA-exempt for 2010 FUTA Form 940 reporting. Save this new entry.
  4. Run the DataMover script upd813279_03.dmsprovided in Tax Update 10-E. This script will add 2010 entries to the Tax Form Definitions table and Tax Form Print Parameters table for new W-2 boxes 12CC (HIRE exempt wages and tips) and 14I (Wisconsin Advance Earned Income Credit payments).
  5. Run TAX710 to print a listing of 2010 Tax Form Definition table entries and review for accuracy.
  6. Run TAX712 to verify that 2010 entries have been added to the Tax Form Print Parameters table.
  7. Update W-2 Company table with entries for calendar year 2010.
  8. Run the DataMover script upd813279_06.dms to update the Tax Form XMLP Options Table with2010 U.S. year-end form PDF templates for XMLP processing.
  9. Update the Year End Form Options Table for XMLP processing by manually adding a new row for Tax Year 2010 for each W-2 Reporting Company.

Ordering W-2 Forms for Tax Year 2010

RR Donnelly has updated their website with information on year-end tax forms for 2010:

In preparing to order W-2 forms for tax year 2010, employers should consider the following issues:

Employers who will be reporting W-2 data to any state where their state Employer Identification Number (EIN) is greater than 13 characters in length should not order Form ID LSR02A (the “four-corner” format which prints four W-2s per page at the four corners of the page). W-2 Form ID LSR02A does not provide sufficient space in box 15 to print State EINs that exceed 13 characters.
States that are currently known to issue Employer Identification Numbers that exceed 13 characters include Kansas, Utah, and Wisconsin. Employers who are considering ordering W-2 Form ID LSR02A should first review all of their state EINs to confirm that none of them exceed 13 characters in length.
* * * * * * * * * * * * * * * * * * * * * * * * * *

Employers who report W-2 data to New Jersey should be aware that, because of the unusually large number of data items that New Jersey requires to be separately printed on Form W-2, there is a very high incidence of data overflow that results in the printing of a second New Jersey W-2 form for each employee with New Jersey reportable data. With the new requirement in tax year 2009 to print the amount deducted for New Jersey Family Leave Insurance (in addition to the amounts deducted for disability insurance and the various components of the New Jersey unemployment insurance program), the problem of data overflow for New Jersey W-2 reporting affected even more employees.
To avoid running short of W-2 forms, in determining the quantity of forms to order, it is suggested that employers anticipate that two forms will be needed for each instance of an employee with W-2 data to be reported to New Jersey.

Special Note – U.S. Savings Bonds

Payroll Savings Bond Purchase Program Discontinued

As first announced in Tax Update 10-C, in conjunction with the U.S. Department of the Treasury’s decision to terminate the issuance of paper U.S. savings bonds through the traditional payroll savings bond purchase program, Tax Update 10-E delivers product modifications which eliminate the functionality related to the traditional payroll savings bond purchase program.

Employers should complete termination of existing traditional savings bond purchase programs andrefundany remaining funds due to employees before applying Tax Update 10-E.

With the application of Tax Update 10-E, the following pages will no longer be viewable or accessible via the menu navigation:

U.S. Savings Bond Table
(Set Up HRMS/Product Related/Payroll for North America/Deductions/U.S. Savings Bond Table)
U.S. Savings Bond Report (PAY706.SQR run control)
(Set Up HRMS/Product Related/Payroll for North America/Deduction Table Reports/U.S. Savings Bond)
Bond Purchase Report (PAY016A.SQR run control)
(Payroll for North America/Payroll Processing USA/Pay Period Reports/Bond-Federal Reserve)
Bond Purchase Report (FGPY011A.SQR run control)
(Payroll for North America/Payroll Processing USF/Pay Period Reports/Bond Purchase)
Bond Purchase Report – Federal Reserve (PAY016B.SQR run control)
(Payroll for North America/Payroll Processing USA/Pay Period Reports/Bond-Federal Reserve)
Federal Bond Reserve File (FGPY011B.SQR run control)
(Payroll for North America/Payroll Processing USF/Pay Period Reports/ Bond-Federal Reserve)
Bond Purchase Suspensions (PAY058.SQR run control)
(Payroll for North America/Payroll Processing USA/Pay Period Reports/Bond Purchase Suspensions)
Bond Purchase Suspensions (PAY058.SQR run control)
(Payroll for North America/Payroll Processing USF/Pay Period Reports/Bond Purchase Suspensions)
U.S. Savings Bond Specification
(Payroll for North America/Employee Pay Data USA/Deductions/Purchase U.S. Savings Bonds)
U.S. Savings Bond Specification
(Payroll for North America/Employee Pay Data USF/Deductions/Purchase U.S. Savings Bonds)

These pages will continue to be accessible via the menu navigation but viewable in read-onlymode:

U.S. Savings Bond Activity
(Payroll for North America/Employee Pay Data USA/Deductions/Review U.S. Savings Bonds)
U.S. Savings Bond Activity
(Payroll for North America/Employee Pay Data USF/Deductions/Review U.S. Savings Bonds)

Detailed information on the termination of the savings bonds payroll purchase program is available on the Federal Reserve Bank Services website:

Included is: “Checklist: Discontinuing Your Paper Payroll Savings Plan”

(Report ID 1984481000)Going Forward: Employee Bond Purchases through TreasuryDirect
Employees still have the opportunity to purchase savings bonds through payroll deductions by authorizing a deduction/net-pay allocation via automated bank-transfer through the TreasuryDirect program. This alternative bond purchase option is already currently available, and employees may begin bond purchases through TreasuryDirect immediately. See the TreasuryDirect website for details:

Below is an excerpt from the information provided for employers at the TreasuryDirect website:

How do we set employees up in TreasuryDirect?

1. First, each employee will need to open a TreasuryDirect account at

2. Then, each will submit a request to you for a payroll direct deposit, providing their TreasuryDirect account number and the amount they want to have deducted from each pay period. An instruction sheet is available in TreasuryDirect to help your employees with this.

3. You establish a direct deposit for the amount requested and deliver the funds to the employee's TreasuryDirect account just as you would to any bank account. It's a standard ACH transaction, and you can classify the employee’s TreasuryDirect account as either checking or savings.

ABA number: 051736158

Account number: Employee's TreasuryDirect account number without hyphens

What are my responsibilities as an employer?

With TreasuryDirect you would be responsible for collecting the requested direct deposit amount and delivering it to the employee’s TreasuryDirect account, just like you would a direct deposit for a mortgage or car payment. That’s it. With TreasuryDirect payroll:

  • You don’t need to hold or accumulate funds toward the purchase price of a security,
  • You don’t request the issuance of securities, and
  • You don’t keep track of registrations.

In PeopleSoft Payroll for North America, an employee may submit a request for a payroll direct deposit for TreasuryDirect bond purchases through Employee Self Service.

PeopleCode modifications are delivered in this tax update to ensure that the employee's TreasuryDirect account number is saved without hyphens as shown below, as required by TreasuryDirect.

Employee Self Service Add Direct Deposit page before Save