What an auditor wants to see in a nonprofit's grant and restricted fund documentation

An auditor wants one thing above all: a clear, traceable paper trail showing where each restricted dollar came from, what restriction applied, how it was tracked, and how it was spent. For every restricted grant, the question is simple and unforgiving: what exactly was this money restricted for, and can you prove it was used accordingly? A strong nonprofit can answer that by following a chain from the financial statements back to the grant agreement and down to individual transactions, with evidence at every link.

The chain an auditor follows

Auditors do not test restricted funds by opening a binder. They pick a grant and follow the money, in both directions, through a logical chain. A grant file that supports this chain sails through; one that breaks a link invites a finding.

Award → restriction → budget → receipt → accounting code → expenditure → supporting document → grant report → remaining balance and release

The auditor should be able to start at any number on the financial statements and trace it back to the grant agreement, and start at the grant agreement and trace forward to the transactions that spent it. That two-way traceability, not the neatness of the folder, is what an audit actually tests.

The evidence they ask for

For each grant or restricted fund, an auditor typically requests the following.

The ideal grant file

A practical way to be audit-ready is to keep one file per significant grant, holding the twelve items an auditor tends to reach for.

The red flags auditors catch

Three problems come up again and again, and all three are avoidable with a coded ledger and a written methodology.

Co-mingling funds. Spending restricted money on general operating overhead without an explicit allocation allowance in the grant agreement. If a restricted fund pays for something the restriction did not cover, that is a finding.

Under-documented allocations. Splitting shared costs like rent or salaries across grants using arbitrary percentages instead of a written, consistent cost-allocation methodology. The number can be reasonable and still fail the audit if you cannot show how you got it.

Mismatched reporting periods. Totals reported to the grantor that do not agree with the financial statements for the same fiscal year. When the funder report and the ledger disagree, the auditor has to reconcile the difference, and so do you.

Where Numetix fits

This evidence is not something to assemble the week before fieldwork. It is a byproduct of keeping the books the right way all year. Numetix builds the traceable grant file as it goes: a coded fund-accounting ledger, expense substantiation tied to each grant, a documented allocation methodology, net-asset release schedules, funder reports reconciled to the ledger, and a per-fund reconciliation at every close, in current ASC 958 terms. When the auditor picks a grant and follows the money, the chain is already there.

Across more than 40 nonprofits and over 25 million dollars in grants managed, Numetix holds 95 percent accuracy on restricted-fund tracking and 99 percent fund-tracking accuracy overall, files Form 990 on time 100 percent of the time, and has zero missed funder deadlines. That is what it looks like when grant documentation is built to be traced, not reconstructed.

The short version

An auditor wants to prove that each restricted dollar was used as the donor intended, traceable from the financial statements to the grant agreement to the individual transaction. Give them the grant agreement, the coded ledger, the expense support, the funder reports reconciled to the ledger, and the net-asset release schedule, and avoid the three classic red flags: co-mingling, undocumented allocations, and mismatched periods. Keep the trail traceable year-round and the grant testing is a formality.

This page describes standard nonprofit grant and restricted-fund audit evidence and is general information, not legal, tax, or audit advice. Numetix figures reflect its nonprofit client base as of the date above and may change.