Phoenix pay system audit: findings and replacement status
- Auditor
- Office of the Auditor General of Canada
- Report date
- 29 May 2018
- Subject
- Building and implementing the Phoenix pay system
- Contractor
- IBM and other project suppliers
- Status
- follow-up pending
- Last checked
- 19 October 2026
What the audit found
The 2018 audit examined the project from April 2008 through the April 2016 launch. It found that the department did not fully test Phoenix, cancelled a live pilot, removed or deferred more than 100 pay functions and implemented the system without a complete contingency plan 2.
The Auditor General reported that the initiative had a $310 million budget, including $155 million for the software project. IBM received the 2011 contract to help design, customise, integrate and implement the PeopleSoft-based system 2.
A separate 2017 audit found more than $520 million in pay errors outstanding at 30 June 2017 and 494,500 outstanding pay requests 1.
The official response
Public Services and Procurement Canada and the Treasury Board Secretariat agreed with the 2018 recommendations. Their responses promised stronger project governance, stakeholder participation, testing, independent reviews, software-upgrade planning and contingency planning for future government-wide IT projects 2.
The 2026 audit found that the bodies planning Dayforce were still in the planning phase. It said they had time to address risks, but pay-rule simplification had moved slowly and the department was developing system customisations 3.
Parliament
The 2017 and 2018 reports were reports of the Auditor General to the Parliament of Canada 1,2. The 2018 report set out the audited bodies' responses beside each recommendation 2.
No separate parliamentary committee conclusion is relied on for this page. The audit reports and the later replacement audit provide the primary record reviewed here.
Follow-up audits and recommendations
The 2026 audit examined the project to replace Phoenix with Dayforce. It recorded that Public Services and Procurement Canada had made limited progress reducing the pay backlog and that the preliminary replacement estimate exceeded $4.2 billion, excluding some transition costs 3.
At 30 September 2025, the backlog stood at 233,653 transactions affecting 133,619 employees. The audit recommended clearer service standards, fuller transition cost estimates and performance measures comparing Dayforce with Phoenix 3.
Courts, tribunals and investigations
No court judgment deciding the Auditor General's Phoenix project-management findings was identified in the official audit sources reviewed as of 19 October 2026. Employee pay claims and labour processes are separate from the audit conclusion.
Where it stands now
Phoenix continues to process federal public-service pay during the replacement project. The 2026 audit said vendor support could end as early as 2036 and recorded that the department shortened its planned Dayforce transition schedule after the audit period 3.
The replacement project had not completed planning by the end of the audit period. The Auditor General said the shortened schedule required early identification and monitoring of new risks 3.
Timeline
| Date | Event |
|---|---|
| June 2011 | The government awarded IBM a contract to help design and implement Phoenix 2. |
| 24 February and 21 April 2016 | Phoenix was launched in two waves 2. |
| 21 November 2017 | The Auditor General published the Phoenix pay problems audit 1. |
| 29 May 2018 | The Auditor General published the implementation audit 2. |
| 23 March 2026 | The Auditor General published the Dayforce replacement audit 3. |
Common questions
Who built Phoenix?
Public Services and Procurement Canada led the project. IBM was contracted to help design, customise, integrate and implement the PeopleSoft-based system 2.
Were the audit recommendations accepted?
The department and Treasury Board Secretariat agreed with the 2018 recommendations 2.
Has Phoenix been replaced?
No. The 2026 audit described a planned move to Dayforce that was still in the planning phase during the audit period 3.
Audit cases move on. Each page shows the date we last checked it. Spotted an error or a newer official record? Email [email protected] with the official link.
Sources
- Office of the Auditor General of Canada: Report 1, Phoenix Pay Problems (21 November 2017)
- Office of the Auditor General of Canada: Report 1, Building and Implementing the Phoenix Pay System (29 May 2018)
- Office of the Auditor General of Canada: Modernizing the Pay System (23 March 2026)
Related
- ArriveCAN audit: findings, responses and where the case stands
The Auditor General audited ArriveCAN in February 2024. What followed: Parliament, the procurement ombud, the RCMP and the GC Strategies ban.
- New Zealand Novopay audits: errors and later controls
Auditor-General findings on Novopay's effect on school accounts, ministry remediation, later payroll controls and the move to EdPay.
- NHS National Programme for IT: audits and final outcome
NAO reports, the Department of Health response, Parliament's recommendations, dismantling of the programme and the final benefits review.
- HealthCare.gov audits: findings, response and fixes
GAO findings on contract oversight, system testing and security after the 2013 HealthCare.gov launch, with recommendation status.
- Universal Credit audit: what happened after the 2013 report
NAO findings on Universal Credit from the 2013 programme reset through the 2024 migration review and current audit position.