IR&C Business Requirements Document

Transcription

1 IR&C Business Requirements Document ScholarShare Transition from FIDELITY to TIAA- CREF Payroll Coordination and Tax Services Created on: 10/06/2011 Last Modified on: 03/26/2012 Page 1 of 22

2 Table of Contents 1 Business Need Section Objective: Issue Tracker Reference Project Type: System Requested by: Implementation Deadline: Urgency Deadline Information Statement of Business Need: Current Process: Proposed Process Proposed process from a functional perspective Proposed changes to system inputs and outputs Processing Considerations: Scope and Estimate Section Phase I Scope Phase I Assumptions Phase I Overview of Changes Phase I Estimate Phase I Time Dependencies Phase I Scope and Estimate Approval Phase I Approval by ITS QA Manager Approval by ITS Programming Manager Approval by Hosted Applications Manager Approval by Requesting Department Manager Scope and Estimate Section Phase II Scope Phase II Assumptions Phase II Overview of Changes Phase II Estimate Phase II Time Dependencies Phase II Scope and Estimate Approval Phase II Page 2 of 22

3 3.6.1 Approval by ITS QA Manager Approval by ITS Programming Manager Approval by Hosted Applications Manager Approval by Requesting Department Manager Functional Requirements Phase I Section Overview of Modifications Phase I One-time Processes Phase I Functional Requirements Approval Phase I Functional Requirements Phase II Section Overview of Modifications Phase II Control Table Updates Compute Process One-time Processes Interface Files Corporate Interface Files Reporting Requirements UPAY UPAY Functional Requirements Approval Phase II Revision History Page 3 of 22

4 1 Business Need Section 1.1 Objective: Transition the management of the ScholarShare Program from Fidelity Investments (Fidelity) to TIAA-CREF (TC). 1.2 Issue Tracker Reference Corresponding Issue Tracker Number, if applicable: PPS_RSCH Project Type: New Development Additional Project Type Information: 1.4 System Other Additional System Information: PPS and PIP 1.5 Requested by: John Barrett Payroll Coordination and Tax Services 1.6 Implementation Deadline: Urgency Urgent Additional Urgency Information: Deadline Information The original deadline was prior to November 4, Due to technical resource availability, this project was postponed. Page 4 of 22

5 The Timing of Phase I Phase I should be released as soon as possible. Campuses should install the release as soon as possible so that they can begin the reconciliation process between the TIAA CREF file and the EDB records for ScholarShare deductions. Phase I has to be completed before Phase 2 can be installed. The Timing of Phase II The deadline for implementation is prior to the end of the 1 st Quarter, Statement of Business Need: Beginning November 4, 2011, management of ScholarShare, California s 529 (Internal Revenue Code) educational savings program transferred from Fidelity Investments (Fidelity) to TIAA-CREF (TC) following Fidelity s contract expiration. The payroll processing arrangements for ScholarShare enrollment and ACH transactions involving TC will be different from the procedures currently in place with Fidelity. TC will also retain the FTP file format currently used by Fidelity to provide UC with initial employee ScholarShare deductions as well as subsequent changes. In order to facilitate the transition from Fidelity to TC and the automatic conversion of employee accounts, TC will use a new ABA/Bank Transit Number (EDB 0782) for State Street Bank & Trust and Bank Account Number/Direct Deposit Account (EDB 0783). 1.8 Current Process: Prior to the transition to TIAA-CREF, Fidelity FTP d a file twice each month to UCOP providing ScholarShare add, change and delete activity. GTN 600 is used to store the ScholarShare deductions in PPS. ScholarShare deductions are currently in-activated. There is a UCOP PIP process which formats the ScholarShare data from TIAA-CREF into PPS transactions and makes them available for campus PPS systems to pick up. If the PIP process doesn t find the employee ID in the AYSO database, it uses the SSN portion of the account number as a secondary lookup. SR modified the PIP process that takes updates from TIAA-CREF and applies them to the campus EDBs so that the changes employees have requested are reflected properly. Although this process is currently in place, TIAA-CREF has indicated that they have not sent UC any updates since the full file was sent on 11/21/11. The transactions are processed by the campus PPS systems; LBNL has indicated that they do not offer the ScholarShare deduction to their employees. The compute is currently set up to send ScholarShare deductions in the NACHA file. The 17-digit account number that s stored in the EDB is used for these deductions. No deductions are being sent at this time, because the GTN has been inactivated (R2000, 11/2011). 1. The following information is stored in the EDB for each ScholarShare participant: GTN number always 600 Transit # always Account # 17 digits: always SSN Page 5 of 22

