TLDR
A monthly grant reconciliation routine is the operational backbone of restricted fund compliance. Organizations that reconcile grants monthly catch errors while they are small and correctable. Organizations that reconcile annually - or only when a report is due - catch them when correction is expensive and audit exposure is real. The routine has four steps and should take no more than half a day for a portfolio of ten to fifteen active grants.
The monthly grant reconciliation routine is the practice that separates organizations that are in compliance from organizations that think they are in compliance. The difference is not effort - it is timing.
An organization that reconciles monthly catches a GL coding error in the month it occurs. The correction is straightforward: reclassify the entry, update the fund balance, document the change. An organization that reconciles annually catches the same error eleven months later, after the error has affected eleven subsequent months of reporting, after staff who might remember the context have moved on, and after the restricted fund balance has been reported incorrectly in interim financial statements.
The work is the same. The consequences are not.
Why Monthly Is the Right Cadence
Grant compliance documentation is time-sensitive in a way that general accounting is not. General ledger errors can be corrected retroactively with journal entries. Grant compliance errors - expenses charged to the wrong grant, drawdowns not supported by posted expenses, restricted fund balances that do not match the accounting records - have compliance implications if they are not caught and corrected.
The monthly cadence keeps the investigation window small. When something does not reconcile, the finance staff member performing the reconciliation has just reviewed that month’s transactions and knows what happened. The bank statements are available. The invoices are accessible. The staff member who approved the expense is still in the same role.
At the annual close, none of those advantages exist. The investigation reaches back twelve months into transactions that no one remembers clearly. The paperwork trail has gaps. The corrections take longer and are less certain.
The monthly reconciliation also creates the documentation trail auditors want to see. A grant file with twelve reconciliation summaries showing that balances were checked monthly, discrepancies were found and corrected, and open items were tracked to resolution is a grant file that passes audit. A grant file with one year-end reconciliation that magically shows everything is in order raises questions.
How the Four Steps Connect
The four steps are designed to move from general to specific: bank confirms the cash is right, grant-to-ledger confirms the coding is right, restricted balance confirms the fund math is right, and drawdown review confirms the forward obligations are managed.
Each step builds on the previous one. If the bank reconciliation finds an unrecorded deposit, that affects the grant-to-ledger comparison, which affects the restricted balance calculation. Doing the steps in order prevents rework.
Each step also has a specific documentation artifact: the bank reconciliation workpaper, the grant-to-GL comparison, the restricted balance summary, and the drawdown checklist. These four documents, produced monthly and signed by the preparer and reviewer, are the reconciliation documentation. They should live in the grant file and in the monthly close folder, organized by period.
What Good Documentation Looks Like
The purpose of documentation is to enable a reader who was not present during the reconciliation to understand what was done, what was found, and how exceptions were resolved. Good documentation is complete enough to stand alone.
A useful reconciliation summary includes the period covered, the grants reviewed, the expected and actual balances for each, a note on any discrepancies and how they were resolved, and the signature of the preparer and reviewer. It does not need to be elaborate. A one-page summary per month is sufficient. The underlying workpapers - the GL reports, the comparison spreadsheets - are attachments.
What the documentation should not do is simply state “reconciliation complete” without showing the work. That is not documentation; it is an assertion. Auditors test assertions. They cannot test documentation that shows the comparison, the discrepancies, and the resolutions.
Building the Routine Into the Monthly Close Calendar
Monthly grant reconciliation works best when it is a scheduled calendar item rather than a task that happens when finance staff find time. Put it on the monthly close calendar with a specific date - typically five to seven business days after month-end, after bank statements are available and after the last period transactions have been posted.
Assign a specific person as the preparer and a different person as the reviewer. The preparer performs the reconciliation; the reviewer confirms it. The two-person process catches the errors the preparer missed and creates an independent check on the work.
For small finance teams where two people are not available, the finance director can serve as reviewer. The preparer completes the reconciliation workpapers; the finance director reviews and signs off before the monthly close is certified.
The routine becomes reliable when it is built into the calendar, assigned to specific people, and tied to a deliverable - the reconciliation documentation - rather than a general intention to stay current on grant tracking.
Free resource
Get the Donor-to-Grant Reconciliation Template
A reconciliation worksheet for matching donor CRM records to grant management records: funder name, CRM entry, grant record, matching status, discrepancies found, resolution steps, and instructions for annual reconciliation and mid-year spot checks. Delivered by email.
- Fund balance
- The net assets in a specific restricted fund, calculated as all revenue received under the restriction minus all allowable expenses charged to the fund. A fund balance should equal zero at grant closeout if all funds were expended correctly, or a positive amount if there are unspent funds to be returned.
DEFINITION
- Drawdown
- A request to receive grant funds from a federal payment system (such as ASAP or HHS Payment Management System). The grantee draws funds either in advance of anticipated expenditures or as reimbursement for actual costs. Drawdowns must be supported by posted expenditures and reconciled to the accounting system.
DEFINITION
- GL coding error
- An expense posted to the wrong general ledger fund code - for example, a salaries expense that should have been split between two grant funds was charged entirely to one. GL coding errors affect restricted fund balances, compliance documentation, and funder reports. They should be corrected in the period they are discovered, not left to correct at year-end.
DEFINITION
Q&A
How long should the monthly grant reconciliation take?
For a portfolio of ten to fifteen active grants with a single finance staff member performing the reconciliation, the full four-step process should take three to five hours. Organizations with larger portfolios, federal grants with drawdown requirements, or system limitations that require manual comparison will take longer. If the reconciliation consistently takes more than a full day, investigate whether the accounting system or grant tracking setup is creating unnecessary manual work.
Q&A
What if the accounting system balance and the expected balance do not match?
Investigate before closing the month. Common causes: a grant receipt was deposited but not coded to the correct fund, an expense was coded to the wrong grant, or an indirect cost charge was calculated incorrectly. Do not carry an unexplained variance into the next period - it compounds. If the source of the discrepancy cannot be found during the reconciliation, note it as an open item, escalate it to the finance director, and continue investigating until it is resolved.
Frequently asked