Year-end close may be finished, but the questions about GASB 105 often keep coming. A debt issuance gets approved after year-end. A grant award is received weeks later. A lawsuit changes status during audit fieldwork. Suddenly, finance teams are left trying to determine:
- Does this affect the financial statements?
- Do we need a disclosure?
- Does this require an adjustment?
- Or do we simply document it and move on?
These are the types of discussions that frequently surface during audit season when evaluating subsequent events.
While the concept sounds relatively simple on paper, applying it in practice often involves more judgment than many governments expect.
What Is a Subsequent Event?
In general, a subsequent event is an event or transaction that occurs after the financial statement date but before the financial statements are available to be issued.
The challenge is determining whether that event is considered “recognized” or “nonrecognized.”
A recognized event:
- Provides additional evidence about conditions that already existed at year-end
- Requires adjustment to the financial statements
A nonrecognized event:
- Has a significant effect (favorable or unfavorable)
- Represents something entirely new that did not exist at year-end
- Requires disclosure only
- Does not require adjustment to the financial statements
This is where many of the real-world questions begin.
Why Subsequent Events Create So Many Questions
Local governments operate in constantly changing environments. Important decisions, approvals, emergencies, and funding changes do not conveniently pause at fiscal year-end.
During the weeks and months between year-end close and financial statement issuance, governments may experience:
- Council-approved debt issuances
- Grant awards or funding notices
- Litigation developments
- Emergency events or disasters
- Labor negotiations
- Significant contract approvals
- Cybersecurity incidents
- Economic or operational disruptions
Finance teams are then tasked with evaluating whether those events should impact the financial statements that are already in process.
The difficulty is that not every post-year-end event is treated the same way.
“We Approved Debt After Year-End… Now What?”
This is one of the most common questions governments encounter during audit season.
Debt issued after the financial statement date, but before the statements are available to be issued, are explicitly listed as nonrecognized events under GASB 105 and must be disclosed in the financial statements.
Suppose a government approves and issues debt shortly after year-end. Since the debt transaction itself occurred after year-end, the liability did not exist as of the reporting date even though the decision and issuance happened shortly afterward.
GASB 105 excludes long-term financing activities such as leases, public-private partnerships, and subscription-based information technology arrangements from the debt-related disclosures. Professional judgement should be used to determine if disclosure is appropriate in these instances. This is where communication between finance teams and auditors becomes critical early in the process.
“We Received Grant Funding After Year-End… Do We Need to Disclose It?”
Grant activity can also create gray areas.
For example:
- A government receives notification of a large grant award after year-end
- Funding approval occurs during audit fieldwork
- Reimbursement requests are still pending
- Eligibility requirements are still being evaluated
The key questions are:
- Did the underlying condition exist at year-end?
- Will this have a significant impact?
If the funding decision or approval occurred after the reporting date, it may point toward disclosure rather than adjustment. If conditions existed before year-end and the later event simply confirms them, the analysis may become more complex.
This is especially important as governments continue managing large federal and state funding programs, infrastructure grants, and emergency funding initiatives.
“A Lawsuit Changed After Year-End… Adjustment or Disclosure?”
Litigation is another area where subsequent event evaluations often become highly judgmental.
Imagine:
- Settlement negotiations progress after year-end
- Legal counsel provides updated estimates
- A court ruling occurs before financial statements are issued
Finance teams must determine whether the post-year-end development provides additional evidence about a condition that already existed at year-end.
If it does, the financial statements may need adjustment.
If the event represents a new development that arose after the financial statement date, disclosure may be more appropriate.
The challenge is that litigation timelines rarely fit neatly into reporting deadlines.
Other Common Subsequent Event Scenarios
Subsequent events are not limited to debt and litigation. Governments may also encounter situations involving:
Natural Disasters or Emergency Events
Floods, wildfires, storms, or infrastructure failures occurring after year-end may require evaluation depending on timing and impact.
Cybersecurity Incidents
A cyberattack discovered during audit fieldwork may trigger discussions around operational impact, disclosure considerations, and financial implications.
Major Contracts or Commitments
Large construction projects, vendor contracts, or development agreements approved after year-end may warrant disclosure, if they will have a significant impact.
The Hardest Part Is Often Timing
One of the biggest challenges with subsequent events is that the evaluation window extends beyond year-end close.
Finance teams may already feel finished with the reporting process—while auditors are still asking:
- “Did anything significant happen after year-end?”
- “Has anything changed since the draft financial statements were prepared?”
- “Were there any major approvals, settlements, or operational events?”
Without a clear process for monitoring subsequent events, important information can easily be missed.
Documentation Matters
Governments should also expect increased focus on documentation during subsequent event evaluations.
Auditors may ask:
- When did the event occur?
- How significant was the event?
- When did management become aware?
- Did conditions exist at year-end?
- How was the conclusion reached?
- Why was disclosure or adjustment deemed appropriate?
Having a documented process for identifying and evaluating subsequent events can significantly reduce confusion during audit fieldwork.
Communication Across Departments Is Critical
One of the most overlooked challenges with subsequent events is that finance departments are not always the first to learn about them.
Important information may initially sit with:
- Legal departments
- City management
- Public works
- Human resources
- IT departments
- Risk management
- Grant administration teams
If communication channels are weak, finance teams may not become aware of reportable events until very late in the reporting process.
That can create unnecessary stress and delays during audit season.
Bottom Line: The Goal Is Not Perfection—It’s Preparation
Subsequent events will always involve some level of judgment. There is rarely a checklist that perfectly answers every scenario.
Governments that prepare early, communicate consistently, and document their evaluations tend to navigate the process much more smoothly.
The earlier finance teams begin discussing potential subsequent events internally, the easier it becomes to avoid last-minute surprises during audit fieldwork.
Need Help Preparing for GASB 105 and Year-End Reporting? If your organization is preparing for GASB 105 implementation or reviewing subsequent event processes ahead of audit season, our team is here to help. Contact us today!
