This page lists known issues with UCPath and UCPath online that have significant impact on the UCSF community. All resolved and unresolved known issues are displayed below.
Performance issue affecting direct retro and funding entry pages
Issue
UCPath identified an issue with the real-time funding validation process between UCPath and Locations. As a result, users may experience an intermittent performance issue with Direct Retro and Funding Entry pages.
Mitigation
The UCPath Center implemented a workaround to alleviate the intermittent performance issue with Direct Retro and Funding Entry pages. UCPath is actively working to resolve the issue and will provide additional information as soon as it becomes available.
If you continue to experience delays or issues, please contact the Controller’s Office Solution Center.
Direct Retro Salary Cap/MCOP Funding Worksheet Error: New Data is not 100%
Issue
Users receive the following message on the Direct Retro Salary Cap/MCOP Funding Worksheet and are unable to complete their direct retro:
Effort % by earnings code for ‘New Data’ is not 100%, Use DR Distribution Worksheet to correct the Effort %.
While this error message is valid when adjustments legitimately do not add up to the original effort percentage, some users are encountering this message when they have made no changes to the original transaction lines.
Root Cause
This error is related to prior defects that impacted the data integrity of the source and is most often encountered when trying to transfer expenses on paychecks that occurred prior to 2021. You may also encounter this issue on paychecks on which a Mass Leave Correction (MLC) has occurred.
Mitigation
If you receive this error, confirm if the sum of the effort percent in the Old Data section is not 100%:
- Click the spreadsheet icon to download the old data table to Excel.
- In Excel, sum the “Percent of Effort” column.
If the percent of effort does not equal to 100% then you are experiencing this issue. You will need to complete an accrual journal using Source Code 549 for invoice reporting or a financial journal using Source Code 547.
Inaccurate Percent of Effort on the Distribution of Payroll Expense Report for salary cost transfers onto capped funding sources (UPDATED)
Issue
The Percent of Effort displayed in the Distribution of Payroll Expense (DPE) Report does not accurately reflect the percent of effort for some earnings distribution lines resulting from salary cost transfers onto capped funding sources. Earnings Amounts and Percent of Pay are accurately reflected in the DPE.
Root Cause
The incorrect calculations are being generated in UCPath and are due to an upstream defect in the General Ledger data. This issue is under investigation by the UCPath Center.
Mitigation Plan
To manually calculate the correct effort percent for each capped funding source, sum the N-OTC Percent of Pay and the Y-OTC Percent of Pay on the earnings distribution lines for the funding source. For example, adding the Percent of Pay from the N-OTC001 up to the cap distribution line to the Percent of Pay from the corresponding Y-OTC001 over the cap distribution line will equal the Percent of Effort for the capped funding source indicated on the N-OTC001 distribution line.
If you need further assistance, contact the Controller’s Office Solution Center.
Issue Status
Update: February 2023
The UCPath Center is working to correct the derived effort percent calculations that we receive on the Labor Ledger and which appear on the Distribution of Payroll Expense (DPE). The target release date is March 2023.
Incorrect Annual and Prorated Annual Cap Rate warning message on Direct Retro page for employees with reduced FTE (UPDATED)
Issue
Transactors receive the following warning message when entering the Direct Retro MCOP worksheet from within the Direct Retro online page:
Incorrect Annual & Prorated Annual CAP RATE for Cap_Type: (32008,575)
To correct “prorated annual & monthly” cap rates, please updated “annual cap rate” in new “Data Section”.
This warning message notifies transactors to reset the cap rate values within the Direct Retro MCOP worksheet “New Data” section because the system is unable to calculate the correct values.
Mitigation Plan
Manually reset the cap rate value for each distribution line in the “New Data” section:
- Clear out the existing annual cap rate value. The value may appear as an inflated dollar amount.
- Update the annual cap rate value based on the employee’s compensation and pay group:
- If the employee’s annualized salary at 1.0 FTE is below the annual cap rate OR the employee is an hourly employee, leave the annual cap rate field blank.
- If the employee’s annualized salary at 1.0 FTE is over the annual cap rate, reenter the correct annualized cap rate by selecting from the drop down list.
- Confirm that the prorated monthly cap rate field recalculates a monthly capped dollar amount based on the employee’s reduced FTE.
After completing the steps above, continue to enter effort percent changes to individual distribution lines. If you need further assistance, contact the Controller’s Office Solution Center.
Issue Status
Update: February 2023
The UCPath Center now plans to address this defect in production prior to the SCT Redesign release. The targeted release date is March 2023.
Department default chartstrings with non-posting level Dept ID (UPDATED)
Issue
44 unique departments (428 positions) are currently setup on the main funding entry page with a default chartstring that includes a Dept ID not at posting level. As a result, any payroll expenses recorded to these default chartstrings will not pass edit and will go to suspense rather than being easily visible in enterprise reports for departments to correct.
Root Cause
In PPS, Home Department could be established at a non-posting level causing the issue with resulting default chartstrings established for these Dept IDs at go-live. The correct posting level Dept ID could not be determined during conversion.
Mitigation Plan
Following the posting of suspended payroll to the suspense account, the Payroll Office will reach out to identify a posting level Dept ID to use to move payroll suspended on Project “2222222” and a non-posting Dept ID. To keep the General Ledger and Distribution of Payroll Expense (DPE) in sync, departments must move salary and benefits in suspense using a salary cost transfer. Outlined in the August 2020 Controller's Office Newsletter are the steps required to move payroll that posts to the suspense account.
Long-term Resolution
Update: February 2023
UCSF Payroll submitted Dept ID edits to UCPath in January; the UCPath Center time to resolve is currently targeted for the end of February 2023.
Update: December 2022
In October, we discovered additional configuration updates that are required to remove non-posting department ids from our UCPath configuration. The Payroll office is working to update the configuration and aims to complete this activity by January 2023. We apologize that this was not completed in full during our initial updates earlier this year and in 2021 and that users are continuing to experience downstream issues as a result.
Update: March 2022
In April 2021, the Payroll Office submitted a mass funding entry update to replace 938 invalid chartstrings set up in UCPath on the department default page. UCSF is awaiting a configutation update by the UCPath Center to ensure that all default chartstrings have posting-level Dept IDs.
VAC for HSCP Faculty incorrectly distributed to default funding (RESOLVED)
Issue
Beginning in the January 2021 accounting period, vacation and other leave taken for some members of the Health Sciences Compensation Plan (HSCP) were charged to the default distribution established using the blank/catch-all chartstring (often times indicated using Project ID 2222222) instead of to the distributions established for HSR/HSP/HSN components of pay.
In addition, salary offsets for the leave earnings were applied only against HSR earnings and not distributed across funding for all components of pay.
Root Cause
Several defects have been identified in the Prior Period Leave Redistribution program since it was implemented in January 2021. Although it works well for most employees (single position and funding source), these defects are exacerbated when an employee has multiple positions or components of pay.
For Health Sciences Compensation Plan (HSCP) faculty whose funding was entered using the Salary Cap/MCOP Funding Worksheet:
- Their positions were skipped during the prior period leave redistribution process and leave transactions on the paycheck were charged to the blank/catch-all chartstring established on the MCOP Funding Worksheet.
- In addition, salary offsets for “REG-like” earnings were applied only against HSR earnings and were not distributed across funding for all components (HSN and HSP) of pay.
It is important to note that these issues affect the financial recording of pay and leave but not the amount of pay or leave for the employee.
Issue Status
Update November 9, 2022
The Enhanced MLC development was moved to production at the end of October 2022, and the UCPath Center immediately began running the program. Below is a schedule of when the MLC will run to correct transactions skipped by the Paid Leave Redistribution program between January 2021 and February 2022. These transactions are identified on the Distribution of Payroll Expense (DPE) Report with a Direct Retro ID value beginning with “MLC”.
| MLC Run Dates | Months Correcting | Run ID |
|---|---|---|
|
Nov 5-6, 2022 |
Jan 2021 through Mar 2021 |
221130M0X |
|
Nov 19-20, 2022 |
Apr 2021 through May 2021 |
221130M0X |
|
Dec 3-4, 2022 |
Jun 2021 through Jul 2021 |
221231M0X |
|
Dec 10-11, 2022 |
Aug 2021 through Oct 2021 |
221231M0X |
|
Dec 17-18, 2022 |
Nov 2021 through Feb 2022 |
221231M0X |
Update October 13, 2022
The development on the Enhanced MLC is on target to complete October 2022. Locations are reviewing the fixes for the identified defects and will provide sign-off by the end of the month.The participating locations will then be scheduled for MLC runs between November 2022 and January 2023. We will provide additional updates once we know where UCSF has been placed in the schedule.
In July of 2021, the UCPath Center ran a Mass Leave Correction (MLC) to correct the way that leave was distributed across funding for pay end dates between March and June 2021. March corrections posted to the July 2021 UCSF General Ledger, and April through June corrections posted to the August 2021 UCSF General Ledger. These transactions are identified on the Distribution of Payroll Expense (DPE) Report with a Direct Retro ID value beginning with “MLC”. In some cases, the MLC corrections resulted in incorrect adjustments moving salary across earning dates and incorrect effort percentage calculations. We anticipate this month that we will receive corrections to this MLC run. The transaction with the incorrect Earnings End Date will be reversed an will be replaced with a transaction containing the correct Earnings End Date. This correction may still result in incorrect hours or effort percentages when summarizing by Earnings End Date.
Update August 11, 2022
Development is underway to fix the last identified defect which impacts the effort percentage on the Mass Leave Correction (MLC) transaction lines. We expect the UCPath Center to complete development by mid-August, after which location user acceptance testing can continue.
Update July 12, 2022
The Mass Leave Correction (MLC) continues to be delayed in order to resolve the identified defects. The UCPath Center has developed corrections for 4 of 5 identified defects. As a next step, UCSF and other participating UC locations will revalidate the results. Once campus locations agree to the new results, the MLC processing will be scheduled and a timeline communicated. It is our best estimate that the MLC will run no sooner than mid-August.
Update June 6, 2022
The UCPath Center delayed the timeline for running the Mass Leave Correction (MLC) process originally scheduled to be completed before fiscal year-end. Testing of the improved MLC process with campus locations in May 2022 identified unresolved defects that require correction, including:
- The processing of checks that do not require any correction to the leave distribution and offset lines
- The assignment of incorrect earnings period end dates to distribution lines resulting in total earnings for an earnings period to become inflated (over 100% effort) or deflated (less than 100% effort) on the Distribution of Payroll Expense (DPE) reports
Campus locations agreed to delay the MLC process until these defects are resolved by the UCPath Center. A timeline will be communicated once available.
Update May 10, 2022
At the end of March 2022, the UCPath Center implemented the last in a series of improvements to the Prior Period Leave Redistribution program aimed at eliminating the programmatic defects we have experienced with leave redistribution since January 2021. As a result of these improvements, there has been a dramatic decrease in the number of skipped positions. March 2022 monthly payroll processing resulted in only 16 faculty positions skipped. While some circumstances will always result in skipped positions, we consider this defect to be resolved for future payroll processing.
In order to determine how to correct leave transactions already recorded in the General Ledger, department finance managers and UCPath transactors need to review positions skipped by the leave redistribution process and identify transactions to be corrected. Paychecks with incorrect leave distribution and salary offsets can be corrected in two ways:
- Manual correction using a salary cost transfer (Direct Retro)
- Automated correction by the UCPath Center using the Mass Leave Correction (MLC) process
A subcommittee of the UCSF UCPath Customer Advisory Board has developed guidance and reports to help UCPath transactors and department finance managers identify leave transactions that require correction and determine whether to make a manual correction or wait for the Mass Leave Correction process. This guidance was emailed to current UCPath salary cost transactors on May 10, 2022 and reviewed during the May 11 office hours session.
- Review the guidance document (MyAccess login required)
- Watch a recording of the May 11, 2022 office hours session (MyAccess login required)
If you need further assistance, contact the Controller’s Office Solution Center .
Users not able to submit salary cost transfers for paychecks distributed to non-posting Dept IDs
Issue
Salary cost transfers for paychecks with earnings distributed to a non-posting Dept ID do not pass validation. In the New Data section, earning detail lines with a non-posting Dept ID will appear with a $0 New Earnings Amount. Users are not able to override these lines to remove the non-posting Dept ID. As a result, they are unable to submit the Direct Retro transaction.
Root Cause
UCPath is functioning as expected. The issue stems from an existing known issue with department default chartstrings set to non-posting Dept IDs. A correction is in progress to remove non-posting Dept IDs from UCSF’s department default funding configuration.
Mitigation Plan
Users will not be able to complete a salary cost transfer in UCPath. Submit the transfer via an accrual journal using Source Code 549 for invoice reporting or via a financial journal using Source Code 547.
Position data difference between original earning lines and transferred lines
Issue
Original paycheck lines recorded on one position are posting to a different position for the same employee when a salary cost transfer is processed in a subsequent month. Typically, this occurs when the employee has changed positions; we would not expect a change in positions to impact salaries that have already posted.
Chartstring distributions and amounts are recorded correctly; however, this can create a reconciliation issue for financial data users.
Root Cause
This issue us under investigation by the UCPath Center.
Salary Cost Transfer Performance Issues for Transactions with More Than 300 Distribution Lines (UPDATED)
Issue
Users may experience an error or timeout when submitting salary cost transfers containing more than 100 earnings distribution lines.
Root Cause
A bug in the UCPath portal has been identified.
Mitigation Plan
If you need to reflect the salary cost transfer for financial reporting purposes, please see Payroll Accrual Guidance for Final Financial and Invoice Reporting.
Issue Status
Update August 12, 2022
This issue remains unresolved. The UCPath Center believes this issue will be resolved as part of system changes with the Salary Cost Transfer (SCT) Redesign project. Due to current resource constraints and the timing of the SCT Redesign project, testing to confirm a resolution of this defect will be incorporated into the overall test plan for the SCT Redesign (scheduled to go live in March 2023).
Update July 12, 2022
Transactors continue to experience timeouts in UCPath resulting in an inability to submit salary cost transfers when there are more than 300 distribution lines. After several attempts, the UCPath Center has not identified a resolution and continues to investigate options. Please open a case with the Controller's Office Solution Center if you encounter this issue so that we can track for resolution as part of the defect. Options to mitigate this issue continue to be to complete an accrual journal using Source Code 549 for invoice reporting or a financial journal using Source Code 547.
Update April 20, 2022
The original March target resolution date was missed. A fix for this defect is scheduled for release in June 2022.
Global Search icons missing in some web browsers
Issue
Depending on your web browser version, search results after performing a Global Search may be missing the image icon used to represent the page's document type. Global Search is a feature of the PeopleSoft Fluid User Interface (UI) for users with tranactor or inquiry roles.
Root Cause
This production defect was identified as part of the October 15, 2022 implementation of the Fluid UI. It will be addressed by the UCPath Center in a future upgrade or fix.
Unexpected increase in chartstring validation errors during August 2022 payroll processing (RESOLVED)
Issue
During the month of August 2022, we observed a higher than normal volume of chartstring validation errors during payroll processing, including examples where payroll transactions with valid UCSF chartstrings went to suspense.
Root Cause
The Controller’s Office is working with IT to investigate a potential issue with the chartstring validation process.
Issue Status
The identified increase was found to be attributable to valid chartstring combo edit errors. Payroll recorded to a department default chartstring must be corrected using a salary cost transfer. For additional assistance please see our reference guide: Understanding Department Default and Catch-All Funding Sources .
System defects resulting from the ‘Redistribution of Prior Period Leave Usage’ enhancement delivered in January 2021 (RESOLVED)
Issue
As announced in the February 2021 Controller’s Office Newsletter, UCPath delivered an enhancement to redistribute prior period leave transactions using the funding source in effect on the earnings end date of the leave transaction recorded in HBS. UCSF has identified several defects related to Salary Cost Transfers as a result of this new functionality.
The items listed below have been reported to the UCPath Center:
- The N-OTC indicator is no longer unique to only one chartstring on the Direct Retro Salary Cap / MCOP Funding worksheet. For example, you may see the N-OTC001 up-to-the-cap identifier attached to two different chartstrings in the Direct Retro MCOP Worksheet.
As a result, when moving from the Direct Retro Salary Cap / MCOP Funding worksheet to the Preview page, the system is mixing up the fund and award values between distribution lines and creating an invalid chartstring combination on the Direct Retro Preview Page. Most likely users will receive a combo/edit error, but may not depending on what fund-project combination UCPath derives. - When moving from the Direct Retro Salary Cap / MCOP Funding Worksheet to the Preview page, the system is not retaining the correct percent of effort and earnings amounts for the Y-OTC distribution lines.
In some cases, the system is also incorrectly calculating the new data amounts (e.g., displaying a negative percent of effort with positive earnings amounts or inflated Y-OTC earnings amounts when compared to percent of pay). - When moving from the Direct Retro Salary Cap / MCOP Funding MCOP Worksheet to the Preview page, the system is miscalculating the total percent of pay and/or percent of effort. Users will receive the error that the % of effort exceeds 100% or the new data % of effort does not match the old data % of effort.
If you encounter these errors you can confirm this issue by extracting the Preview page results to Excel and summing the Percent of Pay column and Percent of Effort column. If either column exceeds 100%, please open a ticket with the Controller’s Office Solution Center for further assistance.
Root Cause
Defects with UCPath.
Mitigation Plan
Update: April 1, 2021
Due to these defects, we have made the decision to remove UCSF from the enhanced process. We are working with the UCPath Center to address all defects related to this enhancement and hope to opt back into the process once they are resolved.
UCSF will be removed from the enhanced process as of the March 2021 monthly pay cycle. When performing salary cost transfers for paychecks issued on or after March 1, transactions in the Earnings details section will resemble transactions posted in December and prior months.
Salary Cost Transfer Initiators and Approvers will continue to see January and February paychecks distributed with the enhanced redistribution lines, including leave reported by day and negative offsets of the reg-like earnings. As a result, Salary Cost Transfer Initiators may continue to experience the reported defects when transferring distribution lines for these paychecks.
Please continue to review salary cost transfers for January and February closely and report any occurrence of the reported defects to the Controller’s Office Solution Center. For further guidance on managing salary cost transfers for January and February paychecks, watch a thirteen-minute recording from a recent office hours session (MyAccess login required).
Issue Status
Update October 13, 2022
The UCPath Center moved a resolution into production in September.
Update September 13, 2022
This issue was originally resolved in August 2021. The defect where the system is mixing up fund and award values between distribution lines and creating an invalid chartstring combination reappeared after the UCPath Center recently made system changes. It will be resolved this month.
Inconsistency in chartstring validation results
Issue
We are investigating reports of inconsistent chartstring validation results during salary cost transfer submission and General Ledger processing. Transactors are reporting the following conditions:
- Earnings distributions containing Projects with expired Activity Periods are passing validation during General Ledger processing and posting without going to the department default distribution or to suspense. However, when a salary cost transfer is initiated on a paycheck containing the same Award, the distribution line is encountering a combo edit error as a result of the expired Project Activity Period.
- Earnings distributions containing Projects that have ended are automatically charged to the department default chartstring, even when the processing end date in RAS has not been reached. This is being observed as a change in how payroll was being diverted to the department default chartstring prior to March.
Root Cause
The cause of this issue has been identified to be related to the change we made locally to the chartstring validation rules in February . Prior to the most recent change, if UCPath sent UCSF an earnings end date or period end date that did not correspond to an activity period, the ‘last’ activity period was used. The chartstring validation rule was updated in February to only assign an activity period if the date fell within an established activity period begin and date for the project.
Issue Status
Update May 11, 2022
New chartstring validation rules will be moved into production the evening of May 11. IT will update the logic to maintain the new flexibility, while accounting for the fact that the validation edit should allow for post award spending and corrections.
UCPath combo/edit validation error
Issue
UCPath Funding Entry and Salary Cost Transfer Initiators and Approvers are encountering a combo/edit validation error with the message, "Combination Code Validation Failed with reason:Communication Error."
Users will not be able to save, submit, or approve transactions until this issue is resolved.
Issue Status
Update May 10, 2022
This issue is resolved. If you experience any further errors, contact the Controller’s Office Solution Center .
Funding Entry Inquiry page is not displaying correct compensation data snapshot
Issue
In some cases, the Compensation Data Snapshot display in the Salary Cap / MCOP Funding Worksheet page within Funding Entry Inquiry does not match the correct employee monthly salary for the funding entry transaction submitted. This is a display issue that only pertains to the Funding Entry Inquiry page.
Root Cause
The UCPath IT team is currently investigating this issue.
Mitigation Plan
Until this issue is resolved, use the following alternative pages to view compensation data for completed funding entry transactions:
- Within the Funding Entry Inquiry page, the Funding Distribution Worksheet continues to display the correct the monthly salary amount for the transaction submitted.
- The Funding Entry > Find an Existing Value page continues to display the correct Compensation Data Snapshot details associated with the approved funding entry transaction.
Issue Status
Update May 2, 2022
This issue is resolved. The Compensation Data Snapshot was updated to display the most recent Job Data compensation effective for the “As of Date”. In cases where an employee has more than one effective dated salary increases on the same day, the last compensation update made effective on that day will be displayed when viewing the page.
Incorrect effort percent on leave expenses and offsets
Issue
When reviewing vacation (or other leave earnings) expense lines and corresponding “Reg-like” offsetting lines in the Distribution of Payroll Expense (DPE) reports, the calculations for Percent of Pay and Percent of Effort are not accurate as provided by UCPath. For these specific lines, data in the DPE do not match the valid calculations within the Direct Retro page in UCPath online.
Mitigation Plan
If a check has been skipped by the Vacation Leave Redistribution process, please use the Paid Leave Redistribution worksheet when making corrections to leave earnings distributions. This worksheet will correctly derive effort percent calculations to match the Direct Retro page.
If you need further assistance with corrections to checks with vacation/leave earnings, contact the Controller’s Office Solution Center.
Issue Status
This error has been reported to the UCPath Center and is currently under investigation.
Hours and effort percent for vacation earnings codes and corresponding offsets do not match (UPDATED)
Issue
A new defect appeared in the October 2021 monthly labor ledger where vacation (or other leave earnings) distribution lines and corresponding “Reg-like” offsetting lines do not have equal and opposite hours and effort percent, as expected.
As an example, the distribution of 8 hours of VAC earnings to a chartstring are expected to result in -8 hours of REG earnings to the same chartstring. The debit and credit for effort percent should also be equal and opposite. This defect is causing the “Reg-like” offset hours and effort percent to be slightly different. In this example, when reporting 8 hours of VAC earnings, the offsetting hours for REG are not equal to -8.
When running the Distribution of Payroll Expense Report (DPE) by earnings end date, the effort percent and hours will be slightly off, and totals are not accurate. Paycheck amounts are not impacted.
Update December 15, 2021
This defect is also impacting the on-cycle total hours and effort percentages for the same population of checks that have the paid leave reported and incorrect offsetting lines.
If an MCOP employee was skipped by the prior period leave redistribution process you will not encounter this defect. If an employee’s leave was distributed correctly by the prior period leave redistribution process you will see the incorrect hours and effort percentages on the DPE.
Mitigation Plan
If the defect is present, use the amounts shown on the Salary Cap/MCOP Worksheet to determine the transfer amounts, rather than the DPE.
Resolution
Update March 31, 2022
The defect was partially resolved with the posting of the February labor ledger, reducing by 80% the number of incorrect leave offset transaction lines. This issue is expected to be fully resolved with the posting of the March labor ledger. The effort to clean up historical transactions on the October 2021 through February 2022 labor ledgers is still under analysis by the UCPath Center and is not yet scheduled for release.
Extra distribution lines with zero dollar amount in Direct Retro Old Data and New Data sections (UPDATED)
Issue
When processing a new Direct Retro transaction, the Old Data and New Data sections of the Direct Retro page contain extra distribution lines with zero dollar amounts.
Mitigation Plan
Update March 1, 2022
It was originally recommended that transactors delete these additional lines from the New Data section on the Main Direct Retro page before the submission and approval of the transaction. When working within the Direct Retro Salary Cap/MCOP Worksheet, the transactor will not be able to delete these additional lines.
Users are reporting that lines cannot be deleted and they are encountering a hard stop on submitting the transaction. The UCPath Center confirmed that deleting the lines is no longer available because it was causing larger downstream technical issues. There is currently no workaround on the page for this issue.
If you need to reflect the salary cost transfer for financial reporting purposes, please see Payroll Accrual Guidance for Final Financial and Invoice Reporting.
Update March 31, 2022
The UCPath Center implemented a partial solution that allows editing of the chartfields on the zero dollar gross distributions lines. Review additional details in the Resolution section below.
Resolution
Update March 31, 2022
At the end of March, the UCPath Center implemented a partial solution that:
- Prevents the creation of zero gross distribution lines in one of the programs creating the lines
- Allows editing of the chartfields on the zero dollar gross distributions lines
Now when Salary Cost Transfer Initiators encounter an invalid chartstring (Invalid Combo Code) error on a zero dollar gross distribution line, they should update the chartstring to any valid chartstring combination. The transaction will pass validation, and the user will be able to submit their transaction. No expenses will post to the General Ledger for the valid chartstring used on the zero dollar gross distribution line.
A long-term fix that permanently prevents the creation of the zero gross distribution lines is still under analysis by the UCPath Center and is not yet scheduled for release.
Funding entry and direct retro limitations using Funds 4300 and 4301 (RESOLVED)
Issue
Funding Entry Initiators and Salary Cost Transfer Initiators receive an error when creating funding distribution lines using Funds 4300 and 4301 in the following cases:
Case 1. When setting up Z-payments to fund flat dollar amounts, users receive the error message: Z payments can only be distributed to compensation plan funds.
Root Cause
UCPath has been configured with an error message that will prevent Funding Entry Initiators and Salary Cost Transfer Initiators from entering funding distributions for Z payments using a sponsored Fund or Project. The configuration is in compliance with UCOP Policy AM-P196-37: Payroll: Health Sciences Compensation. See Section VII of the policy, Charges to Extramural Funds.
Resolution
The error configuration is working as designed. Read more about this announcement on the Controller's Office website.
Case 2. When setting up over the cap (OTC-Y) funding, users receive the error message: Over The Cap cannot be distributed to capped federal or federal flow through funds.
Root Cause
UCPath restricts the use of sponsored projects as a funding source for over-the-cap salary. In order for a cost to be directly charged to a project, it must be identified as benefiting the project that is paying for that cost. Over-the-cap salary cannot be charged to any other contract or grant fund because it is not benefiting any other sponsored project but the project where the salary cap is imposed. It will not pass the “benefit test” referenced in the UCOP Contract and Grant Manual for 6-500 Allowability of Costs or 6-532 Allocable Costs.
Resolution
UCPath will return the error for both funding entry and salary cost transfer transactions. If you feel that a private sponsored fund does allow for the charging of over-the-cap salary from a federally sponsored award, please submit support from the award that specifically confirms the allowability of these costs to CGA Compliance to [email protected].
Accruals for monthly employees on Paid Family Care Bonding Leave (RESOLVED)
Issue
UCPath has identified an issue with monthly employees not accruing hours with earn code “PFL" that are on Paid Family Care Bonding Leave (PFCB).
Resolution
All updates were completed in October, 2021. It is not necessary to submit any requests for accrual updates as these were updated as part of the resolution.
Incorrect benefits eligibility assignments for employees with multiple jobs (RESOLVED)
Issue
Benefits are incorrectly assigned in some cases where an employee holds multiple jobs.
Root Cause
This issue is occurring during the primary job setup and benefits eligibility process in UCPath.
Mitigation Plan
Employees whose benefits are incorrectly assigned should use the Ask a Question feature in PeopleConnect to submit a case to HR/Benefits.
Resolution
UCPath updated the primary job setup and benefits eligibility program.
Salary cost transfer exceptional approval routing issues (RESOLVED)
Issue
Cases have been identified where salary cost transfers meeting high-risk criteria were not routed in UCPath to Contracts & Grants Accounting (CGA) for exceptional approval. Additional cases have been identified where transactions routed for exceptional approval by CGA did not qualify as high-risk transactions.
Root Cause
The UCPath Center identified that project information was not correctly referenced for UCSF in the salary cost transfer program.
Mitigation Plan
Salary Cost Transfer Initiators should continue to follow all Late Cost Transfer guidance. CGA Compliance is monitoring transactions and will escalate when routing is incorrect.
Resolution
This issue is resolved.
HCOMP retro pay adjustments prior to conversion cannot be processed (RESOLVED)
Issue
HCOMP retro pay adjustments with effective dates prior to the conversion to UCPath (prior to May 1, 2020) cannot be processed in UCPath.
Root Cause
UCPath is not configured to process retro pay prior to conversion for HCOMP Faculty.
Mitigation Plan
UCSF was able to process some transactions in PPS; however, PPS is no longer available to process approximately 30 remaining cases.
Resolution
The final remaining batch of backlogged transactions was processed by the UCPath Center. A business process has been established with the UCPath Center to process the HCOMP retro requests.
Salary cost transfers result in arbitrary moving of earnings to a different earnings period (RESOLVED)
Issue
During processing of some salary cost transfers, UCPath is arbitrarily moving earnings from the recorded earnings period to a different earnings period. This results in effort percents that do not sum to 100 percent on the Distribution of Payroll Expense (DPE) reports.
Mitigation Plan
Departments should review salary cost transfer results by earnings end date on the Distribution of Payroll Expense (DPE) report. If you encounter this issue, please contact the Controller's Office Solution Center to open a ServiceNow ticket.
Resolution
A defect fix was implemented by the UCPath Center to resolve this issue.
Funding entry error: "The position entered is not eligible for budget definition within the specified begin date..." (RESOLVED)
Issue
During funding entry, Funding Entry Initiators receive a message indicating that "the position entered is not eligible for budget definition within the specified begin date." Initiators are unable to save and submit funding.
Root Cause
Errors during budget data loads may result in missing budget data for specific positions. Funding cannot be entered when corresponding budget year data are missing.
Resolution
If Funding Entry Initiators experience this issue in the future, log a ticket with the Controller's Office Solution Center for further assistance with this issue.
General Ledger discrepancy: VLA relief does not match vacation salary expense (RESOLVED)
Issue
In some cases, users are seeing a discrepancy between the total vacation salary expense being reported in a pay period and the total vacation relief credits. This issue is being observed in the Distribution of Payroll Expense (DPE) reports and all financial reports that source data from the General Ledger.
Root Cause
The UCPath labor ledger contains vacation salary expense lines marked as "do not post"; as a result, these lines are not being included in the payroll journal. The corresponding vacation leave assessment (VLA) relief credits are marked "ready to post" and are included in the payroll journal.
Resolution
Read more details and the planned resolution on the Controller's Office website.
Approved salary cost transfers have not posted to the General Ledger (RESOLVED)
Issue
Several salary cost transfers were not processed as part of our local payroll journal creation process. As a result, transactions also do not appear in MyReports.
Review a list of identified transactions by Direct Retro (DR) number in UCSF Box (MyAccess login required).
Resolution
This issue has been resolved. Direct retro transaction lines are available in the Distribution of Payroll Expense (DPE) report. Contact the Controller's Office Solution Center if you are still experiencing this issue.
Direct retro distribution lines processed in early December have not posted to the General Ledger (RESOLVED)
Issue
A number of direct retro distribution lines processed by UCPath in early December have not yet posted to UCSF’s General Ledger due to a technical error in UCPath. These lines do not appear on the Distribution of Payroll Expense reports or the Transaction Detail Report. Two scenarios exist:
- Some direct retro distribution lines have posted while the remainder of the lines for the same transaction are still pending.
- The complete direct retro transaction has not yet posted.
Review a list of identified transactions by Direct Retro (DR) number in UCSF Box (MyAccess login required).The UCPath Center is working to identify additional direct retro distribution lines impacted by this issue, after which the list of impacted direct retro transactions will be updated.
Resolution
This issue has been resolved. Direct retro transaction lines will be available in the Distribution of Payroll Expense (DPE) report on December 23, 2021. Contact the Controller's Office Solution Center if you are still experiencing this issue.
Direct retros reported as missing from DPE and GL reports
Issue
Direct retros completed in UCPath with a process date of 10/4/21 and 10/6/21 appear in the Distribution of Payroll Expense (DPE) and General Ledger reports with missing "Activity Period", "Pay Period End Date", "Paycheck Date" and "Direct Retro ID". As a result, users are unable to find these transactions when filtering reports using the above criteria.
Root Cause
The UCPath labor ledger was delivered to locations on Wednesday, October 6 with data discrepancies that were not resolved until Monday, October 13. The UCSF payroll journal and subsidiary reports were created prior to the discovery of the data discrepancies, resulting in the issue we are now seeing on the DPE and General Ledger. This issue impacts over 600 direct retros that were included in these runs.
Resolution
The UCPath labor ledger data was corrected on October 13. The MyReports team has reloaded the DPE reports and is working to reload additional reports sourced from labor ledger data.
Changes to CBRs in MyReports DPE Report (RESOLVED)
Issue
The MyReports Distribution of Payroll Expense (DPE) Report currently displays Composite Benefit Rate (CBR) % only for the employee's primary job. Users would like the report to display the CBR% for each job displayed. Users would also prefer that a CBR% be displayed only for Earn Codes that generate CBR.
Root Cause
The report was designed to show CBR% only for the employee's primary job and in all cases.
Resolution
The DPE reports by Account and Alt Account were enhanced on August 16, 2021, to increase the accuracy of Composite Benefit Rates (CBR) for employees with multiple positions, and those whose primary job is at a different UC. Read more at: https://controller.ucsf.edu/news/202108/strategic-initiatives/upcoming-enhancements-distribution-payroll-expense-dpe-report
Salary cost transfers for biweekly paychecks result in incorrectly derived effort percent
Issue
In some cases when a salary cost transfer is performed on a biweekly paycheck, the effort percent and percent of pay for the transaction are miscalculated or not calculated. As a result, the total effort percent and percent of pay are also incorrect on the Distribution of Payroll Expense (DPE) report. Note that in these cases, the dollar amount and hours are correct.
Root Cause
This issue is under investigation by the UCPath Center.
Funding distributions and retroactive leave usage (RESOLVED)
Issue
When leave usage is reported for a prior period, the position funding distributions for the current month are used to distribute the expense. If funding has changed between the prior and current funding, a salary cost transfer may be needed to move the expense to the correct funding.
Root Cause
Defect with UCPath.
Resolution
This issue was resolved by the release of the Prior Period Leave Redistribution process. For additional details see: https://controller.ucsf.edu/news/202102/payroll/redistribution-prior-period-leave-usage-ucpath.
Completed Salary Cost Transfers with September 21, October 14, and October 19 Process Dates Have Not Posted to the General Ledger (RESOLVED)
Issue:
Salary cost transfer transactions with a Process State in UCPath of “Complete” and Process Dates of September 21, October 14, and October 19, 2020, have not posted to the General Ledger.
Root Cause:
Journals received from UCPath are out of balance and are unable to post to the General Ledger.
Resolution:
UCSF IT has built a workaround to exclude the out of balance portion of the journals so that the balanced portion can be posted. 199 impacted salary cost transfers are now posted to the General Ledger. The out of balance portion pertains to benefit cost transfers and is still pending resolution by the UCPath Center.
Update August 3, 2021
A UCSF fix was implemented to allow posting of the salary cost transfers.
Note: this issue was previously titled, Completed Salary Cost Transfers with September 21 Process Date Have Not Posted to the General Ledger.
Over-the-cap rows are not generated during salary cost transfer creation using the Direct Retro MCOP Funding Worksheet (RESOLVED)
Issue
In the scenario below, Y-OTC rows are not being generated in UCPath during the entry of salary cost transfer transactions. This results in the over-the-cap dollars being added back to the capped funding source which could result in over-allocation of earnings amounts and percent of pay.
Scenario:
- In general, we are seeing this issue when the original paycheck contains VAC earnings codes.
- Initiator moves effort to a capped funding source using the Direct Retro Salary Cap MCOP Funding Worksheet.
- When Initiator clicks on the Preview page, the system only creates the N-OTC line and NO corresponding Y-OTC line is calculated or created.
- The Earnings amount in the N-OTC line includes both the ‘up to the cap’ and ‘over the cap’ earnings amounts.
Mitigation Plan
To identify if you are experiencing this issue during data entry of a salary cost transfer, please confirm on the Preview page that each capped funding source with a N-OTC distribution line has a corresponding Y-OTC distribution line or lines (for example, confirm that a distribution line with the Budget Ref value of N-OTC001 has a corresponding distribution line or lines with the value of Y-OTC001). If there is no corresponding Y-OTC line, do not submit your transaction.
Resolution
The issue has been addressed by the UCPath Center. If UCPath cannot identify the over-the-cap chartstring because no Default Funding Profile has been set up during funding entry, the system now makes the over-the-cap distribution lines editable so that the user may manually enter a chartstring.
If you need further assistance with this issue, contact the Controller’s Office Solution Center.
Direct Retro Transaction(s) Denied Due to Out of Balance Issue (RESOLVED)
Issue
Salary Cost Transfer users were notified by the UCPath Center that a direct retro transaction was identified to cause an error with the UCPath direct retro process and was denied.
Root Cause
Two defects have been identified and are being investigated by UCPath:
- MCOP Capped to Uncapped Direct Retros create Effort Percent and Out of Balance Issues
- The Correct Cap amount is not populating in Old/New Data
- Y-OTC lines are missing from the New Data section resulting in orphaned N-OTC lines and causing the transaction to be out of balance
Resolution
The UCPath Center has created an online error check during data entry for common out-of-balance scenarios. When an out-of-balance issue is detected, Salary Cost Transfer Initiators will receive an error message and must correct the transaction. Contact the Controller's Office Solution Center if you receive an error and need further assistance.
Note: this issue was formerly titled, MCOP capped to uncapped direct retros create effort percent and out of balance issues.
Some salary cap amounts missing on MyReports Distribution of Payroll Expense (DPE) reports (UPDATED)
Issue
In some cases when an employee’s salary exceeds a funding source salary cap, transaction lines for up-to-the-cap amounts on the MyReports Distribution of Payroll Expense (DPE) by Account and Distribution of Payroll Expense by Alt Account reports may appear with an “N-OTC” indicator in the Over Cap column but with no salary cap indicated in the Cap Amount column.
Root Cause
Update August 3, 2021
If no valid Salary Cap / MCOP Funding Worksheet exists, UCPath does not have a data source for the cap data to display on the main Funding Entry page, which feeds the MyReports DPE reports.
Mitigation Plan
Missing cap amounts can be confirmed using the MyReports Employee and Position Distribution Report. Funding Entry and Salary Cost Transfer Initiators and Approvers can also confirm cap types and cap amounts using the respective modules for funding and direct retros in UCPath online.
Resolution
Funding Entry Initiators shoudl confirm that a valid MCOP Funding Worksheet exists and that the worksheet does not contain multiple date ranges.
Salary cost transfer batch delays resulting in denied transactions (RESOLVED)
Issue
The UCPath Center is experiencing a high volume of technical issues when processing salary cost transfer batches. As a result, Salary Cost Transfer Initiators may also be experiencing a higher instance of denied salary cost transfers by the UCPath Center.
Root Cause
Problems stem from a new mass cost transfer tool that was migrated to production in January. Since that time, salary cost transfer batches have required several hours of manual intervention by the UCPath technical team in order to complete processing. This has delayed their scheduled burst to locations and on two occasions has lead to the cancelling of the batch and combining with another scheduled batch. The UCPath Center is denying individual salary cost transfers that are out of balance in higher numbers in order to complete processing.
Mitigation Plan
If you receive a denied transaction please continue to reach out to the Controller's Office Solution Center for assistance to see if resubmission is possible.
Resolution
A fix for the issues creating the out of balance has been implemented by the UCPath Center.
Salary cost transfers do not transfer UCRP, VLA, GAEL benefit rows (RESOLVED)
Issue
In some cases, processing of a salary cost transfer did not also transfer corresponding Vacation Leave Assessment, UCRP Supplemental Assessment, or GAEL benefits transactions.
Resolution
This is a duplicate issue entry. For issue details and resolution, see:
- UCRP-S supplemental interest not transferring with salary cost transfers (RESOLVED)
- VLA assessment calculated using incorrect salary amount (RESOLVED)
Funding Entry Error: “Position entered is not eligible for budget definition with the specified Begin date” (RESOLVED)
Issue:
Funding Entry Initiators may receive the following error when entering a new effective-dated row:
Position entered is not eligible for budget definition with the specified Begin date [DATE].
Root Cause:
The effective date for a new funding transaction must align with a corresponding effective budget definition record for the position. Budget definition records are maintained for positions in UCPath by the Office of Budget & Resource Management. This error generally occurs when there is not a current budget definition record for the position.
Resolution:
Users will experience this error when positions are moved to a new department and funding has not been established for the new department-position combination. To resolve the error, identify the new department-position combination and enter the new funding accordingly.
Salary Cost Transfer error when paycheck includes retro pay earn codes: "Effort % by earnings code for 'New Data' exceeds 100%" (RESOLVED)
Issue
Salary Cost Transfer users are unable to complete transactions when using the Direct Retro Salary Cap/MCOP Funding Worksheet for paychecks containing retro pay earnings codes. These earnings codes typically begin with "9" (e.g., 9SR,9RG,9SP) and reflect pay adjustments for prior pay periods that are included in the paycheck.
Users receive the following error message:
Effort % by earnings code for ‘New Data’ exceeds 100%. Use DR Distribution Worksheet to correct the Effort %.
Root Cause
The system is incorrectly calculating effort percent on the retro pay earnings codes in the total effort calculation, causing the effort percent in the Old Data and New Data sections to exceed 100%.
This issue was due to retro 9XX earnings codes being included in the list of 'effort bearing' earnings codes so that they could be included on the Salary Cap/MCOP worksheet.
Resolution
The UCPath Center has addressed this issue by removing the requirement that an earnings code must be effort-bearing in order to be allowed on the Salary Cap/MCOP Funding Worksheet.
UCRP-S supplemental interest not transferring with salary cost transfers (RESOLVED)
Issue
UCRP-S Supplemental Interest is not fully being credited back to the "transfer from" chartstring in limited cases when a salary cost transfer (direct retro) is processed:
- The transfer crosses fiscal years and the UCRP-S rate has changed. The credit is being calculated based on the current rate rather than the rate in place at the time of the original transaction.
- The employee has terminated or has had a change in their retirement eligibility status. UCRP-S assessment logic uses the employee's current UC retirement plan eligibility.
About UCRP Supplemental Interest
UCRP Supplement Interest is an assessment for the STIP Note and External Financing that covers debt service on advances made to UCRP. The assessment is charged only to non-federal fund sources, and is assessed separately from the Composite Benefits Rate on accounts:
- 50538 - UCRP sup assess interes-staff
- 50638 - UCRP sup assess interes-NFA
- 50738 - UCRP sup assess interes-FA
Root Cause
Defect with UCPath.
Resolution
The UCPath Center has implemented a fix for all prospective transactions.
Update: April 1, 2021
In April 2021, the Payroll Office will complete the historical cleanup of the General Ledger to clear residual benefit amounts and correct leave assessments. The historical cleanup will be completed by financial journal and will not be reflected in the Distribution of Payroll Expense (DPE), which will remain out of alignment with the General Ledger for these benefit amounts. If you have a ServiceNow ticket open with the Payroll Office and an accrual entry was done to temporarily correct one of these defects, we will be reaching out to close your ticket when the correction is posted and your accrual is reversed.
Update: May 1, 2021
The full correction is now estimated to take 35 days, as we receive the correcting entries, we will be posting throughout May and June.
Update: July 26, 2021
The Payroll Office completed the historical cleanup of the General Ledger to clear residual benefit amounts and correct leave assessments. Corrections were completed by financial journal and posted in the July 2021 accounting period.
- Correcting entries have a Journal ID beginning with “01UCRPSIC”.
- The historical cleanup will not be reflected in the Distribution of Payroll Expense (DPE), which will remain out of alignment with the General Ledger for these benefit amounts.
If you have a ServiceNow ticket open with the Payroll Office and an accrual entry was done to temporarily correct one of these defects, we will be reaching out to close your ticket when the correction is posted and your accrual is reversed.
If you have questions, contact the Controller’s Office Solution Center.
Funding override defect impacting transactions between September 5 and October 2 (RESOLVED)
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.
Update: May 1, 2021
The UCPath Center has been unable to confirm a date for our pending corrections. If you have a Qualified Disaster Payment (QDP) that posted incorrectly due to this issue and are able to proceed with transferring off the expense, the "transfer to" chartstring is SFCMP-7000-503034-7030262-72.
Update: July 26, 2021
A portion of the final clean-up for off-cycle payments where the overrides sent on pay transactions lines were not applied was completed on June 6, but have not yet posted to the UCSF ledger. Corrections to remaining October off-cycles were completed by mass cost transfer on June 21.
Transactions with earning codes QDP were not transferred. Payroll initiated an accrual by financial journal (13BENQDPC) to move the expenses to SFCMP-7000-503034-7030262-72 prior to the close of FY21.
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 .
Salary Cost Transfer Reversal and Charge Transactions Do Not Net to Zero (RESOLVED)
Issue
Over 400 direct retro transactions posted since May 2020 have been identified where the sum of the reversal and change do not equal zero. This includes some transactions where the reversal and charge transaction rows are both debits, resulting in chartstrings being charged three times (the original charge, the reversal, and the change).
Root Cause
Defect with UCPath.
Resolution
The UCPath Center has implemented a fix for all prospective transactions.
Update: April 1, 2021
In April 2021, the Payroll Office will complete the historical cleanup of the General Ledger to clear residual benefit amounts and correct leave assessments. The historical cleanup will be completed by financial journal and will not be reflected in the Distribution of Payroll Expense (DPE), which will remain out of alignment with the General Ledger for these benefit amounts. If you have a ServiceNow ticket open with the Payroll Office and an accrual entry was done to temporarily correct one of these defects, we will be reaching out to close your ticket when the correction is posted and your accrual is reversed.
Update: May 1, 2021
The full correction is now estimated to take 35 days, as we receive the correcting entries, we will be posting throughout May and June.
Update: July 26, 2021
The Payroll Office completed the historical cleanup of the General Ledger to clear residual benefit amounts and correct leave assessments. Corrections were completed by financial journal and posted in the June 2021 accounting period.
- Correcting entries have a Journal ID beginning with “PR12VLA”.
- The historical cleanup will not be reflected in the Distribution of Payroll Expense (DPE), which will remain out of alignment with the General Ledger for these benefit amounts.
- To help departments navigate the corrections, the reference field contains information that can be used to tie the GL transaction back to the DPE.
- First 9 characters: Empl ID & Empl Record Number
- Next 8 characters: Paycheck Number
- Last 9 characters: Pay End Date
- There were multiple VLA defect corrections bundled with this historical cleanup, including corrections in which the employee was originally not assessed when an assessment was due.
- The fund source that was incorrectly assessed at the time the earnings posted is referenced in the correction, regardless of subsequent salary cost transfers.
- If a sponsored project activity period was closed the open available period was used, if there was no open period or the project was closed the transactions are not included and will be evaluated by Contracts and Grants Accounting.
- Backup provided by the UCPath Center for the correction can be accessed at this Box folder: https://ucsf.box.com/s/52yq414bsvusonog992yfvcvffgo9pi2 (MyAccess login required).
If you have a ServiceNow ticket open with the Payroll Office and an accrual entry was done to temporarily correct one of these defects, we will be reaching out to close your ticket when the correction is posted and your accrual is reversed.
If you have questions, contact the Controller’s Office Solution Center.
VLA assessment calculated using incorrect salary amount (RESOLVED)
Issue
The UCPath system is calculating on-cycle vacation leave assessment (VLA) using the incorrect salary amount.
Root Cause
Rather than assessing only on the salary amount being recorded for each individual pay distribution line, UCPath is including other salary lines in the calculation.
Resolution
The underlining system defect has been resolved by the UCPath Center.
Update May 1, 2021
The Payroll Office will complete the historical cleanup of the General Ledger to clear residual benefit amounts and correct leave assessments.The full correction is now estimated to take 35 days, as we receive the correcting entries for the VLA we will be posting throughout May and June.
The historical cleanup will be completed by financial journal and will not be reflected in the Distribution of Payroll Expense (DPE), which will remain out of alignment with the General Ledger for these benefit amounts. If you have a ServiceNow ticket open with the Payroll Office and an accrual entry was done to temporarily correct one of these defects, we will be reaching out to close your ticket when the correction is posted and your accrual is reversed.
Update July 26, 2021
The Payroll Office completed the historical cleanup of the General Ledger to clear residual benefit amounts and correct leave assessments. Corrections were completed by financial journal and posted in the June 2021 accounting period.
- Correcting entries have a Journal ID beginning with “PR12VLA”.
- The historical cleanup will not be reflected in the Distribution of Payroll Expense (DPE), which will remain out of alignment with the General Ledger for these benefit amounts.
- To help departments navigate the corrections, the reference field contains information that can be used to tie the GL transaction back to the DPE.
- First 9 characters: Empl ID & Empl Record Number
- Next 8 characters: Paycheck Number
- Last 9 characters: Pay End Date
- There were multiple VLA defect corrections bundled with this historical cleanup, including corrections in which the employee was originally not assessed when an assessment was due.
- The fund source that was incorrectly assessed at the time the earnings posted is referenced in the correction, regardless of subsequent salary cost transfers.
- If a sponsored project activity period was closed the open available period was used, if there was no open period or the project was closed the transactions are not included and will be evaluated by Contracts and Grants Accounting.
- Backup provided by the UCPath Center for the correction can be accessed at this Box folder: https://ucsf.box.com/s/52yq414bsvusonog992yfvcvffgo9pi2 (MyAccess login required).
If you have a ServiceNow ticket open with the Payroll Office and an accrual entry was done to temporarily correct one of these defects, we will be reaching out to close your ticket when the correction is posted and your accrual is reversed.
If you have questions, contact the Controller’s Office Solution Center.
Earnings statements for off-cycle payments (RESOLVED)
Issue
In some cases, employees who have received a paycheck outside of their regular pay cycle (known as off-cycle pay) do not see a corresponding earnings statement in UCPath online.
Root Cause
According to the UCPath Center when there are multiple payrolls running back-to-back, off-cycle earnings statements do not always get posted.
Mitigation Plan
Employees who do not see their earning statement posted within one day of their off-cycle pay issuance can open a ticket with the Controller’s Office Solution Center who will escalate the case with the UCPath Center to have earnings statements posted.
Resolution
The UCPath Center has automated the process of posting earnings statements following off-cycle check processing.
Salary Cost Transfers completed prior to August 31 have not posted to the General Ledger (RESOLVED)
Issue:
An unknown number of salary cost transfers completed prior to August 31 with a processing status in UCPath of “Complete” as of September 2 have not posted to the General Ledger.
Resolution:
Transactions posted to the General Ledger on January 22.
Percent of effort exceeds 100 percent on Direct Retro Salary Cap/MCOP Funding Worksheet with RGC earnings (RESOLVED)
Issue
Salary Cost Transfer users are unable to complete transactions when using the Direct Retro Salary Cap/MCOP Funding Worksheet for paychecks containing RGC (REG Paid Leave-Salaried) earnings. The total percent of effort in the "Old Data" section exceeds 100%. As a result, users receive the following message upon clicking "Preview Direct Retro Distribution": Effort % by earnings code for 'New Data' exceeds 100%. Use DR Distribution Worksheet to correct the Effort %.
Mitigation Plan
To confirm that this issue is the cause of the error above, download the "Old Data" section from within the Direct Retro Salary Cap/MCOP Funding Worksheet into Excel and sum the values in the Percent of Effort column to determine if the sum is over 100%. If you encounter this issue, log a ticket with the Controller's Office Solution Center and include the Direct Retro Transaction ID/Run Cntrl ID or the UCPath employee ID and the pay end date(s) impacted.
Resolution
This issue has been resolved. If you need further assistance, contact the Controller's Office Solution Center .
Salary Cost Transfer Error: “Data being added conflicts with existing data.” (RESOLVED)
Issue
Upon saving a Direct Retro transaction, Salary Cost Transfer Initiators may receive the error message below and are unable to proceed with their transaction.
When adding a new item to the database, the system found a conflicting item already exists.
This problem can happen if another user has entered similar information at the same time as you. Note the changes you have made, cancel the page, then retry your changes.
If the problem persists, it may be because of an application or other programming error and should be reported to technical support staff.
This error occurs when the keys on the record being inserted match a record that is already in the database. The application must ensure that each inserted record has unique keys.
Root Cause
A system error resulted in duplicate Y-OTC rows being created on the Preview page.
Resolution
This issue has been resolved. If you need further assistance, contact the Controller's Office Solution Center .
Enhance MyReports Employee & Position Distribution Report to display percent of effort and salary cap amount (RESOLVED)
Issue
Percent of effort and salary cap amount are not displayed in the MyReports Employee & Position Distribution Report. Percent of effort and salary cap amount have been requested by users.
Root Cause
The Employee & Position Distribution Report was not designed to display percent effort and salary cap amount.
Resolution
Enhancements to the report released in January 2021 include additional funding entry data. Review details on the Controller’s Office website.
PPS Transactions with Zero Dollar Amounts Missing from DPE Report (RESOLVED)
Issue
PPS transaction rows with a zero dollar amount are missing from the Distribution of Payroll Expense (DPE) Report. This includes transactions for DOS codes like SKL, which report only hours and not dollars.
Root Cause
With the June 1 release of the DPE report to align salary and benefit transactions with the new UCPath data format, the logic to categorize PPS transactions as salary or benefits is determined by whether there is an amount in the corresponding “gross earnings” field (classified as salary) or “total benefits” field (classified as benefits). Transaction rows with zero-dollar amounts in both fields could not be categorized and are not displayed on the report.
This issue does not have a material impact on PPS expenses displayed in the DPE Report. The issue primarily impacts the SKL DOS code, where only hours and not dollars are reported.
Resolution
PPS zero dollar amount rows have been loaded into the Distribution of Payroll Expense by Account and the Distribution of Payroll Expense by Alt Account reports.
Time field in MyReports TDR (RESOLVED)
Issue
The Time field in the MyReports Transaction Detail Report (TDR) differs from the Time field in the Distribution of Payroll Expense Report (DPE) in both number of decimal places displayed and formatting of percentages. Preference is for both reports to display the Time field in the same manner.
Root Cause
Underlying report structures are different.
Resolution
An enhancement was released on October 12 to reformat the Time column to match the number fomats of columns on the DPE. Read more on the Controller's Office website.
GAEL posting to sponsored projects that do not allow the expense (RESOLVED)
Issue
In May and June GAEL was identified as posting to sponsored projects that do not allow the expense.
Root Cause
UCSF utilizes functionality in UCPath to exclude federal and federal flow-through sponsored projects from GAEL assessment. 120 Project IDs were identified as missing from the configuration table.
Resolution
The projects identified above have been added to the configuration table by the UCPath Center, and Contracts and Grants Accounting (CGA) has posted a journal to clear GAEL assessments that incorrectly posted. On an ongoing basis, CGA will identify and request that any new federal or federal flow-through sponsored projects be added to the configuration table. CGA will clear GAEL assessments that incorrectly posted and post corrections one month in arrears. If you do not see an adjustment posted by the following month, contact [email protected].
Funding entry updates and salary cost transfers cannot be performed for separated or transferred employees (RESOLVED)
Issue
Users are unable to initiate funding entry/updates or Direct Retro transactions for employees who have separated or who have transferred to another UC location.
Root Cause
The system is working as designed.
Resolution
1. Salary cost transfer (direct retro) transactions can be performed for employees who have separated or transferred to another UC location following the standard procedure outlined in the Salary Cost Transfer (Direct Retro) job aid.
2. Funding updates can be performed for separated or transferred employees whose funding was not entered using the Salary Cap/MCOP Funding Worksheet following the Perform Basic Funding Change instructions in the Position Funding Updates/Changes job aid.
3. Once a termination record is entered into UCPath, funding updates cannot be performed for employees using the Salary Cap/MCOP Funding Worksheet. Should further funding updated be required once a termination record is recorded, departments can perform a salary cost transfer to move payroll expenses after payroll processing.
If you need further assistance contact the Controller's Office Solution Center .
Payroll expenses with valid funding posted to suspense or department default chartstring (RESOLVED)
Issue
In several cases, payroll expenses for positions funded with valid funding distribution charstrings posted to payroll suspense or to the position's department default chartstring. Postings included the Flexfield value "COMBO" indicating the suspense was due to an invalid chartfield combination.
Root Cause
UCPath performs a final combo/edit chartstring validation before generating salary expense transaction rows for posting to the General Ledger. In some cases, the integration between UCPath and UCSF’s financial system failed due to a connection timeout error, which resulted in the charging of expenses to the department default chartstring.
Resolution
UCSF IT has requested the connection timeout period be extended to prevent future timeout errors and is actively monitoring database/connection performance. Expenses that have posted to the department default chartstring should be moved to the correct funding distributions via the salary cost transfer process. If you encounter this issue in the future or need further assistance performing a salary cost transfer, log a ticket with the Controller's Office Solution Center .
Comp Time Holiday balances do not reflect pre-conversion balances (RESOLVED)
Issue
Balances for Comp Time Holiday in UCPath do not reflect the full balance recorded in HBS.
Root Cause
During conversion, UCSF was unable to transmit pre-conversion balances in HBS for Comp Time Holiday.
Mitigation Plan
Employees should continue to view leave balances, including Comp Time Holiday balances, in HBS.
Long-term Resolution
HBS balances have been loaded to UCPath. Contact the Controller's Office Solution Center if you need further assistance.
One-time pay template issues
Issue
In a small number of circumstances, funding overrides and earning periods are not always being applied when a one-time pay template is submitted:
- When the employee is separated: The position funding is used rather than the funding identified on the one-time pay template. In cases where the incorrect funding was applied, campus departments should submit a salary cost transfer and Health departments should submit a Salary Cost Transfer PeopleConnect Management Action form.
- When payments for multiple earning dates are sent for the same employee: Although the funding override is correct, the incorrect earning period is sent to the labor ledger. Funding is correct, and dates appear correctly on paychecks. However, the earning dates viewed in reporting will reflect the incorrect earning period and no local correction option is available. To view the full amount correctly, sort by pay period end date or check date.
Root Cause
Submitted to The UCPath Center for further investigation.
Incorrect Medical Resident Hours and Effort Percent – July and August 2020 (RESOLVED)
Issue:
Total monthly hours and percent of effort are incorrect for approximately 300 Medical Residents for the July and August 2020 monthly pay cycles. Departments are seeing incorrect hours and effort percent in downstream systems, including the Distribution of Payroll Expense (DPE) Report.
Root Cause:
Due to a processing error, the weekly standard hours established in UCPath for these job records was incorrect. This resulted in incorrect calculations of total monthly payroll hours and effort percent. This issue is not pay impacting.
Resolution:
The issue has been corrected in UCPath, and hours and effort will be displayed correctly with the September 2020 pay cycle. Historical July and August data cannot be updated in UCPath and as a result will not be updated in downstream systems including the DPE Report.
Salary cost transfer transactions not posted to the General Ledger (RESOLVED)
Issue
Direct retro transactions completed in UCPath have not posted to the General Ledger.
Root Cause
UCSF's posting logic expects to receive processed transactions flagged from UCPath as "Ready to Post." Several cases have been identified where a processed transaction was received with a different flagged status.
Resolution
This issue has been resolved for all future postings. Outstanding transactions were posted to the General Ledger on August 25.
RESOLUTION UPDATE September 25, 2020
Approximately 6% of the outstanding direct retro transactions that were manually posted to the General Ledger on August 25 (and appearing in MyReports on August 26) were missing a required indicator. As a result, 2,404 transactions in suspense on PeopleSoft payroll journal were displayed incorrectly in MyReports. The missing indicator was populated, and transactions were reprocessed in PeopleSoft. The MyReports team reprocessed the transactions, and they now appear correctly in reports.
Overpayment resulting from reporting of paid time off for a prior period (RESOLVED)
Issue
Less than 60 overpayments resulted from an HBS defect that occurred when Paid Time Off (PTO) was recorded in arrears by an exempt employee.
Root Cause
PTO recorded in arrears is a reclassification of hours with no corresponding net pay. In these cases, only the paid time off-salaried (PON) hours were sent by HBS. The corresponding REG hours previously recorded for the period were not reversed, resulting in an overpayment.
Resolution
Employees who were overpaid are being contacted with repayment options.
The HBS defect was resolved prior to sending hours for the pay period ending August 22, 2020 and should not reoccur.
Posting of September 3 salary cost transfers delayed until September 9 (RESOLVED)
Issue
Salary cost transfers with a posting date of September 3, 2020 that should have been posted to Accounting Period 2 were not posted to the general ledger until September 9, 2020 into Accounting Period 3. These 430 salary cost transfers should be available in the Distribution of Payroll Expense (DPE) report on September 10, 2020.
Root Cause
The salary cost transfer batch was not received from the UCPath Center in time for posting in the correct period.
Resolution
UCSF Central Payroll is following up to determine why the batch was late and did not post as intended.
Resolution Update
The UCPath Center reported that their timing to complete this salary cost transfer batch was delayed due to the implementation of a defect correction. When migrated into production, the correction stopped the processing of the salary cost transfer batch. An additional two days were needed to troubleshoot and fix the batch before it could be delivered to all UC locations.
Distribution of Payroll Expense Rate column reflects current rate only (RESOLVED)
Issue
When running the Distribution of Payroll Expense (DPE) report by Account or Alt Account, the Rate column may not reflect the compensation rate at the time of the transaction.
Root Cause
The DPE report displays the current rate information for the job at the time the data was loaded into the report.
Resolution
An enhancement has been made to display the rate effective during the time of the transaction.
Error message when logging into UCPath after Google Chrome update (RESOLVED)
Issue
If you use Google Chrome, you may encounter the following error message when using single sign-on to access UCPath applications:
"Oops. There was an issue processing your login. Please try again. If you've tried logging in multiple times and continue to receive this message, please contact your location's desktop support provider. We apologize for the inconvenience."
Root Cause
Google is releasing updates to the Google Chrome browser beginning July 14, 2020. The expected completion is September 1, 2020.
Resolution
Should you encounter this error message, take the following action:
- Retry the UCPath application by manually entering the URL (for example: ucpath.universityofcalifornia.edu) into your web browser or by using your browser history.
- Navigating again to the URL will allow access to the application after the failed attempt.
Future distribution expense in MyReports Payroll Funding Report may be incorrect (RESOLVED)
Issue
Future distribution expenses in the MyReports Payroll Funding Report may be incorrect.
Root Cause
The Payroll Funding Report was designed to categorize over-the-cap records based on details supplied in the UCPath technical specification. It was later discovered that the specification changed but had not been shared with downstream systems.
Resolution
A new methodology for categorizing over-the-cap records was developed, and an update to the report has been released.
Salary cost transfers posting to incorrect Activity Periods (RESOLVED)
Issue
UCPath is posting salary cost transfers to the sponsored activity period that corresponds with the month in which the transaction occurred rather than the month in which the original effort was charged.
Root Cause
The activity period is being derived during the journal generation process using the pay period end date. For salary cost transfers, UCPath assigns the next logical open payroll cycle end date as the pay period end date for the transaction.
Resolution
UCSF has completed a change in the logic to derive the correct activity period for future salary cost transfers. Impacted transactions that have already posted to the General Ledger have been identified, and a central unit journal is planned to correct activity periods for impacted transactions. A journal will post into the July 2020 accounting period.
Additional details were announced in the August 2020 Controller's Office Newsletter.
Funding entry and salary cost transfer approval errors (RESOLVED)
Issue
For some MCOP funding entry transactions, Funding Entry Approvers and Salary Cost Transfer Approvers are receiving an error message when approving or denying transactions. This is occurring when transactions were submitted for approval with pay distributions per Earnings Code that do not total 100% or with chartstring validation errors.
Root Cause
Initiators were able to submit transactions where distributions per Earnings Code did not total 100%.
Mitigation Plan
If you encounter this issue in the future, log a ticket with The Bridge Center by emailing [email protected] Please include the Funding Entry Request ID or Direct Retro Transaction ID/Run Cntrl ID for the transaction where you are encountering the error.
Certain salary cap rates unavailable in UCPath (RESOLVED)
Issue
The following salary cap rates are not yet available for selection in UCPath during funding entry and salary cost transfer updates:
- California Institute for Regenerative Medicine (CIRM): $284,000 (7/1/2020 – 6/30/2020)
- Patient-Centered Outcomes Research Institute (PCORI): $200,000
- Office of Personnel Management: Rates of Basic Pay for Members of the Senior Executive Service (SES) – Agencies without a Certified SES Performance Appraisal System: $181,500 (January 2020)
Resolution
The Office of the President has submitted the rate details to the UCPath Center. The rates above were loaded are now available in UCPath.
Approved salary cost transfers have not posted to the General Ledger (RESOLVED)
Issue
Several salary cost transfers were not processed as part of our local payroll journal creation process. As a result, transactions also do not appear in MyReports.
Root Cause
Transactions assigned the same Run ID and Accounting Date across multiple batches were being identified as duplicates and were not processed.
Resolution
A programming change was implemented and missing journals have been posted.
May over-the-cap actuals missing from MyReports Payroll Funding Report (RESOLVED)
Issue
May over-the-cap actuals are missing from the MyReports Payroll Funding Report.
Resolution
Data has been reloaded and is now appearing in MyReports.
June Labor Ledger: Percent of Effort and Percent of Pay are zero for some employees (RESOLVED)
Issue
Payroll journal results for 4,170 employees are showing zero values for Hours, Percent of Pay, and Percent of Effort. This issue mainly impacts transactions for academic employees posted for the June monthly payroll cycle.
Users may see zero values in the Hours, Percent of Pay, and Percent of Effort in the Distribution of Payroll Expense Report and in the Time and %/H fields in the Transaction Detail Report in MyReports. Other downstream systems may be impacted.
Root Cause
Data was missing from the Labor Ledger received from UCPath.
Resolution
Data has been reloaded into the Labor Ledger. MyReports is now reflecting the missing data.
April distributions missing from MyReports Payroll Funding Report (RESOLVED)
Issue
April distributions are missing from the MyReports Payroll Funding Report.
Root Cause
As part of cutover to UCPath, April distributions were initially loaded from UCPath. However, distribution data was converted from PPS to UCPath with May effective dates.
Resolution
April distributions have been reloaded from PPS and are available again in the report.
Error in cap rate for some employees (RESOLVED)
Issue
At go-live, 73 employees have a cap rate in UCPath that is higher than the cap rate established in PPS. In some cases, the cap rate in PPS was out of date and the cap rate in UCPath is correct. In other cases, the lower cap rate in PPS is correct and should be applied in UCPath.
Root Cause
Most differences in cap rate were resolved during conversion. The remaining 73 were not corrected prior to conversion.
Resolution
Due to the complexities of applying the salary cap, Central Payroll cannot determine whether the cap rate in UCPath or the cap rate in PPS is correct. A report of these employees was provided to Funding Initiators to determine how to proceed. Funding Initiators should review the report and can make corrections in UCPath online as required. Contact The Bridge Center if you need assistance with corrections.
Not enrolled in Duo error message at login (RESOLVED)
Issue
Employees who are enrolled in Duo multi-factor authentication are receiving an error message that they are not enrolled in Duo when they try to log into UCPath.
Root cause
Duo multi-factor authentication is tied to a user's Active Direct credentials and will not recognize SF ID or UCSF email account name.
Resolution
Log into UCPath using your Active Directory credentials; do not use your SF ID or UCSF email account name.
Missing salary cap amount in MyReports DPE Report (RESOLVED)
Issue
Salary cap amount is not displayed in the MyReports Distribution of Payroll Expense (DPE) report.
Root Cause
The UCPath rate field is different than the PPS rate field, and the cap is not embedded in the rate field.
Resolution
The report has been enhanced with a new Cap Amount field.
Over cap attribute not populating in MyReports DPE Report (RESOLVED)
Issue
The over cap attribute is not populating in the MyReports Distribution of Payroll Expense (DPE) Report.
Root Cause
Report logic is not working as expected.
Resolution
The report has been enhanced to load the over cap attribute.
Postdoctoral fellowships not visible in MyReports DPE Report (RESOLVED)
Issue
Postdoctoral fellowships are not visible in the MyReports Distribution of Payroll Expense (DPE) Report.
Root Cause
Only expenses in 5000B, 5040B, and 5080B in the Account Tree are included in the DPE. Postdoctoral fellowships are not located in these levels of the Account Tree.
Resolution
The report has been enhanced to source expenses in the 5579D Scholarship/fellowship node of the Account Tree.
Duplicate records in MyReports Employee & Position Distribution Report (RESOLVED)
Issue
Duplicate records in the MyReports Employee & Position Distribution Report have been identified in 1 instance to date.
Root Cause
Related to join conditions used to create the report.
Resolution
Resolved in conjuction with fix for MCOP records with blank Earn Codes.
Missing records in MyReports Employee & Position Distribution Report (RESOLVED)
Issue
Records are missing from the MyReports Employee & Position Distribution report.
Root Cause
Health Sciences Compensation Plan (HSCP) records are not loading when Earn Code is blank.
Resolution
Change report to source blank Earn Code records for HSCP employees.
Combo edit error on salary cost transfers (RESOLVED)
Issue
During the combo edit (chartfield validation) process, Salary Cost Transfer Initiators receive an invalid chartstring combination error.
Root Cause
The pay end date was not being passed by the web service during the combo edit validation. The pay end date is needed in order to derive the correct activitiy period to validate the charstring.
Resolution
This issue has been resolved. If you received this error please try resubmitting the transaction.
As a reminder, use the COA Validator to confirm whether your chartstring is valid. If the activity period is not active, work with Contracts and Grants Accounting to extend by contacting [email protected]
AFLAC deduction file was not processed (RESOLVED)
Issue
For the June 1 monthly pay cycle, AFLAC deductions were not taken.
Root Cause
The AFLAC deduction file did not get picked up by UCPath Center for processing.
Resolution
Impacted employees have been notified and the UCPath Center is working with these employees to bring their deductions up to date. Future AFLAC deduction files will be processed so that deductions are taken from employee paychecks.
Incorrect CBR for some employees in MyReports Employee & Position Distribution Report (RESOLVED)
Issue
The incorrect Composite Benefit Rate (CBR) was displayed for a small number of employees on the MyReports 'Employee & Position Distribution Report.'
Root Cause
A remnant of code used during development to compensate for data quality issues was not fully removed at go-live causing a number of employees to display the incorrect CBR.
Resolution
Code was remediated on June 4, 2020.
Missing records in MyReports DPE Report (RESOLVED)
Issue
Records were missing for 11 employees on the MyReports Distribution of Payroll Expense (DPE) Report.
Root Cause
Report logic required a Check Date when loading records, but employees with multiple appointments where UCSF is not the primary job do not have Check Date information.
Resolution
Report logic was changed on June 9, 2020 to not require Check Date when loading records.
Percent effort not displayed in MyReports DPE Report (RESOLVED)
Issue
Percent effort was not correctly displayed for monthly paid employees in the MyReports Distribution of Payroll Expense (DPE) report.
Root Cause
The data source contains both the percent effort and percent of pay. The report was using percent of pay when it should have been using the percent of effort.
Resolution
The report was modified on June 11, 2020 to display percent of effort in the Time field for monthly paid employees.
Work location is incorrect or out-of-sync (RESOLVED)
Issue
Employees report that incorrect work location information is displayed in UCPath and on pay statements.
Root Cause
At go-live, some employee work locations stored in Hitachi, UCSF's identity management system, were not converted to UCPath.
Resolution
- Work location data between UCPath and Hitachi has been corrected and is in sync as of June 15, 2020.
- Note that work location is not entered in UCPath. Employees can update work location details using the UCSF Directory .
Missing funding distributions for some additional pay lines (RESOLVED)
Issue
Funding for 200 additional pay lines from PPS (primarily HZA) are missing corresponding funding distribution information in UCPath. As a result, these expenses will be charged to the department default chartstring.
Root Cause
The conversion process did not correctly set up some additional pay lines for positions funded using the MCOP worksheet.
Resolution
Central Payroll has the necessary information and is making the required corrections. A report of the distributions added in UCPath for these additional pay lines will be provided to Control Points.
Supervisor (reports to) relationship is incorrect (RESOLVED)
Issue
The supervisor relationships for some employees was incorrect at go-live. In UCPath a supervisor relationship is established for each position an employee holds. Individuals who hold multiple positions can have different supervisors (and direct reports) for each position. This allows for more accurate and detailed organizational reporting.
Root Cause
Some supervisor relationships for employees with multiple appointments did not convert with the correct supervisory assignment.
Resolution
For departments that have already submitted a ServiceNow ticket to change a supervisor, changes will be processed centrally.
For all other changes, use the new supervisor self-service update tool-UCPath Reports to Tool.
- UCPath Reports to Tool is available to campus departments via MyAccess beginning on Thursday, June 18.
- Initial access will be given to anyone who has access to the HR Reports.
- Updates submitted by the end-of-day Friday each week will be uploaded to UCPath the following week.
Note that supervisor 'reports to' relationships in UCPath have no impact on timesheet approver roles in Huntington Business Systems (HBS). If you need to update a timesheet approver in HBS, continue to submit a PeopleConnect Management Action case.