The Canadian federal government is piloting a decentralized payroll support model to resolve ongoing failures within the Phoenix pay system. This new strategy assigns dedicated support staff to specific agencies rather than relying on centralized hubs.

Moving away from the Miramichi centralized model

Since its implementation in 2016, the Phoenix pay system has been defined by a centralized architecture, often routing support through hubs in locations such as Miramichi, New Brunswick. As the report indicates, this model has been plagued by systemic failures, resulting in thousands of public servants being either overpaid or underpaid for years. The current pilot represents a strategic retreat from this centralization, attempting to return to a model where payroll staff are embedded within the departments they serve.

This shift reflects a broader tension in government digital transformation: the struggle between the theoretical efficiency of a "single window" service and the practical necessity of institutional knowledge.. By moving support closer to the individual departments, the Canadian federal government is betting that specialized knowledge of agency-specific rules will reduce the errors that have haunted the Phoenix system for nearly a decade.

The 214,000 transaction backlog and 97% accuracy rate

Recent data suggests some progress in the system's stability, though the scale of the remaining work is immense. According to data from Public Services and Procurement Canada (PSPC), pay accuracy has remained above 97% since the start of 2025, with monthly rates fluctuating between 97.8% and 99.3%.

Despite these accuracy percentages, the volume of unresolved issues remains a significant burden. The report notes that the backlog of transactions was reduced to 214,000 from a peak of 320,000 in May 2025. while the reduction is a positive trend for Public Services and Procurement Canada (PSPC), the remaining quarter-million transactions highlight why the government is desperate to find a support model that actually functions for the end-user.

The Government Services Union's warning on worker isolation

The transition to decentralized support is not without internal friction. The president of the Government Services Union (GSU), which represents over 12,000 members including payroll workers, has reported that feedback regarding the new model is mostly negative. The GSU warns that processing cases is taking longer and that employees feel increasingly isolated when removed from the centralized support environment.

This internal conflict is mirrored by the Professional Institute of the Public Service of Canada (PIPSC). While PIPSC views decentralization as a viable path to fixing the Phoenix pay system,the union has cautioned that the government must ensure this move does not create "silos" between different departments, which could lead to inconsistent pay applications across the federal workforce.

Who are the two departments testing the 167-worker pilot?

A critical gap in the current reporting is the identity of the specific agencies involved in the trial. The report mentions that 167 support workers are currently deployed across two departments as part of the year-long pilot, but it does not name which departments these are. These workers are currently dealing with a 10% error rate in their respective areas.

Beyond the missing names of the departments, it remains unclear how the government will define "success" for this pilot. While the trial will analyze the number of closed cases and adherence to service standards, the government has not yet clarified if a successful pilot will lead to a full-scale reversal of the centralized Miramichi model or a hybrid approach that maintains some level of central oversight.