Accounting & Reporting

Support Contact

415.502.8432
415.390.9100
Box 0815

Management Contact

Alma Martinez
Director - Accounts Receivable and Banking Services

General Ledger Schedule

March 2024

Sunday Monday Tuesday Wednesday Thursday Friday Saturday
Sunday, Feb 25
25
Monday, Feb 26
26
Tuesday, Feb 27
27
Wednesday, Feb 28
28
Thursday, Feb 29
29
Friday, Mar 1
1
Saturday, Mar 2
2
Sunday, Feb 25
 
Monday, Feb 26
 
Tuesday, Feb 27
 
Wednesday, Feb 28
 
Thursday, Feb 29
 
Friday, Mar 1
 
Saturday, Mar 2
 
Sunday, Mar 3
3
Monday, Mar 4
4
Tuesday, Mar 5
5
Wednesday, Mar 6
6
Thursday, Mar 7
7
Friday, Mar 8
8
Saturday, Mar 9
9
Sunday, Mar 3
 
Monday, Mar 4
Submit journals requiring BO & CO approval for Febuary close
 
Tuesday, Mar 5
Febuary Electronic Recharges due
 
Wednesday, Mar 6
Departments check Worklist to ensure all journals have posted for Febuary
 
Thursday, Mar 7
Campus Febuary Month End
 
Friday, Mar 8
Febuary actuals loaded into Uplan
 
Campus: PS GL Open for March (Period 9)
 
Saturday, Mar 9
 
Sunday, Mar 10
10
Monday, Mar 11
11
Tuesday, Mar 12
12
Wednesday, Mar 13
13
Thursday, Mar 14
14
Friday, Mar 15
15
Saturday, Mar 16
16
Sunday, Mar 10
 
Monday, Mar 11
UCSF Health: Febuary Month End
 
Tuesday, Mar 12
Delete Febuary journals not posted
 
UCSF Health: PS GL Open for March (Period 9)
 
Wednesday, Mar 13
GLV data published for verification - Febuary
 
Thursday, Mar 14
 
Friday, Mar 15
 
Saturday, Mar 16
 
Sunday, Mar 17
17
Monday, Mar 18
18
Tuesday, Mar 19
19
Wednesday, Mar 20
20
Thursday, Mar 21
21
Friday, Mar 22
22
Saturday, Mar 23
23
Sunday, Mar 17
 
Monday, Mar 18
 
Tuesday, Mar 19
 
Wednesday, Mar 20
 
Thursday, Mar 21
 
Friday, Mar 22
March Intercampus Charges due to Controller's Office
 
Saturday, Mar 23
 
Sunday, Mar 24
24
Monday, Mar 25
25
Tuesday, Mar 26
26
Wednesday, Mar 27
27
Thursday, Mar 28
28
Friday, Mar 29
29
Saturday, Mar 30
30
Sunday, Mar 24
 
Monday, Mar 25
 
Tuesday, Mar 26
 
Wednesday, Mar 27
 
Thursday, Mar 28
Last day to submit March Dept A/R to Controller's Office
 
Friday, Mar 29
 
Saturday, Mar 30
 
Sunday, Mar 31
31
Monday, Apr 1
1
Tuesday, Apr 2
2
Wednesday, Apr 3
3
Thursday, Apr 4
4
Friday, Apr 5
5
Saturday, Apr 6
6
Sunday, Mar 31
 
Monday, Apr 1
 
Tuesday, Apr 2
 
Wednesday, Apr 3
 
Thursday, Apr 4
 
Friday, Apr 5
 
Saturday, Apr 6
 
