Allovue Budgeting: Setting Up a New Fiscal Year
Purpose
Use this guide to prepare a new Fiscal Year for planning in Allovue Budgeting. The process starts with the creation of a new fiscal-year Scenario and ends when personnel, non-personnel, and supplemental expenses are ready for budget owners.
Important: Complete the following steps in order, when possible. Staffing calculations and budget-owner readiness depend on configuration established earlier in the process.
Phase 1: Create the Planning Scenario
1. Create the new fiscal-year Scenario
Start by creating the Scenario that will represent the upcoming fiscal year.
Fiscal Year-Specific Configuration
Some elements of the planning Scenario are specific to the fiscal year. Before creating a new Scenario, the following elements should be reviewed. Job Types and associated salaries must be updated for the new FY - other elements may use placeholders from previous FYs and be updated later.
-
Job Types and Average Salaries (Required)
-
Navigate to Configuration > Allocate > Job Types
-
Confirm that the upcoming planning year is listed in the table. If job types need to be added, or salaries need to be updated, select Upload Job Types then Download CSV Template to add or update values.
-
-
Enrollment Projections
-
Navigate to Future > Allocations > Enrollment Projections.
-
Select Create Enrollment Projection. Enter Name and Sort Order. Click Save.
-
Navigate to the newly created Enrollment Projection and select the Eye Icon.
-
On the next screen, select Upload Enrollment Projection and then Download the CSV Template.
-
Enter enrollment values and then re-upload the template, following the upload instructions.
-
To add Organization Characteristics or Sub-Enrollment Types, navigate to Configuration > Allocations. On the Organization Characteristics or Sub-Enrollment Page, create the new value and then re-download the Enrollment Projection Template, which will include a new blank column for each Organization.
-
-
-
Assumption Sets
-
Navigate to Future > Allocations > Assumption Sets.
-
Select Create Assumption Set. Enter Name and Fiscal Year. Click Save.
-
Navigate to the newly created Assumption Set, and select View Assumptions from the three-dot menu.
-
On the next screen, select the three-dot menu on a particular assumption and choose Set Assumption Value. Make changes and click Save.
-
-
Revenue Projections
-
Navigate to Future > Allocations > Revenue Projections.
-
Select Create Revenue Projection. Enter Name and Fiscal Year. Click Save.
-
Navigate to the newly created Revenue Projection and select the Eyeball Icon.
-
On the next screen, select Create Revenue Source to enter values manually, or select Upload Enrollment Projection and then Download the CSV Template to create multiple sources via upload following the uploader instructions.
-
-
Historical Comparisons
-
Navigate to Configuration > Allocate > Historical Comparisons.
-
Choose Upload Historical Data.
-
Enter values for historical comparison for the FY preceding the one you are working to create. These values will appear on the Scenario output as a point of comparison. Re-upload the template following the uploader instructions.
-
Option 1: Create a New Scenario
-
Navigate to Future > Allocations > Scenarios area.
-
Select +New Scenario.
-
In the Form, enter Name and Fiscal Year and select an Enrollment Projection. Optionally, you may associate a Revenue Projection, Assumption Set, and Gains and Losses Policy.
-
Click Save.
Option 2: Duplicate Existing Scenario
-
Navigate to Future > Allocations > Scenarios area.
-
On an existing Scenario, select the Duplicate option.
-
In the Duplicate Scenario Form, update the Name and Fiscal Year.
-
Review duplicated elements (Enrollment Projection, Revenue Projection, Assumption Sets, and Gains and Losses Policy) and update values that should change.
-
Create or update enrollment projections for the upcoming year.
-
Review the allocations generated by the formulas.
Adopting a Scenario
Scenarios will be visible only on the Allocate Scenarios page until set as Adopted.
When creating a new Scenario or editing an existing Scenario with the Pencil icon, you may select the checkbox to Set as Adopted Scenario for Fiscal Year. This will connect the indicated Scenario to the Budget Planning module and allow for expenses to be created.
Note: Only one Adopted Scenario is allowed per Fiscal Year. A Scenario may be Adopted and Un-Adopted, but any associated Budgeting Data will no longer be visible to end-users when the Scenario is Un-Adopted. Administrators can still view Un-Adopted Scenarios and associated Budgeting Data.
Phase 2: Prepare Personnel Data
1. Check staffing data before importing
Before running the Scenario Staffing Import, verify that staffing data exists for the period you intend to import.
At minimum, check:
-
Configuration > Staffing > Positions
-
Configuration > Staffing > Assignments
-
Configuration > Staffing > Employees
-
Configuration > Pay > Employee Pay Rates
Compare these records and values to what you reasonably expect based on the current year.
Large unexplained differences, particularly zero or unexpectedly small counts of records, should be investigated before proceeding.
Determine whether future-year Pay Schedules have already been loaded.
-
Navigate to Configuration > Pay > Pay Schedules.
If values are not present in the table for the upcoming fiscal year, use Option A in the Scenario Staffing Import steps below.
If values are present in the table for the upcoming fiscal year, use Option B in the Scenario Staffing Import steps below.
Correct pay-schedule configuration is important because missing schedules or ranges can lead to apparently missing personnel costs.
2. Run the staffing import
Once the Scenario, staffing source data, and pay configuration are ready:
-
Navigate to Future > Pays and Benefits > Scenario Staffing Import. You will see a list of Adopted Scenarios; a Scenario must be adopted for the appropriate Fiscal Year before the Importer can be run.
-
Choose the appropriate configuration for your data:
-
Option A (future-year pay schedule data is not present in Configuration): Start from a Copy of FYXXXX Pay Schedules.
-
This will create a copy of previous-year Pay Schedule data as a starting place for the upcoming Scenario; it can be adjusted via Pay and Benefit Proposals later.
-
-
Option B (future-year pay schedule data is present in Configuration): Only import Pay Schedules active on the selected date. Enter the appropriate date (likely, the start of the upcoming fiscal year).
-
This will import only future-dated Pay Schedule details.
-
-
-
Select Import.
Validate the imported staffing data
Navigate to Future > Budget Proposal.
Two Proposals have been automatically created by the Importer.
Review the Pay and Benefits Proposal first, followed by the All Budgets Proposal.
In the Pay and Benefits Proposal, confirm that:
-
Expected Employee Pays were imported
-
Expected Employee Benefits were imported
-
Expected Vacant Job Pays were imported
-
Expected Benefits Packages were imported
In the All Budgets Proposal, confirm that:
-
Expected positions were imported.
-
Employee assignments are present.
-
Account codes are populated correctly.
-
Note: Pays and Benefits will show as $0.00 on expenses until the above Pay and Benefits proposal is approved.
-
Review several representative records rather than relying exclusively on aggregate totals.
Note: once either of these Proposals has been approved, the Scenario Staffing Import will be disabled for this Scenario. If the data imported looks incorrect, delete the Proposals without Approving in order to make adjustments in Configuration and run the import again.
3. Approve Pay & Benefits, Adjust All Budgets Proposals
From the Budget Proposals page, navigate to the Staffing Import, Pay and Benefits Proposal.
Approve the Proposal. This may require multiple Approvals, depending on your district’s configuration.
Once approved, return to the Budget Proposals page and select the Staffing Import, All Budgets Proposal.
Now that the Pay & Benefits Proposal has been approved, the Personnel Expenses should be populated with Salary information. Review:
-
Filled position salaries
-
Account assignments
Optional: Perform the initial allocation assignment
Once personnel costs are correct, assign personnel expenses to the appropriate allocations. Any personnel expenses not assigned an Allocation and Organization code will be flagged as Unassigned Expenses.
For a district with a large number of expenses, the recommended administrator workflow is to use bulk download/upload rather than assigning every expense manually in the application.
The goal at this stage is not necessarily to make every assignment perfect. Instead, the administrator should make the best initial assignment possible so that budget owners start with a usable budget.
Recommended workflow
-
From the Personnel Expenses tab of the All Budgets Proposal, select Upload Expenses.
-
On the next screen select Click here to download a list of your district’s current codes. This will allow you to reference Allocation codes.
-
On the same screen, download the CSV Template.
-
Assign the appropriate allocation to each expense in Excel by filling in the columns for Allocation code AND Organization code.
-
Upload the completed file.
-
Review upload errors.
-
Correct rejected rows and upload them again as needed.
-
Review the resulting expenses in Allovue.
Note: After saving an upload, error rows can be downloaded for correction.
Excel tip: Be careful with automatic fill and formatting behavior. Excel may interpret account codes or other values as dates or automatically extend a pattern differently than expected. Validate the populated columns before uploading.
Phase 3: Prepare Non-Personnel Expenses
1. Decide how the district will initialize non-personnel expenses
There are several ways to establish non-personnel expenses for a new planning year.
Option A: Carry forward prior-year accounts
Use the prior-year budget to establish the non-personnel account lines available for the new planning year.
This is useful when administrators want budget owners to see familiar accounts and prior-year structure.
Option B: Use actuals or prior-year financial data
Export prior-year financial information and transform it into the non-personnel expense upload format.
This can preserve richer historical detail for budget owners.
Option C: Start budgetable accounts at $0
Upload the district's allowable/budgetable accounts with $0.00 amounts.
This establishes which accounts users may budget against without automatically carrying forward prior-year spending.
This is particularly useful for a more zero-based budgeting approach.
Option D: Let budget owners create their own expenses
Budget owners can create their own non-personnel expenses during planning.
This requires less administrative setup but provides less consistency at the beginning of the budgeting process.
2. Prepare the non-personnel upload
Create a new All Budget Proposal, or add changes to the All Budgets proposal containing Personnel Expenses from the Scenario Import.
From the Non-Personnel Expenses tab, select Upload Expenses. Download the CSV Template.
Uploaded expenses must include:
-
Account string
-
Expense name
-
Amount
Uploaded expenses may optionally include:
-
Description
-
Vendor
-
Organization Code
-
Allocation Code
-
Strategies and Priorities
Any expenses without an Organization Code and Allocation Code will be flagged as Unassigned Expenses.
Use meaningful names
Each non-personnel expense requires a name.
Avoid using a long account string as the name unless necessary. Doing so can create difficult-to-read lists for budget owners.
When possible, use meaningful object, function, vendor, or expense descriptions so users can understand the purpose of the budget line.
3. Validate organization and allocation mappings
Before uploading a large number of non-personnel expenses, confirm that the expected organizations have the appropriate non-personnel allocations.
Watch for:
-
Organization codes that differ from location codes
-
Organizations missing an appropriate allocation
-
Accounts associated with an incorrect fund
-
Inactive or invalid account codes
-
Expenses that cannot be systematically assigned to an organization
Organization and allocation can be left for later assignment where a district cannot determine them programmatically, but pre-populating as much as possible gives budget owners a cleaner starting point.
Phase 4: Configure Supplemental Pay
1. Create supplemental pay types
If the district will budget supplemental expenses:
-
Create the applicable pay types in a Pay and Benefits Proposal for the new fiscal year.
-
Review and approve the pay types as required.
-
Confirm they are available for use in the new Scenario.
2. Upload existing supplemental expenses
After pay types are established:
-
From an All Budgets Proposal, navigate to the Supplemental Expenses tab. Select Upload Expenses. Download the supplemental expenses template.
-
Populate the district's supplemental pay information.
-
Upload the completed template.
-
Review errors and correct rejected rows.
-
Confirm uploaded supplemental expenses display correctly.
There are two valid approaches:
-
Admin-preloaded: Load existing supplemental expenses so budget owners begin with an established baseline.
-
Budget-owner entered: Establish the pay types but allow budget owners to submit the actual supplemental expenses themselves.
Choose the approach that best fits the district's budgeting process.
Phase 5: Complete Administrative Cleanup
1. Review optional configuration changes
Before releasing the Scenario to end users, this is a good time to complete other annual configuration work.
Depending on the district, this may include:
-
Creating new account segments
-
Updating organization/location mappings
-
Reassigning old codes
-
Archiving unused jobs
-
Updating permissions
-
Cleaning up invalid accounts
-
Reviewing allocation configuration
These activities do not necessarily block the core rollover, but completing them before end-user budgeting can reduce cleanup later.
2. Perform a final financial sanity check
Review the new Scenario end-to-end.
Personnel
Confirm:
-
Filled positions have salaries.
-
Vacant positions have expected costs.
-
Benefits calculate correctly.
-
Assignments are accurate.
-
Pay Schedules and steps are correct.
-
Personnel expenses have allocations.
Non-personnel
Confirm:
-
Expected accounts exist.
-
Invalid/inactive accounts have not been added.
-
Expense names are understandable.
-
Organizations and allocations are populated where expected.
-
Amounts reflect the district's selected rollover strategy.
Supplemental
Confirm:
-
Required pay types exist.
-
Existing supplemental expenses were loaded if applicable.
-
Uploaded expenses appear under the expected organizations/allocations.
Scenario configuration
Confirm:
-
Fiscal year is correct.
-
Enrollment projections are current.
-
Allocation formulas are correct.
-
Assumption sets exist.
-
Revenue projections exist.
-
Job-type salaries exist.
Phase 6: Release the Scenario to Budget Owners
Prepare for end-user budgeting
At this point, administrators should have established the basic structure budget owners need.
Before users begin:
-
Resolve significant upload errors.
-
Verify headline totals.
-
Review permissions.
-
Confirm users will be working in the correct Scenario.
-
Make the Scenario available according to the district's budgeting timeline.
-
Provide budget owners with instructions for creating and submitting their detailed proposals.
The goal of administrator preparation is to give budget owners a credible starting point, not necessarily to make every detail final. Budget owners can then make smaller adjustments and proposals during their review.
Final Rollover Checklist
Scenario
- New fiscal-year Scenario created
- Fiscal year verified
- Prior-year reference verified
- Formula copied and reviewed
- Enrollment projections created/updated
Fiscal-year configuration
- Assumption sets created
- Revenue projections created
- Job-type salaries created
- Account/job configuration reviewed
Staffing
- Position count reviewed
- Assignment count reviewed
- Employee count reviewed
- Salary data reviewed
- Import date verified
- Staffing import complete
Pay
- Future-year pay-schedule strategy selected
- Pay Schedules validated
- Pay steps/ranges validated
- Vacancy pay validated
- Personnel costs recalculated and reviewed
Allocations
- Personnel expenses assigned to allocations
- Upload errors resolved
- Organization/allocation mappings reviewed
Non-personnel
- Rollover strategy selected
- Active/budgetable accounts identified
- Non-personnel upload completed
- Expense names reviewed
- Invalid accounts resolved
Supplemental pay
- Pay types created
- Supplemental pay template prepared
- Existing supplemental expenses uploaded, if applicable
Launch
- Headline totals reviewed
- Significant data exceptions resolved
- Permissions reviewed
- Scenario visibility reviewed
- Scenario ready for budget owners
Troubleshooting
|
Problem |
Check first |
|---|---|
|
Employees/positions missing |
Import date and existence of active staffing records in configuration |
|
Salary is blank |
Employee salary data, pay schedule, and pay steps/ranges in configuration |
|
Position has no personnel cost |
Pay schedule, job configuration, account/object code, and recalculation |
|
Vacant position has no dollars |
Vacancy pay and recalculation |
|
Benefits are missing |
Pay/benefit configuration and cost calculation |
|
Personnel expense is unassigned |
Personnel allocation mapping/upload |
|
Non-personnel upload fails |
Account validity, organization, allocation, and required expense name |
|
Expense is assigned to wrong organization |
Location-to-organization mapping |
|
Upload contains errors |
Save the upload and download the error rows for correction |
|
Account codes look different after Excel editing |
Check Excel's automatic formatting/fill behavior |
|
Supplemental pay cannot be added |
Confirm the applicable pay type exists for the fiscal year |
|
Totals appear wrong despite an apparently successful import |
Compare representative positions and accounts to the prior year and validate source configuration |