How to Document Grant Expenses With Audit-Ready Records

A questioned cost rarely begins with an obviously improper purchase. More often, it begins with a charge that may have served the program but cannot be connected clearly to the award, the approved budget, and the supporting records. Knowing how to document grant expenses means building that connection at the point of transaction, not reconstructing it when a funder, auditor, or board asks questions months later.

For organizations managing federal, state, local, foundation, or pass-through awards, expense documentation is a core internal-control responsibility. It supports reimbursement requests, financial reporting, indirect cost calculations, program oversight, and, where applicable, Single Audit compliance under 2 CFR Part 200. It also gives leadership the clearest picture your board will ever get of whether restricted resources are being used as promised.

Start With the Award, Not the Invoice

Every expense file should be traceable to the governing award documents. Before an expense is approved or posted, finance and program personnel should be able to identify the grant name, award number, funding period, approved budget category, and applicable restrictions. The notice of award, grant agreement, approved budget, budget narrative, amendments, and correspondence establishing special conditions should be accessible to the people approving charges.

This matters because allowability depends on the specific award as well as the broader compliance framework. A cost that is ordinary and necessary for an organization may still be unallowable under a particular grant. For federal awards, organizations commonly assess whether costs are allowable, reasonable, allocable, consistently treated, and incurred during the period of performance. State agencies, private foundations, HUD programs, and other funders may impose additional requirements involving procurement, participant eligibility, match, reporting, or prior approval.

A useful grant coding structure makes this assessment practical. The general ledger should identify the funding source and, when needed, the program, activity, location, budget category, and year of award. Coding should be detailed enough to support grant reporting without becoming so complicated that staff routinely select incorrect accounts. For multi-year or renewed awards, distinguish each funding period rather than relying on a broad program code alone.

Build an Expense File That Tells a Complete Story

An invoice is evidence of a purchase. It is not, by itself, complete grant documentation. A reviewer should be able to follow the transaction from authorization through payment and understand why it belongs to the grant.

For most non-payroll transactions, the file should include the following records:

• The vendor invoice, receipt, contract, or other source document describing what was purchased
• Evidence of approval under the organization’s delegation-of-authority policy
• Documentation showing the expense was charged to the correct grant and budget category
• Procurement records when required, including quotes, bids, evaluations, sole-source justification, or conflict-of-interest disclosures
• Proof of payment, such as a check image, bank record, credit card statement, or accounts payable payment report

The level of documentation should match the nature and risk of the transaction. A recurring utility bill may require a different file than a consulting contract, technology purchase, construction change order, or subaward payment. The governing principle remains the same: a knowledgeable reviewer should not need to make assumptions about the purpose, approval, source of funds, or timing of the charge.

A concise programmatic explanation can be particularly valuable. For example, instead of recording “supplies,” the documentation might state that the purchase provided curriculum materials for 85 participants in the grant-funded after-school program. This is not an invitation to create narrative for every low-risk purchase. It is a control that becomes necessary when the invoice itself does not establish the connection between the cost and the grant objective.

Document Payroll With Greater Discipline

Payroll is frequently the largest grant expenditure and often receives the most scrutiny. Salary charges should be supported by records that accurately reflect the work performed, align with the organization’s payroll system, and reasonably allocate compensation across funding sources and activities.

The appropriate method depends on the organization’s operations and the award requirements. Some organizations use timesheets with actual hours by project. Others use periodic personnel activity reports, after-the-fact certifications, or documented allocation methodologies. Whatever approach is used, it should reflect actual work rather than a budgeted percentage that is never revisited.

A strong payroll file connects the employee’s role to the grant-funded activity. It typically includes the employee’s compensation rate, job description or position authorization, payroll register, allocation support, supervisor approval, and any required time-and-effort records. If an employee’s distribution changes because program activity shifts, the payroll allocation should change promptly as well.

Do not overlook fringe benefits. Health insurance, retirement contributions, payroll taxes, and other benefits must follow a supportable allocation method when charged to multiple programs. The methodology should be consistently applied and reconciled to the general ledger. Unsupported fringe allocations can create the same compliance exposure as unsupported salary charges.

Reconcile Monthly, Not at Reporting Time

Grant documentation becomes unreliable when the grant ledger, reimbursement request, and supporting files are maintained separately until a report is due. Monthly reconciliation is the control that brings those records together.

At a minimum, reconcile the grant expenditure report to the general ledger and confirm that each material charge is supported, correctly coded, within the performance period, and consistent with the approved budget. Investigate negative balances, unusual fluctuations, late journal entries, and charges posted to inactive grants. If the funder requires cost-sharing, program income reporting, or a matching contribution, reconcile those schedules with equal care.

This review should also identify costs that require prior approval or budget modification. Moving costs between line items may be permissible under one award and prohibited under another. A budget variance is not automatically a compliance violation, but it is a signal that the award terms should be consulted before reimbursement is requested or a financial report is certified.

Finance should document the reconciliation and reviewer sign-off. A simple monthly grant checklist can be effective if it identifies the report period, preparer, reviewer, exceptions found, corrective action, and completion date. The objective is not paperwork for its own sake. It is a clear audit trail showing that management monitored restricted funds in a timely manner.

Keep Procurement and Subrecipient Records Connected

Procurement records should not live apart from the grant expense file when a purchase is grant-funded. If federal procurement standards, state rules, or funder-specific purchasing requirements apply, retain the records that show the organization followed them. This may include the independent cost estimate, solicitation, vendor responses, evaluation criteria, selection rationale, contract, and evidence that the vendor was not suspended or excluded when such verification is required.

For subawards, documentation must go beyond invoices. The organization should retain the executed subaward agreement, risk assessment, monitoring plan, financial and performance reports, payment approvals, corrective-action correspondence, and closeout records. A subrecipient’s invoice may be mathematically accurate while still lacking the programmatic or compliance support needed for the pass-through entity to approve payment.

Distinguish subrecipients from contractors early. The classification affects the applicable agreement terms, monitoring responsibilities, and documentation expectations. When the relationship is unclear, a contemporaneous analysis is far more defensible than a decision made after an audit finding.

Preserve Records and Control Access

Electronic records are generally acceptable when they are complete, legible, protected from unauthorized alteration, and readily retrievable. A shared drive can work for a small organization, but it requires naming conventions, restricted access, defined folder ownership, and a process for retaining records when staff leave. Larger institutions may need an integrated grants-management or document-management system.

Retention periods vary by funder and may be extended by litigation, audit resolution, closeout requirements, or other conditions. Organizations should apply the longest applicable retention requirement and suspend destruction when a review, claim, or dispute is pending. Retain the documents that explain adjustments as well. Journal entries moving costs between grants should include a clear rationale, approval, and reference to the underlying support.

Access controls matter because grant documentation is also financial evidence. Limit the ability to alter coding, approve expenses, process payments, and modify supporting records without independent review. Segregation of duties may be challenging in smaller organizations, but compensating controls such as board treasurer review, executive approval, or periodic independent testing can reduce risk.

Treat Documentation as a Governance Tool

The most effective grant documentation process is not the most burdensome one. It is the one staff can follow consistently, leadership can monitor, and an independent reviewer can test without chasing missing explanations. Policies should be specific enough to guide daily decisions while leaving room for appropriate judgment when an award has unique terms.

Goldenthal & Suss sees the strongest organizations treat grant files as evidence of stewardship, not merely reimbursement support. When documentation is timely, connected to program purpose, and reconciled to reliable financial records, finance leaders can respond to funders with confidence and give governing boards meaningful assurance that restricted resources are protected.