We receive too many phone calls that sound like: “We’re not sure we have a problem, but we’d like someone to look.”

The organization has a similar story, they had received a $75,000 grant from a regional foundation eighteen months earlier, restricted for a specific program. The program had run. The money had been spent. The annual report to the funder had been submitted, and the funder had been satisfied.

Then a new program director had taken over and started asking questions. She wanted to see exactly how the $75,000 had been spent — line by line, against what the original grant proposal had promised. The answer turned out to be: nobody knew. The expense had been “coded to the program,” but not to that specific grant. The bookkeeper had been treating it as a single bucket of program expenses, which is fine when there’s one funder, but the organization had three funders supporting that program.

We spent two weeks reconstructing the trail from bank statements, invoices, and email approvals. The work had actually happened. The money had genuinely been spent on the program. But the books couldn’t prove it for that specific grant. The reconstruction got us to about 90% confidence. The remaining 10% — about $7,500 of expenses — couldn’t be definitively tied to one funder versus another.

If that funder had ever asked for a detailed accounting, the organization couldn’t have provided one. That’s a compliance risk most nonprofits don’t realize they’re carrying.

Why restricted fund accounting is harder than people think

Most nonprofit bookkeepers can handle the basics: when a restricted gift comes in, code it to the right fund. When an expense is paid from that fund, code it back.

Where it breaks down is in the middle:

When one program is supported by multiple funders, every expense needs to be allocated to a specific funder, not just “the program”
When one expense benefits multiple programs, it needs to be split with a documented methodology
When a grant period ends but the work isn’t complete, the unspent balance needs to be either returned, extended (with funder approval), or moved to a different fund
When a restriction is met (the program runs, the time period passes, the purpose is fulfilled), the funds need to be formally “released” with a journal entry that moves them from temporarily restricted to unrestricted

That last one — release from restriction — is the most commonly missed entry in all of nonprofit accounting. We see it missed at small organizations and at large ones. The result is a Statement of Financial Position that shows temporarily restricted balances that don’t actually exist anymore, because the restrictions were satisfied months ago and nobody recorded the release.

Three questions that reveal whether your fund management is solid

1. Can you produce a real-time report showing the remaining balance of every restricted fund or grant?

Real-time is the key word. Not “I can build that report next week.” Not “I can pull it together from a spreadsheet.” Real-time, from the books, in five minutes or less.

This is the test that separates fund accounting from “fund tracking in a spreadsheet.” If a funder calls today and asks about their grant, you should be able to answer within minutes. The information should be a query, not a project.

2. Are grant expenses coded to the specific grant as they happen — not recategorized at year-end?

Year-end recategorization is how compliance problems hide. When you wait until November to figure out which grant paid for which expense, you’re making allocation decisions long after the fact, often based on which grants happen to have budget remaining rather than which expense actually benefited which grant.

Real-time grant coding requires two things: a chart of accounts that supports per-grant tracking (classes, sub-customers, dimensions — depending on your software), and a workflow rule that says no grant-related expense gets recorded without the grant being identified at entry time.

3. Do you have a documented process for releasing funds from restriction when the restriction is met — and does it actually get done?

The documentation part matters because release entries are easy to forget. They don’t happen automatically; someone has to recognize that a restriction has been satisfied and post the entry. Without a written process and a trigger (usually tied to grant period end dates or program completion milestones), they get missed.

The “does it actually get done” part is even more important. Many nonprofits have a documented process that exists in a binder somewhere but isn’t followed. The test: pick three grants from the last two years whose restrictions should have been met. Check whether a release entry was posted for each. If even one is missing, the process isn’t actually running.

The four most common restricted fund mistakes

After enough engagements, patterns emerge. These are the four mistakes we see most often.

Mistake 1: Treating “restricted” as a label, not a tracking category

The donation gets coded as restricted revenue when it comes in. Expenses get coded to the program. But there’s no ongoing reconciliation between what came in restricted and what’s been spent against it. The fund balance is theoretical, not actual.

Mistake 2: Pooling multiple funders

Several grants support the same program, so the bookkeeper codes expenses to “Program X” without specifying which grant paid for what. When one funder asks for detail, the answer requires reconstruction.

Mistake 3: Missing release entries

The grant period ends, the work is complete, but no one moves the funds from temporarily restricted to unrestricted. The Statement of Financial Position now shows restrictions that no longer exist. The auditor catches it, posts the entries in audit adjustments, and the next year’s books look strange because the prior year’s beginning balance doesn’t match what you remember.

Mistake 4: Ignoring the grant period

Grants are often time-restricted — money has to be spent by a certain date. If the period ends and the money isn’t spent, you may owe it back. Without explicit tracking of grant period end dates, this gets discovered when it’s too late to do anything about it.

The story’s epilogue

The organization from the opening of this post survived their compliance scare — the funder never asked for the detailed reconstruction, though the new program director got the answer she wanted internally. But it was a wake-up call. We spent the following six months restructuring their grant tracking: separate classes per funder, written coding rules, monthly grant balance reports added to their close process, and a quarterly review of grant period end dates.

Two years later, when a different funder did request a detailed accounting (it happens), the report ran in twenty minutes. The funder noted in their response how unusual it was to receive a complete accounting that quickly.

That’s the cost-benefit of doing this right. The work to set it up is real. The cost of not setting it up is just deferred — until a funder asks the question you can’t answer.

What to do this month

Pick the largest single grant or restricted fund your organization holds right now. Try to produce a one-page summary showing:

Total received
Total spent to date
Specific expenses charged (with documentation links)
Remaining balance
Grant period end date

If you can produce that report from the books in under thirty minutes, your fund tracking is in good shape. If it takes longer — or if you have to rely on spreadsheets to fill in the gaps — that’s where to focus.

Two ways to go deeper:

Download the Nonprofit Bookkeeping Health Check— fifteen questions across five categories, including the three from this post and twelve more.
Book a free 30-minute Finance Review— we’ll talk through your specific grant portfolio and tell you honestly whether your tracking is sufficient for the level of compliance you need.

Next in the series: The five things auditors flag every time — and how to make sure they don’t flag yours.

Previous: What Your Board Can’t Actually See

*Details have been changed to protect client confidentiality.