Business Requirements Documentpayroll.ucop.edu/requirements/DART/SR101NNN_Year_End... ·...

Year End Processing 1 8/1/2018

Business Requirements Document

Year End Processing


Document Information

Document Attributes Information ID SR101NNN Owner Author(s) Contributor(s)

Revision History

Version Issue Date Changes 1.0 4/20/17 B. Burkart – first draft 1.1 5/1/17 Updated in meeting with Barbara 1.2 5/9/17 B. Burkart – reviewed and updated assumptions and outstanding items. 1.3 5/10/17 B. Burkart – updates to requirements 1.4 6/5/17 B. Burkart – updates based on latest spreadsheet 1.5 6/8/17 B. Burkart & B. Vanden Borre updated 1.6 6/12/17 B. Burkart & B. Vanden Borre updated functional requirements and

assumptions. 1.7 6/13/17 B. Burkart – minor cleanup of unused sections. 1.8 6/15/17 B. Burkart & B. Vanden Borre – finished functional requirements. 1.9 9/19/17 B. Burkart – updated Requ 2 re: demographic data from UCPath 1.10 9/20/17 B. Burkart – updated with Barbara. 1.11 9/28/17 B. Burkart – updated link to spreadsheet.

Document Approvals

Role Name Signature Date


Table of Contents

1 Overview ............................................................................................................................................................... 4

2 Product/Solution Scope ........................................................................................................................................ 8

3 Business Services and Processes ......................................................................................................................... 12

4 Business Rules ..................................................................................................................................................... 12

5 Business Requirements ....................................................................................................................................... 12

6 Non-Functional Requirements ............................................................................................................................ 21

7 External References ............................................................................................................................................ 21


1 Overview

There will be a need to perform year end processing for any location(s) that transitioned to UCPath during the tax reporting year (e.g., ACA, W-2, processing of unsubstantiated Health FSA claims, adjustments, etc.). Depending on the cutover timing and other factors, the exact steps may differ from the year end processing steps performed for locations remaining on PPS. Steps may also differ based on cutover timing.

1.1 Background

Current year-end processes include Open Enrollment, Affordable Care Act processing, W-2 and other tax-related processing, etc. In addition, some month-end processes may be impacted by the UCPath conversion occurring at year end.

1.2 Objectives

Plan the year end processing in PPS for locations that transitioned to UCPath during the tax year. A greater emphasis will be placed on year end processing for locations cutting over to UCPath at year-end, since the pilot is currently planned for the end of 2017.

• Determine which year end processes (e.g., OE, salary bases, Affordable Care Act, etc.) must run at the end of the cutover year in order to insure that employees are transitioned smoothly to UCPath and that any required reporting is completed accurately and timely.

• Create PPS year-end instructions for the transitioning locations, for example, notations on the year-end sequence document.

• Determine if any existing PPS processes require modification.

• Determine if any new PPS processes are needed. For example, there may be a need to get demographic data from UCPath to update W-2 extract files.

• Determine what PPS functionality must be available to support year-end processing. Careful coordination will be needed between this DART sub-project and the Disable PPS features, jobs, etc. sub-project, to insure access to any PPS functionality needed at year-end.


• Identify which year-end processes can be run solely by UCPath.

• Identify year-end processes that can be split between PPS and UCPath without negative impacts.

• Identify year-end processes that will be run solely by PPS (for example, 2017 W-2, 2017 ACA reporting, etc.)

• Identify processing tasks that will potentially be problematic, due to PPS having an incomplete set of PAR files for the month of December 2017, and explore options.

1.3 Related Projects & Dependencies

• Other related DART sub-projects identified by UCOP ITS:

o Provide UCPath Center with access to online PPS (Note: not just inquiry. This includes CICS and web.)

o Expense Transfer Processing

o Disable PPS features, jobs, etc.

o Provide support for future lump sums. Scenarios: lump sums that go against PPS and the location already on UCPath; lump sums that go against both PPS and UCPath; use of Flat files vs. DB2. Lump sums could be calculated using PPS data, but not paid out from PPS. Would need to pass the payment data over to UCPath.

o Provide access to archived data not available online.

o Migrate data from the mainframe

o Explore Interfaces: Which entities must be informed when output that they are used to receiving will no longer be received from PPS? E.g., PIN might be expecting output from RV, vendors, avidity, etc.

• Affordable Care Act standard and initial measurement and reporting processes

