One system for staff, the business office and the board.
Set up with your district's chart of accounts, approval limits and vendors.
Requests from staff
Teachers and staff request supplies and services against a budget line. Each request is checked against the money left before it goes on for approval.
Approvals and purchase orders
Approval routes by amount, up to the board above its limit. An approved purchase order sets the money aside, and invoices are matched to it before payment.
Reports for the board
Budget against actual by fund, function, object or building, with spent, on order and remaining for every line. Export any report to Excel.
How the money moves.
Every dollar is tracked from the budget line to the paid invoice.
- Request: checked against the budgetA request that would overspend its budget line is stopped before anyone approves it.
- Purchase order: money set asideThe approved amount is encumbered on the budget line, so it can't be spent twice.
- Invoice paid: money released and recordedPaying the invoice closes out the amount set aside and records the actual spending.
- Every change: loggedEach change to a budget, order or invoice records the person, the time and the old and new values.
How it's built.
On the Microsoft stack most district IT offices already run.
Microsoft SQL Server
The money rules run as stored procedures, each in a single transaction. Reports run on indexed views.
ASP.NET MVC
Screens and approval rules live in MVC controllers and services, so approval limits change without touching the database.
REST API and webhooks
OpenAPI documentation, sign-in by client credentials, and change alerts to other systems.
Your servers or ours
Run it on your own Windows and SQL Server servers, or have Consul host it on Google Cloud in the US.