6 1.9 Proposed Process Proposed process from a functional perspective Overview A one-time process should be developed to convert the existing EDB ScholarShare data to the new transit routing and account numbers. The one-time process should update the EDB and produce change records for the standard PPP180 audit report. (Note: the new transit routing and account numbers will not be used at this time, since the ACH transmittal will be handled at the campus level.) ScholarShare deductions should be re-activated. During the payroll compute, PPS will take ScholarShare contributions from gross pay (this will happen automatically once the GTN is re-activated) and record the deductions on a new ScholarShare interface file (new process). After the compute, locations will send an ACH transmittal to Boston Financial Data Services (BFDS) in the amount of the total ScholarShare deductions for that compute. Locations will also send UCOP their ScholarShare files, which will include a totals record. Each ACH amount must exactly match the total represented in a single FTP file. UCOP will encrypt the individual campus files and make them available to BFDS. UCOP has received a full file from TIAA-CREF, with all ScholarShare employees and their current deduction elections. A one-time process should be run to report any discrepancies. This should be released first, to allow the campuses to resolve any discrepancies before the deductions are re-started. ACH Process The current ScholarShare ACH process will be deactivated; i.e., locations will not send ACH transactions to TIAA-CREF via the standard PPS ACH process. Instead, ACH transactions will be sent manually via a nonpayroll system (e.g., via the Accounts Payable system). The ScholarShare Campus File is a new interface which should be FTP d to UCOP, so that UCOP can make it available to BFDS. To facilitate the ACH process, a report containing a list of employees contributing to ScholarShare and the amounts of the contributions should be produced after each payroll compute and be made available to the campus central Payroll office. The individual deductions by employee are needed, as well as a total deduction amount. The Standard Deduction Report by GTN, PPP490 can be used; heading should be renamed GTN 600 ScholarShare Deduction Report; employee SSN is not needed, but employee ID# is needed. Each ScholarShare Campus file sent to UCOP and provided to BFDS should be saved with a naming convention: UC_location code_pay cycle code_paydate UC01BW = UC Location 01 (Berkeley) BiWeekly 1/18/12 paydate ScholarShare Campus File File format specifications Fixed length, 27-byte lines terminated with carriage return, line-feed characters. The VAX payroll process at BFDS accepts text files in the following format: Page 6 of 22

7 Description Position Format Comments Employee SSN 1-9 NNNNNNNNN 9 digits, right-justified, zero-left filled. Pay Date CCYYMMDD Must be valid business date. Amount NNNNNNNNN 9 digits, right-justified, zero-left filled with implied decimal place Sign 27 Space for positive amount, - for negative amount Example: An employee with SSN contributes $500 to ScholarShare on the January 3, 2012 paycheck. Employee with SSN has a $250 reversal, so it is shown as a negative amount. The $500 contribution would be recorded on the ScholarShare file (first example) and the $250 negative deduction as indicated in the second example with a minus sign at the end: $ $ Banking Information The campuses will need the following ScholarShare banking information for the ACH process: Bank Name: State Street Bank &Trust Bank Address: 225 Franklin St, Boston, MA ABA Routing Number: Plan DDA number: BFDS has indicated that the file should come first, followed by the ACH. Since they cannot hold onto funding, it is best that they receive the file first and then the ACH. The file and the ACH should occur within 48 hours of each other Proposed changes to system inputs and outputs In Phase I, a one-time process should produce a discrepancy report that the campuses can use to reconcile their EDB with the TC file. The one-time process should update the EDB and produce change records for the standard PPP180 audit report. (Phase II) ScholarShare deductions should be re-activated. (Phase II) A ScholarShare file that lists employees contributing to ScholarShare and the amounts of the contributions should be produced by PPS after each payroll compute and made available to UCOP ITS. UCOP ITS should also provide this same file to BFDS. To facilitate the ACH process by the campus disbursements office, PPS should provide a report to the campus Central Payroll office. (Phase II) The ScholarShare deductions should no longer appear in the PPP430 reports, since these reports specifically relate to employee deductions sent on the regular ACH, which is not part of the proposed process. (Phase II) Page 7 of 22