o There may be upcoming government-mandated changes to these programs.

• There is a need to closely coordinate Open Enrollment and other year-end activities between PPS and UCPath.


• SR100740 (R2157) – Include HSA Employer Contribution In CA Gross: An annual process generates DA transactions to add the YTD HSA employer contribution amount to the CA-taxable gross, if the employee has no out-of-state grosses or deductions (report as an exception otherwise). The DA transactions are processed in a compute. The DA transactions must be processed against the prior year/’frozen’ EDB before producing W-2s.

• Generate health cost dollar adjustment transactions for Box 12 DD on the W-2. The DA transactions must be processed against the prior year/’frozen’ EDB before producing W-2s.

• If the transition to UCPath is at the tax year boundary, then PPS will report the employer HSA contribution for the tax year on the W-2. For mid-year UCPath conversions, responsibility for this item will need to be determined. Note that it will have been recorded at the beginning of the year in PPS. It should not be reported by both PPS and UCPath.

• Need to discuss with UCPath – ask Christopher to make sure it is on UCPath list.

• In order to make sure critical year-end functions can be run, make sure PPS functions associated with Year-end are not “turned off” prematurely.

1.4 Stakeholders

Acronym Description Role * Authorize Has ultimate signing authority for any changes to the document

R Responsible Responsible for creating this document

A Accountable Accountable for accuracy of this document (e.g. project manager) S Supports Provides supporting services in the production of this document

C Consulted Provides input

I Informed Must be informed of any changes

Name Position * R A S C I Barbara Vanden Borre ITS Programmer/Analyst X X X Beth Burkart ITS Business Analyst X X Norm Flynn ITS Programmer/Analyst X X Stacey Johnson ITS Architecture, Design, And

Development Manager X

Shaun Ruiz Payroll Coordinator * X X X Gayelea Allison Production Director, UCPath * X X X


Center

1.5 Proposed Strategy

Identify the processes that need to be run in PPS at year end for locations that cutover during that year. Year end schedules for past years will serve as input.

Due to the current UCPath conversion schedule (pilot in end of 2017), the focus is on PPS to UCPath conversions that occur at year end. Depending on cutover timing, there will be different considerations when planning year end processing. For example, locations transitioning mid-year in future deployments will not need to be concerned with Open Enrollment processing in PPS, but they will still need to perform W-2 and Affordable Care Act reporting. It appears that running the ACA Standard Measurement process in November for locations that transitioned mid-year would not produce meaningful results because the full measurement period’s data would not be available.

Year end processing tasks that appear problematic due to lack of a full set of PAR files in PPS will be further explored, and any issues are being raised to the UCPath cutover team.

1.6 Glossary

Term Description UCOP University of California Office of the President UCPC UCPath Center ITS Information Technology Systems PPS Payroll/Personnel Systems DART PPS Data Archive, Retrieval and Transition EDB Employee Database contains demographic, employment, and payroll data for each

employee in the payroll system. PAR Payroll Audit Record Database contains data on employee earnings and deductions

from the compute cycles. ACA Affordable Care Act UI Unemployment Insurance


2 Product/Solution Scope

2.1 Included in Scope

• Determine which year end processes must be run for locations that transitioned to UCPath that tax year.

o Open Enrollment activities

o Tax year end activities

o Affordable Care Act related activities

• Determine:

o Which processes should be run solely in PPS

o Which processes should be run in both PPS and UCPath

o Which processes normally run in PPS should be run in UCPath instead

o Which processes require further analysis to determine how they should be handled

o If there are any new processes that need to be developed to support year end processing for transitioning locations. This could include handover of historical files needed by UCPath for startup. These needs should be coordinated with the UCPath Cutover team.

Examples: UCRS, Graduate Student History, Financial Aid Fiscal YTD

o If there are modifications to existing processes that are needed to support PPS year end processing for transitioning locations

2.2 Excluded from Scope

• Accuracy of data conversion from PPS to UCPath

• Creation of new processes to support the handoff of data from PPS to UCPath for Affordable Care Act compliance


2.3 Assumptions & Constraints

ID Assumption / Constraint 2.3.1 The year end inventory spreadsheet produced by this DART sub-project will include

only those tasks to be performed when the cutover is at a tax year break unless noted.

2.3.2 Some batch processing will still need to run after cutover, but not full monthly reporting. JCL and AJS (Automated Job Scheduler) modifications may be needed.

