PSAB fund accounting readiness means a municipality can support year-end reporting with clear fund structures, reliable balances, complete schedules, documented evidence, and reconciled workflows before audit pressure begins. For municipal CFOs and finance leaders, the goal is not only to close the year. It is to make sure the finance team can explain, support, and reproduce the numbers behind the year-end package.
Year-end readiness should be checked before the final reporting cycle, not during the audit.
Why PSAB readiness matters before year-end
Municipal year-end reporting often depends on more than the core finance system. It may involve spreadsheets, fund schedules, deferred revenue tracking, grant files, reserve continuity, tangible capital asset records, payroll handoffs, and manual reconciliations.
If these inputs are not reviewed early, the finance team may spend year-end chasing evidence instead of validating results.
PSAB readiness helps municipalities reduce last-minute pressure by confirming:
- Fund balances are explainable
- Reporting structures are aligned
- Audit evidence is accessible
- Year-end schedules are current
- Deferred revenue and grants are supported
- Reserve movements are documented
- Tangible capital asset records are reconciled
- Manual adjustments are reviewed
- Reporting dependencies are understood
The earlier these items are checked, the easier it is to resolve gaps before audit timelines tighten.
1. Check fund structures and reporting alignment
Start with the fund structure.
Municipalities should confirm that funds, departments, cost centres, projects, grants, reserves, and reporting categories are still aligned with how the municipality needs to report.
Review:
- Fund setup
- Chart-of-accounts structure
- Department and program coding
- Project and grant coding
- Reserve and restricted fund tracking
- Interfund activity
- Closing entries
- Reporting hierarchies
- Financial statement mapping
If the fund structure has grown over time without cleanup, year-end reporting can become harder than it needs to be.
2. Check deferred revenue and grant schedules
Deferred revenue and grant reporting often create year-end pressure because finance teams need to support both balances and movement.
CFOs should confirm:
- Opening balances are reconciled
- New funding received is recorded correctly
- Eligible expenditures are tracked
- Recognition entries are documented
- Restrictions are clear
- Supporting agreements are accessible
- Grant reporting deadlines are known
- Unspent balances are explainable
- Related schedules tie back to the general ledger
This is especially important when grant details live outside the ERP in spreadsheets, shared drives, or department-managed files.
3. Check reserve continuity
Reserve reporting should clearly show what changed during the year and why.
Review:
- Opening reserve balances
- Contributions
- Transfers
- Approved uses
- Council approvals where applicable
- Restricted versus unrestricted treatment
- Project or capital links
- Closing balances
- Supporting documentation
- Financial statement presentation
If reserve movements are not documented clearly, year-end review can become dependent on institutional memory.
4. Check tangible capital asset readiness
Tangible capital asset records are a common source of year-end complexity.
Finance leaders should review tangible capital asset readiness details including:
- Asset additions
- Disposals
- Betterments
- Work in progress
- Amortization
- Accumulated amortization
- Useful life assumptions
- Asset categories
- Capital project closeouts
- Reconciliation to the general ledger
- Supporting invoices and project files
For municipalities, this is not only an accounting exercise. Tangible capital asset readiness often depends on handoffs between finance, public works, engineering, facilities, utilities, and asset management teams.
5. Check year-end schedules and audit evidence
Before year-end, CFOs should confirm which schedules are required and who owns them.
Common schedules include:
- Cash and bank reconciliations
- Accounts receivable
- Accounts payable
- Deferred revenue
- Grants
- Reserves
- Tangible capital assets
- Debt
- Accruals
- Commitments
- Contingencies
- Payroll-related accruals
- Post-employment benefit inputs
- Pension-related handoffs
Each schedule should have an owner, source data, review process, and evidence location.
6. Check spreadsheet dependencies
Many municipalities rely on spreadsheets for reporting, reconciliations, schedules, and audit support.
That is not automatically a problem. The risk is when no one knows which spreadsheets are critical, who owns them, or how they connect to the general ledger.
Review:
- Which spreadsheets support year-end
- Which spreadsheets feed financial statements
- Which files include manual adjustments
- Which formulas are not reviewed
- Which files depend on exports
- Which versions are final
- Which files are stored outside controlled locations
- Which spreadsheets should be replaced, simplified, or retained
Spreadsheet dependency mapping is especially important before ERP modernization or finance-system migration.
7. Check payroll-to-finance handoffs
Payroll can affect year-end reporting through accruals, benefits, pension-related inputs, retroactive pay, banked time, leave balances, and department costing.
Finance should confirm:
- Payroll expenses reconcile to finance
- Accruals are complete
- Benefit and pension inputs are available
- Retroactive pay or adjustments are identified
- Department or program coding is accurate
- Payroll-to-GL handoffs are documented
- Manual payroll adjustments are reviewed
- Supporting records are accessible
For unionized or public-sector environments, pay rules and payroll handoffs may be more complex than they appear in summary reporting.
8. Check reporting and system dependencies
Year-end reporting may depend on reports, exports, queries, and tools that are not well documented.
CFOs should identify:
- Standard financial reports
- Custom reports
- Management reports
- Excel exports
- Report writers
- Saved queries
- Manual data pulls
- External reporting templates
- Audit request reports
- Council or board reporting packages
The goal is to confirm which reports are required, where they come from, and whether the finance team can reproduce them consistently.
9. Check controls and approvals
Year-end readiness also depends on controls.
Review:
- Journal entry approvals
- Closing entry approvals
- Reserve transfer approvals
- Grant recognition approvals
- Capital asset approvals
- Bank reconciliation review
- Manual adjustment review
- Evidence retention
- Segregation of duties
- Audit access requirements
Controls should be practical and visible. If approvals happen outside the system, the evidence still needs to be retained and easy to locate.
10. Check modernization risks before they become year-end risks
If the municipality is planning ERP modernization, Dynamics GP migration, reporting redesign, or workflow cleanup, year-end is the best time to identify what must be preserved.
Finance should document:
- Reports that must continue
- Schedules that must be migrated or redesigned
- Data that must remain accessible
- Evidence trails that must be retained
- Manual processes that need improvement
- Controls that need to be configured
- Historical records required for audit or reference
- First-year stabilization needs after go-live
This makes modernization planning more realistic because it is based on actual year-end requirements.
What this means for your municipality
PSAB fund accounting readiness is not a one-time year-end task. It is an operating discipline that connects finance structure, data quality, audit evidence, reporting workflows, and municipal controls.
For CFOs, the practical starting point is to identify which schedules, reports, reconciliations, and evidence trails are required before year-end pressure begins.
A stronger readiness review can help the municipality reduce audit friction, protect reporting continuity, and prepare for future finance modernization with more confidence.
Sources
Frequently Asked Questions
What is PSAB fund accounting readiness?
PSAB fund accounting readiness means the municipality can support fund balances, reporting schedules, reconciliations, deferred revenue, grants, reserves, tangible capital assets, and audit evidence in a clear and reviewable way.
When should municipalities review PSAB readiness?
Municipalities should review PSAB readiness before year-end, ideally early enough to resolve gaps in data, schedules, approvals, reconciliations, and supporting evidence.
What should CFOs check first?
CFOs should start with fund structures, chart-of-accounts alignment, deferred revenue, grants, reserves, tangible capital assets, year-end schedules, audit evidence, and spreadsheet dependencies.
Why do spreadsheets matter for PSAB readiness?
Spreadsheets often support year-end schedules, reconciliations, audit evidence, and manual adjustments. If they are not documented or controlled, they can create reporting and audit risk.
How does PSAB readiness connect to ERP modernization?
PSAB readiness helps identify the reports, data structures, workflows, controls, and evidence trails that must be preserved or improved during ERP modernization.
What is the biggest year-end risk for municipalities?
The biggest risk is discovering too late that critical balances, schedules, evidence, or reporting dependencies are incomplete, undocumented, or spread across disconnected systems and spreadsheets.