Specifications include, but are not limited to: 5.2.1 USER EXPERIENCE • Intuitive, user-friendly, and esthetically pleasing for users. • Ability to create user-favorites for frequently used features/functions. • Single sign-on capability through the University ERP system. 5.2.2 BUDGETING DEVELOPMENT AND FORECASTING 5.2.2.1. BUDGET TOOL CORE FUNCTIONS • Departments need to be able to input data into a tool to be manipulated and extracted. • Budget Tool must have Workflow capability (approval hierarchy of users within the group.) • Budget Tool must be able to handle outside allocations. • Budget Tool must be able to spread any changes across all the units. • Budget Tool must allow for transfers between units/chartfields. 5.2.2.2. DETAILED BUDGETING BY CHARTFIELD • Budget Tool must be able to handle full Chart of Accounts (12 segments). • Budget Tool must handle all funds (including CI and Investment funds – non operating). • Budget Tool must be able to handle budgeting down to lowest chartfield level (including account). • Budget Tool must be able to budget by department or group of departments, split by fund type. • Need ability to configure additional fields to be used by departments, to allow for unit specific tracking. 5.2.2.3 POSITION AND PAYROLL BUDGETING • Budget Tool must be able to split personnel salary between multiple chart of accounts. • Budget Tool must be able to perform calculations on payroll and personnel. • Budget Tool must be able to handle multiple employee benefit rates and apply them to less than all pay periods. For example, not applying all benefits to a 3rd bi-weekly in a month or other special payments. • Budget Tool must handle various payroll budgeting scenarios including bi-weekly, monthly payroll, summer school and off-cycle payrolls, prorated by number of pay periods. • Budget Tool must handle calendar of bi-weekly and monthly payroll, allowing for payrolls that cross fiscal years and a 3rd bi-weekly for a month. 5.2.2.4 BUDGET SCENARIOS, HIERARCHY AND VERSIONING • Budget tool must be able to create multiple scenarios before budgets are finalized. • Budget tool must allow new budgets to be created throughout the year based on changes. • Budget Tool must have hierarchy to allow entries to rollup to different chartfield levels. • Budget Tool must be able to create multiple year budgets per cycle. • Budget Tool must accommodate multi-year scenario planning and cost changes to be completed at any level (centrally and departmental). • UNC-CH plans on using this tool as the Budgeting database of record. Please ensure your response speaks to this. 5.2.3 REPORTING, DASHBOARDS, AND ANALYSIS • Budget tool must provide reporting on Budget to actual activity. • Budget tool must allow data to be consolidated/rolled up in multiple ways. • Budget Tool must allow Data trending and reporting by UNC-CH defined periods. Example could include monthly, quarterly, semi-annually and annually. • Allow cash flow planning / reporting using both actuals and commitment funding.