2.3.3 For locations transitioning to UCPath mid-year, the employees at those locations will receive two Form W-2s and two Form 1095-Cs. PPS will report for the months up to the cutover. Coordination is required to make sure all the months are accounted for and there is no double-counting.

2.3.4 UCPath has a plan for continuation of the ACA measurement processes following cutover. Per Sudhakar Kalpa (UCPath ACA technical contact): “We are converting service hours (average weekly hours of service) from the outcome reports off of PPS programs – PPP071 (SMP), and PPP072 (IMP). This would cover the SMP (Standard Measurement Process), and IMP (Initial Measurement Process) that would have run in PPS in the month of November, 2017.

A 14 month history of Payroll earnings balances for the ACA special accumulator, and Job/employment stack is also being converted so that E-383 will be able to process in December, 2017, and onwards, for those attaining their 1st anniversary in prior month of the month in which it is run.” (Initial Measurement)

2.3.5 Employees will need to pay the advance premiums effective Jan 1st, 2018 in BW cycles paying 12/13/17 and 12/27/17. Therefore there is a need to install OE, update advance rates, and process OE 1 transactions in PPS. Other OE transactions may be processed for contingency purposes (see below).

2.3.6 Apply Arrears Benefits Rates Updates: this step will be done in both PPS and UCPath, as part of contingency planning.

2.3.7 The second set of OE transactions, which are for Health FSA, DepCare FSA, and TIP changes, will be processed. This step normally takes place in December, after periodic maintenance to begin the new tax year, and before the first compute with a January check date. The current plan is to process the OE2 transactions in a non-production environment and then hand off the data to UCPath. Only MO or MO and BW? Depends on timing.

2.3.8 Process third set of OE transactions as needed for contingency. 2.3.9 Employees at transitioning site make OE selections in AYSO. 2.3.10 BRT (Benefits Rates Table) transactions for transitioning sites will be needed by PPS

and UCPath. 2.3.11 IVR interface questions, such as “At what point should PPIIVR cease to be run for

transitioning locations?” are being addressed by the DART Interface sub-project and will be included in the UCPath cutover plan.


2.3.12 4th quarter UI processing is included with year-end W-2 processing, unless the transition is in the middle of the quarter. UI processing for the other quarters is a separate process. If the transition to UCPath is at a quarter boundary, then PPS will do the UI processing for that quarter; otherwise, UCPath will do this. For locations transitioning at the tax year break, 4th Quarter UI (Unemployment Insurance) processing will be done by PPS.

2.3.13 There is a potential annual update of the employee-paid Post-Doctoral Scholar Supplemental Disability rate. This rate is stored as a G balance on the EDB for GTN 635. Locations may use any preferred method for updating the employee rates, such as manual update, batch EDB update with transactions generated by PPP060, or a preferred local process. This employee-paid Post-Doctoral Supplemental Disability rate should be updated after December Month End Reporting but prior to the first compute for January earnings. This will not be handled by PPS, but will be a UCPath responsibility.

2.3.14 The UCPath contingency plan is to use PPS to generate pay if necessary (if cutover is unsuccessful). PPS must be positioned correctly in case this occurs.

2.3.15 PPS will run the ACA initial measurement process for the last time in December 2017 (for Nov anniversaries).


2.4 Outstanding Items

ID Description

2.4.1 Will these processes need to be performed for a year-end cutover? They typically take place in December.

• 'Freeze' the EDB and CTL databases, i.e., take a backup of current data and load it into tax year-end databases.

• Load new year tax tables • Perform year-end periodic maintenance. Includes zeroing out YTD balances

and purging of employees who have been inactive for X amount of time. Answer: yes, per the team in the 4/20/17 DART meeting.

2.4.2 Responsibilities (PPS only, UCPath only, or both) need to be clarified for several items as identified in the DART Year End Inventory spreadsheet. (Norm) Examples:

• Financial Aid history file turnover • Graduate Student Remission file turnover

2.4.3 • Further analysis needed on: Generate ACA year end file for ACA web system. • December monthly reporting: ACA processing (PPP072, PPP073, PPP074) – TBD,

possibly PPS. (Norm) 2.4.4 Monthly periodic maintenance to begin a new month (should this continue while

expense transfers are occurring post-UCPath transition?) 9/20/17 This will be run in PPS to begin January. The 6 month period post transition is still unclear.

