Overview
The Transfer of Funds (TF) document is used to transfer funds (cash) between accounts.
The Year End version is similar except for the following:
- Entries will post in period 13.
- Will not route to the Fiscal Officer, Organization Review must be set up in order to submit the document.
There are two kinds of transfer transactions, mandatory and non-mandatory.
- Mandatory transfers are required to meet contractual agreements. Specific object codes are used to identify these transactions. An example of this type of transfer is moving dedicated student fees to the retirement of indebtedness fund group for principal and interest payments on bonds.
-
Non-mandatory transfers are allocations of unrestricted cash between fund groups, which are not required by any external agreements. These transfers are most commonly used throughout the university.
Business Rules
The following parameters drive business rules around the Transfer of Funds:
-
MANDATORY_SUB_TYPE: Object sub type codes categorized as Mandatory Transfer. From accounting lines with an object sub-type of mandatory transfer must balance with To accounting lines with an object sub-type of Mandatory Transfer.
-
NON_MANDATORY_SUB_TYPES: Object sub type codes categorized as Non-Mandatory Transfer. From accounting lines with an object sub-type of non-mandatory Transfer must balance with To accounting lines with an object sub-type of Non-Mandatory Transfer.
-
BALANCING_FUNDS: If the account used has a fund group in this parameter, the From amounts must match the To amounts for each specified fund group.
- MANY_TO_MANY_TRANSFERS_IND: When set to Y, multiple accounting lines can be entered in both the From and the To sections. If the parameter is set to N, multiple accounting lines can be entered in either the From or the To, but not both.
Routing
-
The TF routes based on the account numbers in the From and To sections as follows:
-
The fiscal officer or delegate for each account must approve.
- Note: The Year End version does not route for fiscal officer or delegate approval.
-
Optionally, organization review routing occurs for the organization that owns each account .
- Note: Organizaiton Review routing must be set up for the Year End version because it doesn't route to the fiscal officer or delegate.
- Optionally, sub-fund routing occurs based on the sub-fund of each account.
- Optionally, object code routing occurs based on the object codes used on the document.
- Optionally, award routing occurs based on the CG Responsibility ID assigned to Contracts and Grants accounts.
-
The fiscal officer or delegate for each account must approve.
Comments
0 comments
Please sign in to leave a comment.