Issue
If your department submitted requests for one-time additional pay using a payroll one-time payment template between September 5 and October 2 or selected a chartstring override on an HBS timesheet for pay periods ending September 5 and September 19, salary expenses were charged to the employee’s position-level funding rather than the chartstring provided on the override. You can confirm this by running the MyReports Distribution of Payroll Expense Report.
Root Cause
The UCPath Center identified a defect with the application of funding distribution overrides during payroll processing. As a result, funding overrides sent on pay transactions were not applied, and salary and benefit expenses defaulted to position-level funding.
Resolution
The UCPath Center corrected the override defect on Monday, October 5, and is in the process of correcting all impacted transactions via a mass update.
UPDATE: February 9, 2021
The UCPath Center initiated processing for a mass cost transfer on January 27, 2021. The UCPath Center encountered an error that caused the loading of transactions to the General Ledger to fail. The revised target resolution date is February 13. Prior to the start of processing the UCPath Center alerted UCSF that they will not include October activity, consisting primarily of QDP payments, in this round of processing. We are expecting the mass cost transfer will include the transfer of September activity.
UPDATE: February 22, 2021
The salary cost transfer lines are now posted for this correction; two unique SCT IDs were used for the transfers: FAUSFCMP200905B2X95128 and FAUSFCMP200919B3X919128. Still pending are the transfers for September and October off-cycles.
Mitigation Plan
We recommend that departments wait for the UCPath Center to complete the mass correction process. However, as a timeline has not been finalized, departments may proceed with salary cost transfers to make the corrections they are comfortable making or need updated most urgently.
If you have questions or need assistance determining whether a transaction that posted is impacted by this defect, contact the Controller's Office Solution Center .