2.4.5 Update Post-Doc Supplemental Disability Rate (Early January, after Dec MR but prior to the first January earnings compute) – this would need to be done on the UCPath side. Assume: done in PPS also for contingency Ask Christopher to raise with UCPath to make sure they are aware.

2.4.6 Employees in locations transitioning to UCPath will need to go through open enrollment in AYSO if the cutover is occurring at year-end. What files (if any) does PPS need to give to UCPath to support the smooth transition of Open Enrollment? (Need to look at OE2 and 3 transactions) (Christopher)

2.4.7 For Affordable Care Act measurement and reporting processes, what handoffs are needed from PPS to UCPath? Are there any new interfaces? 9/20/17: resolved: Per conversation between Christopher and UCPath cutover team, no new interfaces are needed.


2.4.8 ACA Initial Measurement: analysis is needed to determine the last ACA initial measurement process that should be run in PPS. December for Nov anniversaries. (Yes, December for November anniversaries will be the last ACA Initial Measurement done in PPS.) For employees who will reach their one year anniversary during the first year after UCPath cutover, what data does PPS need to provide to UCPath so they will have the entire year of data? 9/20/17: Resolved: Hosted Apps discussed with UCPath Cutover team, who indicated that they are able to get all the information they need without PPS creating any new files.

2.4.9 Will UCPath need to do any ACA reporting (1095-C, 1094-C) for 2017 for transitioning locations, or will this be done only on the PPS side? Assume only PPS, not UCPath, based on pilot conversion timing.

2.4.10 Who will inform recipients of files that they will either receive 2 files (one from PPS, one from UCPath) for December data in some cases, or just one file from UCPath or just one file from PPS for others? (copied from Interface spreadsheet)

3 Business Services and Processes N/A

4 Business Rules N/A

5 Business Requirements

5.1 User Requirements Req ID Requirement Type Requirement Description Priority

[L/M/H] Comments

UR1 Tax Be able to perform the usual tax year-end processing for locations that transitioned to UCPath during the tax year.

H

UR2 UI Accurately report unemployment insurance (UI) tax information to the state for the 4th quarter of the

H


year. (Part of calendar year-end processing.)

UR3 Benefits Insure continuous and accurate benefits coverage and deductions. Make sure that PPS correctly deducts from December 2017 pay for any advance benefits for January 2018 for the BW population.

H Plans and rates must be correct. Employees should seamlessly transition to UCPath without impact on OE enrollments and ongoing benefits.

UR4 Interfaces Be able to accurately and timely create the last internal and external interface files of the year out of PPS (e.g., CPS, CONEXIS and other vendor files).

H

UR5 ACA Be able to produce 1095-C forms for ACA purposes out of PPS for the same months covered by the W-2. For years where two W-2s are produced (one from PPS, one from UCPath), the reporting period for the 1095-C forms should correspond to the reporting period for the W-2.

H Coordinate with UCPath in terms of who is to make sure all months are accounted for and none are double-reported. .


5.2 Functional Requirements

Req ID Requirement Type

Requirement Description Priority [L/M/H]

Comments

R0001 W-2 W-2 processing must be performed accurately and completely for the year of transition to UCPath. In order to support accurate W-2 processing, the unsubstantiated Health FSA claims files must be processed via PPP615, which creates Dollar Adjustment (DA) transactions file in the format of UPAY 649, for applying the input HFSA imputed income amount to the FICA YTD Gross, Medicare YTD Gross, and HFSA Unsubstantiated Claims depending on the FICA Eligibility Code of the employee. This processing is normally completed in advance of the other year-end steps. Some other key processes that impact the W-2 are: • Annual health insurance

reporting process: o PPP606 derives, collects,

and reports the health insurance costs for Box 12-DD for Form W-2. It creates a tab-delimited report file and a DA transaction file.

o Load YTD Health Insurance Costs from Non-PPS sources (including medical resident data) for Box 12 DD –GTN 607

• PPP607 to “Include HSA

H Some related GTNs are: • GTN605: YTD EAP • GTN606: YTD

Health PPS • GTN607: YTD

Insurance Non-PPS. Per the 2016 year end schedule, both PPP606 (health cost data) and PPP607 (adds HSA employer contributions to CA taxable gross) are intended to be run against the old tax year EDB (part of old year cleanup compute). Note that the Wellness component for Box 12 DD no longer exists.


Employer Contribution in CA Gross” (R2157). This process involves DA transactions that are processed in a compute.

