GASB 103 ACFR Compliance: What the New Standard Will Expose About Your Reporting Process

Jim Lee is Head of Solutions Engineering at ClearGov.

Every week, I talk to Finance Directors who tell me, in some version, the same thing: their Annual Comprehensive Financial Report (ACFR) runs on a stack of linked spreadsheets that only one or two people fully understand, and the institutional knowledge that holds it all together lives in someone’s head. For most of the last 25 years, that’s been a workable, if fragile, way to produce an ACFR. Under GASB 103, it isn’t anymore.

What GASB 103 Is, and Why It Matters Now

GASB Statement No. 103 was 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. The Finance teams we work with are using this as an opportunity to build a reporting infrastructure that will set their teams up for success for this year and beyond.

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: MD&A, unusual or infrequent items, proprietary funds, major component units, and budgetary comparison changes. While manageable individually, these provisions together make consistent compliance more challenging, particularly during staff changes. For more details, see our new guide.

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.

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.

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.

Institutional knowledge that walks out the door. This is the one I hear most often. The person who knows 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 is often one or two people on the team. 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.

That’s what ClearGov Financial Reporting Disclosure Studio is built for.

Connected data that flows automatically. ClearGov links your budget, actuals, periods, and disclosures into 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.

Compliance built into the workflow. We’re GASB 103-Ready. The new proprietary fund categories, the new RSI variance columns, and the structural MD&A requirements: all of them 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. Our ACFR templates applied to the financial statements are also GFOA-compliant.

Build it once, use it every year. Once your GASB 103-compliant structure is built in ClearGov, it rolls forward automatically and supports 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, OH reduced ACFR preparation time from two weeks to one day using ClearGov Financial Reporting. Read more. Over 1,700 local governments, school districts, and state agencies use ClearGov to manage 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.

You don’t have to figure this out alone, and you don’t have to start from scratch.Ready to see what GASB 103-Ready reporting looks like for your organization? Connect with a ClearGov rep for a personalized consultation and find out how other municipalities, counties, school districts, and special districts are getting GASB 103 compliant from day one.