Restricted funds in one paragraph
Accounting sorts a nonprofit's net assets into two classes — net assets with donor restrictions and net assets without donor restrictions — a presentation FASB standardized in ASU 2016-14. A restricted grant sits in the first class: the funder has limited what the money may buy, which program it serves, or when it may be spent, and those limits come from the award document, not from your budget. Managing restricted funds therefore means managing each grant as its own small economy — its own budget, its own clock, its own rules — rather than as a slice of the organizational budget. This guide covers the operating discipline; your accountant handles the formal fund accounting, and nothing here replaces either the general ledger or professional advice.
Why the calendar view misleads
Most budget reviews compare spending to the fiscal year: "we are 40% through the year and 45% spent — fine." A restricted grant does not care about your fiscal year. It runs on its period of performance, and a grant that started in March is on a different clock from one that started in October. Roll them into one calendar view and the portfolio can look healthy while individual grants run hot and cold in opposite directions — the two errors cancel on paper and compound in reality.
The federal rules assume you can see through this. 2 CFR 200.302 requires financial management systems that identify the source and expenditure of funds award by award and permit "comparison of expenditures with budget amounts for each Federal award." The same discipline is simply good practice for foundation money.
The elapsed-period method
The method fits in two divisions and a subtraction:
- Percent spent = amount spent on the grant ÷ amount budgeted for the grant.
- Percent elapsed = days of the grant period used ÷ total days in the period.
- Variance = percent spent − percent elapsed, in percentage points.
A worked example. A $120,000 grant runs twelve months, January through December. At the end of May, $69,600 has been spent. Percent spent is 69,600 ÷ 120,000 = 58%. Percent elapsed is five of twelve months ≈ 42%. Variance: +16 points — the grant is spending roughly six weeks ahead of its clock. At that pace the budget exhausts around October, leaving two funded months with no funds; caught in May, the options are still open.
The reverse case matters just as much. The same grant with $36,000 spent at the end of May is 30% spent at 42% elapsed — 12 points behind. Underspending feels virtuous and is not: it usually means delayed delivery, and at closeout unobligated federal funds you were not authorized to keep must be promptly refunded (2 CFR 200.344). Foundation funders may allow an extension or reallocation, but only if asked in time.
A tolerance of about ±15 points separates signal from noise. Inside it, normal lumpiness; outside it, someone should look. Spending is naturally lumpy — a prepaid insurance policy or an equipment purchase in month one can push an honest grant past the line — so the tolerance triggers a question, never a verdict.
Warning signs worth a monthly look
Run the calculation for every active grant in the monthly finance review — the same meeting the post-award checklist builds the rest of the rhythm around. Investigate when you see:
- Variance beyond ±15 points with no known timing explanation.
- A widening trend — +6, +11, +17 over three months is a trajectory, not noise.
- A flat line — zero spending for consecutive months on an active grant usually means stalled delivery or costs landing on the wrong grant.
- A late spike — a jump in the final quarter invites the question auditors ask: were these costs incurred for this award, or to use it up?
Each check is also an allowability checkpoint. Under 2 CFR 200.403, federally charged costs must be necessary and reasonable for the award, allocable to it, consistently treated and adequately documented — spending fast is only a pace problem if the costs themselves belong on the grant; spending fast on unallowable costs is a findings problem.
What to do when a grant runs hot or cold
Ahead of schedule: verify the numbers first (miscoded costs are the most common cause), then identify what is driving pace. If delivery genuinely costs more than budgeted, slow what is controllable and open the conversation with the funder early — reallocation between budget lines, or additional funds, may need prior written approval under 2 CFR 200.308 for federal awards, and most foundation agreements have their own thresholds. Funders respond better to a projection in month five than a confession in month eleven.
Behind schedule: diagnose whether the underspend is delivery (the work is late), invoicing (the work happened, the costs have not landed), or plan (the budget overestimated). Delivery problems need a program conversation; invoicing problems need process; plan problems need a funder conversation about reallocation or a no-cost extension — for federal awards, 200.308 permits a one-time extension of up to twelve months without prior approval when the award's conditions allow it and the agency is notified in writing at least ten calendar days before the period ends.
In both directions, write down what was decided and why. The trail of "who noticed what, when, and what changed" is most of what a monitoring visit wants to see.
Where software fits
A spreadsheet can run the elapsed-period method — add spent, planned, period dates and a variance formula to your reporting calendar and review it monthly. What the spreadsheet cannot do is notice between reviews.
GrantConsole computes this continuously: every grant's restricted budget is measured against its elapsed period, amounts are stored as integer cents, and when spending runs more than 15 points ahead of the clock — or more than 15 behind — the grant is flagged with the calculation shown: "58% of the restricted budget is spent with 42% of the grant period elapsed." The warning names the rule and the numbers behind it, so finance can verify rather than trust. The live demo includes grants deliberately running hot and cold so you can see the signal on example data. GrantConsole tracks the obligations and budgets you enter; it does not interpret the award, decide allowability, or replace your general ledger.
The habit that makes it work
Restricted funds management is not a year-end reconciliation; it is a monthly question — is each grant's spending where its clock says it should be? — asked early enough that the answers still have options attached. Put the variance column beside every active grant, hold the ±15 line, and treat every breach as a conversation to have now instead of a surprise to explain at closeout.