School & University Procurement System
Budget controls, cost centers, approval limits, and departmental requests — designed for education institutions that need accountability without bureaucracy.
Start free trial →the problem
Sound familiar?
Departments overspend without visibility
Each department raises POs independently. The bursar only sees the total when invoices arrive at month-end.
Approval chains are inconsistent
Some purchases get signed off by email, some by paper form, some not at all. There is no single source of truth.
No cost center tracking
Kitchen, sports, science lab, and admin all buy from the same suppliers — but nobody can split costs accurately.
Reimbursement chaos
Staff buy things out-of-pocket and submit paper receipts weeks later. Finance cannot reconcile in time.
the solution
How Mise solves it
Cost center budgets
Assign monthly budgets per department. The system tracks allocated, committed, and spent — live.
Tiered approval limits
Set dollar thresholds per role. A department head can approve up to $500; anything above routes to the bursar.
Departmental request workflow
Any staff member raises a request. It routes to the right approver based on department and amount — no confusion.
Market buy & reimbursement
Staff snap a receipt photo for out-of-pocket purchases. OCR reads the total, logs it against the cost center, and queues reimbursement.
How it works against a budget
Education procurement is spending someone else's money against a line agreed months earlier, and the binding constraint is rarely the price of an item. It is whether this request, from this department, still fits what that department has left.
Cost centres make that answerable. Each department has its own centre and its own monthly budget, and the money moves through four states you can see at any point: allocated, committed, spent, remaining. A request that would breach the line is caught before the order goes out, not discovered in a reconciliation.
Approval limits sit on the person, not on the role alone. A department head can approve up to their ceiling; past it the request escalates instead of quietly proceeding. Twelve capabilities can be set per user, so a long-serving storekeeper and a new one need not carry the same authority.
All of it ends up as a record with a reason attached, which is what makes the annual conversation with finance short. The question is usually not whether the money was spent, but whether anyone can show why — and that is exactly what the log holds.
related
Explore more use cases
Ready to take control?
14-day free trial · no credit card required · set up in minutes