How schools and universities can minimize operating costs and optimize spending in 2026

Federal pandemic relief for K–12 finished liquidating in February 2026, and districts are now building budgets without it. McKinsey projects that fears, a decline of roughly $24 billion, while per-pupil spending stays flat in nominal terms through 2026–27.

The effects are already visible at scale. As of May 2026, more than half of the 50 largest school districts in the country are managing cuts or deficits, and nearly 30 of them cite declining enrollment as a driver. Broward County is closing six schools and cutting 1,000 positions against a $90 million shortfall. Chicago Public Schools is working through a deficit above $730 million. In higher education, the demographic contraction that has been forecast for a decade is now arriving, with the college-age population projected to shrink around 15 percent between 2025 and 2029.

What makes this difficult operationally is not the size of the reduction. It is that spending authority in most institutions is distributed across departments, campuses, and individual schools, while budget accountability sits centrally. Purchases are made by people close to the need and reviewed by people who see them weeks later, often at reconciliation. When funding tightens, that lag is what turns a manageable variance into a mid-year problem.

This guide covers where recoverable cost actually sits in an institutional purchasing process, and how visibility, automation, and policy control at the point of request change the outcome.

The short answer: where the recoverable money actually is

Most institutions cannot cut their way to balance through headcount and program reductions alone, and the savings that remain are rarely dramatic line items. They sit in purchases the institution was always going to make: duplicate vendors, off-contract buying, unused negotiated pricing, retroactive approvals, and reimbursement cycles that consume administrative hours. These are recoverable without touching instruction, but only if spending is visible before it is committed rather than after.

The sections below work through that in the order the money moves: how work gets done, where purchasing happens, what leadership can see, who you buy from, how staff get reimbursed, how budgets are checked, and what the audit record looks like at the end.

Cutting costs starts with cutting manual work

Manual purchasing steps are a cost in themselves, and they are the first place to look. Before evaluating technology, map the purchasing process from request to payment: how many approvals are required, where requests stall, and how many staff hours go to chasing documentation and following up on status.

That mapping usually surfaces a specific pattern. Requests move through email and shared documents, approvers are identified informally, and no single record shows where a request currently sits. Staff spend time reconstructing status rather than processing work, and the same question gets asked repeatedly across departments.

Automated purchasing workflows replace those repetitive steps with a defined path. Each request enters one system, routes to the right approver based on rules the institution sets, and carries its own status. Finance stops assembling the picture manually because the picture is a byproduct of the process.

Work smarter from anywhere

Purchasing does not stop when staff leave campus, and access is the constraint that decides how fast approvals move. Administrators approve requisitions between meetings, staff make time-sensitive purchases for classrooms and facilities, and finance teams reconcile across multiple sites.

When approvals depend on someone being at a desk, requests queue behind availability rather than priority. During closing periods and at the start of terms, that queue is where delay accumulates.

With mobile-friendly, cloud-based access, requests can be raised, reviewed, and approved from any device. Receipts and supporting documents are attached at the point of the transaction rather than reconstructed later, and automated notifications tell approvers what is waiting without a follow-up email.

Turn visibility into control

Visibility only reduces cost when it arrives before the commitment, not after. Spending data that surfaces in a month-end report describes decisions that have already been made. Spending data that surfaces at the point of request is still actionable.

The distinction matters most under the conditions districts and institutions are operating in now. When per-pupil funding is flat and enrollment is moving, the ability to redirect funds mid-year depends on knowing what has been committed but not yet invoiced.

Fraxion gives administrators a single view of purchasing activity across requisitions, approvals, and payments, with budget tracking, reporting, and a complete audit trail. Committed spend is visible alongside actuals, so available budget reflects what has been promised rather than only what has been paid.

Buy smarter with approved vendors

Off-contract buying is one of the most reliably recoverable costs in education procurement. When departments buy from whoever is convenient, institutions accumulate duplicate suppliers, pay inconsistent prices for the same goods, and fail to hit the volume thresholds that negotiated agreements are built around.

This is particularly acute in multi-site environments. A district with dozens of schools, or a university with independently operating departments, can hold a strong negotiated agreement that a meaningful share of its actual purchasing never touches.

Approved vendors can be loaded directly into the system with category and location-specific permissions, so the approved option is also the easiest one to select. Vendor-provided catalogs and PunchOut integrations hold negotiated pricing and institutional discounts at the point of purchase, which is where the savings are either captured or lost.

Simplify expense claims without losing accountability

Out-of-pocket spending by staff is common in education, and slow reimbursement raises both administrative cost and policy risk. Teachers and staff regularly pay for classroom and program needs directly. When the reimbursement process is slow or unclear, submissions arrive incomplete, late, or outside policy.

The administrative cost of correcting those submissions is usually larger than the reimbursements themselves, and the resulting records are the ones auditors examine most closely.

Receipts can be uploaded from mobile devices at the time of purchase, approvals follow the same routing rules as other spending, and each claim is linked to a budget and cost center. Staff get predictable turnaround, and finance gets complete records without a correction cycle.

