Nonprofit fund accounting support: evidence, releases, and review

Nonprofits often use the word fund for several different things: a donor-restricted purpose, a grant, a program, a board designation, an endowment, or simply an internal reporting bucket. Those labels are useful only when their meanings are explicit.

For a not-for-profit entity applying U.S. GAAP, FASB ASU 2016-14 organizes external reporting around net assets with donor restrictions and net assets without donor restrictions. The standard does not require external statements to reproduce every internal fund. A practical ledger can therefore carry more detail, but each internal code needs a documented path to the appropriate reporting class.

Keep these concepts separate:

• Donor restriction: an outside stipulation attached to contributed resources, subject to the organization's approved accounting interpretation.
• Condition: a barrier and a right of return or release, as described in ASU 2018-08. A condition affects whether and when a contribution is recognized; it is not merely another fund tag.
• Board designation: an internal limit established by the governing board on resources without donor restrictions. It should not be presented as donor-imposed.
• Program or department: an operating dimension used to understand activities and expenses. It does not by itself establish a restriction.
• Cash location: the bank or investment account holding assets. It does not by itself prove the amount of net assets subject to restrictions.

This separation prevents a common design error: treating one spreadsheet balance as the cash balance, available spending authority, donor-restricted net assets, and grant-reporting balance at the same time.

The restriction master is the controlled index that connects source language to ledger treatment. Open or change a record only from a source accepted under the nonprofit's document policy, such as an executed gift agreement, award, donor communication, will or trust record, or approved governing action. If the documents conflict or the meaning is unclear, log the ambiguity rather than resolving it through a coding choice.

At minimum, record:

Do not overwrite the original terms when an amendment arrives. Add a version with its effective date, link it to the prior version, and identify which transactions require reassessment.

1. Intake and identify

Capture the source document, counterparty, amount, date, program, and proposed restriction ID. Reject or queue records that lack the minimum evidence defined by policy. A memo written after the transaction should not silently replace the original donor or grant record.

2. Apply approved dimensions

Apply only valid combinations from the chart and restriction master. Useful dimensions can include natural account, program or function, restriction ID, grant or donor, location, and project. Prevent retired IDs and incompatible combinations where the accounting system permits it.

3. Preserve allocation support

When a cost benefits more than one activity, attach the approved allocation method, input population, calculation, and period. The preparer should be able to reproduce the result from retained evidence. A round percentage copied from the budget is a forecast, not automatically evidence of actual resource use.

4. Reconcile three views

At each close, reconcile rather than collapse:

1. General ledger: activity and ending balance by approved net-asset class and internal dimension.
2. Restriction register: opening balance, additions, releases, transfers or corrections, and ending balance for each restriction ID.
3. Source populations: contribution records, grant schedules, investment activity when relevant, and the documents supporting qualifying expenditures or elapsed time.

An operational rollforward can be expressed as:

opening restriction balance + restricted additions + applicable return or other changes - approved releases +/- approved corrections = ending restriction balance

That equation is a control template, not a substitute for the nonprofit's accounting policy. Each component must tie to the ledger, and each nonroutine item must identify its preparer, reviewer, date, and evidence.

5. Prepare release packets

A release packet should identify the restriction ID, amount proposed for release, period, satisfaction event, qualifying transaction population, calculation, source links, and proposed entry. The reviewer should be able to answer both questions: what requirement was satisfied, and which evidence proves it?

Do not release a restriction merely because cash was spent, a budget period ended, or management would prefer to use the balance elsewhere. Conversely, do not leave a supported release unrecorded simply because the resource is held in pooled cash. The approved accounting policy and the underlying terms govern the conclusion.

6. Close exceptions visibly

Keep unresolved items out of informal chat and in an exception queue. Record the restriction, affected amount or transaction population, issue, date raised, owner, required decision, due date, status, and final disposition. Reopen the reconciliation if a late amendment or corrected source changes a prior conclusion.

A control measure is useful only when its numerator, denominator, period, owner, and source system are defined. Suitable measures include:

• transactions using an invalid, missing, or retired restriction ID;
• restriction-register balances that do not tie to the general ledger;
• proposed releases awaiting program confirmation or accounting approval;
• allocations missing a current method or reproducible calculation;
• amendments not yet reflected in the restriction master;
• exceptions aged by reason and decision owner; and
• post-close corrections traced to source, coding, allocation, or review causes.

These measures describe workflow condition, not compliance by themselves. A zero-exception dashboard can result from incomplete testing, and a balanced register does not prove the underlying interpretation is correct. Reviewers should inspect evidence and investigate changes in the measured population.

A support team can perform controlled preparation without owning the judgments that create financial authority.

The organization should also separate preparation from review where feasible and restrict system permissions to the assigned task. Remote staffing changes the location of preparation, not the nonprofit's accountability for its records, policies, reporting, or approvals.

This brief synthesizes FASB standards updates that address U.S. GAAP reporting by not-for-profit entities and contribution accounting, plus IRS recordkeeping guidance specifically for U.S. 501(c)(3) public charities. The operating register, workflow, fields, and measures above are implementation recommendations derived from those bounded principles; they are not quoted requirements from every source.

The brief does not determine whether a transfer is a contribution or exchange transaction, whether an agreement contains a legally enforceable restriction, when a condition has been substantially met, how an endowment law applies, or whether a specific release entry is correct. It also does not establish tax, audit, legal, grant, or financial-reporting requirements outside the cited scope. Applicable rules depend on the entity, reporting framework, jurisdiction, governing documents, donor or grant terms, and facts. A qualified accounting or legal owner should decide those matters and document the conclusion.