Overview
FRS Architecture
The Financial Records System from Systems & Computer Technology Corporation is a comprehensive system consisting of both online and batch processing features that are used to manage most of the complex financial functions at UConn. FRS supports the myriad of functions related to the procurement of goods and services, the resultant payment of vendors, the recording of University revenues and expenditures, and the final reporting of total University financial resources through a comprehensive financial reporting capability. Like most other modern computer systems, FRS is designed in a modular manner which permits selective implementation of individual features to best match each institution's unique needs. The major modules of FRS are as follows:
Purchasing (PR) Module
This module can be considered the origination point for a continuous stream of financial transactions through the FRS system. Requests for goods and services normally originate as purchase requisitions and the requestor's funds can be initially encumbered at this point to provide automatic control against over-expenditure of budget allocations. From this stage, a purchase order can be created which ultimately results in an order being placed with a vendor. When the requested goods are received here at UConn, receiving information is posted to the Purchasing module either by Central Warehouse or the receiving department. Finally, when the vendor sends a billing invoice for the goods provided, this information is also posted to the Purchasing module, whereupon a voucher (request for payment) is automatically generated to the Accounts Payable module.
Accounts Payable (AP) Module
This module is the second stage of the FRS transaction stream. It is here that payments to vendors for goods and services are generated. In addition to accepting vouchers generated from the Purchasing module, payment requests for other items that do not go through Purchasing can be originated here. The final result of creating a voucher in the Accounts Payable module is normally a check written to a vendor. Most checks for expenditures at UConn are now written using the FRS system, however, a few checks for State controlled purchases are still produced by the State Comptroller's office.
In addition to the basic payment function, the AP module has a a tracking capability to prevent duplicate vendor payments and to perform check reconciliation for cancelled checks processed through University or State bank accounts. As a result of the payment process, transactions are automatically sent "downstream" to the Financial Accounting module. This process results in a liquidation of the original encumbrance, an adjustment of the department'saccount balance, if necessary, and an ultimate reduction of the University's cash position.
Fixed Assets (FX) Module
The purpose of the Fixed Assets module is to help university managers fulfill their responsibility to administer, account for, and preserve the institution's investment in property, plant, and equipment. This responsibility extends across departments with implications for Accounting, Inventory Control, Purchasing, Maintenance and Risk management.
To Accounting, it provides accurate detail reports to support the values recorded in the General Ledger plant fund accounts. It calculates and records annual depreciation and helps establish use allowances for indirect cost recovery on grants and contracts.
To Inventory Control, it provides the ability to fix custodial responsibility for assets, to track acquisitions, transfers and disposals, and to perform periodic inventory assessments.
To administrators, it provides information about the availability of equipment, allowing managers to use existing property more efficiently and to avoid the purchase of duplicate equipment.
To Risk and Maintenance managers, it provides information for determining the extent of losses in case of fire or theft and establishing insurance requirements. It centralizes maintenance contract information and calculates replacement costs.
These primary functions may be summarized as follows:
- Recording the value of plant assets
- Calculating and recording depreciation
- Fixing custodial responsibility for assets
- Providing current and accurate data to support resource allocation and budgeting
- Providing maintenance and insurance data
Financial Accounting (FA) Module
Although the Financial Accounting module is the end of the FRS transaction stream for expenditures, it is the entry point for information on Univesity revenues and the State's budget allocations. In addition, it is the repository for a great deal of other information concerning the assets, liabilities , and fund balances of the University. Finally, data pertaining to UConn's bank account balances is maintained here as well. This repository of data serves as the basis for preparing numerous monthly and annual financial statements.
Major FRS Files
Purchasing Module
- Vendor (VN) File (shared with Accounts Payable)
- Document (PO) File
- Receiving (PR) File
- Invoice (PI) File
- Duplicate Invoice (VD) File (shared with Accounts Payable)
This file contains a record for every vendor and employee who provides goods, services, or receives payments from UConn. Information such as name, address, and Federal Tax ID are maintained here as well as cumulative statistics concerning the volume of business that the University transacts with each vendor.
This file contains purchase requisitions, regular purchase orders, stading orders, master orders, and standard text descriptions printed on each of these documents. In addition, "bid" documents used in the associated Bid module are stored here as well.
This file stores detail records for each receipt posted to the system.
This file stores detail records for each invoice posted to the system.
The Purchasing and Accounts Payable modules use the Duplicate Invoice file as a control, preventing the payment of an invoice more than once.
Accounts Payable Module
- Voucher (VO) File
- Check Reconciliation (VC) File
This file contains a record for each payment made. Invoice or voucher information is added to the VO file as check requests and credit memos are added to the system. At the time of writing checks, all vouchers for each vendor are normally accumulated and one check is written. The user can, however, request separate checks as the need arises.
This file contains a record for each check issued by the University. The data is used to reconcile checks written by UConn with bank records of checks cleared. Each check record contains a status indicator showing whether the check is currently outstanding, voided, or cleared.
Fixed Assets Module
- Asset Master (TA) File
- Batch (TB) File
- Building (TD) File
- History (TH) File
- Notes (TN) File
- Table (TT) File
This file contains basic asset data. Each record represents an asset or asset component and contains information about that asset.
This file contains a history of batch and online session activity. Each record represents a batch or online session that has been processed, or an extract program update run.
This file contains additional specialized information about buildings. Each record represents a building; a building number links this record to the corresponding asset record.
This file contains a history of asset activity. Each record reflects a Fixed assets transaction (direct record), or a related journal entry created by the Accounting feed (indirect record).
This file contains free-form comments to supplement the basic asset information stored in the Asset Master (TA) file.
This file contains processing controls. It is actually comprised of five separate data tables plus the system control record.
Financial Accounting Module
- General Ledger (GL) File
- Subsidiary Ledger (SL) File
- Open Commitment (OC) File
- Transaction History Files
This file contains an account for each unique fund that an institution maintains. It also may have accounts that function as revolving or clearing accounts. The main function of these accounts is to maintain a record of the assets, liabilities, and the fund balances of the institution. In addition, the GL file contains records for University and State bank accounts which track the University's cash position on a daily basis.
This file contains accounts that track revenues, expenditures, and encumbrances throughout the institution. Accounts may be designated in group for such things as Tuition revenue, investment income, auxiliary services, and externally sponsored grants and contracts. Each account maintains its own record of revenue and expense by subcode (object code).
This file contains a detail record for each outstanding encumbrance. These records are catalogued by a reference number (normally Purchase Order number) within SL expense account. FRS permits any number of encumbrances againsts a single expense account number. The system uses information on this file for automatic encumbrance liquidation when disbursements and/or journal entries are posted.
FRS maintains detailed transaction history files for inquiry, reporting and auditing purposes. These files contain an image of every batch and online financial transaction presented to the system. A sequential is history file is continually accumulated throughout the year to support reporting and system auditing. An abbreviated history file is maintained online for the user to obtain convenient access to transactions recently posted to an account. Due to the volume of FRS activity at UConn, transactions from only the current month and one previous month are maintained online.
FRS Reporting
FRS reporting is handled either through standard batch jobs scheduled by the FRS System Administrator or by user generated FOCUS reports.
- Batch reporting
- FOCUS reporting
- Personnel Activity Reporting System (PARS)
A variety of standard daily, monthly, and cumulative fiscal year reports are available by running batch jobs which use COBOL report programs provided as part of the standard FRS system software.
The FOCUS EXPRESS module of FRS is used to extract data from the FRS master files on a nightly basis. FOCUS procedures written here at UConn are then used to build FOCUS files from this extract data. By using these extract files, the user can then run any type of FOCUS report desired through VM/CMS on the mainframe. A menu capability for basic FRS FOCUS reporting is available to authorized users by executing FOCEXEC F9530S01 after entering the mainframe FOCUS environment. Data can also be extracted from these FOCUS files for importing into various PC-based software packages such as LOTUS 1-2-3, EXCEL, and PC-FOCUS.
A locally developed FOCUS reporting system called PARS is available for use by the Grants and Contracts office to comply with Federal government reporting requirements for personnel expenditures on various grants and contracts.
FRS Documentation
A variety of documentation is available for FRS including written manuals for the base system, FOCUS reporting guides, and the FRS Online Reference System.
- Reference Manuals
- FOCUS Reporting Manual
- Online Reference System
- Online Reference System Menu:
- Screen Help:
- Data Element Help:
- Error Message Help:
A complete set of vendor supplied reference manuals is maintained by the FRS System Administrator in the Accounting Office. These manuals describe overall system and module capabilities, online and batch program operation, system reports, and a great deal of other specific information about FRS use and operation.
A written manual containing FOCUS Master File descriptions and FOCUS reporting hints for FRS is maintained by the Information Systems Support Group at the University Information Technology Services (UITS).
The FRS Online Reference System is accessible to the user only after signing onto the FRS system using an authorized system number, operator number, and password. The information available includes general system information similar to that contained in the written manuals, together with more specific screen help, data element help, and error message help.
A brief guide to accessing this system is as follows:
Place the cursor on the FRS screen field and press PF1. General system instructions are available by typing "?" in the field at the bottom of the menu screen.
Place the cursor on the FRS screen field and press PF2.
Place the cursor on the specific data element field and Press PF2.
Place the cursor on the error message being displayed and press PF2.
University of Connecticut