The long-awaited transition from the beleaguered Phoenix pay system is projected to cost a staggering £4.2 billion, according to a recent report from Auditor-General Karen Hogan. This figure highlights the federal government’s ongoing struggle to resolve a mounting backlog of unresolved pay complaints, which have plagued public servants for years. The issues stemming from the system, launched in 2016, serve as a cautionary tale of how large-scale IT projects can falter, leaving thousands of employees grappling with payment inaccuracies that date back several years.
Phoenix System’s Troubling Legacy
In the wake of its launch, the Phoenix pay system quickly became synonymous with crisis as a tide of complaints emerged from the public service. Despite efforts to address these issues, the backlog remains formidable, comprising over 233,000 cases as of September 30, 2025. Alarmingly, more than 155,000 of these cases involve transactions that are over a year old.
The government has pledged to phase out Phoenix in favour of a new system named Dayforce, with an initial rollout planned for three departments starting next year. However, this transition is set against a backdrop of significant uncertainty regarding the costs and the potential for repeating past mistakes.
Rising Costs and Uncertain Future
Hogan’s report reveals that the estimated cost of replacing Phoenix has escalated dramatically since earlier projections. In 2019, the Parliamentary Budget Officer estimated the transition would require £2.6 billion, yet the latest figures from Public Services and Procurement Canada indicate a preliminary estimate of over £4.2 billion. Notably, this figure does not encompass all anticipated costs necessary for departments and agencies to complete the transition.
Hogan expressed her concern that actual costs could exceed current estimates. “I do expect that the actual cost of making this transition will be higher than what’s currently estimated. The £4.2 billion is a preliminary estimate. It’s rough,” she stated at a press conference. The Auditor-General’s report, while not independently verifying the department’s figures, warns of the high risks associated with projects of this scale and complexity.
Addressing the Backlog Before Transition
The report underscores the necessity for departments to clear their existing backlog of complaints before migrating to the new Dayforce system. The Auditor-General emphasised that without resolving these issues, the new platform risks inheriting the same problems that have plagued Phoenix. Despite setting a target to eliminate all pay transactions older than one year by March 2026, recent internal reports indicate that the government is unlikely to meet this goal.
Hogan also pointed to the complexity of federal pay rules as a significant barrier to progress. The Treasury Board of Canada has been slow to simplify these regulations, which have historically led to myriad complications within the Phoenix system. “The need to simplify and standardise pay rules before introducing a new system was a core lesson learned from the transition to the Phoenix pay system,” she remarked. “It is concerning to me that, a decade later, there has been little progress made to simplify these rules.”
Government’s Response and Future Plans
The report’s findings have prompted a response from the government, with Joël Lightbound, Minister of Government Transformation, Public Works and Procurement, pledging to address the concerns raised. In his statement, he focused primarily on the backlog issue, sidestepping specifics regarding the cost estimates.
During a subsequent press conference, when pressed for details on the financial implications of the transition, Lightbound noted that officials are currently working on a detailed costing strategy. Meanwhile, Nathan Prier, president of the Canadian Association of Professional Employees, voiced scepticism regarding the government’s plan, suggesting that the introduction of artificial intelligence could exacerbate existing pay issues rather than resolve them. “The AG has just confirmed what public servants already know: Phoenix continues to do untold damage as the cost to taxpayers continues to rise,” he stated.
Why it Matters
The staggering costs associated with replacing the Phoenix pay system reflect deeper systemic issues within the Canadian federal payroll framework. As the government navigates this transition, the stakes are high—not just for public servants awaiting resolution of their pay discrepancies, but for the integrity of public service operations as a whole. The lessons learned from Phoenix must inform future IT projects to avoid repeating past mistakes, ensuring that the government can deliver on its promise to its employees and restore faith in its administrative capabilities.