Carry forward is used to track cumulative life to date cash (portion of fund balance) that relates to a restricted or dedicated program code from prior year financial activity.

A typical general fund program code is not eligible for carry forward.

Financial Management has made improvements to standardize and simplify the carry forward process and to improve visibility for cost center managers.  This work will continue in Fy26.

Status of FY25 to FY26 Carry forward

Some FY25 to Fy26 ESTIMATED carry forwards were loaded with Fy26 budgets. 

Once FY25 financials are finalized, Financial Management will recalculate carry forwards using final FY25 actuals, and will adjust carryforward budget accordingly.

As of Sept 29, 2025 many carryforwards are on hold until System Office correct FY25 payroll expense (entries went to wrong fiscal year).

Carry forward entries are done as a two sided BUDGET entry.  This will aid in carry forward visibility and future calculations.

• Revenue budget:  49940 Carryforward Reserved for Future Years 
• Expense Budget:  Typically loaded to Nonpersonnel but may vary by program
  • Any Expense budget that exceeds the amount in Revenue budget:  49940 Carryforward Reserved for Future Years, is likely new budget for the current fiscal year. 

Types of carry forwards (and basic calculation)

• Special Appropriation or Earned Revenue (Based on ACTUAL Revenue less ACTUAL expenses - cumulative life to date)
  • Example COLLABS, Mental Health funding, JDA, IT COE, and others
• IFO and MSUAASF Professional Development and Professional Improvement Funds  (based on unspent BUDGET - cumulative life to date)
• Multi-year Facilities projects (Current BUDGET less Commitments/Obligations less YTD ACTUAL expense; in Fy25, Budget Amendment required to make budget visible in eBuilder; this may not be necessary in Fy26.)
• Tech fee (Based on ACTUAL Revenue less ACTUAL expenses - cumulative life to date from FY19 forward, both 218500 and 218550)
• Revenue Funds Student Center and Parking are in separate funds.  However, we are considering carryforward to make cash for operations vs deferred maintenance more visible.
• Other / Ad hoc are rare; typically for a specific expense item or one time revenue less any expenses spent against it in current year
  • Fiduciary example:  Black Men Healing, Mass Incarceration, Mn State IT Conference 2024
  • One time example:  Career fair revenue not spent in current year;  NOTE: This type requires CFO approval and will be rare - Carry forward increases our budget for the new year and essentially uses fund balance.  

More detailed documentation is underway and will be shared here and via email as it develops.