GASB Statement No. 103 is a financial reporting standard issued by the Governmental Accounting Standards Board (GASB) that improves the financial reporting model for state and local governments. This statement updates requirements for Management’s Discussion and Analysis (MD&A), proprietary fund financial statements, and budgetary comparison information.
GASB 103 is effective for fiscal years beginning after June 15, 2025, which puts most finance teams in their first reporting year right now.
For governments with a June 30 fiscal year-end, FY2026 financial statements will be the first to reflect the new requirements. Understanding how payment reconciliation supports GASB 103 compliance will help teams prepare for these new reporting standards.
Key Takeaways
- GASB 103 mandates budgetary comparison information as required supplementary information for major funds.
- Finance teams must provide written explanations for significant budget-to-actual variances in their reporting.
- Accurate financial reporting relies on reconciled data to ensure actual results are fully defensible.
- Effective payment reconciliation identifies timing differences and unapplied receipts before the period closes.
- Automated reconciliation workflows provide a clear audit trail for all government revenue collections.
Key Changes to Budgetary Comparison Requirements Under GASB 103
GASB 103 requires governments to present budgetary comparison information as required supplementary information (RSI), using that single method rather than the previous option to report it as a basic financial statement. The schedules apply to the general fund and each major special revenue fund that has a legally adopted annual budget.
GASB 103 introduces two primary requirements for budgetary comparison schedules. First, they need separate columns for the variance between the original and final budget amounts, and the variance between the final budget amounts and actual results. Second, for significant variances in either column, you now must include a written explanation in the notes to RSI.
That requirement for written variance explanations fundamentally changes the financial reporting process for government agencies. It’s no longer enough to present the numbers and let them speak for themselves. A reader of your statements will see, in writing, why your final budget moved from your original budget, and why your actual results landed where they did against that final budget. Those explanations become part of the record your auditors review.
The Role of Reconciled Financial Data in GASB 103 Variance Reporting
The variance columns are only as trustworthy as the actual financial results used as inputs. GASB Statement No. 103 doesn’t prescribe how governments reconcile transactions, but producing reliable actual results and defensible variance explanations depends on accurate, reconciled financial data. This is exactly how payment reconciliation supports GASB 103 compliance by ensuring the integrity of the underlying numbers.
The original and final budget figures come from the adopted and amended budget. The actual results column is where reported financial results enter the schedule and where the greatest audit risk exists.
Each actual revenue figure in a budgetary comparison schedule must be traceable to specific collections recorded in the right fund and account. If your payment records and your general ledger disagree, the actual results you report are built on an unverified number. The written variance explanation you attach to it then rests on the same shaky footing. If an auditor questions the actual figure, they’re questioning whether the underlying collections were reconciled before they reached the financial statements.
For many governments, those collections arrive through a mix of online portals, in-person counters, kiosks, lockboxes, and third-party payment providers. Bringing that payment activity together before it reaches the general ledger is one reason governments use platforms such as Euna Payments. With collection and reconciliation connected in a single workflow, finance teams have a clearer path from payment activity to the actual results that flow into budgetary comparison schedules.
While the reporting change appears minor, they increase the demand for high-quality underlying financial data.
How Payment Reconciliation Keeps Actual Results Accurate
Reconciliation keeps actual results accurate by verifying that every recorded transaction matches an actual movement of money before it reaches your reporting. A working reconciliation process matches what your payment systems captured against what your bank actually settled, then confirms both agree with your general ledger before the period closes.
Consider a common example:
A batch of online utility payments posts to the collection system on the last business day of the month, but the bank settles them two days later, in the next period. Without reconciliation, that timing difference can leave the utility fund’s actual revenue overstated in one period and understated in the next. Caught during reconciliation, it gets recorded in the correct period, and the actual results in your budgetary comparison schedule reflect what truly happened. Left uncaught, it becomes a variance you can’t cleanly explain, because the number itself is wrong.
Multiply that single example by every fee, tax, permit, and utility payment a government collects in a year, and the value of reconciliation to your reported actuals becomes clear.
While payment reconciliation isn’t the only control that supports accurate actuals, it’s one of the first places where timing differences and unapplied receipts appear and posting errors are caught before they reach the general ledger. Catching those issues before period close gives finance teams greater confidence in the numbers.
Clean reconciliation is what lets you stand behind the actual figure when someone asks how you arrived at it.
Best Practices for Leveraging Reconciled Data in GASB 103 Implementation
Start with one rule: reconcile before you report. In year one especially, every variance explanation in your notes to RSI should trace to reconciled data you can produce if asked, not to memory or estimate.
A defensible variance explanation names the cause of the variance in plain language and ties it to reconciled figures that can be supported during audit.
A weak explanation reads: “Actual revenues exceeded the final budget due to higher-than-expected collections.” A strong one reads: “Actual sales tax revenue exceeded the final budget by $412,000, or 6.1 percent, driven by stronger fourth-quarter retail activity. The figure reflects collections reconciled to bank deposits through June 30 and matched to the general fund.”
The difference between those two is reconciled data. The first explanation could have been written before the books were closed. The second could only have been written after the numbers were verified, which is the standard you want your notes to meet in your first reporting year.
Preparing Government Reconciliation Processes for GASB 103 Compliance
Getting ready starts with looking at how, and how often, your collections are reconciled today. The easiest year-one implementation won’t happen because finance teams worked harder during year-end close. They’ll happen because reconciliation was already part of the monthly close process.
A short readiness review for the months before your first GASB 103 close:
- Confirm which funds carry a legally adopted annual budget, since those are the ones that need budgetary comparison schedules.
- Check how long it currently takes to reconcile collections to bank statements and to the general ledger, and whether that timing lets you close cleanly.
- Identify the revenue sources most prone to timing differences or misapplied payments and tighten reconciliation there first.
- Decide who owns the written variance explanations and make sure that person can pull reconciled figures on demand.
- Run a practice reconciliation and draft variance narratives on a recent period, so year one isn’t the first time you write them.
Teams that already reconcile every month walk into that first close with actual figures verified and explanations defensible before anyone asks.
Euna Payments supports that work by bringing payment activity from multiple collection channels into one reconciliation workflow, helping finance teams move into period close with less manual reconciliation and greater confidence in the actual results they’ll report.
Frequently Asked Questions
How does payment reconciliation support GASB 103 compliance for local governments?
Payment reconciliation supports GASB 103 compliance by ensuring that actual financial results are accurate and verifiable before they enter budgetary comparison schedules. By matching payment records to bank settlements and the general ledger, finance teams can produce defensible variance explanations that satisfy audit requirements for required supplementary information.
Why is variance explanation important under the new GASB 103 standards?
GASB 103 requires written explanations for significant variances between final budget amounts and actual results in the notes to required supplementary information. These explanations must be supported by reconciled data, as auditors will review the underlying financial records to verify the accuracy of the reported revenue figures.
What role do timing differences play in government financial reporting?
Timing differences occur when collections and bank settlements happen in different reporting periods, potentially misstating actual revenue. Effective reconciliation identifies these discrepancies before the period closes, ensuring that actual results in the budgetary comparison schedule reflect the correct period and preventing unexplained variances that could trigger audit concerns.
How can finance teams prepare for the first GASB 103 reporting cycle?
Finance teams should prioritize monthly reconciliation of all revenue collections to bank statements and the general ledger. By establishing a consistent reconciliation workflow, agencies can verify actual results and draft defensible variance narratives well before the fiscal year-end, ensuring a smoother transition to the new GASB 103 reporting requirements.
