The moment a municipal CFO approves an ERP replacement, they have made one of the largest and most consequential technology commitments in the organisation's operating history. The software will touch every financial transaction, every payroll run, every utility payment, every levy cycle, and every report that goes to council. It will be the system of record for fund balances, asset values, budget actuals, and arrears — for the next ten to fifteen years.
The approval decision deserves more rigor than most procurement processes give it. This article is not about software selection criteria. It is about the questions a CFO should be asking internally — and of any prospective implementation partner — before the RFP goes out, before the evaluation committee is formed, and before the organisation commits to a path it cannot easily reverse.
Before you evaluate any software
The most common failure mode in municipal ERP replacements is not choosing the wrong platform. It is entering a procurement process before the organisation understands what it is actually trying to fix.
Ask your team to answer three questions with specificity, not generality:
What are the five workflows where your current system creates the most operational friction?Not "reporting is difficult" — that is a category, not a workflow. The specific answer might be: "Our billing exceptions route through email with no tracking. Our arrears report requires three people and a spreadsheet to produce. Our year-end TCA schedule is rebuilt manually every March." Those are solvable problems with defined success criteria. "Reporting is difficult" is not.
Where does your current system create audit risk? Municipal finance operates under PSAB, provincial audit requirements, and council accountability frameworks. Identify the specific workflows where your audit trail depends on institutional knowledge rather than system records — approval paths that live in email threads, journal entry adjustments with no documented rationale, asset records that exist only in a spreadsheet someone maintains. These are not just operational inconveniences. They are governance exposures.
What would have to be true for this replacement to be considered a success in three years? The answer to this question — stated in operational terms, not technology terms — is the foundation of your scope definition, your UAT criteria, and your post-implementation evaluation framework. If you cannot answer it now, you are not ready to approve a procurement.
Scope questions worth getting right before the RFP
Scope is where most municipal ERP projects fail — not at go-live, but in the twelve months before it, when decisions made too early or too vaguely come back with a cost attached.
Are your civic modules in scope — and does your implementation partner have depth in them? The modules that drive the most operational risk in a Canadian municipality are often not the finance and HR modules that dominate generic ERP discussions. They are property taxation, utility billing, permitting, licensing, asset management, and work orders. These modules have operating requirements — assessment authority integrations, levy blackout windows, billing cycle dependencies, PSAB capital asset treatment — that a partner without Canadian municipal experience will discover mid-project, not in discovery.
Ask directly: which of these civic modules has your prospective partner implemented, in which Canadian municipalities, and against which legacy systems? A partner that can name the municipalities, describe the assessment authority integration they configured, and explain how they handled the levy blackout calendar is a different proposition from one that can show you a feature list.
Is fund accounting in scope — and is it configured for PSAB, not commercial accounting? Fund-based financial statements, full-accrual reporting, TCA classification, reserve fund tracking, and deferred revenue treatment are not optional additions to a municipal finance configuration. They are the core of how your organisation reports to council and to provincial auditors. An ERP finance implementation that treats these as afterthoughts — configuring a commercial chart of accounts and adding fund segments later — will produce a system your finance team cannot rely on for statutory reporting.
What happens to the data from the system you are replacing? Data migration is consistently underestimated in municipal ERP projects. Assessment history, utility account history, asset records, permit history — this data is often scattered across legacy systems, spreadsheets, and filing cabinets. Poor data quality in the source systems is the single most common cause of go-live delays. Before approving a replacement, your organisation needs to understand what data exists, where it lives, how clean it is, and who will own the validation process. That assessment cannot be delegated entirely to an implementation partner.
Questions to ask any implementation partner before shortlisting
The RFP process will surface many capable-looking responses. These questions are designed to distinguish genuine municipal depth from polished capability claims.
Walk us through how you approached fund accounting configuration in a recent Canadian municipal implementation.A partner with genuine depth will describe the fund ledger structure, explain how they handled PSAB accrual requirements, and be able to name the specific challenges they resolved — deferred revenue classification, reserve fund transfers, year-end fund balance reporting. A partner without that depth will describe the platform's fund accounting capabilities without reference to how they configured them for a specific municipality.
How did you handle the assessment authority integration in your most recent property tax implementation? The answer should include the assessment authority involved (MPAC, BC Assessment, SAMA, or other), the data format and frequency, the validation rules configured before the levy run, and any data quality issues encountered in the assessment data and how they were resolved. If the partner has not done this integration, that is important information to have before shortlisting.
What does your data migration process look like — how many cycles, who validates, and what is your reconciliation standard?The correct answer involves multiple migration cycles, a defined validation methodology, and a clear statement of who owns sign-off on each data category. A migration described as "a few passes before go-live" with validation owned entirely by the partner is a risk factor, not a methodology.
What does hypercare cover, and when does it end? Hypercare that ends one week after go-live is not hypercare — it is a handoff. For a municipality, the first real test of a new billing system is the first full billing cycle. The first real test of the payroll module is the first payroll run. The first real test of the tax module is the first levy run. Hypercare should run through each of those milestones. Ask specifically: does hypercare continue through our first full utility billing cycle? Through our first property tax levy? If the answer is no, negotiate the answer to yes before contract.
The procurement process itself
Canadian municipal procurement has specific characteristics that affect how an ERP replacement should be structured and evaluated.
RFP evaluation criteria need to weight implementation methodology, not just platform capability. Most municipal RFPs over-weight software features and under-weight implementation approach, team experience, and post-go-live support discipline. A platform with every feature your municipality could want, implemented by a team that does not understand Canadian public-sector operating constraints, will produce a worse outcome than a well-scoped implementation by a team with genuine municipal depth.
Reference checks matter more than demonstrations. A software demonstration shows you what the platform can do in a controlled environment with curated data. A reference conversation with a finance director or tax administrator at a Canadian municipality that recently went live tells you what the implementation was actually like — the data migration challenges, the training quality, the go-live experience, and what post-go-live support looked like in the first six months. Prioritise references over demonstrations in your evaluation process.
Council approval requirements shape the timeline, not the other way around. Municipal ERP procurements often involve standing committee review, council approval, and public reporting requirements that add weeks or months to the procurement timeline. Build these into the project plan from the start. A realistic procurement and implementation timeline for a full-scope municipal ERP replacement — from RFP to stable go-live — is typically eighteen to thirty-six months, depending on scope and municipal capacity. Organisations that compress this timeline to meet an internal target usually pay for it in implementation quality.
What a well-prepared CFO looks like going into this decision
The CFOs who navigate municipal ERP replacements most successfully share a few characteristics. They are specific about what they are trying to fix before they evaluate how to fix it. They understand which of their workflows are civic-specific and insist on an implementation partner with depth in those areas. They are honest about their organisation's internal capacity to support an implementation alongside normal operations. And they treat data migration as a strategic workstream, not a technical detail.
They also ask the questions above — not in the RFP evaluation, but before it. The time to discover that a prospective partner has never configured PSAB fund accounting for a Canadian municipality is not during reference checks after shortlisting. It is in the first conversation.
Before you go further
If your municipality is at the stage of internal assessment rather than active procurement, the Municipal ERP Readiness Guide covers the diagnostic questions worth answering before any external process begins — across scope, data, governance, and implementation risk.
If you are ready to discuss your specific situation, a 30-minute Municipal Workflow Review is available. We focus on one or two workflow areas — the friction in the current state, and what improvement looks like in your operating context.