• Other assorted dollar balance adjustments by campuses (done at various times, including year-end).

R0002 W-2, UI

(Unemployment Insurance)

W-2 and 4th quarter UI processing:

• PPS will create the W-2 and UI extract files (phase 1).

• Updating the W-2 extract file with more current demographic data (phase 2) is more complicated. More recent data will be in UCPath, not PPS, e.g., employment status and address. UCPath to provide data to PPS as input into this phase. This approach may require modifications to the existing PPS W-2 process, or run the EDB update process against a flat file provided by UCPath.

H For tax year-end cutovers: Report on full tax year for W-2 and all of 4th quarter UI. For all other cutovers: • W-2: Report on

partial year worked at campus.

• UI: o Quarter boundary

(Q1, Q2, Q3): PPS should do UI reporting.

o Other cutovers: UCPath should do UI reporting, because PPS will not have the full set of data.

New version of PPP610 may be needed.

R0003 State Tax Processing to Campus

Produce 4th quarter 'other state' tax reports for the locations.

H PPP884, run in December. This requires an entire quarter’s worth of data. There are no issues if the cutover is on the tax year boundary, which is the case for the planned December 2017 pilot. • Quarter boundary


(Q1, Q2, and Q3): PPS should do UI reporting.

• Other cutovers: UCPath should do UI reporting, because PPS will not have the full set of data.

R0004 998 exempt alien status

Form 8233 renewal of 998 exempt alien status: For cutovers at tax year boundary, reporting will be done only in November, December, and January.

H Spans Nov through Feb; multiple runs. There are no issues if the cutover is on the tax year boundary, which is the case for the planned December 2017 pilot. Cutovers in February could be problematic.

R0005 Tax Reporting Run old year cleanup computes to process campus, PPP606, and PPP607 dollar adjustments in preparation for tax reporting. These computes must not generate employee pay.

H This would be needed for both year-end cutovers and mid-year cutovers.

R0005 Tax Reporting Finalize tax YTD merged PAR file by adding data for old year cleanup computes.

H This would be needed for both year-end cutovers and mid-year cutovers, for later inquiry.

R0006 1042-S Perform 1042-S reporting (not the forms themselves) on request. All sites requiring this currently use Glacier, but some like the PPS extract file to be created for comparison.

H Needed for year-end cutover if requested by campus.

R0007 ACA – Standard Measurement

Affordable Care Act Measurement: • Standard Measurement may

need to be performed in PPS, depending on when the location cut over to UCPath. It should be performed for tax year-end cutovers, because the location was on PPS for the entire measurement period.

H Standard Measurement (PPP071) is run annually in November and only includes employees who have been at the location for at least a year.


R0008 ACA Standard

Measurement Process

The standard measurement process generates transactions to update the secondary BELI status qualifier code. The transactions are processed immediately. PPS should process these transactions for transitioning locations if the standard measurement process was run in PPS.

H

R0008A ACA Standard Measurement Process

The standard measurement process generates X1 transactions to update the assigned BELI. The transactions are processed in December, prior to the first December compute. Process the X1 transactions generated from the annual ACA Standard Measurement in PPS and provide the file to UCPath, if UCPath has already captured the transition data.

Offer letters? Coordination with UCPath is required.

R0009 ACA – Initial Measurement

Initial Measurement: analysis and coordination are needed to determine the last initial measurement process that should be run in PPS. For a tax year end transition, PPS should run the initial measurement in December for employees with November anniversaries, and apply the transactions. Depending on timing of the data capture for transition, PPS may need to provide the transaction files to UCPath as well. The January initial measurement for employees with December

H Initial measurement (PPP072) is run monthly and includes employees who had their one-year anniversary in the previous month.


anniversaries will need to be run in UCPath.

R0010 ACA – Annual Reporting on 1095-C and 1094-C

Affordable Care Act Tax Year Reporting for employees and IRS: • Reporting for the months up

to the cutover – careful coordination is needed with UCPath to avoid double reporting the month of conversion or missing the month of conversion. Transition is smoother if the cutover is at the tax year boundary.

• Generate ACA year end file for ACA web system. (Early January, after monthly reporting carrier file processing is completed.) This is for the purpose of collecting data to send to UnifyHR, the print and mail vendor.

H Assume only PPS is reporting for 2017 for the locations transitioning in the end of 2017. Data is sent to ACA Web application annually for this reporting. From ACA Web, data is sent to the print and mail vendor. Need to make sure PPS will have a complete picture of December 2016 coverage and offers (BELI) for transitioning locations.