8 1.10 Processing Considerations: None. 2 Scope and Estimate Section Phase I 2.1 Scope Phase I Small Additional Scope Information: 2.2 Assumptions Phase I Campuses will work with TIAA-CREF to resolve discrepancies prior to Phase II. Testing for Phase I should utilize a mocked up file in place of the real TIAA-CREF file, so the PPS testing environment can be used. 2.3 Overview of Changes Phase I The full file provided by TIAA-CREF is intended to contain all ScholarShare deduction information. A PIP process will split out this file by campus and make it available to campuses via FTP. A reconciliation program will be developed which will report on any discrepancies between the TC file and the campus EDB. 2.4 Estimate Phase I Task Estimated Work Hours/$ Based on Business Needs Working Days* Requirements 8 hours ($552) 1.25 days Gathering Technical 8 hours ($672) 1.25 days Specification Preparation PIP 2 hours ($138).5 days Mainframe 24 hours 3.75 days Development ($1656) Web Development n/a QA 16 hours 3 days ($1104) User Acceptance Testing 8 hours 2 days New Estimate Based on Functional Requirements? (Enter new estimates if applicable) New Estimate Based on Technical Spec? (Enter new estimates if applicable) Actuals After completion Page 8 of 22

9 Task Estimated Work Hours/$ Based on Business Needs Working Days* Release Preparation 4 hours ($276).625 days Installation in 56 hours 5 days Production ($3864) New Estimate Based on Functional Requirements? (Enter new estimates if applicable) New Estimate Based on Technical Spec? (Enter new estimates if applicable) Actuals After completion Total 126 hours ($8,262) 17.5 days * Estimate Notes: Working days may take into account productivity adjustments, overlap between phases, and multiple resources working on a phase at the same time. Working days do not include weekends. Requirements Gathering elapsed time allows time for document approval. Costs associated with estimated work hours are figured using an hourly cost of $69 if a PAIII is assigned the task and $84 if a PAIV is assigned. 2.5 Time Dependencies Phase I We expect that few or no updates have been received from TIAA-CREF since they provided the full file to UC. Final requirements needed: lead time of 4 weeks 2.6 Scope and Estimate Approval Phase I Approval by ITS QA Manager Version Date Name /04/12 Mary Ann Gohl Approval by ITS Programming Manager Version Date Name 1.0 1/13/12 Bob Franks Approval by Hosted Applications Manager Version Date Name /22 Christopher Scott Approval by Requesting Department Manager Version Date Name 1.0 1/12/12 John Barrett 3 Scope and Estimate Section Phase II 3.1 Scope Phase II Page 9 of 22

10 Medium Additional Scope Information: 3.2 Assumptions Phase II BFDS will log into vsftp to get the FTP files See vendor testing information in the Time Dependencies section. 3.3 Overview of Changes Phase II The changes for this request are as follows: A GTN update to re-activate the ScholarShare deduction (GTN 600). Removal of GTN 600 from the ACH process. This involves updates to the PPPNGL and PPPNGO CTL tables. Addition of messages to the System Messages table A one-time program to update the EDB (PPPDDG) with the new bank information. This isn t strictly necessary because the bank information will no longer be used for ACH transactions, but leaving the Fidelity bank information on that table is misleading. A process to report ScholarShare deductions by employee (with total) on a report or file for the campus. The Standard Deduction Report (PPP490) will be used for this purpose. A PIP process to encrypt the files and place them in the BFDS folder on vsftp (a new vsftp account for BFDS will be established). A new program to create the ScholarShare FTP file from the deduction file created in PPP490. These files will be sent to the UCOP vsftp server. 3.4 Estimate Phase II In initial phase, provide work hours/days. After requirements, this can be revised and dates added. Note: PIP and PPS work can be done concurrently. Task Requirements Gathering Technical Specification Preparation Mainframe Development Estimated Work Hours/$ Based on Business Needs Working Days* 12 hours ($828) 2 days 8 hours ($672) 2.5 days 87 hours ($6003) New Estimate Based on Functional Requirements? (Enter new estimates if applicable) New Estimate Based on Technical Spec? (Enter new estimates if applicable) 17 days 119 hours Actuals After completion Page 10 of 22

