As part of Project One, UCSF is implementing an enhanced Chart of Accounts (COA) that will provide a standardized financial structure across the enterprise. During Project One Phase 2, systems primarily used by the campus community, as well as systems shared by campus and UCSF Health, will transition to the new Oracle COA. This includes UCPath, where payroll funding distributions and related financial transactions are managed.

Beginning with the July 2027 Project One go-live, UCPath transactors—including Funding Entry and Salary Cost Transfer Initiators and Approvers—will use updated chartfield segments and revised business processes that align with UCSF’s Oracle Cloud Finance implementation.

What UCPath transactors need to know about the COA transition

As part of the transition, UCPath users can expect:

• Updated funding entry, salary cost transfer, and benefit cost transfer pages that use the enhanced Oracle COA chartfield segments.
• New chartfield requirements and default values for funding transactions.
• Conversion of department values for position assignments and organizational relationships to new seven-digit Dept ID values.
• Updated reports and tools to support payroll funding review and reconciliation, and new suspense handling processes in Oracle.
• Updates to job aids and training resources that reflect UCPath’s alignment with the new Oracle COA and business processes changing with Project One. 

Planning for the UCPath transition is underway. Implementation details, including system availability during cutover, transaction cutoff dates, and training opportunities are still being finalized. These resources will be shared well in advance of the July 2027 go-live to give departments sufficient time to prepare.

What UCPath transactors can do now to prepare for the COA transition

1. Departments should continue to review and update payroll funding regularly and promptly resolve transactions that post to department default chartstrings or payroll suspense. While no immediate changes are being implemented in UCPath, maintaining accurate funding today will help reduce the number of payroll transactions requiring manual correction during and after the Project One transition.
2. After the July 2027 go-live, payroll expenses that posted using the previous Chart of Accounts structure cannot be corrected through the UCPath Salary Cost Transfer process. Because of this, departments are strongly encouraged to address funding issues and complete payroll expense corrections as they arise.

Additional information, including key dates and guidance for addressing transactions after July 2027, will be shared in advance of go-live.

For more information

• Visit the Project One website for implementation updates, timelines and resources.
• Learn more about the enhanced Chart of Accounts.

Further communications, training opportunities and job aids for UCPath transactors will be shared as we get closer to go-live.