School District Position Control and Budget Planning Software: Why the Adopted Budget Never Reconciles to Payroll

The October surprise that was created in April

It is the third week of October. Payroll has run twice against the new fiscal year and your monthly distribution report shows $412,000 charged to the general fund that the adopted budget said would sit in a federal grant. Someone traces it back. A reading interventionist was hired in April into a position that had been vacant for two years. The vacancy was still carrying its old funding split, seventy general fund and thirty Title I, from a grant year that closed. Human resources (HR) filled the position because the requisition existed. Payroll charged what the position record said. Nobody was wrong at any single step, and you are now $412,000 short with eight months to absorb it.

That is the failure mode this category exists to prevent, and it is not a rare event in a district with thousands of employees. Salaries and benefits dominate a school district budget, which means budget accuracy is almost entirely a function of whether every filled and vacant position ties to a funded allocation with a correct split. When it does not, the error is not a rounding difference. It is a full time equivalent, and full time equivalents cost six figures with benefits.

Position control is not a report, it is a constraint

Most districts have something called position control because their finance system has a screen with that name. What they usually do not have is the constraint behaviour: a hiring requisition that cannot be released unless an authorised, funded, currently vacant position exists to receive it, and a position record that cannot silently change its funding split without an approval trail.

The distinction matters because the failure is always upstream of finance. A principal is told at a spring staffing meeting that she gets a half time counsellor. She hires a full time one and covers the other half with a stipend nobody budgeted. A grant coordinator moves a coach from Title I to Title II in the middle of the year because the Title I allocation is running hot, and tells nobody in budget. Neither of these people is misbehaving. They are working around a system that records decisions rather than enforcing authorisations.

Split funded positions and the audit finding waiting to happen

The hardest object in this whole category is a person paid from four sources. A bilingual instructional coach might sit thirty percent general fund, thirty percent Title I, twenty five percent Title III, and fifteen percent a state grant. Federal funds carry time and effort documentation expectations, so the split on the position record must agree with the semiannual certification or the personnel activity report on file, and both must agree with what payroll actually distributed.

In practice these three numbers drift within weeks of the school year starting, because the split is entered once and the reality changes. A custom build treats the split as a versioned, effective dated object with an approval workflow, ties each version to the grant period that funds it, and refuses to let a split extend past the end of a grant award. It also produces the reconciliation that a single audit asks for without anyone rebuilding it: for this position, in this month, here is the authorised split, here is what payroll charged, here is the variance and its reason.

Salary schedules are the projection engine, and nobody else models yours

Your salary schedule is a specific grid of steps and columns with your own advancement rules, your own longevity increments, your own stipend table, and your own eligibility conditions for column movement based on credits earned. Projecting next year's salary cost means walking every employee across that grid, applying the rules that actually govern advancement, layering benefit rates that change by tier and by plan election, and doing it again for the two out years your board wants to see.

Finance systems compute the current year correctly because that is a payroll calculation. What they do not do is project across years with your advancement rules and produce an employee level result you can drill into. That is why almost every district in the country has a budget analyst maintaining a workbook with thousands of rows, one tab per bargaining unit, and a set of formulas only one person understands. That workbook is the real budget system, and it walks out of the building when its author retires.

What Tyler, Skyward, Frontline, Allovue and Forecast5 actually do and do not do

Tyler Technologies and Skyward are systems of record. They are strong at transactions, general ledger integrity, payroll processing, and encumbrance, and if your requirement is bookkeeping they are the answer. What they are not built for is planning: multi year projection over your specific salary grid, scenario branching, and staffing allocation from enrollment. Their position control is transactional and current year oriented, which is why the workbook exists alongside them.

Frontline ERP (Enterprise Resource Planning) covers human resources and finance together, which helps with the requisition to position link, though districts consistently tell us allocation formula configuration is narrower than their staffing rules require. Allovue is a genuinely useful planning and visualisation layer, particularly for pushing budget down to school leaders and showing funding source composition, but it sits over your ledger and does not replace employee level step and column projection. Forecast5 is good at multi year forecasting and peer comparison, and it works at fund and object level rather than at the individual position level, which is precisely where the phantom position problem lives.

