There are two angles there.
When it comes to pay for individuals who work in the public service, as you'll recall, when there was a transformation of the HR-to-pay systems and Phoenix was put into place, there were many pay issues. Some of those pay issues remain.
What we highlight here is that it isn't about Phoenix itself not calculating people's salary but that a significant portion of the errors we continue to find are data entry errors or delays in entering things—for example, promotions, acting pays and so on. That's about fixing the process even before things are entered into an IT system.
That would be the first issue, and that's ongoing. I think the big concern is that, as the government is moving towards modernizing pay and changing the Phoenix pay system, you have to fix all of these errors before you put them into a new system, because bad data will still result in errors in people's pay. It's important to fix all of that before a new system is put into place.
The second issue has to do with IT issues. This is a new issue we've found in the last couple of years. It's important because you want to properly manage control over important IT systems in the public service. We found that many users had access to systems they did not need in order to carry out their functions. While we were able to do work to make sure they didn't do anything they shouldn't have done, like perhaps changing numbers in error, it is still a risk, and it does create inefficiencies for our audit and for the government.
This is where we need Shared Services to start working on some of the recommendations that we've given them to improve IT general computer controls, especially when they provide lots of services to the broader public service. It's something we're going to keep monitoring, because in the vein of being more efficient in delivering audits, we need to be able to rely on IT computer controls to have a faster and more effective audit.