Add to My Calendar
  • Departments manage the request and setup for Projects within PeopleSoft. Workflow moves requests through department and Control Point approval, then through the final approval process by the Controller’s Office to complete the Project setup. This guide provides an overview of how Projects are set up, general guidelines for the types of activities that should be tracked using Projects, and step-by-step instructions on how departments request new Projects.
  • General Ledger Verification (GLV) is a UCSF key internal control required by Campus Administrative Policy 300-46. The system is comprised of 3 roles – Verifier, Viewer, and Approver. This job aid discusses how to perform your role as a Verifier.
  • General Ledger Verification (GLV) is a UCSF key internal control required by Campus Administrative Policy 300-46. The system is comprised of 3 roles – Verifier, Viewer, and Approver. This job aid discusses the Approver role.
  • General Ledger Verification (GLV) is a UCSF key internal control required by Campus Administrative Policy 300-46. The system is comprised of 3 roles – Verifier, Viewer, and Approver. Depending on your Departmental practice, Verifiers or Approvers may perform monthly trend analysis.
  • This step-by-step guide explains the differences between creating journals in foreign currency and U.S. dollars.
  • The General Ledger (GL) Verification online tool streamlines the General Ledger Verification (GLV) process with the goal of ensuring overall reasonableness of department financials. The tool uses a risk and sampling approach rather than a full reconciliation.
  • This guide explains how to delete journals in PeopleSoft.
  • This job aid contains instructions for running and working with the General Ledger (GL) Verification tool's reports.
  • Select from the training options below to learn how to navigate in the Peoplesoft Fluid User Interface (UI). This introduction provides a general overview of the components most commonly used by department administrators at UCSF. To learn about the steps to navigate to a specific page, refer to training materials available on the Controller's Office website. eLearning: How to Navigate in the PeopleSoft Fluid User Interface Start Course Select a link below to jump to a specific lesson.
  • Completion of this two-part course is required for access to the PeopleSoft General Ledger module.
  • This guide explains how to use the PeopleSoft Worklist. The Worklist provides one easy-to-locate tile within PeopleSoft to view and take action on items.
  • This step-by-step guide demonstrates how employees with direct reports can assign and monitor the completion of required training courses available in the UC Learning Center. Satisfactory completion of training is a prerequisite for certain financial roles at UCSF. Managers can assign any required training available in the Learning Center to direct reports and monitor completion.
  • This Payment Card Industry Security Awareness Training is required annually for all UCSF Medical Center (UCSF Health) and Campus staff handling credit cards and/or cardholder information. New employees handling this information must complete this course upon hire, and annually thereafter. The purpose of this course is to familiarize employees with credit card security issues and enhance your skills in maintaining the security and safety of the UCSF payment card environment and cardholder data.
  • Click the links above to watch the video from the June 8, 2023 broadcast and to download the PDF for easy access to the website references used in the presentation.
  • Journals are created to enter financial information into the General Ledger. Financial information includes deposits, payments, transfers, allocations, and other types of activity necessary to accurately describe the finances of the University.
  • General Ledger (GL) verification is a key control of UCSF and is a requirement per Campus Administrative Policies.
  • UCSF's chart of accounts (COA) is the coding structure that defines operations in financial terms. The COA serves as the foundation of the general ledger. The UCSF chartstring is a 38-character coding string that consists of 8 individual "blocks", or segments, called chartfields.  The chartfields and resulting chartstring facilitate accounting, reporting, and budgeting. 
  • The fiscal year-end close process is required to prepare the general ledger accounts for financial statement presentation and for the start of the next accounting process.
  • Recharges and central costed activities occur when one unit of the University provides services that benefit other units internally. These activities may be specifically identifiable based on usage such as expenses for off-site storage, or generally in support of a shared resource such as information technology. Only units approved by Budget and Resource Management may use recharges and distribution of central costed activities.
  • This guide defines and explains how to search for, enter into transactions, create, and maintain SpeedTypes in PeopleSoft.
  • In certain instances, the University may act as a fiscal agent for outside agencies such as student, faculty, staff, governmental, or private organizations or activities. An agency fund is used to record the administration of monies for the outside agency where the intended use is for a mutually beneficial and agreed-upon purpose that supports or enhances the mission of the University. Agency funds are not considered University monies or charitable contributions to the University. Examples of appropriate agency funds include establishing funds for:
  • This guide describes how to enter and maintain Department Functional Roles in PeopleSoft.
  • This job aid provides step-by-step instructions on preparing a recharge journal. 
  • This guide describes how to prepare, edit, and submit Source Code 535 financial journals.
  • This guide explains Journal Approver responsibilities and how to review and approve or deny a journal in PeopleSoft. 
  • This step-by-step guide explains how to log into PeopleSoft Mobile Approvals to approve or deny journals on Apple iOS or Android devices.
  • With UCSF’s upgrade to the PeopleSoft Fluid User Interface in March 2021, the mobile approvals interface mirrors the Approvals tile in the web-based version of PeopleSoft, with one key exception: Journal Approvals will not find a link to Go To Journal Entry Details when clicking the Approvals tile on a mobile device. The requirements to review and approve journals are the same whether using the web version or the mobile application. Journal Approvers may need to complete their review using the web version prior to taking approval action from a mobile device. 
  • This step-by-step guide explains how to act as a Control Point Approver in PeopleSoft.
  • As a Journal Approver, when an absence takes you out of the office you have the ability to temporarily assign an alternate approver who can review and approve or deny your journals so they post as intended. Approval delegation is performed in the PeopleSoft My System Profile page.
  • If you need to print or save a PDF of a PeopleSoft journal, you can do so using the Print Journal process from the journal’s Lines tab. The process creates a PDF file that can be saved or printed. There is no requirement to save PDFs or print journals; PeopleSoft is the system of record. This step-by-step guide explains how to download and/or print a PeopleSoft Journal PDF file.
  • This document describes the process of preparing and submitting journal entries electronically via flat files.
  • PeopleSoft Standard Journal Entries (SJEs) provide functionality to automate the scheduled recurring entry of similar or identical journals. This job aid explains how to define and review Standard Journals.
  • Moving Money The method used to transfer money or balances (e.g., "move money") depends on the Account Type. Specific Accounts and Account Types must be used consistently to ensure that reporting is accurate, clear, and consistent. Refer to the Moving Money Quick Reference Guide for details on:
  • This step-by-step guide assists PeopleSoft users who have the Chartfield Approver role in identifying requests to approve new Projects and Flexfields.
  • Department managers must maintain a ledger of all staff currently eligible for handling electronic payments at any stage within the department and are required to report new credit card handlers to Merchant Services to ensure PCI Security Training is assigned and completed prior to payment acceptance. Proof of background check completion for new or established employees must be maintained on file within the department as well as the appropriate HR Service Center.
  • Email [email protected] to request decommissioning of Merchant IDs and return of terminal equipment in order to protect from fraudulent use and ensure that continued merchant expenses are not incurred.
  • Merchants who wish to obtain user guides for terminals at their location can find them in this section or contact [email protected] when troubleshooting issues with an existing terminal.
  • Departments that wish to establish a new method of accepting credit cards or make changes to existing payment methods must contact UCSF Merchant Services to obtain authorization and support prior to change or implementation. All departments who accept electronic payments in any form are required to adhere to PCI DSS standards, including initial training of staff, periodic updates to policies and procedures, and periodic testing of knowledge, policies, and procedures, as required by the PCI Council, in order to retain merchant status.
  • This article outlines the procedures required for departments to accept electronic transfers of funds as a depository option.
  • Department accounts receivable (Dept A/R, also known as Sundry Debtor) invoices are provided to external customers (customers not affiliated with the University of California) who use UCSF property or receive goods or services and do not make payment at the time of service. External customers must first be established in the University’s financial system and the department providing the goods or services must be associated with the external customer in the system before invoices can be submitted for recording and distribution to the external customer.
  • Establishing a New Petty Cash Custodian, Setting up a Petty Cash or Change Fund, Replenishing Petty Cash Funds, Change of Custodian for an Existing Fund, Decreasing Petty Cash or Change Funds, Terminating a Petty Cash or Change Fund
  • This article outlines procedures for handling the most common types of payments received by campus departments.
  • Establishing Journal Preparers and Approvers in PeopleSoft Take the two-part online course “Understanding PeopleSoft Journals” in the UC Learning Center. Completion of this course is required for access to PeopleSoft General Ledger and Journals. Journal Preparers must complete Understanding Journals: Journal Preparer Actions (opens in new window).
  • UCSF routinely conducts business with other campuses and with Office of the President (UCOP). These transactions are divided into four categories:
  • All merchants who accept electronic payments are required to understand, adhere to, and provide evidence of compliance to international payment security standards. UCSF is committed to ensuring the utmost protection of payment and personal information for our customers and patients.
  • Collection efforts for department accounts receivable (Dept A/R) invoices are the responsibility of the department providing the property, good, or service. If an external customer does not pay an invoice within 30 days it is considered delinquent. Departments should contact the external customer to follow-up on delinquent invoices.
  • Department Accounts Receivable (Dept A/R, also known as ‘sundry debtor’ receivables) is the amount due to the University from an external customer for payment of a good supplied and/or service already rendered. Dept A/R excludes sponsored projects, student/employee and UCSF Health related receivables. Dept A/R is not applicable to business conducted with other campuses or with the Office of the President (UCOP); see Handling ITF and IOC for procedures related to Interlocation Transfer of Funds (ITFs) and Intercampus Orders & Charges (IOCs).
  • UCSF implemented Total Compliance Tracking (TCT) to efficiently manage PCI DSS testing and compliance tracking across the University. This online web-based tool assists in documenting our efforts to maintain data security standards across all merchants.
  • Review the procedures to record credit card journals in UCSF's PeopleSoft financial system following UCSF's credit card journal entry process.
  • Cash and Credit Card journals in PeopleSoft are used to record payments received from third parties. Journal Preparers and Journal Approvers are responsible for ensuring that all journal entries are reasonable and accurate based on the documentation, knowledge of the activity, and conformity to applicable UCSF Policies and outside agency requirements. 
  • This article explains how UCSF departments should review the Unclaimed Payments List and how to claim these funds.
  • Customers who receive an invoice for use of property or receipt of goods or services provided by a UCSF department (other than from UCSF Health or for a sponsored project), should use the following information to prepare payments. Payments that include all the necessary information are more easily and quickly applied to invoices. Payments should be made as an electronic transfer, either as a wire transfer or ACH (Automated Clearing House). Checks should only be used when payment by electronic transfer is not possible.
  • Departments send requests for UCSF deposit supplies to the Controller's Office Cash Operations Team.
  • This article describes the requirements and procedures to establish Cash Handlers at UCSF.
  • Equipment Custodians are assigned by departments and are responsible for providing current equipment information including physical location, custody code, disposal, and sales. UCOP and Federal Regulations require that campus departments perform a physical verification of all capitalized assets listed in the UCSF asset management database system every two years. This is essential for continued federal, state, and private donor funding of operations and research projects. Equipment custodians are charged with conducting the physical inventory on a biannually-scheduled basis. Assigning or Changing Equipment Custodian Responsibility When a new custodian is assigned responsibility by a department, the department must:
  • The Asset Management Report can be found under the Transactional Reports tab in MyReports. There are numerous ways to search for and filter data in MyReports to meet your needs. For inventory purposes it is easiest to search by Custodian Name or Custody Code. These fields are in the Report Specific Filters section on the bottom of the page:
  • UCOP and Federal Regulations require that campus departments perform a physical verification of all capitalized assets listed in the UCSF asset management database system every two years. The Controller's Office schedules the inventory date for each department. Each department custodian is given 45 working days to:
  • Capital Lease or Operating Lease A Capital Lease or Operating Lease is a lease agreement in which the University executes a written contract with a vendor through SCM Procurement to purchase or rent real property with scheduled installment payments during the life of a contract. Title to the property remains with the lessor throughout the contract term. The University may have the right to take possession of the property at the end of the contract, or earlier, subject to payment of any outstanding principal and the buy-out amount specified in the contract.
  • Effective July 1, 2014 through 2030, California Department of Tax and Fee Administration's Regulation 1525.4 - Manufacturing and Research & Development Equipment allows “partial sales and use tax exemption” on certain manufacturing and research and development equipment purchases and leases.
  • No property shall be removed from University custody without first obtaining the necessary approvals outlined in the procedures below. Only equipment for which the University holds clear title can be disposed ­of without the written permission of the title holder. Departments are responsible for verifying title on all sponsored funded equipment.
  • Article Contents Introduction Definitions Scope Purpose Process Ownership Life Cycle Outcomes Procedures Self-Assessment Reference Documents Introduction The purpose of Capitalized Asset Management (CAM) is to:
  • University of California Office of the President (UCOP) Risk Services manages a self-insurance program that provides coverage for loss of assets. All campuses and medical centers contribute to the fund annually. Valuation of loss is based on repair or replacement of damaged or destroyed property. Deductibles per occurrence:
  • Capital equipment has a value of $5,000 or more, or software with a per copy cost of $5,000 or more, with a normal life expectancy of more than one year, and is not "expendable". There are specific procedures for capital equipment purchases as well as special procedures applicable over the lifetime of the capital asset. Before you make a purchase of capital equipment, be sure that you understand and follow the specific procedures:
  • The gift should meet the criteria of a capital asset: Tangible, Freestanding, Useful life of one year or longer, and Estimated value of $5,000 or greater. Donor, private individual, a corporation, or some other entity should provide a statement in writing that:
  • This guide outlines how to submit stipend requests.
  • The Student Accounting Team works with departments to disburse funds to students and post doctoral candidates.  Stipends A stipend is a payment made to an individual under a fellowship or training grant in accordance with pre-established levels to provide for the individual's living expenses during the period of training. A stipend is not considered to be compensation for the services expected of an employee. The Stipend Payment Request application allows departments to submit an Excel spreadsheet to request stipend payments for students, Clinical Fellows, and Visiting Scholars.
  • UCSF Building Codes
  • Commonly used codes and schedules for capital assets and equipment:
  • Internal controls are divided into key and non-key controls. Key controls are the primary procedures relied upon to mitigate a risk or prevent fraud. Non-key controls are considered secondary or back up controls. All controls can be grouped into one of the four components of internal control:
  • Letter from Bank of America confirming bank information needed to accept incoming Electronic Funds Transfers (EFT).
  • Accessing the Chart of Accounts Account Tree via the Controller's Office website now requires a connection from the UCSF network or VPN. If you are already connected to the UCSF network or VPN you may proceed. If you are connecting remotely, please connect to the UCSF VPN before accessing this resource. Review these Frequently Asked Questions (opens in new window) for more information about the UCSF VPN.
  • Letter from the State of California Franchise Tax Board confirming that the University of California and its affiliated organizations are considered part of the State of California and not subject to income tax. 
  • Accessing the Chart of Accounts Alt Account Tree via the Controller's Office website now requires a connection from the UCSF network or VPN. If you are already connected to the UCSF network or VPN you may proceed. If you are connecting remotely, please connect to the UCSF VPN before accessing this resource. Review these Frequently Asked Questions (opens in new window) for more information about the UCSF VPN.
  • Accessing the Chart of Accounts Fund Tree via the Controller's Office website now requires a connection from the UCSF network or VPN. If you are already connected to the UCSF network or VPN you may proceed. If you are connecting remotely, please connect to the UCSF VPN before accessing this resource. Review these Frequently Asked Questions (opens in new window) for more information about the UCSF VPN.
  • Accessing the Chart of Accounts Dept ID Tree via the Controller's Office website now requires a connection from the UCSF network or VPN. If you are already connected to the UCSF network or VPN you may proceed. If you are connecting remotely, please connect to the UCSF VPN before accessing this resource. Review these Frequently Asked Questions (opens in new window) for more information about the UCSF VPN.
  • The Fund chartfield is a 4-character alphanumeric value which identifies source of money. Fund identifies the source of financial support and demonstrates restrictions imposed by the governing board or in accordance with regulations, restrictions, or limitations imposed by sources outside the institution. It is a required field on revenue, expense, and transfer transactions.
  • The Account chartfield is a 5-character numeric value which identifies the nature or type of the transaction by classifying them into Assets, Liabilities, Equity (net position), Revenues, and Expenses. It is a required field on all transactions. The Accounts are organized into reporting levels using a PeopleSoft tree. The Accounts are designed to facilitate reporting and are generally used across the organization. The campus, foundation, and medical center will share the same list of Accounts. (See the Alternate Account section for additional information for medical center accounts). In other words, the Accounts do not have departmental ownership.
  • Department (also referred to as Dept ID) chartfield is a 6-character alphanumeric value which identifies the organizational unit involved in transaction or responsible for resource. Departments are seen as “Cost Centers” whose managers are responsible for all its associated costs and for ensuring adherence to its budgets. It is a required field on revenue, expense, and transfer transactions. A Department is defined as a distinctly identifiable department, division, or unit of an organization whose managers are responsible for all its associated costs and for ensuring adherence to its budgets
  • The Activity Period chartfield is a 2-character alphanumeric value which identifies the activity period for projects with multiple periods. Activity period chartfield allows reporting in a unit of time within an overall project. Activity period is primarily intended for sponsored projects to allow reporting on multi-year awards with competitive renewals for different project periods. Nevertheless, it can also be used for non-sponsored projects across multiple periods where interim reporting is needed. Values Examples of Activity Period values are: 01, 02, 03, 04, etc. through to 99.
  • The Project chartfield is a 7-character alphanumeric value which assists in uniquely identifying and tracking charges to a discrete set of activities, initiatives or projects. The focus of a Project is tracking an activity or a specified purpose. The Project is often associated with a person that is responsible or accountable for the activity. It is a required field on revenue, expense, and transfer transactions. Projects should not be confused with Funds. The Fund chartfield identifies the source, whereas a Project allows tracking for a particular activity or purpose (how a department uses funds). A Project usually has a specific beginning and ending date. Generally, a new Project may be established:
  • The Function chartfield is a 2-character alphanumeric value which fulfills internal and external reporting requirements to track higher education functional classifications. Function code also determines how costs are treated in the research Facilities & Administrative (F&A) or indirect cost rate calculation. For this purpose, it is particularly important that costs are accurately coded and that it is consistent with OMB Circular A-21 (federal) functional definitions. Function also facilitates internal mission-based reporting. Purpose/Use
  • Purpose The Flexfield chartfield is an optional value for departmental use designed to track information not captured by other chartfields. Before creating a Flexfield, a department should determine whether or not it is possible to track the activity using the other chartfields, or combinations of chartfields, in the new COA such as Account, Fund, Department, Project, Activity Period, or Function.
  • This table of Project Use, Project Name, and Project Descriptions indicates whether a user can add a non-shared Project.
  • Use the Combo Edit Guide to identify which chartfield combinations may or may not be used together. It is especially useful when planning or troubleshooting journals which have unusual combinations of chartfields.
  • Account Description 51321 Spon proj equip >$5K, non-comp 51322 Spon proj computer >$5K 51323 Spon proj software >$5K 52303 MC USE-equipment less than $5K 52304 Computers less than $5K 52305 Software less than $5K 52315 Furniture 52601 Computers $5K and above 52602 Software $5K and above 52603
  • Outlines the reasons for requesting a new Chartfield, and how the set-up and request are coordinated.
  • Business Registration Renewal Confirmation Document
  • UCSF Custody Codes list.
  • UCSF Campus 2022 Annual Financial Report 2021 Annual Financial Report 2020 Annual Financial Report 2019 Annual Financial Report
  • UCSF Physical Inventory Custodian Schedule 2019 - 2021 Cycle
  • This is the list of Journal Preparer IDs currently in use.
  • Source Codes identify the purpose of PeopleSoft journals. They are also a selection criterion for reporting in the MyReports Transaction Detail Report. Some source codes are limited to PeopleSoft Journal Preparers who are assigned a specific PeopleSoft role to use the source code. Several source codes have additional approval workflow connected with them. Online Financial Journals Campus Departments and Controller’s Office
  • The chart is this document summarizes the rules for account types that can be used for transferring money or balances. By using these types of accounts, reporting is clear and consistent. The other pages highlight the accounts to use: Page 2 when transferring money within the Campus, and Page 3 between the Campus and UCSF Health.
  • GL Monthly Schedule
  • PeopleSoft Journal Header - Input Record Definition Field Name Length Column Positions Comments/Issues Record Type 1 1 'H' indicates a Journal Header record Business Unit 5 2- 6 Required field; Input value of 'SFCMP' or ‘SFMED’ or ‘SFFDN’ Journal ID 10 7-16 Required field; assigned by Accounting Office Journal Date 8 17-24
  • This letter can be used as a confirming statement that UCSF retains tax exempt status as described in the April 2014 letter from the Internal Revenue Service (IRS).
  • Slide deck from the Spring 2018 go-live training sessions for the new General Ledger Verification Online Tool.  
  • This reference details a history of enhancements to the GL Verification tool.
  • The General Ledger (GL) Verification Advisory Group's charter is to support the continuous improvement of the GL Verification Tool.
  • It is the responsibility of each department to ensure that financial transactions recorded in the general ledger are in accordance with all relevant policies, regulations, and sponsor or donor terms and conditions. The following guidelines are provided for Verifiers and Approvers when using the GL Verification Tool for general ledger verification activities.
  • Both the video from the June 8, 2020 broadcast, and the PDF slides include the question and answer session. For easy access to the website references used in the slide presentation, see 2019-20 Fiscal Year-End Close Presentation Website Links.
  • Watch the video from the June 8, 2021 broadcast. The PDF slides include the question and answer session, as well as easy access to the website references used in the presentation.
  • Watch the video (opens in new window) from the May 31, 2021 broadcast. The PDF slides (opens in new window) provide easy access to the website references used in the presentation.
  • This reference guide describes Self-Assessment Questionnaire (SAQ) Types used in the PCI DSS compliance monitoring process.
  • Regular inspections of credit card devices for tampering or skimmers is essential to protect UCSF and our customers, clients and patients from credit card fraud.
  • A SpeedType is a 6 to 10 character shortcut key which can be used in many transactional systems including BearBuy, Connexxus, MyCores, and MyExpense. Establishment and use of SpeedTypes is recommended for situations where some system users (such as BearBuy Requesters and MyExpense self-preparers) are unfamiliar with the full financial chartstring. When a SpeedType is entered in these systems, it is expanded to the full chartstring (except for Account). Departments are responsible for creating and maintaining SpeedTypes. Following a naming convention for SpeedTypes is highly recommended and will make searching for SpeedTypes more efficient.
  • Departments are responsible for notifying the Controller's Office General Accounting Service Desk, when changes to this list are required. See the end of this page for detailed instructions on how to update this list.
  • UCSF routinely conducts business with other campuses and with Office of the President (UCOP). This guide provides an overview of these transactions, describes how transactions are processed, and identifies resources for users who need assistance with related processing. These transactions are divided into the following categories: Category Source Code(s) Interlocation Transfer of Funds (ITFs) 150, 574 Intercampus Orders & Charges (IOCs) 57X
  • Article Contents Employee Tax Forms Using GLACIER for Non-resident Alien Tax Compliance Exempt Organization Business Income Tax Return Campus Tax Information UCSF Foundation Tax Information Sales and Use Tax Unrelated Business Income Tax (UBIT) Miscellaneous Income City & County Who to Contact
  • Use the following guidelines to ensure journal submissions include appropriate supporting documentation for the most commonly prepared journal types.
  • For each country outside of the United States where UCSF has established operations, financial transactions are recorded in PeopleSoft using a foreign Business Unit. Intended only for use by UCSF Global Programs accounting teams, the Business Units allow for the recording and reporting of transactions in each country's respective local currency. Current Business Units, countries and corresponding currencies are as follows:
  • Here are key responsibilities merchants have in handling credit card payments safely. Failure to adhere to the Merchant Services agreement can result in termination of credit card payment acceptance privileges.
  • Function is a two-character chartfield in the UCSF Chart of Accounts that fulfills internal and external reporting requirements to track higher education function classifications.  Function defines the mission/purpose of the transaction.  Functions also determine how costs are treated in the Facilities & Administration (F&A), or indirect cost, calculation.  Functions are designed for specific uses.  Users should select the Function code that best reflects the mission associated with the transaction or activity. 
  • There are 12 main requirements in the PCI DSS, which are designed to provide a comprehensive framework for securing cardholder data.
  • Introducing two new business units in preparation for recent acquisitions.
  • UCSF implemented changes to PeopleSoft Financials in July 2023 to comply with the UC Office of the President’s Common Chart of Accounts (CCOA). In an ongoing effort to meet contract and grant reporting requirements since the CCOA go-live, the Controller’s Office is implementing a change in the use of Account numbers when recording journal entries for Intercampus Orders and Charges (IOC) and Interlocation Transfer of Funds (ITF). Moving forward, these recharges must be recorded using an Account number that indicates the UC location, instead of an Account reflecting the nature of the expense.
  • Complete semi-annual petty cash verifications
  • Beginning April 2024, the Controller’s Office Cash Operations Team will resume transfers to the Central Fund of cash, wire, and ACH payments received in UCSF’s main depository account that remain unclaimed for over 12 months. This transfer process was paused in early 2023 to allow Controller’s Office personnel to make improvements to the cash application and department accounts receivable processes.
  • Make petty cash account updates now ahead of the January petty cash verification process.
  • As part of UCSF’s unrelated business income tax (UBIT) filing, we are required to report any donations made by the University to charitable organizations. These donations may reduce UCSF’s unrelated business taxable income, provided the University received an acknowledgement letter from the recipient organization.
  • Review important restrictions on allocating the UCGPC Systemwide Fee assessment.
  • Get additional guidance on the timing of department cash journal postings following improvements to the cash application process.
  • Review upcoming training dates for the non-payroll stipend request process.
  • Further cash application process improvements to make identifying and claiming deposits and payments easier for departments.
  • Review upcoming training dates for the non-payroll stipend request process.
  • Read about a recent General Ledger Verification Tool enhancement to improve verifying payroll by award or project.
  • In September, the Controller’s Office will implement further improvements to the cash application process to make identifying and claiming deposits and payments easier for departments. While departments will continue to follow established procedures for identifying and recording sponsored research payments and credit card transactions, here’s a look at what’s changing for claiming all other types of payments and transactions.
  • Review upcoming training dates for the non-payroll stipend request process.
  • On July 1, 2023, UCSF implemented changes to PeopleSoft Financials to comply with the UC Office of the President’s new Common Chart of Accounts (CCOA).
  • Read about the new Fund 4007 created for central accounting use.
  • Refer to the following resources and dates to ensure you are prepared for fiscal year-end close activities.
  • Here's what UCSF merchants need to know to begin using Total Compliance Tracking to manage their PCI DSS compliance tracking.
  • Key dates and resources to help prepare for fiscal year-end close
  • Review changes in UCSF accounting procedures required to comply with the July 1, 2023, UC Common Chart of Accounts implementation.
  • Important policy reminders related to the inventory and disposition of capital equipment assigned to faculty or PIs separating from the University.
  • Update: The original version of this announcement incorrectly stated that journals “must be prepared and approved by departments no later than 7 p.m. on the second business day of the following month.” This has been revised to reflect that journals must be prepared, approved, and posted by departments before month end close. Beginning April 27, 2023, journals for recording cash receipts (using Source Code 320) and credit card payments (using Source Code 323) are no longer routed to the Controller’s Office via PeopleSoft workflow for review and approval. Journals post as part of the PeopleSoft nightly batch process upon approval by department journal approvers.
  • The Controller’s Office will host a presentation on Thursday, June 8, 2023, to communicate fiscal year-end close activities, timelines, and expectations. Participants will have an opportunity to raise questions during the live broadcast. Department managers, financial administrators, financial analysts, research administrators, and anyone else involved in the year-end close process should plan to watch the live broadcast or review the recorded presentation.
  • Prepare for an upcoming change to the Millberry Union drop safe location
  • New employees responsible for submitting non-payroll stipend requests are encouraged to attend an upcoming training conducted by the Controller's Office Student Accounting team. The training is also a good refresher for all administrators who submit these requests. The following sessions are available for registration:
  • We need your help to ensure that we receive a copy of every IRS Form 1099-MISC issued to UCSF. During tax season, the Controller’s Office must review all IRS Forms 1099-MISC issued to UCSF to verify if tax has been withheld and to report and reclaim withholding amounts. Review the guidelines below to identify when your department may receive a Form 1099-MISC issued to UCSF and how to submit it to the Controller's Office for review. What is Form 1099-MISC?
  • April 1, 2023, begins the next biennial cycle for the physical inventory process. Department Finance Administrators and their Equipment Custodians should review the updated 2023-2025 Physical Inventory Custodian Schedule on the Controller’s Office website.
  • Improvements to the department accounts receivable (Dept A/R) process became effective on March 1. The improvements announced in last month’s Newsletter were based on stakeholder survey responses and interviews with the goal of making the process easier and more efficient for departments without requiring modifications to the UCSF financial system.
  • Credit Card Merchant Services is excited to announce the planned implementation of Total Compliance Tracking (TCT) compliance software to support UCSF’s PCI compliance management process. The tool provides automated PCI testing, including automated task management and email reminders. It will also help manage the retention of testing documentation for each merchant, including task activities, guidance, and supporting materials. With the release of PCI Data Security Standard (DSS) version 4.0 on March 31, 2022, UCSF will adopt new PCI compliance standards beginning this year. The TCT software will include updated guidance to ensure adherence to the new regulatory changes.
  • New employees responsible for submitting non-payroll stipend requests are encouraged to attend an upcoming training conducted by the Controller's Office Student Accounting team. The training is also a good refresher for all administrators who submit these requests. The following sessions are available for registration: