Single Audit Preparation Checklist for Grant Teams

A Single Audit rarely becomes difficult because an organization lacks one invoice or cannot locate one policy. It becomes difficult when federal award activity, financial reporting, compliance ownership, and supporting documentation have not been reconciled before fieldwork begins. This single audit preparation checklist helps finance and program leadership create an orderly audit process that gives management and the board a clear, supportable view of federal funds.

For organizations subject to 2 CFR Part 200, readiness is more than an administrative exercise. It is evidence that the organization understands its stewardship responsibilities, can demonstrate compliance with award terms, and has controls that operate beyond the written policy manual.

Start With Scope, Timing, and Responsibility

The first task is to confirm whether a Single Audit is required for the fiscal year under audit. The federal expenditure threshold and applicable Uniform Guidance requirements can change, so management should verify the rules in effect for its fiscal year, rather than relying on a prior-year conclusion. This review should consider all federal awards expended, including funds passed through state agencies, local governments, and other nonfederal entities.

Prepare a complete schedule of federal awards activity early. It should identify the assistance listing number, federal agency, pass-through entity where applicable, award number, program name, beginning and ending grant periods, and total expenditures. Reconcile this schedule to the general ledger, grant reports, and, ultimately, the Schedule of Expenditures of Federal Awards (SEFA).

Assign a responsible person for each audit area. The controller may own the trial balance and cash reconciliations, while program directors substantiate eligibility, service delivery, and performance reporting. Human resources may be responsible for personnel files and time-and-effort support. A Single Audit is cross-functional by nature. When all requests flow through one finance employee without defined program ownership, delays and incomplete responses are predictable.

Create an internal calendar that works backward from the filing deadline and the planned audit fieldwork date. Include dates for closing the books, completing reconciliations, preparing the SEFA, reviewing grant agreements, gathering support, and holding an entrance meeting with key staff. Audit readiness is strongest when leaders resolve open items before auditors arrive, not while reports are being drafted.

Build a Reliable SEFA Before Fieldwork

The SEFA is central to the engagement because it drives major program determination and frames the federal compliance work. It deserves the same level of review as the financial statements.

Management should reconcile federal expenditures by program to the general ledger and investigate every difference. Common issues include recording a drawdown as an expenditure, omitting noncash assistance, failing to identify expenditures under a pass-through award, or using an outdated assistance listing number. For loan and loan-guarantee programs, the applicable expenditure basis may differ from ordinary grant spending. HUD, education, human services, healthcare, and housing programs can each introduce specialized reporting considerations.

The SEFA should include required notes, including the significant accounting policies used to prepare it and, when applicable, disclosure of indirect cost rate elections. Do not treat this schedule as a last-minute spreadsheet. Have a knowledgeable reviewer trace major line items to grant records and ask whether the schedule tells a complete, consistent story about federal activity.

Single Audit Preparation Checklist for Documents

Auditors need evidence that is complete, organized, and traceable. A secure request portal or well-structured electronic folder is usually more effective than sending documents in disconnected email threads. Establish clear file names, retain final versions, and avoid mixing draft support with approved records.

At a minimum, prepare the following materials before fieldwork:

• Final trial balance, financial statements, bank reconciliations, accounts receivable and payable detail, debt schedules, and board-approved budgets.
• A completed SEFA with reconciliation support, grant award agreements, amendments, notices of award, approved budgets, and correspondence affecting award terms.
• Grant reimbursement requests, cash drawdown reports, expenditure reports, and reconciliations showing that cash management practices align with program requirements.
• Personnel records, payroll registers, job descriptions, allocation methodologies, time-and-effort support where required, and approval evidence for payroll charged to awards.
• Procurement files, including policies, solicitations, bids or quotes, conflict-of-interest documentation, vendor selection analysis, contracts, and approval records.
• Subrecipient monitoring files, if the organization passes federal funds to other entities, including risk assessments, agreements, monitoring results, corrective actions, and required reports.

The correct support depends on the program and compliance requirements selected for testing. A human-services provider may need to demonstrate eligibility determinations and service documentation. A school or charter school may need support for allowability, equipment, procurement, and payroll allocations. A housing entity may need to address program-specific tenant, development, or subsidy documentation. The point is not to create a larger file than necessary. It is to make the path from transaction to compliance conclusion easy to follow.

Test Controls as They Actually Operate

A written policy is only the starting point. Single Audit work examines whether key controls were designed appropriately and whether they operated during the year. Management should test its own processes before the audit team selects samples.

Walk through a small number of transactions from initiation to recording and reporting. For a payroll charge, confirm that the employee worked on the program, the allocation method was reasonable, the charge was approved, the payroll entry agreed to supporting records, and the related reimbursement was properly reported. For a procurement transaction, verify that the purchasing method was appropriate, required competition or justification was documented, conflicts were considered, and the payment matched the approved contract.

Focus on areas where staff workarounds have become normal. Shared passwords, late reconciliations, unsigned approvals, manual spreadsheet changes, and informal grant budget revisions may appear manageable to staff but can indicate a control deficiency. Resolve what can be corrected prospectively, document the remediation, and be candid with auditors about matters that affected the period under audit.

Segregation of duties requires particular attention in smaller organizations. Limited staffing does not eliminate the need for oversight. Compensating controls, such as independent bank statement review, documented board treasurer review, or timely management review of disbursement activity, may be appropriate if they are specific, consistent, and evidenced.

Prepare Program Leaders for Compliance Questions

Program staff should not first encounter the audit process when they receive a sample request. Hold a brief readiness meeting that explains why their records matter and identifies the requests they may receive. This is especially valuable where eligibility, matching, reporting, special tests and provisions, or subrecipient monitoring are significant compliance areas.

Ask program leaders to review whether reporting submitted to funders agrees with accounting records and operational data. If a report was revised, retain both the original and corrected versions with an explanation. If an award budget changed, preserve the approval. If a participant file has an exception, document the facts and the organization’s response rather than attempting to reconstruct a record after the fact.

Finance leadership should also confirm that program managers understand the distinction between a contractor and a subrecipient. The classification affects monitoring responsibilities and cannot be determined solely by the label used in an agreement. A thoughtful review of the relationship before funds are disbursed is far less costly than correcting the classification after audit testing begins.

Address Prior Findings With Evidence, Not Assurances

Prior-year findings, questioned costs, and management letter comments should be reviewed well before the current-year audit. For each item, identify the corrective action, the person accountable, the date implementation began, and the evidence showing the change is operating.

A statement that management has "addressed" a finding is not enough. If a prior finding involved late financial reporting, produce the completed reporting calendar and proof of timely submissions. If it involved inadequate subrecipient monitoring, show the risk assessment, monitoring plan, completed reviews, and follow-up. Auditors will evaluate whether corrective action was taken, and repeat findings can create concern for funders, boards, and oversight agencies.

Keep the Board Informed Without Turning It Into a Staff Exercise

The audit committee or board treasurer should understand the engagement timeline, significant federal programs, prior findings, and any emerging compliance concerns. The board does not need to manage document collection. It does need enough information to exercise informed oversight and to ask whether resources, staffing, or policies need attention.

A well-prepared Single Audit offers more than a compliance report. It can be the clearest picture your board will ever get of how federal funding moves through the organization, where accountability rests, and whether controls are keeping pace with program complexity. That perspective is most valuable when preparation begins while management still has time to act.