Nonprofit grant restriction reconciliation: an award-by-award control method

A nonprofit may call a donor gift, foundation agreement, government award, reimbursement contract, or board-funded initiative a grant. Those arrangements do not automatically have the same accounting treatment, spending rules, reporting basis, or cash mechanics. A useful reconciliation begins with the actual governing records and the organization's approved conclusion, not with the label used in a project list.

For a not-for-profit entity applying U.S. GAAP, donor restrictions and contribution conditions are accounting questions addressed by the cited FASB updates. For a Federal award in scope of 2 CFR part 200, financial management, cost allowability, and allocability add a separate compliance layer. A private foundation award may instead be governed by its agreement and other applicable requirements. The workflow below keeps these layers connected without treating them as interchangeable.

Create one controlled record for each award or restriction ID before reconciling activity. Preserve the original agreement and every amendment rather than overwriting terms. The master should include:

A board action can be retained in the master as a designation or internal funding decision, but it should not be presented as donor-imposed unless an external source created the restriction. If documents conflict, open an exception and identify the affected periods; do not resolve the conflict by changing a code.

Start with an opening balance that agrees to the prior approved reconciliation. Then classify current-period movements using the nonprofit's approved accounting policy. A working rollforward may include opening balance, recognized additions, qualifying expenditures or other satisfaction events, approved releases, returns or refunds, transfers permitted by policy, corrections, and ending balance.

The arithmetic template is:

approved opening balance + supported additions - approved releases or other reductions +/- authorized corrections = ending balance

The labels and signs must be adapted to the arrangement. The equation does not decide whether an award is conditional, whether revenue should be recognized, or whether a cost satisfies a restriction. Those are inputs approved by the responsible accounting and grant owners.

For each movement, retain the transaction or batch ID, ledger account and dimensions, amount, date, source document, restriction or award rule applied, preparer, reviewer, and any journal reference. Grouped lines must remain traceable to a transaction population.

1. Governing terms to the master

Confirm that the master reflects the current executed award, gift record, amendment, notice, and approved accounting memo. Compare effective dates and version history. A late amendment should identify which prior transactions, draws, releases, or reports require reassessment.

2. Detailed activity to the general ledger

Extract the complete ledger population for the award or restriction dimensions with report name, parameters, extraction time, row count, and accounting period. Tie detailed debits and credits to the ledger control total and identify manual journals, inactive codes, missing dimensions, duplicate imports, and postings outside the approved period.

3. Costs or satisfaction evidence to the approved rule

For each selected or required item, preserve the invoice, payroll or allocation support, service period, program relationship, approval, and the exact award or policy criterion applied. For Federal awards in scope, the responsible owner should apply the current allowability and allocability requirements, including any award-specific limitation. The bookkeeping preparer may test required fields and calculations but should not make an undocumented legal or compliance conclusion.

When a cost benefits multiple activities, retain the allocation objective, population, driver, calculation, period, result, and approval. Do not shift a cost merely to use an available budget or clear an overrun. If the basis is uncertain, leave the item in the exception population.

4. Accounting balance to releases or other movements

Tie every proposed release, recognition entry, return, or correction to the approved accounting conclusion and source evidence. A cash payment does not by itself prove that a donor restriction was satisfied. A program milestone does not by itself prove that a contribution condition was met unless the approved analysis identifies it as the relevant barrier and addresses the agreement's return or release provision.

The review packet should show the opening balance, movement population, calculation, proposed journal, net-asset presentation, and resulting ending balance. Preserve rejected proposals as part of the decision trail.

5. Draws and reports to their own control totals

For reimbursement or advance-funded awards, reconcile requests and receipts separately from expense and revenue. Record the request ID, covered period, submitted amount, accepted amount, receipt date, cash account, unresolved reduction, and linked expenditure population. For program or financial reports, retain the submitted version, control totals, certification or approval, amendments, and tie-out to the reconciled records.

A draw-to-ledger difference may be a timing item, receivable, advance, rejected cost, or error. It should not be forced to zero with an unsupported journal. Likewise, a report that agrees to the ledger can still include an ineligible cost if the underlying evidence and rules were not reviewed.

Use an exception register with award ID, transaction or balance affected, amount, period, issue type, source links, requirement or policy in question, date opened, owner, next action, due date, blocked output, disposition, approver, and closure evidence.

Useful categories include missing agreement or amendment, conflicting terms, unapproved code, expense outside the approved period, unsupported allocation, missing match evidence, questioned allowability, duplicate charge, budget variance requiring action, draw difference, stale receivable or advance, report-to-ledger variance, unsupported release, and post-close correction.

Age from the original open date rather than the latest comment. Priority should reflect reporting deadline, known exposure, decision dependency, and whether cash, a release, a draw, or an external report is blocked. This brief provides no universal monetary or age threshold; management must approve thresholds for the specific award portfolio.

Remote or offshore support changes where preparation occurs, not who owns grant compliance, donor interpretation, accounting policy, cash custody, or external certification. Access should be limited to the required records and tasks, with named accounts and review of privileged changes.

This brief synthesizes FASB standards updates for U.S. GAAP nonprofit reporting and contribution accounting with selected provisions of 2 CFR part 200 for Federal awards. The award master, five-layer reconciliation, exception fields, and role table are implementation recommendations. They are not mandatory templates quoted from the sources.

The brief does not determine whether an arrangement is a contribution or exchange transaction, whether a donor stipulation is legally enforceable, whether a condition has been met, whether a specific cost is allowable, whether a Federal rule applies, or whether an accounting entry or external report is correct. It does not address every grantor rule, state requirement, endowment law, tax issue, audit procedure, or contractual remedy. Apply the current agreement, reporting framework, jurisdiction, regulations, organizational policy, and facts with qualified owners before approving a release, draw, correction, or submission.