Classification Is Only Half the Battle
You can classify a fund perfectly and still have a broken system.
Many districts spent the last few years moving student activity funds from fiduciary buckets to the general fund, or to a special revenue fund, to comply with the administrative involvement rule. But recording what happened after the fact in accounting software or on a spreadsheet does not fix a weak workflow.
If your process still relies on “we’ve always done it this way,” email approvals from a principal, and a file cabinet full of faded receipts, you have not actually implemented GASB 84. You have just renamed your risk.
The real danger is not where the money sits at year-end. It is what happens on a Tuesday morning in October when an advisor spends $500 before getting approval.
Control is not something you declare in a board policy or a footnote in your financial statements. Control is something your process either demonstrates or it does not.
Why the Workflow Is the Real Audit Trail
GASB 84 pushed districts to acknowledge administrative control. If you acknowledge control, you should be able to prove it.
In the real world, control looks like a clean, defensible lifecycle for every dollar:
The Request: Can you prove who asked for the funds and why?
The Approval: Is there a clear, role-based authorization that happened before the money moved?
The Evidence: Is the documentation—receipts, invoices, meeting minutes—tied to the transaction, or is it floating in someone’s email or sitting in a desk drawer?
When the process is weak, the accounting team spends months playing financial archaeologist, trying to reconstruct the intent of a transaction after the fact. When the process is strong, the district is not just recording transactions; it is managing them.
In practice, this means districts need systems that require requests before spending, route approvals to the right people, connect documents to each transaction, and preserve a clear record of who did what and when. With this structure in place, control becomes something the district can demonstrate.
Moving from Recording to Managing
For decades, school systems were designed to answer one question: How do we record this? GASB 84 forces us to ask a better one: How do we prove this was handled under district oversight?
That shift changes what a good system looks like. A good system should not just capture a final dollar amount for a report. It should define responsibilities, make approvals visible, reduce the ambiguity that leads to audit findings, and serve as the audit trail.
If staff consistently find the process confusing, that usually points to a control problem in the system, not a people problem. If bookkeepers are guessing at the purpose of a transfer, that is a control failure. If the approval for a payment is somewhere in an inbox, that is a control failure.
Control Is a Verb
Control is not something you declare in a board policy or a footnote in your financial statements. Control is something your process either demonstrates or it does not.
The real opportunity of GASB 84 is not better year-end analysis. It is the chance to fix the day-to-day operations that keep school business officials up at night. Districts that get this right will not just satisfy auditors. They will build systems that are defensible, transparent, and, most importantly, easy for their people to follow.
The standard did not just change where the money goes. It changed our responsibility for how it gets there.
Compliance is no longer just a year-end cleanup exercise. It is a digital workflow of requests, approvals, documentation, and oversight that begins before the first dollar is spent.
That is the difference between accounting for what happened and managing the process.