Money with a purpose attached
Every school holds at least a little money that isn't really theirs to spend as they see fit. Parents pay in instalments for a specific residential trip. A PTA raises funds for a specific piece of playground equipment. A sports club collects termly subs meant only for that club's costs. None of it is the general budget, even though all of it, in most schools, sits in the very same bank account as the money that is.
That distinction — between money the school can spend on anything appropriate and money that carries a stated purpose — is what “restricted funds” means in practice. It matters far more than the label suggests, and this article explains why, using the situations that actually come up in a typical school year rather than the abstract accounting definition alone.
What makes a fund restricted
A fund becomes restricted the moment it's given, raised or collected with a stated purpose attached — a parent paying instalments specifically for a named trip, a donor giving specifically toward a named piece of equipment, a grant body attaching explicit conditions to how their money can be used.
The purpose is what defines the restriction, not the amount, the source, or how the money is physically held. A five-pound club subscription is restricted in exactly the same sense as a five-thousand-pound trip fund — both carry an expectation about what they'll be spent on, and both deserve to be tracked against that expectation.
Why funds end up mixed in the first place
Almost nobody sets out to mix restricted and unrestricted funds deliberately. It happens gradually, because both sit in the same account, because a general finance person handles all of it, and because the day-to-day pressure of running a school rarely leaves room for a separate accounting process for every small fund.
A common pattern: a trip fund runs slightly short right before a deposit is due, and the general budget quietly covers the gap “temporarily”, with every intention of reimbursing it once the remaining parent payments come in. Reasonable in the moment, and exactly the kind of thing that becomes invisible the moment nobody tracks it explicitly — the reimbursement either happens and nobody notices, or it doesn't happen and nobody notices that either.
None of this happens out of carelessness. It happens because tracking a fund separately takes a small amount of ongoing discipline, and that discipline is the first thing to slip when a school year gets busy — which, for most schools, is most of the year.
What actually goes wrong
A donor or PTA asks where their money went
Without a tracked balance, answering means reconstructing months of transactions by hand under time pressure.
An audit flags unexplained transfers between funds
Even innocent, well-intentioned covering of a shortfall looks irregular without documentation explaining it.
A trip or fund runs out of money mid-way through spending
If the balance was never tracked separately, nobody notices it's depleted until a payment fails to go through.
Governor reports become harder to prepare and less trustworthy
Fund balances have to be reconstructed from scratch each time instead of pulled from an ongoing record.
The second is the one with the sharpest, most immediate cost, and the next section puts real numbers behind it.
A term, traced
A secondary school, one term, three active restricted funds running alongside the general budget.
| Fund | Raised | Spent | Balance |
|---|---|---|---|
| Ski trip fund | $41,200 | $38,900 | $2,300 |
| PTA playground appeal | $6,850 | $0 | $6,850 |
| Football club subs | $1,140 | $980 | $160 |
Three funds, each with a clean, traceable balance at any point in the term — not because the accounting is exotic, but because every deposit and payment was tagged to its fund the moment it was read, instead of reconstructed at the end of term from a general ledger that never distinguished them.
How to keep funds separate without separate accounts
Opening a dedicated bank account for every fund is one way to enforce separation, but it's heavy — extra admin, extra reconciliation, extra bank fees for what might be a fund worth a few hundred dollars a term. Most schools don't do this, and don't need to.
What actually works is tagging every deposit and payment with the fund it belongs to at the point it's read, and keeping a running balance per fund inside the same reconciliation used for everything else. The money stays physically together; the accounting stays logically apart.
Scenario: the oversubscribed trip
A popular residential trip fills beyond its planned capacity, and the school opens a small waiting list, collecting deposits from waiting families in case a place opens up. Some of those deposits eventually need refunding when places don't materialise; some convert into full payments when they do.
Without fund-level tracking, distinguishing a confirmed trip payment from a waiting-list deposit — and knowing exactly which waiting-list deposits still need refunding at the end of the process — becomes a manual reconstruction task, done under time pressure once the trip is finalised and parents start asking.
With payments tagged by status as well as fund, the waiting list resolves itself as a filtered view of the same data — no separate spreadsheet, no separate reconciliation, just the same fund tracked with one additional field.
Scenario: the PTA-funded playground
A parent-teacher association raises money over an entire school year specifically for new playground equipment, through bake sales, a sponsored event and direct donations, all paid into the school's account because the PTA doesn't hold its own.
A year is a long time for a fund to sit untouched inside a general account without dedicated tracking — long enough for the original purpose to blur, for a well-meaning but undocumented “borrow” against it to happen, or for nobody to be entirely sure of the running total when the PTA finally asks for an update.
Tagged from the first donation, the fund's balance is always available on demand, and the PTA gets a clear, immediate answer instead of a promise to “check and get back to you”.
What schools actually do about it
| Situation found | Typical response |
|---|---|
| A shortfall covered informally by the general budget | Document the transfer explicitly and set a repayment date, rather than leaving it unrecorded |
| A high-value, long-running fund like a PTA appeal | Tag every transaction from the start and report the balance termly to the group involved |
| Many small club and trip funds | Track them together in one tagged reconciliation rather than a separate process per fund |
| Uncertainty about whether something counts as restricted | Check the original communication — an appeal letter, a grant agreement — for the stated purpose |
None of these responses require rethinking the school's entire financial process — they're targeted, specific corrections, made possible only once the problem has actually been identified rather than just vaguely sensed.
What all four responses have in common is that they turn an implicit, unspoken assumption into an explicit, written decision. That single shift — from assumed to documented — is usually enough to satisfy a governor or auditor, even before any deeper process change happens underneath it.
Three schools, three levels of separation
The same set of restricted funds, tracked with three different levels of rigour.
| School | When it discovers a problem | Room to act |
|---|---|---|
| A — no fund tracking | During the audit, or when a parent group asks directly | None — decisions made under pressure |
| B — informal awareness, no records | Sometimes, if someone happens to remember | Limited — little documentation to fall back on |
| C — fund-tagged reconciliation | As soon as a fund's balance looks unusual | Wide — time to correct before it becomes an issue |
School A faces exactly the same underlying risk as School C — the difference isn't the funds themselves, it's the amount of time available to notice and correct a problem before someone outside the school notices it first.
Common mistakes
Treating every deposit as general income
Loses the fund it actually belongs to the moment it hits the account, making it hard to reconstruct later.
Building a fund tracker once and never updating it
A fund balance that isn't reconciled against real transactions each period drifts from reality quietly.
Covering a shortfall informally, without a record
Turns a reasonable short-term decision into an undocumented, unexplainable transfer at audit time.
Assuming small funds don't need the same rigour as large ones
A small trip fund with an unexplained shortfall raises exactly the same governance question as a large one.
Waiting for the annual audit to check fund balances
By then, a problem has had a full year to grow before anyone notices it.
Most of these mistakes share a single root cause: treating fund tracking as a project to complete once rather than a habit to repeat every period. A fund tracker built once and left alone drifts from reality in exactly the same way an untracked fund does — just more slowly, and with a false sense of confidence attached to it.
Building a simple routine
None of this requires a full overhaul of how a school manages its finances. A short, written routine covering four points is enough for most schools to move from “we think it's fine” to a concrete, checkable number.
How each restricted fund is tagged, in terms anyone in the finance team can verify.
How often the balance is reviewed — termly at minimum, more often for high-turnover funds.
Who owns the decision when a fund looks over- or under-spent relative to its purpose.
What the default action is if a shortfall appears — even 'covered informally, repaid within one term' is a legitimate answer, as long as it's written down rather than assumed.
Four sentences, and the difference between a school that occasionally notices its funds have blurred together and one with a concrete routine for catching it early.
Why governors and auditors care
A governing body reviewing termly accounts isn't just checking that the school hasn't overspent — part of its role is confirming that money given or raised for a specific purpose was actually used for that purpose, which is precisely the question a general budget total can't answer on its own.
An auditor asks the same question more formally, and expects it answered with records, not recollection — a transfer between a restricted fund and the general budget that isn't documented reads as irregular, regardless of how innocent the original intention was.
For an academy trust preparing statutory accounts, this isn't optional context — restricted and unrestricted funds typically need to be reported separately under the applicable accounting framework, which means the underlying tracking has to exist well before the accounts are actually prepared, not reconstructed retroactively in the weeks before the deadline.
The gap between these two positions — reconstructing records retroactively versus having them ready — is exactly where most of the stress around a statutory audit actually comes from. Schools that keep fund tracking current all year round routinely describe their audit as a formality; schools that don't describe it as a fire drill.
Which side of that gap a school ends up on is rarely about resources — it's about whether fund tracking happens weekly, in small increments, or gets attempted all at once, months after the fact, when nobody quite remembers the details anymore.
That single choice, made consistently or not, explains most of the difference between the two experiences — and it costs little to make correctly from the very first term, well before any fund has had the chance to drift far enough to matter.
How this differs by school type
An academy or independent school preparing its own statutory accounts faces this as an explicit reporting requirement, with a defined framework for what counts as restricted and how it should be presented. The tracking described in this article isn't optional there — it's the groundwork the formal accounts are built from.
A maintained school within a local authority often has a lighter formal reporting burden, but the underlying practical need is identical — governors, parent groups and the school itself all benefit from knowing, at any point, what a specific fund's balance actually is, independent of what the statutory reporting framework technically requires.
Neither situation calls for a different tool to track funds — the method stays the same, reading deposits and payments and tagging them by fund. What changes is how formally that tracking eventually needs to be presented, and to whom.
A school that finally traced its funds
A mid-sized secondary school had never formally separated its restricted funds — the business manager kept a rough mental sense of what the trip fund and the PTA fund held, cross-checked occasionally against the bank balance, but with no ongoing record either group could review on demand.
Building a tagged reconciliation for the current term, following the method described above, took an afternoon the first time — reading every deposit and payment for the term, tagging each one by fund where a fund applied, and reconciling the results against a bank statement. The result surfaced something nobody had noticed explicitly: the football club's subs fund had been running a small deficit for two consecutive terms, quietly covered by the general budget each time without anyone flagging it.
With the deficit identified and quantified, the school raised subs slightly for the following term and the fund returned to balance within one term. The same tagged reconciliation, repeated each term going forward, now surfaces this kind of drift automatically instead of relying on someone happening to notice.
What made the difference wasn't a more sophisticated accounting method — it was simply having the question answerable at all. Before the tagged reconciliation existed, nobody had a wrong answer to “is the football fund in deficit” — they had no answer, because the data to form one had never been assembled in one place.
The role of refunds
Restricted funds don't only receive money — they frequently need to pay some back. A trip that gets cancelled or downsized, a family that withdraws after paying a deposit, a club that overcollects relative to its actual costs, all produce refunds that need to come out of the same fund the money originally went into, not out of the general budget.
Without fund-level tracking, a refund often gets processed correctly from the bank's perspective — the money leaves the account — but incorrectly from the fund's perspective, because nothing records which fund the refund should be debited against. The fund's balance then silently overstates what's actually still available.
Tagging refunds the same way as original payments — against the fund they belong to — keeps this from happening. A trip fund's balance after refunds reflects exactly what's left to spend on the trip, not an inflated figure that assumes every payment ever received is still sitting there.
Refunds also deserve the same source-document discipline as original payments — a bank statement line showing money leaving the account should be read and matched to the specific family and fund it belongs to, not assumed correct because the amount looks roughly right. A refund sent to the wrong family, or debited against the wrong fund, is exactly the kind of small error that a payment-level record catches and an aggregated total never would.
What a fund's history teaches you
A single term's snapshot of a fund answers an immediate question. A history built across several years answers a different, more useful one: does this fund reliably raise enough to cover its purpose, or does it structurally run short every year, papered over by an informal transfer that nobody ever quite closes the loop on?
Building that history doesn't require a separate project — it's simply the same termly tagged reconciliation, kept rather than discarded once used. Each term adds a data point that, added to the ones before it, reveals a pattern a single term in isolation never could.
Schools that reach two or three years of this kind of record often describe the same experience: the first time a fund runs short is a surprise, the second time starts to look familiar, and by the third it's simply a known, budgeted part of how that fund behaves — worth pricing into next year's subs or trip cost rather than covering quietly again.
That same multi-year record is also what makes a genuinely new problem easy to distinguish from a familiar, already-priced-in one — a fund that suddenly deviates from its usual pattern stands out clearly against a known baseline, in a way it never could against a single term viewed in isolation.
What we don't do
We don't decide what counts as restricted
That depends on your school's specific arrangements — an appeal letter, a grant agreement, a governor decision. A document reader has no basis for making that call.
We don't decide how to resolve a fund shortfall
Repayment plan, budget adjustment, a conversation with the PTA — those stay decisions for the school, not something a tool decides automatically.
We don't prepare statutory accounts
We read the bank statements and payment records that the underlying fund tracking is built from, not the formal accounts themselves.
We don't audit your school
Fund-level tracking gives you and your auditor better source records — it doesn't replace the audit process itself.
What we do is the part that has to happen before any of that: an honest, complete reading of every deposit and payment, so the fund picture you build on top is based on real data, not an approximation. For that, see school fee reconciliation, and for the weekly routine to build it on, see match parent payments to pupils.
A useful rule of thumb: the sooner a restricted fund's real balance is visible, the more options remain for handling a shortfall calmly. Found early, it costs a planned adjustment. Found at audit time, it costs an uncomfortable conversation and usually a worse outcome.