Budget Transfers

 System Training   |     FRMS

  • Account Transfers vs. Transaction Corrections

    Budget transfers and corrections are different from transaction transfers and corrections.

    • Transaction Corrections: When you need to move or correct a transaction that has already occured, such as a purchase that was charged to the wrong account. That represents a transaction correction - and there's a distinct process for that within *Define (See *Define VT6)
       
    • Budget Corrections aka Intra-Account Rebudgeting: Transferring or correcting an existing budget involves moving unspent funds around inside of an account so that the funds are arranged in specific types of spending categories, what we call subaccounts, such as salary, fringe benefits, travel, etc. This is accomplished via the FRMS transfer function. (See FRMS Budget Transfer Instructions, above)
       
      • For sponsored awards, there are often rules regarding which type of funds can or can't be adjusted, how much can be moved around within the account or within specific spending categories. Some accounts don't have any limitations, others do. (See *Define CA3 & Research Administration: Transfers)

     

    Inter-Account Transfers - From One Account to Another

    Transferring some or all of the funds from one account to another represents a Budget Group Transfer. 

    This typically happens with certain types of gift funds (30 accounts) and state funds (aka appropriated, instructional, education and general funds, 14 and 20 accounts). 
    See: Types of Accounts (opens in new tab)
     

    • The university has very specific policy for Budget Group Transfers, including rules about allowability and purpose, and all transfer activity is controlled by Object Codes that 'live' inside of each subaccount and determine types of allowable costs. --the object codes have to match to allow for these types of transfers, assuming transfers are at all allowable on the account. 
       
    • BUDGET GROUP TRANSFERS (between whole accounts) are ALWAYS UNALLOWABLE with SPONSORED FUNDS. Behind each sponsored project, there's a fully executed contract with clear terms & conditions that prohibit this activity. There is no flexibility with this. The university is legally bound by the contracts it signs.
       

    For more information about budget transfers, check out Process Assistance Corrections & Transfers

  • Transfer Instructions Steps 1-8 - Setting Up the Document
    1. Log into FRMS, step through DUO Authentication
       
    2. Click on Transfer in the nav-bar across the top of the site
       
    3. Click on Create in the sub nav-bar
       
    4. Fill in purpose field
      • For sponsored funds, example: 'Moving funds to cover project-related (or research-related) costs'
         
    5. Select which type of transfer: sponsored or non-sponsored
       
    6. Effective date can be changed, though it's rarely used
       
    7. Change Creator Desk available only if assigned to more than one desk in *Define
       
    8. The Read & Confirm statement references your understanding and compliance with the university's Direct Cost policy. The link in the transfer process is broken, but if you need to familiarize yourself with the policy, it's here
       
      • Upon selecting 'I agree,' you land on the first of four areas in the transfer document: 
        • General
        • Transfer Groups
        • Transactions
        • Document Review
           
      • At this point, you can see a summary at the top of the document that contains:

        Document ID: 90VTC######
        Document Status: CREATED
        Creator: Your Name
        Created: MM/DD/YYYY
        Summary: Moving Funds to cover research-related project costs
        Transfer ID: TRF######
        Creator Desk: Your *Define Desk
        Effective Date: MM/DD/YYY
  • Transfer Instructions Steps 9-18 - Transfer Details

     9. The next section is called Transfer Information. It contains the transfer ID (different from the Doc ID), the effective date (which you can still change if needed), the stated purpose, which can also be changed, and then a blank field for comments.
     

    • In the comment section, it isn't necessary to go into a great deal of detail, but any extenuating circumstances should be included here, if applicable, and mention of PI approval for the transfer should be stated here
       
    • Note: If a PI requests the transfer being processed for specific need/purpose, reference that in the comments.

      If the transfer is a result of the admin and PI having a general understanding that admin should process transfers as and when needed in order to keep the account in good health (no negative balances), in concert with any team planning and budget projections being done, then the comment regarding PI approval can be phrased as 'Per PI, transferring funds to ________________.
       

    10. At this point, either Save & Verify or Save & Continue. It doesn't matter which, as FRMS WILL fuss at you if you've gotten something wrong. FRMS has hard audits to make sure a document is completed correctly. 

    • Just below this section is a place to upload documents - this is the perfect place to upload written approval from the sponsor (if applicable) so that the Pre-Award Specialist will 1. be okay approving the request and then 2. will also have the approval on file, which is required.
       
    • Upon hitting Continue, you'll move into the second area of the transfer document: Transfer Groups 
       

    11. In the next step, don't let the red text put you off. You've done nothing wrong. FRMS just comes with built-in unnecessary fussing capabilities. Like a pre-emptive waggling of its finger at you, for the sake of having something to do. 

    • Add your transfer group by starting off with a description, such as 'Misc sub to Fringe sub' to identify the specific transfer activity happening for this group - you're labelling the subaccounts to keep them straight.  


    12. Enter the full 10-digit account numbers you're transferring from and to, followed by the amount.

    13. Hit enter and you'll see details about each of the subaccounts populate inside of that transfer group including the pooled amount, which is the free balance. 

    • If you use dept codes for tracking and reporting, you'll see the hotlink for adding them at this same place. 
       
    • NOTE: If you are processing a transfer for a non-sponsored account (as mentioned back in step 5), at this same place, you will see an error in red text letting you know to input additional information, at which point, you can select the Additional Information link, select the type of funds you are moving -- which is typically the rollover balance from the previous year that reverted back to the income subaccount and needs to be moved back into an expenditures sub. 
       

    14. You can add more transfer groups, if needed. You'll also need to add a transfer group for moving F&A funds, if it's the case that you are transferring funds that have differing exempt and non-exempt status as for as F&A rate goes. --see the formulas tab for more details on that. 

    15. Once you've entered all the transfer groups needed, manually click on the third area that appears in the left-side panel of the page: Transactions

    • This is where you check your math and make sure everything appears as you need it to. 
    • If all is correct, manually click on the fourth and final area of the transfer document: Document Review
       

    16. From the Document Review area, you can review the entire document.

    • Click on the Verify Document button. If the document is correct, a message in green text appears in the top left corner that states, 'The document has been successfully verified.' At which point, you are free and clear to hit the Approve Document button to forward it to its next approver. 
      • You can see the desk and approver information in the router history box, which updates as the document clears each approval level.
         

    17. Just under the Verify Document button is a dropdown menu that gives you additional choices, it needed, including:

    • CPY - Copy to a New Document (which is helpful if you are doing multiple similar transfers)
    • FYI - To send an information copy to someone
    • FYA - To approve and route to a specific person
    • DEL - For deleting a document
    • REC - Recall to my inbox
      • This requires a reason be input into the small box -something like 'Need to correct amount' will do.
         

    18. You'll receive an email confirmation once the transfer goes through.

    • Your PI will get this same confirmation message
       
      • Consider proactively forwarding that same message to your PI along with a short explanation to let them know what it is, to ensure they remain informed. 
         
        • Example:
          'Hi, PI Such-N-Such. There's no action item here for you. I'm moving the funds into the needed subaccounts to handle project-related transactions.'  --this assumes that the PI is expecting you to make these transactions to keep the account healthy and that such transfers are allowable on the account. If the PI wants to be more informed, let them know specifically what is being transferred.

          Always note in the transfer document that what you are doing has PI approval --which assumes that it does. Your PIs should have knowledge of what you are doing, both generally and specifically. PIs are the responsible party for every account in their name. Make SURE they are fine with you moving the funds around as needed, OR get their approval if that's what they prefer.

          Per policy (HBP 2.7.B), PIs are required to review their accounts every month, so the idea of moving funds areound to keep it in good health shouldn't come as a surprise!
  • Accordion 4
    Panel 4. Add body text in this space.
  • Accordion 5
    Panel 5. Add body text in this space.