Preparing Early for GASB 105: Subsequent Events and Year-End Disclosure Discipline 

GASB Statement No. 105, Subsequent Events, is effective for fiscal years beginning after June 15, 2026, and all reporting periods thereafter. While that date may feel distant, the practical work of preparing begins much earlier. The standard defines subsequent events as transactions or other events that occur after the date of the financial statements but before the date the financial statements are available to be issued. It also clarifies recognized and non-recognized subsequent events and requires disclosure of the date through which subsequent events have been evaluated. 

For governments, this is more than a technical accounting update. It is an opportunity to strengthen year-end communication, documentation, and disclosure discipline. 

Subsequent Events Require a Wider View 

Many important events occur after year-end but before financial statements are issued. Some may provide additional information about conditions that existed at year-end. Others may not affect recognition but could still be important to financial statement users. 

Common examples include board actions, litigation developments, new debt issuances, significant grant awards, disaster-related events, major contracts, settlement activity, or changes affecting component units. These items often originate outside the finance office, which makes coordination essential. 

A city council decision, school board resolution, emergency declaration, or legal update may be well known operationally but not immediately connected to financial reporting. GASB 105 reinforces the importance of making those connections in a timely and consistent way. 

Process Matters as Much as Policy 

Governments that wait until the audit begins to gather subsequent events information may face unnecessary pressure. By that point, key personnel may be focused on budget cycles, grant reporting, construction activity, or other competing priorities. 

A stronger process starts with a clear internal question: who knows about events after year-end, and how does that information reach the finance team? The answer may include department heads, administrators, legal counsel, grant managers, debt advisors, emergency management personnel, and governing board liaisons. 

Creating a consistent tracking process can help ensure events are evaluated rather than overlooked. This may include maintaining a year-end subsequent events log, reviewing board minutes through the financial statement issuance date, documenting legal and claims updates, and identifying new financing or grant agreements entered into after year-end. 

Early Preparation Builds Confidence 

GASB 105 was issued to improve consistency in how subsequent events are reported and to better meet the information needs of financial statement users. For governments, consistency begins with routine discipline. The goal is not to create unnecessary complexity. The goal is to build a reliable process that captures relevant events, supports management’s evaluation, and helps the audit proceed more smoothly. 

Now is a good time for governments to review their year-end close calendars, communication channels, and documentation practices. A proactive approach can reduce surprises, improve disclosure quality, and give elected officials, management, auditors, and financial statement users greater confidence in the information presented. 

Brady Martz can help government finance teams think through upcoming standards, reporting timelines, and year-end processes in a practical way. A conversation now can make implementation feel more manageable when GASB 105 becomes effective.