What GASB 103 Is, and Why It Matters Now
GASB Statement No. 103, issued by the Governmental Accounting Standards Board in April 2024, is the first significant update to the government financial reporting model since GASB 34 in 1999.
Governments with a June 30 fiscal year-end must submit their first GASB 103-compliant ACFR for the fiscal year ending June 30, 2026. Those with September 30 or December 31 year-ends will comply in subsequent cycles.
This isn’t a formatting refresh. It’s a structural change to how finance directors plan, prepare, and present their ACFR, and it asks more of your reporting infrastructure than the previous model did. Finance teams are using this as an opportunity to build a reporting infrastructure that will set their teams up for success for this year and beyond.
Once a GASB 103-compliant reporting structure is established, it can be rolled forward to support monthly, quarterly, and annual cycles.
The Five Provisions Finance Teams Need to Plan For
GASB 103 affects five main areas of the ACFR, each with specific technical and operational requirements:
2. Unusual or infrequent items.
4. Major component units.
5. Budgetary comparison changes.
What GASB 103 Compliance Will Really Expose
GASB 103 compliance often gets framed as a technical accounting problem. It’s actually an operational problem and it’s going to put real pressure on three things many finance teams have quietly tolerated for years.
1. Spreadsheets that aren’t connected. When the new MD&A requires you to explain why a number changed, the explanation has to match the number exactly. Teams running their ACFR across disconnected workbooks already lose hours every cycle reconciling figures across statements, tables, charts, and narrative when something updates late. Under GASB 103, that disconnection is more costly than ever.
2. Variance reasoning that lives in someone’s head. GASB 103 requires significant budget variances to be explained in writing in the RSI notes, as part of your official ACFR. If your team doesn’t track variance reasons in real time, reconstructing them after year-end is hard, time-consuming, and exposes the team in audit conversations.
3. Institutional knowledge that walks out the door. Often, it's only one or two people on the team who know how the MD&A template was built, why fund transfers are categorized the way they are, and what the budget variance pattern means for each major fund. When they retire or move on, the next ACFR is built from a blank page. GASB 103 raises the cost of that gap dramatically.
What “GASB 103 Compliant From the Get-Go” Looks Like
GASB 103 compliance is achievable, but it requires finance teams to think about the ACFR as a process — one that connects data to narrative, captures reasoning when decisions are made, and rolls forward year over year, rather than a project rebuilt from scratch every reporting season.
True GASB 103 compliance means:
1. Connected data that flows automatically. Budgets, actuals, periods, and disclosures are connected within a single structured foundation. When numbers change, updates flow across statements, tables, charts, and narrative. The “why it changed” story in your MD&A stays connected to the numbers that back it up, without manual hand-offs or version-control chaos before audit.
2. Compliance built into the workflow. The new proprietary fund categories, the new RSI variance columns, and the structural MD&A requirements are supported in the templates from day one. Map your accounts to the predefined categories and your statements are aligned with the new requirements automatically.
3. Build it once, use it every year. Once a GASB 103-compliant reporting structure is established, it can be rolled forward to support monthly, quarterly, and annual cycles. Institutional knowledge moves from people into process. New staff can step into a documented, structured workflow on day one, instead of rebuilding from scratch.
The City of Columbus, Ohio, reduced ACFR preparation time from two weeks to one day by modernizing its financial reporting process. https://cleargov.com/rc/case-study/columbus-ohOver 1,700 local governments, school districts, and state agencies use structured reporting approaches to support the complete finance cycle: planning, budgeting, reporting, and engaging the community.
Your ACFR Deadline Is Closer Than You Think
The finance directors who get through their first GASB 103 cycle without a fire drill aren’t the ones with the most staff or the biggest budgets. They’re the ones who used GASB 103 as a forcing function: a chance to revisit their ACFR process and rebuild it on infrastructure that doesn’t fall apart when one or two key people move on.
If your reporting infrastructure today is a stack of linked spreadsheets and one finance manager who knows where every assumption lives, GASB 103 is going to put that under pressure. The question is whether you address that pressure before close, or after.