Before the Findings Find You: A Nonprofit CFO's Playbook for Single Audit Readiness
By Daniel B. Sefick, CPA, CGFM, HBK CPAs & Consultants –
November 17, 2026
Single audits and parenting share a material amount in common: lots of rules, endless documentation and someone repeatedly asking, "But why?" In both cases, consistency matters far more than a heroic cleanup immediately before company arrives.
Speaking from experience, rules cannot be introduced retroactively, routines cannot be recreated at year-end and “we usually do it that way” is unlikely to satisfy either an auditor or a persistent four-year-old. When my toddler proudly exclaims, “I found something,” a sinking feeling washes over me and I know in some form or fashion that my day is probably about to get more complicated. Nonprofit CFOs and controllers may recognize that same feeling when an auditor says, “We found something.” We, as auditors, may prefer the phrase, "We noted an exception," but the message lands about the same.
In a single audit, that “something” could be a missing approval, an unsupported payroll allocation, a procurement mishap or a report that cannot be reconciled to the general ledger. Unlike my toddler’s latest “discovery,” a single audit finding may be newly uncovered, but the condition behind it is rarely new. By the time it reaches the audit report, the underlying issue is likely something that has been present for months or even years.
Implementing AICPA Single Audit Guidance
The American Institute of CPAs (AICPA)has substantially revised the single audit guidance contained in its audit guide, Government Auditing Standards and Single Audits. The 2025 edition introduced the revised material in a nonauthoritative appendix to provide practitioners with time to evaluate and prepare for the changes. In the 2026 edition, that material will replace the existing single audit guidance in Part II of the guide. These enhancements do not amend the Uniform Guidance, Generally Accepted Auditing Standards (GAAS) or Government Auditing Standards, nor do they independently create new compliance requirements for federal award recipients.
The revised guidance establishes clearer linkages among the identification of direct and material compliance requirements, the assessment of risks of material noncompliance, the understanding and testing of internal control over compliance, and the nature and extent of substantive compliance testing. It also provides expanded guidance concerning information technology controls, the completeness of populations used for testing, audit sampling, the sufficiency and appropriateness of audit evidence and the evaluation of identified instances of noncompliance — including their effect on findings, questioned costs and the auditor’s opinion.
Although the underlying compliance requirements have not necessarily changed, the revised guidance may result in more rigorous and consistent audit execution. Auditors may place greater emphasis on whether controls were appropriately designed, implemented and documented, not simply memorialized in a policy. A control that exists only on paper is, after all, not much more effective than a bedtime rule no one enforces. Auditors may also focus
more closely on whether management’s compliance populations are complete and accurate and whether identified exceptions represent isolated errors or evidence of a broader control deficiency.
Nonprofit finance teams may notice the change through more detailed inquiries and more explicit requests for evidence. Auditors may look beyond whether a policy exists to determine how management identified the applicable compliance requirement, which control addressed the related risk, who performed the control and what documentation demonstrates its operation. They may also devote greater attention to the completeness of system-generated reports and other populations used for sampling, including the information technology processes supporting those reports.
Addressing Common Weaknesses
The revised guidance is unlikely to create entirely new categories of findings. Instead, it may expose weaknesses within familiar processes that previously received less attention, such as:
- Controls without evidence: Management performs a review but retains no documentation showing its scope, conclusions or resolution of exceptions.
- Incomplete populations: The listing provided for audit testing does not include all transactions subject to the applicable compliance requirement.
- Overreliance on system reports: Management uses system-generated information without controls over report parameters, data completeness or accuracy.
- Exceptions treated too narrowly: One error is corrected, but management does not determine whether the same condition affects other transactions or indicates a broader control deficiency.
Preventing these findings requires more than updating a policy manual before fieldwork. Revising policies at the last minute is the compliance equivalent of announcing new house rules five minutes before the babysitter arrives: well intentioned, but hardly evidence that anyone has been following them. Nonprofit finance leaders should instead focus on whether compliance responsibilities are clearly assigned, controls operate throughout the year and sufficient evidence is retained to demonstrate that they occurred. The following practical steps can significantly reduce the risk:
1. Translate award requirements into assigned responsibilities. Identify the requirements applicable to each major federal program and assign an owner to each one. Finance cannot independently control participant eligibility, program performance, procurement, payroll allocation and subrecipient monitoring.
2. Document the control, not merely the process or transaction. A signature or checkmark may show that someone touched a document, but not what they reviewed. Evidence should demonstrate the purpose, scope and result of the review, including how exceptions were resolved.
3. Reconcile the populations auditors will test. Payroll records, procurement activity, reimbursement requests, program reports and subrecipient payments should reconcile to the general ledger and ultimately to the Schedule of Expenditures of Federal Awards (SEFA). An incomplete or unreliable population creates risk before the auditor selects the first sample.
4. Test compliance before year-end.Mid-year self-assessments allow management to determine whether controls are operating while corrective action remains possible. The objective is not to conduct a shadow audit, but to identify gaps before they affect an entire year.
5. Treat exceptions as information, not isolated annoyances. If management identifies a problem, it should ask what caused it, whether similar transactions are affected and whether the control itself needs to change. Correcting one transaction without addressing the underlying process leaves the organization vulnerable to recurrence.
Federal compliance is one responsibility the accounting department cannot keep to itself. As parents often remind their children, sharing matters — but effective sharing still requires everyone to understand what they are responsible for. Finance may maintain the SEFA and prepare reimbursement requests, but program personnel often determine eligibility, approve services, monitor performance and maintain the underlying documentation.
The goal is not to make certain the auditor finds nothing; it is to make certain that the organization can demonstrate that compliance was understood, assigned, performed and documented throughout the year. After all, unlike a toddler, an auditor generally tells you where they plan to look.
 | Daniel B. SefickDaniel B. Sefick, CPA, CGFM, is principal and national director in Nonprofit Solutions at HBK CPAs & Consultants. More content by Daniel B. Sefick: |