11 PIP Changes Web Development QA User Acceptance Testing Release Preparation Installation in Production 32 hours ($2208) Concurrent with PPS changes n/a 80 hours 13 days ($5520) 10 hours 2 days 16 hours ($1104) 56 hours ($3864) 2.5 days 5 days 170 hours/10 days Total 301 hours ($20,199) 44 days * Estimate Notes: Working days may take into account productivity adjustments, overlap between phases, and multiple resources working on a phase at the same time. Working days do not include weekends. Requirements Gathering elapsed time allows time for document approval. Costs associated with estimated work hours are figured using an hourly cost of $69 if a PAIII is assigned the task and $84 if a PAIV is assigned. 3.5 Time Dependencies Phase II Phase II cannot be implemented until the Phase I campus reconciliation process is complete. BFDS would like to be able to test picking up the file, decrypting it, and processing it to the point that the file is on the VAX (their processing system) to make sure that the file can be picked up, decrypted, and has the correct format. Final requirements needed: lead time of 9 weeks 3.6 Scope and Estimate Approval Phase II Approval by ITS QA Manager Version Date Name /04/12 Mary Ann Gohl Approval by ITS Programming Manager Version Date Name 1.0 1/13/12 Bob Franks 1.1 2/23/12 Bob Franks (approved new mf devel. estimate of 119 hours) Approval by Hosted Applications Manager Version Date Name /22 Christopher Scott Approval by Requesting Department Manager Version Date Name Page 11 of 22

12 1.0 1/12/12 John Barrett 4 Functional Requirements Phase I Section 4.1 Overview of Modifications Phase I Phase one consists of a one-time process to compare the full file from TIAA-CREF with EDB participant data and report on the results. Control Table Updates: None EDB Maintenance: None History (HDB, CDB) Process: None Compute Process: None Distribution of Expense: None Consolidated Billing and Self-Billing: None Merit/Range/ATB Processes: None Other Processes: None One-time Processes: Yes, one. Interface Files: None Other Tax Processing None CICS Screen/Web Page Modifications: None Online Help Modifications: None Reporting and Notification: None Forms: None 4.2 One-time Processes Phase I Req. ID Requirement Type/Category Requirement Description PI.R0001 One-time Process PIP Process Description: TIAA-CREF has provided a file of all active deductions. A PIP process should be developed to break up the full file provided by TIAA-CREF into separate files by campus, and make them available on the mainframe for the campuses. PI.R0002 One-time Process PPS Process Description: A reconciliation reporting process should be developed to highlight discrepancies between the TC file and the campus EDB Page 12 of 22

