èapp this Policy
Transfers
Policy Number: 22102
Effective Date:
Last Updated:
Responsible Office:
èappSystem Controller's Office
Responsible Administrator:
èappSystem Controller
Policy Contact:
èappSystem Controller's Office
Categories:
- Finance
Menu:
- Scope
- Reason for Policy
- Policy Statement
- Definitions
- Accountabilities
- Forms
- Related Information
- History
- Procedure
Scope
This policy outlines the responsibilities and process to ensure appropriate movement of funds within the University of èapp’s financial statements.
Reason for Policy
The purpose of this policy is to ensure the consistent and appropriate recording of transfers in the University’s financial records. Transfers are needed to carry out accounting and fiduciary responsibilities as defined by the Governmental Accounting Standards Board (GASB) and the National Association of College and University Business Officers (NACUBO).
Policy Statement
A transfer is the movement of funds from one ChartField string to another as a result of a Nonexchange Transaction. Transfers are neither expenditures of the contributing fund nor revenue to the recipient fund. Under Governmental Accounting Standards Board (GASB) 34/35 reporting standards, transfers are not included with expenditures, but are shown in the transfers section of the financial statements.
There are three types of transfers used by the University to move funds. They include: Intra Unrestricted Current Fund, Non-mandatory, and Mandatory Transfers. All transfers should follow the guidelines set forth in this policy and apply for both budgeted and actual transactions.
- Transfer transactions must be coordinated with budget requests for transfers to ensure both sides of the transfer are budgeted.
- Transfers in total should net to zero on the consolidated financial statements. Both sides of a transfer journal entry must use a transfer account.
- Transfers between unrestricted and Restricted Funds are not allowed except when the Restricted Funds require a match or the transfer is expressly required or allowed in the restrictive covenant/agreement. Campus Accounting Offices must approve these transfers and the required supporting documentation.
- A transfer journal entry should only be made to move funds between Chartfields to record “non-exchange” transactions. Common transactions confused with transfers include:
- Correcting Entries should be used to correct errors in previously recorded transactions where original transactions occurred in the current fiscal year, with the exception of grants and contracts and other project to date funds that can cross fiscal years.
- Internal Sales and Services Accounts should be used to account for the exchange of goods and services between departments.
- Full Costing Accounts should be used to allocate the cost of a department that is shared among other departments or to allocate institutional costs. Examples include service centers spreading costs back to departments or the charge to auxiliaries for institutional support.
- Transfers are NEVER allowed between any University fund and an Agency Fund. However, transfers are allowed within Agency Funds.
- See the Transfer Grid (under Procedures) for allowable transfers between funds and related accounts.
Definitions
Fund Group - a grouping of funds of a similar nature such as Unrestricted Current Funds, restricted current funds, loan funds, endowment & similar funds, and plant funds.
Agency Fund - monies held by the University on behalf of others. These monies do not belong to the University.
Nonexchange Transaction - a transaction where one party gives (or receives) value without directly receiving (or giving) equal value in return.
Restricted Funds - funds that are restricted in purpose by a third party covenant or agreement recorded in the fund range of 20XX, 2100-3400. Examples include gifts and sponsored program (grant and contract) funds from donors, grantors, or other external sources that are restricted as to how they can be spent.
Unrestricted Current Funds - funds that are available to be spent in the near term for operational purposes that are not restricted by external sources.
Intra Unrestricted Current Fund Transfers - movements of monies between ChartField strings within unrestricted current funds, whether within or between Business Units.
Non-mandatory Transfers - transfers used to move unrestricted funds from one fund to another at the discretion of administrative management (excludes transfers within Unrestricted Current Funds). Non-mandatory transfers can serve various purposes, such as, funding the renovation or construction of fixed assets, increasing the amount of financial aid available to students through voluntary additions to the loan fund, or transferring funds to or from a quasi-endowment fund. Transfers within a fund group other than Unrestricted Current Funds should be done as Non-mandatory transfers.
Mandatory Transfers - transfers used to move funds as required by a third party (external to the University). Examples of Mandatory transfers include debt service payments, required institutional matching on financial aid and/or student loan programs and the transfer of funds to or from an endowment as required by the endowment agreement.
Accountabilities
èappSystem Controller’s Office:
- Ensure the balances of transfer accounts net to zero.
èappSystem Budget Office:
- Ensure transfer budget entries net to zero in the budget.
Campus Accounting Offices:
- Monitor transfers and provide oversight.
- Review transfers on an as needed basis for appropriateness.
- Approve exceptions to policy.
Campus Budget Office:
- Ensure internal budget transfer entries net to zero within their business unit.
Departments:
- Ensure transfers are properly budgeted, executed and documented.
- Ensure the prescribed accounts are consistently used.
Additional Details
Forms
Related Information
History
Formerly Accounting Policy Manual 70.15 – Transfers-Intra Unrestricted Current Funds, Non-Mandatory, and Mandatory (revised 7/1/2014)
Procedure
Transfer Quick Reference Guide: www.umsystem.edu/media/fa/controller/TRANSFER%20QUICK%20REFERENCE.xlsx
Transfer Grid:
Reviewed 2021-04-23