Build budgets into every decision

A budget check is most useful at the moment of request, when the decision can still change. When requesters can see available funds before submitting, the conversation about affordability happens before a commitment exists rather than after an invoice arrives.

Budget validation can be enabled at the requisition stage, so requests are checked against available funds as they are raised. Requests that exceed available budget can be flagged or routed for additional approval, and approved purchases update committed spend so the remaining balance reflects real obligations. Institutions configure how strict that check is, which matters in environments where some funding sources carry restrictions others do not.

Grant-funded and categorically restricted spending benefits most here, because the cost of discovering an ineligible charge after the fact is not just the charge itself but the reporting correction that follows.

Make compliance a byproduct of the process

Compliance holds up better when it is produced by the workflow than when it is assembled for the audit. Purchasing in education is decentralized by design, and maintaining consistent documentation manually across schools, departments, and funding sources is where most institutions lose ground.

When each transaction follows defined approval rules and the system records what happened at each step, the audit record accumulates as work is done. Preparing for a review becomes a retrieval task rather than a reconstruction project.

That record supports the school-level per-pupil expenditure reporting states have published on report cards annually since the 2018–19 school year underESSA section 1111(h)(1)(C)(x), as well as institutional grant reporting and internal transparency obligations to boards and communities. Fraxion maintains that record from the first request through final payment.

Bringing it all together

Cost control in education comes from connecting people, processes, and technology around the same objective rather than from reducing what institutions deliver.

• People: Give staff purchasing tools that show budgets, approved vendors, and policy rules at the point of decision, so the compliant choice is also the straightforward one.
• Processes: Standardize how the institution requests, approves, and reports on spending, so records are consistent across sites and departments without individual interpretation.
• Technology: Choose a system that applies controls at the point of request, works alongside your existing finance system rather than replacing it, and scales across campuses without adding administrative overhead.

Fraxion connects those steps from requisition through payment, giving finance teams visibility into committed spend, reducing administrative time for staff, and producing an audit-ready record as a byproduct of normal work. Where institutions integrate with an ERP or accounting system, Fraxion extends it rather than replacing it, leaving the system of record in place for posting and reporting.

See how Fraxion helps schools and universities control spending before it is committed.

FAQs

What is the most effective way for schools and universities to cut operating costs in 2026? The most recoverable savings are in purchases the institution is already making: duplicate vendors, off-contract buying, unused negotiated pricing, and administrative time spent chasing approvals and documentation. Capturing them depends on seeing spending at the point of request rather than at reconciliation. Fraxion supports this by routing requests through defined approval rules, applying budget checks at the requisition stage, and holding approved vendor catalogs where staff make purchasing decisions.

How should districts adjust purchasing now that ESSER funds have been fully liquidated? The main adjustment is moving from allocating one-time funds to controlling recurring spend. ESSER-era purchasing was often planned centrally against a defined pot of money, while ongoing operational spending is distributed across departments and harder to see. Districts that tighten requisition and approval processes gain visibility into that distributed spending, which is where variance now originates.

Does procurement software replace our existing ERP or financial system? No. Procurement software manages the process before a transaction reaches the financial system: requests, approvals, budget checks, and purchase orders. The ERP or accounting system remains the system of record for posting transactions and producing financial statements. Where institutions choose to integrate the two, approved transactions carry consistent coding into the ERP, though many organizations run procurement software alongside their financial system without a direct integration.

How does this work across multiple schools, campuses, or departments? Approval rules, budgets, and vendor permissions can be configured by location, department, and category, so each site operates under its own structure while leadership retains a consolidated view. This is the main practical difference from managing purchasing in spreadsheets and email, where each site's process develops independently and consolidation happens manually.

Can we control spending on grant-funded and restricted budgets specifically? Yes. Budget checks can be applied at the requisition stage against the specific funding source, and each transaction is coded to its budget and cost center as it is raised rather than assigned afterward. This matters because the cost of an ineligible charge on restricted funding includes the reporting correction, not just the charge.

Will implementing this create more administrative work for teachers and staff? The intended effect is the opposite, though it depends on configuration. Staff submit requests through one defined path instead of assembling emails and forms, attach receipts from a mobile device at the time of purchase, and can see status without following up. The administrative reduction is largest in reimbursement processing, where incomplete submissions and correction cycles consume the most finance time.

How does this support ESSA and other transparency reporting? Each transaction carries its approval history, coding, and supporting documents in one place, so the underlying detail behind reported figures is retrievable rather than reconstructed. States have published school-level per-pupil expenditure data on report cards annually since 2018–19 under ESSA section 1111(h)(1)(C)(x), and institutions face parallel obligations to boards, grantors, and communities.

What should we look for when evaluating procurement software for an educational institution? Prioritize controls that apply before commitment rather than reporting that describes it afterward: budget validation at the requisition stage, approval routing configurable by site and category, approved vendor catalogs with negotiated pricing, and mobile access for approvers who are not at a desk. Then confirm the audit record covers what your reporting obligations actually require, and that the system works alongside your existing financial system rather than requiring you to replace it.