A complete school district ERP — purchasing, claims, payroll, the general ledger, the ST-3 and the year-end close. Ten statutes are enforced at the door rather than found by an auditor in March, and eight control totals are proved on the screen you are looking at, from the postings, every time you look.
An ERP that keeps a running total keeps a number that can be wrong. Every figure on every screen here — the appropriation, what is expended, what is encumbered, what is left, the fund balance, the §1318 percentage — is computed from the postings at the moment you look at it. There is no total to rebuild, no month-end that corrects last month, and no report that disagrees with the screen it came from.
Every district ERP can produce these answers eventually. The question is whether you get them while the decision is still reversible, or in a management letter nine months later. Left is the pattern districts describe. Right is what this does instead, and each one is on a screen in the demonstration.
Not a compliance report run in March. A refusal at the moment somebody tries, naming the section and the number, while it can still be fixed for nothing.
| Statute | What it decides | Where it fires |
|---|---|---|
| GML §103 | Competitive bidding above the threshold | Raising an order |
| GML §104-b | How many quotes, and written or verbal | Raising an order |
| GML §101 | Separate specifications on public works | Awarding a contract |
| RPTL §1318 | Unassigned fund balance may not exceed 4% | Adoption and close |
| Education Law §1716 | The budget the board actually voted | Amendment |
| 8 NYCRR §170.8 | The administrative component cap | Budget development |
| Education Law §3651 | Reserve funds and what they may be spent on | Funding a reserve |
| Labor Law §220 | Prevailing wage on public work | Claim audit |
| GASB 54 | Fund balance classified to five buckets | Close and reporting |
| 2 CFR §200.501 | Single audit at $1,000,000 of federal awards | Close |
Every control is two sides and a difference, recomputed from the ledger when the page renders. A control that cannot be proved is shown as unprovable — not as passing — which is the only honest way to display one.
Exactly one of the eleven modules owns each object, so there is never a question of which screen is right about a purchase order. The rail is not organised by those eleven: it is organised into nine groups named for what you are doing, because a business official does not think "I need module 4", they think "I need to pay someone".
The person who raised an order may not audit a claim against it. A requisition the business official may approve is one they may not raise. Each rule is a named rule with a citation, and every refusal says which one fired and who can do it instead — because "permission denied" is not an answer somebody can act on.
This product has a rule about itself: a control whose only possible outcome is a refusal does not get drawn. Where a document cannot yet be filed against a record, the screen says exactly why instead of opening a file picker that fails. Where a figure cannot be derived, it reads as unprovable rather than as zero. Where a district has no data yet, the screen says so and says what to do first.
The fastest way to judge this is to load something you already know the answer to and see whether the eight controls agree with you. There is a demonstration district in the product for looking around, and it is clearly labelled as one.
Request a demonstration → Or read the Privacy Policy · Terms · Pricing