Introduction
The Chart of Accounts serves as the foundation for all financial reporting. The CSU must have a standard set of ChartField definitions in order to facilitate comparable reporting, training, and common business processes. The ChartField definitions outlined in this paper must be followed by all campuses and participating auxiliary organizations.
With the implementation of the CSU Data Warehouse, corporate reporting needs previously met by the FIRMS data will be produced from the CSU Data Warehouse. In addition, campus departmental reporting will be obtained from the CSU Data Warehouse.
CSU Systemwide Attributes will be the basis for systemwide, legal, GAAP and campus reporting. Hierarchical relationships will be established within the OBIEE reporting tool based on these attributes. The campus department organizational tree will be extracted for warehouse reporting. These hierarchies will allow for drill down capability when using the data warehouse reporting tool.
In order to achieve consistent and meaningful reporting, it is necessary for all campuses to adhere to the following standards and use the ChartFields as defined:
- ChartFields are distinctly defined and are not interchangeable
- Certain ChartFields have required lengths
- The Account ChartField value must equal the FIRMS Object Code value at a minimum and campus unique values must begin with the first three characters of the FIRMS Object Code (GAAP Object Category) which is currently a CSU Systemwide Attribute of the Account ChartField.
Fund Chartfield
CSU Business Requirements
The Office of the State Controller establishes statewide funds to account for resources appropriated by acts of the State legislature. Campus administration of these funds must conform to accounting rules issued by the State Controller, the State Treasurer and other relevant State regulations and provisions of State law.
In addition to appropriated funds, the CSU also collects fees from students. These funds are regulated solely by Executive Order 1000 and CSU policies, standards and definitions.
State funds are allocated to the CSU. The CSU manages all funds by CSU Fund – which is a sub set of the State fund. Each CSU Fund is administered according to the appropriate rule set – be it legislative or based on CSU Policy. Each campus manages these various CSU Funds by establishing campus unique fund values based on reporting requirements, day to day administration of the funds, Generally Accepted Accounting Principles (GAAP) requirements, and the governing rule sets.
As a State “agency,” each campus is required to report to the State Controller their fund activity using the State of California Chart of Accounts. For the CSU, this activity is reported via an annual electronic submission (SAM99). In addition, in order to spend funds that have been appropriated by the State, campuses must file a request for payment (State Claim Schedule) which also must use the State’s chart of accounts. Campuses are also required to submit GAAP adjustments to the State using these same values.
For non-appropriated/non-governmental funds, the Chancellor’s Office files a statement of financial position for the CSU as a whole. Campuses report to the Chancellor’s Office using the CSU Systemwide Attributes assigned to the Fund ChartField (FNAT Key) that allows for consolidated and comparable reporting.
Since 1989, the CSU has been required to prepare GAAP statements for all campuses. Most campuses prepare stand-alone GAAP statements along with being part of the overall CSU GAAP financial statements. These financial statements are prepared using the Net Asset Category assigned to the Fund ChartField as one of the CSU Systemwide Attributes (FNAT key).
All of the electronic processes mentioned are facilitated by the CSU Systemwide Attributes assigned to the Fund ChartField when it is created. Campuses are able to focus on campus operations and management’s request for information using the PeopleSoft Fund ChartField while the common chart of accounts for the State of California, GAAP and CSU are used for all external required transactions and reporting.
Definition
The Fund ChartField value is required for moneys held on deposit with the State Controller’s Office for which we are required to reconcile SAM99.
The Fund ChartField value is used when an activity requires a Trial Balance.
The Fund ChartField is required for every financial transaction.
Length
The Fund ChartField must have five characters.
Value/Structure
The Fund ChartField value is not prescribed and may contain both alpha and numeric characters.
Attributes
The Fund ChartField requires a corresponding fund attribute key (FNAT Key) be assigned when the value is created. The attributes provide the common and necessary information for CSU Systemwide, Office of the State Controller and GAAP reporting at the fund and Net Asset Category level.
Campus specific attributes may be assigned to a fund using the PeopleSoft Attribute Hyperlink. This set of attributes is independent of the FNAT key. Sonoma uses the GAAP override and Program Code fund attribute.
Additional Information
Funds should be established in accordance with Executive Order 1000. Individual campuses determine the fund values for their operating Business Unit. Campuses may expand the required set of funds for operational purposes.
Examples
- IRA Athletics
- Operating Fund
- Smith Endowment Trust
- Sponsored Program Award
Account Charfield
CSU Business Requirement
The Office of the State Controller establishes statewide accounts (State GL Account). Campuses must conform to accounting rules issued by the State Controller, the State Treasurer and other relevant State regulations and provisions of State law.
State GL accounts are maintained as CSU Systemwide Attributes. As a State “agency,” each campus is required to report to the State Controller their activity using the State GL account. For the CSU, this activity is reported via an annual electronic submission (SAM99).
For non-appropriated/non-governmental funds, the Chancellor’s Office files a statement of financial position for the CSU as a whole. Campuses report to the Chancellor’s Office using the CSU Systemwide Attributes assigned to the Account ChartField (AAT key) that allows for consolidated and comparable reporting.
Since 1989, the CSU has been required to prepare GAAP statements for all campuses. Most campuses prepare stand-alone GAAP statements along with being part of the overall CSU GAAP financial statements. These financial statements are prepared using the Natural Classifications assigned to the Account ChartField as one of the CSU Systemwide Attributes (AAT key).
All of the electronic processes mentioned are facilitated by the CSU Systemwide attributes assigned to the Account ChartField when it is created. Campuses are able to focus on campus operations and management’s request for information using the PeopleSoft account ChartField while the common Chart of Accounts for the State of California, GAAP and CSU are used for all external required transactions and reporting.
Definition
The account ChartField represents the line item breakdown for a Balance Sheet and Income Statement. This ChartField classifies Assets, Liabilities, Fund Equities, Revenues, and Expenses and captures the nature of the financial transaction that is entered into the system.
The Account ChartField is required for every financial transaction.
Length
The account ChartField must have six characters.
Value/Structure
The account ChartField value must equal the FIRMS Object Code (CSU corporate account value) value at a minimum. Additional campus specific accounts may be added as needed to meet campus reporting requirements but must adhere to the following specific value structure:
- first three digits equal the first three digits of the associated FIRMS Object Code (GAAP Object Category),
- fourth digit is an 8 or 9 or Alpha
- Certain characters are recognized by Excel as a functional symbol. For example, when the letter E is in the center of an otherwise numeric ChartField value, Excel will convert it to an exponential number. These should be avoided.
Attributes
The account ChartField and its corresponding account attribute key (AAT key) provide the common and necessary information for CSU Systemwide, SCO and GAAP reporting using the FIRMS Object Code, State GL and Natural Classification, respectively.
Campus specific attributes may be assigned to an account using the PeopleSoft Attribute Hyperlink. This set of attributes is independent of the AAT key. Sonoma uses the attribute OLD_ACCOUNT to enable mapping for CFS Chart of Account changes.
Additional Information
Reasons for unique campus Account values that differ from the FIRMS Object Code values:
- Sub-system activity - Accounts are created by campuses to uniquely identify subsystem feeds to facilitate reconciliation between the ledger and subsystem. It is highly recommended to use control value PeopleSoft functionality that restricts the transactions posted to the control account to be from the subsystem feed only.
- Reconciliations other than sub-system – Unique accounts are created to facilitate accurate and timely reconciliation.
- For reporting and management purposes – Unique accounts facilitate reporting and management decisions. Campus/auxiliary organizations create accounts to uniquely identify campus level transactions for various reasons. An example would include the NCAA audit.
Examples
- Supplies and Services
- Accounts Payable
- Fund Balance Clearing
Department Chartfield
CSU Business Requirements
There are no State reporting requirements associated with the department ChartField.
Definition
The department ChartField represents the detailed structure of campus organizations. Combined with other ChartField values, they can form the basis for department budgets that track expenditures and revenues and organizational reporting requirements. The department ChartField is required for all revenue and expense type transactions.
Length
The department ChartField length is not prescribed and may have up to ten characters. Sonoma uses four numeric digits for operations. The exception is FIRMS departments which begin with the letter “F” followed by four numeric digits.
Value/Structure
The department ChartField value is not prescribed and may contain both alpha and numeric characters.
Attribute
Campus specific attributes may be assigned to a department using the PeopleSoft Attribute Hyperlink. Sonoma has no department campus attributes.
Additional Information
This ChartField corresponds to the organizational structure identified by each campus.
The department ChartField is also used by HCM for student financial transactions and payroll data. This data is transferred to and from HCM and Finance via integration broker. These values must be the same in both modules.
Examples
- VP of Academic Affairs
- College of Business
- Department of Accounting
Project Chartfield
CSU Business Requirements
There are no State reporting requirements associated with the project ChartField.
Definition
The project ChartField is used to identify a discrete set of activities that have a strict start and end date. Activities associated with this ChartField may span multiple fiscal years, departments, funds and/or accounts.
The project ChartField is only required on revenue and expense transactions for activities as defined above.
Length
The project ChartField length should be between 5-7 characters. For Sponsored Programs, Sonoma uses up to seven alpha numeric. For all other uses (except Auxiliaries) Sonoma uses five numeric. Auxiliaries use five alpha numeric.
Value/Structure
The project ChartField value is not prescribed and may contain both alpha and numeric characters.
Attributes
Campuses may use PeopleSoft Attributes Hyperlink available on project ChartField to further define a specific set of activities or projects on a campus. Sonoma does not use PeopleSoft project attributes.
Additional Information
The use of this ChartField does not eliminate the need for a fund ChartField if balance sheet transactions must be tracked.
Program Chartfield
Definition
The Program ChartField is used to define ongoing general activities which need to be tracked for reporting purposes or campus policy. A Program, unlike a Project, does not have a strict start and end date.
The program ChartField is only required on revenue and expense transactions for activities as defined above. This definition applies to the program ChartField used in the campus legal Business Unit. The program ChartField in the CSU Business Unit is the derived NACUBO program code.
Length
The program ChartField length is not prescribed and may have up to five characters. Sonoma uses four alpha. Auxiliaries use four numeric.
Value/Structure
The program ChartField value is not prescribed and may contain both alpha and numeric characters.
Attributes
There are no FIRMS attributes related to the program ChartField. Campus specific attributes may be assigned to a program using the PeopleSoft Attribute Hyperlink.
Additional Information
Required systemwide programs have not been identified to date.
Class Chartfield
Definitions
The class ChartField is provided for any special cost reporting needs a campus department or other organizational unit may have that are not met by the other defined ChartFields.
The class ChartField is only required on revenue and expense transactions for activities as defined above.
Length
The class ChartField length is not prescribed and may have up to five characters. Sonoma uses four alpha.
Value/Structure
The class ChartField value is not prescribed and may contain both alpha and numeric characters.
Attributes
There are no FIRMS attributes related to the class ChartField. Campus specific attributes may be assigned to a class using the PeopleSoft Attribute Hyperlink.
Additional Information
A class should only be assigned when the campus needs cannot be met using other ChartFields. Identification of this ChartField is completely at the discretion of each campus.
Examples
- Used for UBIT reporting
Scenario Chartfield
Definitions
A ledger consists of posted balances that represent a set of books for a business unit. A scenario is a ChartField used specifically in the budget ledger to categorize activity. Examples of common scenarios are New, Project to Date (PTD), and Transfers. Sonoma uses ORIGINAL, PTD, BBA, TRANSFERS, ALLOC, and OTH_SPEC.
Required External Reporting based on Chart of Accounts Attributes
SAM99 Reconciliation to State Controller -- The SAM99 process reconciles the records of the State Controller’s Office (SCO) to those of Cal State on a monthly basis and generates year-end reports required by the State Controller.
SAM07 Trial Balance by SCO Fund -– State Administrative Manual (SAM) requires a pre-closing and post-closing trial balance be produced by SCO Fund. Production of this report will also facilitate the error detection and resolution of the SAM99 process.
SAM06 Final Budget Report -- Provides required revenue and expenditure reporting for each campus. SCO Claim Schedule -- PeopleSoft Payables can meet some of the functional requirements, but modifications were needed in order to satisfy the claims processing.