None of these criticisms are about product quality. They are about level of granularity. The position is the unit of a school district budget, and most of the market models the account code instead.

Staffing allocation and the settlement scenario your board will ask for

Every spring you run allocations: enrollment projection by school and grade, class size rules from the contract, programme driven staffing for special education and English learner services, then a negotiation with principals about the edge cases. It is done in a workbook and it produces the position roster for next year.

Then in July your board asks what a three percent settlement with a one step schedule adjustment costs across three years, including the benefit rate increase and the effect on the state minimum requirement. In most districts the answer takes a week and comes back as a single number nobody can decompose. A build changes that into a scenario: clone the baseline, apply the settlement parameters, and get the cost by year, by fund, by bargaining unit, with the ability to compare two scenarios side by side in a board meeting. Districts that have this negotiate differently, because they can price a proposal in the room instead of promising to get back to the table.

What a custom build has to include

• Authoritative position records with status, full time equivalent, salary placement, and effective dated funding splits
• Requisition gating so hiring cannot proceed without a funded, vacant, authorised position
• Grant award periods that constrain how long a split may run, with expiry warnings before the fiscal year turns
• Salary schedule engine covering steps, columns, longevity, stipends, and advancement eligibility, versioned by bargaining unit and by year
• Benefit rate modelling by plan and tier, including employer contribution changes
• Enrollment projection input with class size and programme driven staffing allocation rules
• Scenario branching for settlement modelling with side by side comparison and multi year output
• Monthly reconciliation of adopted budget to actual payroll distribution, with variance reasons at position level
• Chart of accounts mapping to your state's required structure, since state reporting will not accept your internal codes
• Bidirectional synchronisation with the finance and human resources system of record so the ledger stays authoritative for actuals

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this is the honest shape for district budget work. A first release covering position control with requisition gating, split funding with grant period constraints, and salary schedule projection runs $90,000 to $180,000 and ships in 16 to 22 weeks. That timeline is longer than most categories because the first eight weeks are spent extracting rules that exist only as practice, and because you must land before your budget development calendar starts, not during it.

The full platform adding allocation, scenarios, and payroll reconciliation runs $250,000 to $600,000 phased over 9 to 15 months. Cost climbs with the number of bargaining units, since each carries its own schedule structure and advancement rules. It climbs with the age of your finance system, because an on premise Tyler or Skyward instance often means database level integration and a negotiated interface rather than an API. It climbs sharply if you want write back into the ledger rather than one way reads, which we usually advise against in phase one. It comes down if you accept that the finance system stays the system of record for actuals and your build owns planning only.

Build versus buy, stated plainly

Do not build if you are under about 500 employees, run largely on general fund with a handful of grants, and have one or two bargaining units. Your finance system's position control plus a well maintained workbook is proportionate, and a custom platform would be a maintenance obligation you do not need.

Build when two or more of these are true. Your budget is above roughly $150 million. You have three or more bargaining units with materially different schedule structures. More than about a fifth of your staff is grant funded or split funded, which makes time and effort reconciliation a recurring audit exposure. You have taken an audit finding on personnel charges in the last three years. Your entire multi year projection depends on one analyst's workbook. Or you are a county office, regional service agency, or charter management organisation running budgets for multiple entities, where multi tenancy alone rules out most options.

How to choose a developer for district budget software

Ask them to draw the data model before you sign anything. The right drawing has position as its own entity distinct from employee, because a position exists while vacant and an employee can hold parts of several. If they draw employee and account code and nothing between, they will build you a reporting tool and you will still have the workbook.

Ask how they handle an effective dated funding split change applied retroactively to September in the following January, which happens every year when a grant award arrives late. Ask what happens to two scenarios when the baseline changes underneath them. Ask specifically whether they have integrated with your finance system, by name and by version, and what the interface actually was: an API, a nightly extract, or direct database access with a negotiated schema.

Ask who owns the code and the cloud accounts, in writing, before kickoff. At Digital Heroes the district owns the repository from the first commit and can hire anyone to continue the work. Anyone reluctant to put that in the contract is selling you a dependency, and districts in particular pay for those dependencies for a very long time.