R0011 Open Enrollment – benefit rates, OE transactions

For tax year-end cutovers, there will be a need to install OE, update rates, and process OE1 transactions as usual. To allow advance benefits for January 2018 to be paid out of BW PPS checks paid 12/13/17 and 12/27/17, the following processes will need to run in PPS for transitioning locations: - Monthly Maintenance to begin

December 2017 - Install OE release - Apply advance premiums table

updates - Run PPP570 (ADVC): Advance

Benefits only (‘ADVC’ in spec card) – Annual Benefit Premium Audit and process resulting transactions.

H Advance rate updates are needed if December pay will be generated from PPS where employees are paying for the next year’s benefits. This is the case for a year-end cutover, e.g. the 2017 year-end cutover, but not for a mid-year cutover. Usual timeframe to create the last regularly scheduled CONEXIS interface file of the year is December 15th or 16th. May be shifted earlier depending on when the site rolls forward to the new tax year.


- Process OE1 transactions (first set of OE plan enrollment transactions), to support enrollment in benefits effective Jan 1st and for advance premium payments in December pay cycles run in PPS.

- First December earnings compute (BW)

- Produce CONEXIS S2DEC17 (last two digits are the year) file

- Second December earnings compute (BW)

- Produce CONEXIS S3DEC17 (last two digits are the year) file: Last activity for the calendar year.

- 'Freeze' the EDB and CTL databases, i.e., take a backup of current data and load it into tax year-end databases.

- CTL Update: Apply Year-End updates. Tax table and OASDI updates.

- Perform year-end periodic maintenance. Includes zeroing out YTD balances and purging of employees who have been inactive for X amount of time.

For continuing HSA participants, generate and apply X1 transactions for the HSA employer contribution GTN 613 (for contingency purposes). D-balance and G-balance amounts are the same, which will result in a one-time, full year payment in the next (new tax year) compute for the employee. (PPP575). However, for transitioning locations, this payment should not be generated. The payment should occur on the UCPath side, so these transactions need to be provided to UCPath.

Create special final CONEXIS interface file for the tax year: Can be empty if no compute was run since the last regularly scheduled interface, but file must still be produced. Assume PPS to run PPP575 (HSA Contribution for continuing employees). UCPath might not have the data needed to run this, since it compares prior year’s HSA enrollment with new year’s HSA enrollment. There are contingency planning considerations.


R0012 Open Enrollment

Transfer employees out of obsolete insurance plans, if applicable, before the first December compute. (Employee did not select an alternative in OE.) (one-time process)

H The usual timeframe is Approximately December 7-10, after applying first set of OE transactions.

R0013 UCRS Payroll Reporting

This process will need to be run for December earnings: Create split UCRS Payroll Reporting MEM730 interface file: December computes with old tax year check dates (the first two BW in Dec 2017)

H Monthly process Dollars split out by tax year. Only run in PPS if December earnings are paid in PPS during the old tax year.

R0014 UCRS Interface Create split UCRS MEM730 interface file: January old year cleanup computes.

H Regardless of timing of transition to UCPath, because we will be doing tax processing at the end of the year.

R0015 ACA – monthly monitoring

Campus Monthly Monitoring – PPP073 Coordinate with UCPath about timing of the last run from PPS.

R0016 ACA – Campus Eligibility Report

PPS to run for last time for the last full earnings month processed. Then run by UCPath.

PPP074 For end of 2017 cutover (pilot), PPS to run for the last time for November.

R0017 High level processes were highlighted in the functional requirements. Please reference the DART year end inventory spreadsheet for more detailed requirements for year end processing.

5.3 Reporting Requirements N/A


6 Non-Functional Requirements N/A

7 External References

< List all other documents referenced in this document>

Document Location Author DART Year End Inventory

https://sp.ucop.edu/sites/its/apptech/ppers/basepps/PPSBusSpnc/2017/DART%202017/2%20-%20Year%20End%20Processing/SR101NNN_DART_Year_End_Processing_Inventory.xlsx

Barbara VandenBorre

Business Requirements Documentpayroll.ucop.edu/requirements/DART/SR101NNN_Year_End... ·...

Documents

Transcript of Business Requirements Documentpayroll.ucop.edu/requirements/DART/SR101NNN_Year_End... ·...