Why Dynamics GP End of Life Is a PSAB Reporting Risk for Canadian Municipalities

Microsoft Dynamics GP end of life is not only an IT concern for Canadian municipalities. It can become a finance, reporting, audit, and PSAB readiness risk when core workflows depend on aging reports, spreadsheet workarounds, municipal add-ons, and legacy data structures that are difficult to validate during year-end.

For municipal finance leaders, the real question is not only “when does GP support end?” The bigger question is whether the municipality can continue producing reliable PSAB reporting, audit evidence, and finance continuity as the system approaches the end of its lifecycle.

Why does Dynamics GP end of life matter to municipalities?

Dynamics GP has supported finance teams for many years, but many municipal environments have grown around it in complex ways. A municipality may rely on GP for general ledger, accounts payable, accounts receivable, reporting, fixed assets, payroll handoffs, tax integrations, utility billing handoffs, or spreadsheet-based year-end processes.

Microsoft states that Dynamics GP product support and updates end on December 31, 2029, with security patches ending on April 30, 2031. Microsoft Learn also describes the current Dynamics GP 18.x release as governed by the Modern Lifecycle Policy, where support and servicing include bug fixes and tax updates while customers stay current.

For municipalities, these dates matter because finance systems are not isolated. A change in support, regulatory updates, technical support, or long-term viability can affect reporting controls, audit preparation, data extraction, integrations, and the ability to plan a controlled Microsoft Dynamics GP migration without disruption.

Why is this a PSAB reporting risk?

PSAB reporting depends on reliable financial structures, supporting records, and evidence trails. If those workflows are spread across Dynamics GP, spreadsheets, reports, add-ons, and manual reconciliations, the municipality may face risk when planning migration or year-end reporting.

The risk is not that Dynamics GP immediately stops working. The risk is that the municipality may not fully understand which reports, data fields, integrations, and manual processes are required to support PSAB reporting until the migration is already underway.

That can create pressure around:

• Fund accounting structures
• Chart-of-accounts mapping
• Tangible capital asset records
• Deferred revenue
• Grants and reserves
• Year-end schedules
• Audit evidence
• Historical reporting
• Management Reporter or Excel dependencies
• Finance-to-payroll and finance-to-tax handoffs

When these dependencies are not mapped early, migration becomes more than a technology project. It becomes a reporting continuity issue.

How can Dynamics GP migration affect PSAB 3150 readiness?

PS 3150, Tangible Capital Assets, establishes how public-sector organizations account for and report tangible capital assets. PS 3150 applies to tangible capital assets such as non-financial assets with physical substance that are held for use, have useful economic lives extending beyond one accounting period, are used on a continuing basis, and are not held for sale in the ordinary course of operations.

For municipalities, this matters because tangible capital asset records often connect finance, infrastructure, asset management, public works, spreadsheets, and audit schedules. During a Dynamics GP migration, municipalities need to understand how tangible capital asset records are currently maintained, where supporting data lives, and how those records connect to finance reporting.

Common issues include:

• Asset records maintained outside the core finance system
• Historical cost data stored inconsistently
• Amortization schedules managed manually
• Infrastructure asset details stored in spreadsheets or side systems
• Gaps between asset management records and financial reporting records
• Limited audit trail for changes or adjustments

PS 3150 summaries also emphasize that tangible capital assets must be recorded at cost, and that the cost of a tangible capital asset with a limited life is amortized over its useful life, less any residual value. If those cost, useful life, amortization, and evidence details are incomplete or scattered, migration can create pressure during year-end, audit review, or post-migration reconciliation. Municipalities can mitigate this risk by integrating a PSAB Fund Accounting Accelerator to pre-align their ledger structures.

What should municipalities map before moving off Dynamics GP?

Before selecting or implementing a new system, municipalities should complete a current-state workflow review. This review should identify the full municipal stack behind Dynamics GP, not only the finance application itself.

At minimum, municipalities should map:

1. Core finance workflows
   General ledger, accounts payable, accounts receivable, cash management, budgeting, reporting, grants, reserves, and year-end processes.
2. Reporting dependencies
   Management Reporter, Excel reports, board or council reports, audit schedules, PSAB schedules, and recurring finance extracts.
3. Data dependencies
   Chart of accounts, vendors, customers, funds, departments, projects, grants, assets, historical transactions, and opening balances.
4. Integrations and handoffs
   Payroll, property tax, utility billing, banking, document systems, GIS, resident service systems, and other municipal add-ons.
5. RICE inventory
   Reports, interfaces, conversions, and extensions or enhancements that must be understood before migration.
6. Cutover and blackout periods
   Month-end, year-end, tax billing, utility billing, payroll cycles, council reporting, and audit timelines.
7. First-cycle stabilization needs
   The first financial close, first reporting cycle, first tax or utility handoff, and first audit period after go-live.

This mapping helps reduce the risk of discovering critical reporting dependencies after implementation has already started.

Why should this be handled before procurement?

Many municipalities begin ERP replacement by asking which system they should buy. A safer starting point is to ask what must not break.

For a municipal finance team, that means understanding:

• Which reports are required for PSAB reporting
• Which spreadsheets are part of the real process
• Which manual reconciliations are relied on
• Which data must be migrated
• Which historical records must remain accessible
• Which workflows are tied to year-end and audit evidence
• Which add-ons or integrations are critical to daily operations

This current-state discovery gives the municipality a stronger basis for procurement, vendor evaluation, implementation planning, and internal decision-making.

What this means for your municipality

Dynamics GP migration should not be treated as a simple system replacement. For Canadian municipalities, it should be treated as a finance continuity and PSAB readiness project.

The practical first step is not to rush into configuration. It is to map the current state clearly enough that finance, IT, operations, and leadership understand what the future system must preserve, improve, or replace.

A well-planned migration should help the municipality protect reporting continuity, reduce audit friction, and avoid recreating legacy complexity in a new environment.

Sources

• Microsoft announcement: Announcing End of Support for Dynamics GP
• Microsoft Learn: Dynamics GP Lifecycle Policy
• BDO Canada: PSAS at a Glance: Section PS 3150 Tangible Capital Assets

Frequently Asked Questions