13 Req. ID Requirement Type/Category Requirement Description PPPDDG and PPPDBL tables. Output Files or Reports: A report will be produced listing the discrepancies which can be used by campuses along with TIAA-CREF for reconciliation. The report should include any employees who are listed in the EDB as ScholarShare participants but who are not on the file from TC, or vice versa. It should also list employees who appear in both places (TC file and EDB) but for whom there is a discrepancy in the deduction amount. The report will be sorted by Employee ID. The report should list: Employee ID Employee Name EDB (Y/N) TC File (Y/N) EDB deduction amount TC file deduction amount An appropriate message (can be listed on a separate line below the data record if necessary: o o o o Emp SSN in EDB ScholarShare table; not on TIAA- CREF file Emp SSN on TIAA-CREF file, not in EDB ScholarShare table Discrepancy in employee deduction amounts Emp ID different on EDB and TIAA-CREF file; EDB ID = XXXXXXXXX 4.3 Functional Requirements Approval Phase I Version Date Name 1.0 1/12/12 John Barrett 5 Functional Requirements Phase II Section 5.1 Overview of Modifications Phase II Phase II Changes include: Control table change to re-activate the ScholarShare GTN Page 13 of 22

14 Control table change to remove ScholarShare GTN from the existing ACH process Control table changes to add two new system messages to the System Messages table. Removal of GTN 600 from the 430 reports Conversion of existing EDB ScholarShare data to new transit routing and account numbers Creation of a new interface file Use of PPP490 report to provide the campus Payroll office with the information they need to do the ACH transmittal. PIP process to receive campus files and make them available to BFDS o o The campus file should be sent to UCOP no later than two days after compute (to provide enough time for review and reconciliation by the campus); UCOP ITS should provide the file to BFDS when received by the campus, but no later than one day after receipt. UCOP Banking Services Group stated that they do not receive any special notice of ACH transactions done at the campus level, outside of the echo back transmission received from Mellon Bank. If it is below $250,000 per transaction, BSG does not need separate advance notification. The Scholarshare deductions per pay compute at the campuses are anticipated to be well below this threshold. Control Table Updates: GTN table update to reactivate GTN 600. PPPNGL and PPPNGO table updates to remove GTN 600 from the existing ACH process. Addition of new system messages. EDB Maintenance: None History (HDB, CDB) Process: None Compute Process: o o o o The ScholarShare deduction should be taken from the participant s gross pay (this will happen automatically once the GTN is re-activated). ScholarShare deductions should be recorded on a new interface file (new process). In post-compute processing, GTN 600 should no longer appear on the PPP430 (Surepay Bank Activity) report. (This will be accomplished by removing it from the PPPNGL and PPPNGO tables.) GTN 600 should be excluded from the existing ACH process (This will be accomplished by removing it from the PPPNGL and PPPNGO tables). Distribution of Expense: None Consolidated Billing and Self-Billing: None Merit/Range/ATB Processes: None Other Processes: None One-time Processes: Existing EDB ScholarShare data should be converted to new transit routing and account numbers. (for possible future use; no process will use this data) Interface Files: New ScholarShare interface file for BFDS. Page 14 of 22

15 Other Tax Processing: None CICS Screen/Web Page Modifications: None Online Help Modifications: None Reporting and Notification: See One-time Processes section. Use of PPP490 report to provide the campus Payroll office with the information they need to do the ACH transmittal. Forms: None 5.2 Control Table Updates Req. ID Requirement Type/Category Requirement Description PII.R0001 Control Table Table 02 Gross To Net Table GTN 600 should be re-activated (See Attached UPAY 545). PII.R0002 Control Table Table 45 NACHA GTN Organization Table GTN 600 should be removed from PPPNGL and PPPNGO tables to exclude it from the existing ACH process. This will be accomplished by end-dating. (See attached UPAY 918) PII.R Control Table Two new messages should be added to the System Messages Table: DEDUCTION GTN IS NOT SCHOLARSHARE (600) severity level 3 INPUT DEDUCTION FILE FOR SCHOLARSHARE IS EMPTY severity level Compute Process Req. ID Requirement Type/Category PII.R0003 Compute Requirement Description Pay and Deduction Calculation: the ScholarShare contribution should be taken from the participant s gross pay (should happen automatically as a result of the table change) PII.R0004 Compute Pay and Deduction Calculation: the ScholarShare contribution should be recorded on a new interface file (New process. See Interface Files section below). If there are no ScholarShare deductions for the compute (for the campus), a new severity level 3 message INPUT DEDUCTION FILE FOR SCHOLARSHARE IS EMPTY should be produced. This will provide a warning message without stopping processing. Page 15 of 22

16 Req. ID Requirement Type/Category PII.R0005 Compute Requirement Description Post-compute Processing: GTN 600 should be excluded from the existing ACH process. (This should happen automatically as a result of the table changes.) Instead, ACH transactions will be sent manually via a non-payroll system (e.g., via the Accounts Payable system). GTN 600 should be removed from the 430 reports. (This should happen automatically as a result of the table changes.) PII.R0006 Compute Rush Checks: Rush Checks should be tested to make sure any ScholarShare deductions are properly processed. The amounts should be included in the total to be sent by AP to ACH. PII.R0007 Compute ORCA: ORCA should be tested to make sure any ScholarShare deductions are properly processed. The amounts should be included in the total to be sent by AP to ACH. 5.4 One-time Processes Req. ID Requirement Type/Category PII.R0008 One-time Process Requirement Description Process Description: A one-time process will be developed to make the following changes to the EDB ScholarShare information on table PPPDDG: Modify the current DDA/TIN combination which creates the employee account number. The current DDA number will be replaced with the new DDA ( ). Change the bank ABA number to which the funds are transmitted to that of State Street Bank and Trust ABA number ( ) Campuses should be able to run in report or update mode. Output Files or Reports: An ECF Change File should be produced (feeds into PPP180) Standard PPP180 audit reports should be produced. Page 16 of 22

17 5.5 Interface Files Corporate Interface Files Req. ID Requirement Type/Category Requirement Description PII.R0009 Interface File A new vsftp account for BFDS should be established so that they will be able to pick up the interface files from UCOP. PII.R0010 Interface File A new interface file should be produced after each compute. The file should include data regarding ScholarShare participants deductions taken during that compute. The format should match specifications in the Proposed Process section. File naming convention: SCH_UC_location code_pay cycle code_paydate SCH_UC01BW = UC Location 01 (Berkeley) BiWeekly 1/18/12 paydate The totals trailer record should be as follows: in the social security section, the trade date in the trade date, total dollars in the amount field, and a space in the sign field Campuses should FTP the files to UCOP. A file should be sent to BFDS only if funding will also be sent. If there are no Scholarshare deductions for the compute (for a particular campus), then a file should not be provided to BFDS. PII.R0011 Interface File UCOP should encrypt the ScholarShare files with the totals records and make them available to BFDS on the UCOP vsftp server. A PIP process should be set up to encrypt the campus files (using PGP encryption). The file extension should be.pgp. A PIP process should be set up to strip the SCH_ from the file names before the files are put on vsftp for BFDS. A PIP process should be set up to place the campus files in the BFDS folder on vsftp. Page 17 of 22

18 5.6 Reporting Requirements Campuses will use the PPP4903 report to get the information they need to do the ACH transmittal. Req. ID Requirement Type/Category Requirement Description PII.R0012 Reporting A PPP4903 Report (Standard Deduction Report) containing only ScholarShare deductions should be provided to the campus Payroll offices. The report should be provided after each compute. SSN should be omitted from the report. The title should read 600 ScholarShare Deduction Report The report will provide the total dollar amount to be used for the ACH transmission. Page 18 of 22

19 5.7 UPAY 545 Page 19 of 22

20 5.8 UPAY 918 Page 20 of 22

21 5.9 Functional Requirements Approval Phase II Version Date Name 1.0 1/12/12 John Barrett 6 Revision History Version Date Name Description /10/11 Elizabeth Burkart Initial draft posted /10/11 Maxine Gerber Added mainframe estimate and assumptions /11/11 Beth Burkart Added PIP estimate /11/11 Maxine Gerber Modified estimate section with 3 options /12/11 Beth Burkart Added Issue Tracker number, Christopher s estimates /13/11 Beth Burkart Estimate Table. Totaled estimates for the 3 options. Need Release prep for 2 nd and 3 rd options /13/11 John Barrett Complete Replacement of original business needs sections /13/11 Maxine Gerber Removed original scope and estimate information /15/11 Maxine Gerber Created separate scope, estimate and function spec sections for the two phases /20/11 John Barrett Additional details on file to BFDS /21/11 Maxine Gerber Changed from Date Mandated to Urgent /22/11 Maxine Gerber - Added hosted apps estimate - Removed references to encrypting the file for BFDS. - Added PIP Phase 2 estimate /4/12 Beth Burkart Functional requirements /5/12 Beth Burkart Refined functional requirements after meeting with Maxine. Added QA estimates /6/12 Beth Burkart Updates to functional requirements /9/12 Maxine Gerber Added new encryption requirement to BNS and functional requirements. Updated estimate to reflect using the 490 file instead of the PAR to create the FTP file /10/12 Maxine Gerber Updated PIP estimate from 4 to 32 hours to accommodate new requirement to encrypt files for BFDS /10/12 Beth Burkart Updated Functional Requirements. Reporting, rush checks, ORCA, vendor testing /11/12 Beth Burkart UPAY forms and updated timing /12/12 Beth Burkart John s approval, and finalizing for web. Updated wording in /17/12 Beth Burkart Bob approved estimates. Page 21 of 22

22 2.15 1/18/12 Beth Burkart Changes to PII.R0010 and PII.R0011 re: file naming /19/12 Beth Burkart Updated Christopher s estimates post TSD, phase II /7/12 Marcia Johnson Updated section PI.R0002 output report specifications /22/12 Beth Burkart Updated mainframe programming estimate based on TSD /23/12 Beth Burkart Bob approved new MF devel estimate /1/12 Beth Burkart Corrected file length from 26 to 27 on p. 6 (ScholarShare Campus File) it became 27 when the sign was added /6/12 Beth Burkart PII.R0004 and PII.R0010 to state what should happen if there are no ScholarShare deductions. Added Control Table section regarding the new system messages /14/12 Beth Burkart Replaced UPAY918 form with updated form. It had been discovered that end dating is more effective than deleting, in this case /26/12 Beth Burkart Two minor changes to the table at the top of p. 7. There is no need to mask the SSN. Sign is position 27. Page 22 of 22