Fiscal tools built inside a district business office.
Every tool here exists because someone who files SACS submissions, ties out funds, and answers to a board needed it to exist. Drop the files you already have, get the answers you already needed, and never upload district data anywhere: everything runs in your browser.
Licensed tools
| Ref | Tool | Annual license |
|---|---|---|
| DFT-01 | SACS Pre-Flight
Drop a SACS Web System export (.dat) and see what the technical review checks will flag before the Official Export does: bad strings, invalid combinations against CDE's current tables, balances that don't tie. Line numbers included. |
Findings free, alwaysopen the tool |
| DFT-02 | Corrections Engine
Every finding as an exact correcting entry: the full 19-digit account string, the amount, and an Excel-ready export. Kept current with CDE's validation tables all year. The license that opens the rest of the catalog. |
$2,000 / district / yr |
| DFT-03 | Fund Balance Health
Every fund's roll-forward, ending balance components, deficit spending flags, and your reserve ratio against the standard. Same file, no new exports. |
Opens with your license |
| DFT-04 | Restricted Resource Risk
Deficit resources, contribution dependencies, oversized and idle carryover balances, ranked by risk before an auditor ranks them for you. |
Opens with your license |
| DFT-05 | Indirect Cost Maximizer
What each restricted program could carry in indirect at your CDE-approved rate versus what's booked, and the headroom left on the table. |
Opens with your license |
| DFT-06 | Actuals Tie-Out Pack
The pre-submission checklist, run automatically: record counts, balance ties, contributions, transfers, cash, and component placement, stamped ready or not. |
Opens with your license |
Why districts trust it
Designed by someone who does this work in a district business office, for the deadlines and forms you actually face: not a vendor's idea of them.
Processing is entirely client-side. District data is never uploaded, stored, or seen by us. Licensing is the only thing that touches a server.
Flat per-district annual licenses, unlimited files and users. Quotes on demand, purchase orders welcome, and a deadline never waits on paperwork.
Filing-season field guides
Short, practical write-ups of the problems that surface when a SACS file meets the technical review checks. Written from the business-office side of the desk.
- TRC fatal exceptions, explained
What Fatal, Warning, and Informational actually mean, and what has to happen before the export runs.
- When the Official Export aborts
The fix, reimport, rerun loop, and how to get through it in one pass instead of three.
- Invalid code combinations
How CDE's seven valid-combination matrices work and how to recode a failing pair.
- Unknown or retired SACS codes
Why a code that posted all year can fail validation, and how to find the right one.
- An ending fund balance that will not tie
The B-series identity behind objects 9700-9790 and the shape of the correcting entry.
- Contributions that do not net to zero
Objects 8980-8999 must sum to zero across the file. Finding the missing side.
- Interfund transfers out of balance
Transfers in must equal transfers out across all funds. Where the missing side hides.
- Negative balances in a SACS file
Negative restricted-resource balances and negative expenditures: which matter and what to do.
- Reading a SACS .dat export
The Other Export file format, field by field, and why it is the right input for early checking.
- Writing TRC explanations that hold up
What a reviewer needs from an explanation, and the wording habits that draw follow-up calls.