Hidden risks of Australian or New Zealand non-comprehensive award interpretation and poor implementation management processes are the two biggest risks that need to be avoided
We have one of the most complex award systems in the world
The award interpretation capabilities should be at the core of deliberation, not just the UI or workflows
Additionally, the project delivery must ensure all steps are efficiently covered by the project system, with visibility of each sequential component
The following case study provides evidence of the issues when the project is not well run
Dayforce Payroll System Fails Go-Live Performance Due to Poor Set Up and Project Delivery
AI Overview
Sydney Water is facing a massive backlash after rolling out a new “Dayforce” payroll system, leaving hundreds of workers underpaid, unpaid, or receiving their wages late. The botched transition has sparked significant union pushback, with the Australian Services Union lodging an application with the Fair Work Commission. [1]
The major issues surrounding the payroll disaster include:
- System Transition Failure: At the start of July, Sydney Water transitioned to the new Dayforce software. The Australian Services Union (ASU) alleges the system failed in testing and that employees received little to no training, leading to chaotic implementation. [1]
- Impact on Staff: Hundreds of workers have experienced delayed or incorrect pay. Staff have reported mass-level anxiety, with essential workers struggling to pay their mortgages, rent, and other day-to-day bills. [1]
- Union & Management Response: The ASU has applied to the Fair Work Commission, demanding that Sydney Water either fix the Dayforce system immediately or temporarily revert to the old payroll system until the issues are resolved. Sydney Water has officially apologised, admitting the transition “had not gone as we planned,” and stated they are working to rectify issues as a matter of urgency. [1]
https://www.youtube.com/shorts/aP6GG1Tf1lE
Payroll Projects Can Go Array Due To Poor and Incomplete Payroll Specific Project Management and Expertise
Cases of catastrophic payroll projects include Queensland Health, ACT Government and more recently the Sydney Water Payroll upgrades.
“When a payroll implementation goes wrong, employees may struggle to pay rent, mortgages, child support, or everyday living expenses” Mahbub-Afim-Cahri
Payroll Projects Problems:
Media report https://streamlinefeed.co.ke/news/sydney-water-dayforce-payroll-blunder-leaves-workers-unpaid , employees experienced problems following the implementation of the new Dayforce payroll platform, including under and, overpayments, delayed pays, incorrect superannuation outcomes. Reports also highlighted poor training, testing, and readiness for go-live.
Much discussion has focused on the payroll vendor involved in the system and the project management
Questions to ask are why the payroll implementation failed
The top 5 contributing factors towards poor payroll implementations include:
- Poor cross-business buy-in into the need for the change.
- Incomplete business needs analysis and documentation, and
- Poor project management, governance, and
- Need to undertake client-specific developments and integration activities across scheduling, T&A, Timesheet process and award-interpreted payroll systems, and
- Poor or incomplete training and pre- and post-go-live support
In this case, was this a technology failure, a project governance failure, or both?
At this stage, it has not been published outside the project to determine the root cause. However, when we look beyond the Dayforce system in the headlines, the reported symptoms are familiar to many payroll professionals.
They often indicate not just system defects, but weaknesses in project planning, governance, change management, testing, and organisational readiness.
Payroll is not just a management or IT project;
Payroll transformations are not just standard technology implementations. Payroll projects are high risk where project and outcome errors and omissions can be serious for the employees and the business
When a payroll implementation goes wrong, employees may struggle to pay rent, mortgages, child support, or everyday living expenses and even bee required to repay overpayments.
That is why payroll projects should be viewed through each user group’s experience and learnings
Many of the business team members are involved across layers of departments including:
- Finance
- HRM
- Tech
- Department/Team supervisors
- Payroll
- Audit & Compliance
- C/suite Management and Board Members
The Solution to Efficient Project Delivery
Is an award-winning, Australian-designed and developed solution, supported by an Australian-based, knowledgeable Inzenius implementation support team.
Out-of-the-box, all-in-one Rostering, T&A, Timesheet, and Award-Interpreted payroll solution where the only configuration required is using the Implementation online project design and delivery tool; no development.
The step-by-step Implementation portal will allow client-specific added tasks and provide the full required steps and process for open-source viewing by all team participants in project activity and reporting. The portal should manage the database setup.
Local Australian Pre and Post-Qualified Team Members Project Delivery
The quality of the system and services provided continues beyond the project and is also critical, with the many regulation changes like the recent Payday Super. The need for Better-Off-Overall Testing (BOOT) is another feature unique to Australia, with the Inzenius system incorporating not only the automated award rate updates each year but also the undertaking of the BOOT every payrun
Linked Sydney Water Article by Mahbub-Afim-Cahri
Sydney Water Dayforce Payroll Blunder Leaves Hundreds of Workers Without Wages
A botched migration to the Dayforce payroll system at Sydney Water has left hundreds of utility workers without wages, triggering a major union intervention.
A catastrophic enterprise software migration has paralysed the financial stability of hundreds of essential utility workers across Australia’s largest metropolis. Employees at Sydney Water have been left severely out of pocket, panicked, and unable to meet basic living expenses following a devastating breakdown in the state-owned corporation’s newly implemented Dayforce payroll system in early July 2026.
The system transition, intended to modernize the utility’s human resources infrastructure, fundamentally collapsed upon deployment. When staff checked their accounts for their first fortnightly pay packet under the new regime, the outcomes ranged from chaotic to disastrous. Numerous employees discovered they had been severely underpaid, inexplicably overpaid, paid days late, or in the worst cases, had not received a single cent for their labor. The failure has triggered immediate legal threats from labor unions and exposed the severe human cost of botched digital transformations.
The Dayforce System Transition Failure
Sydney Water management switched to the Dayforce platform to replace aging legacy systems deemed unable to meet the corporation’s complex operational needs. However, the rollout immediately failed to process the intricate variables associated with maintaining an essential urban water grid. Crucial elements such as overtime calculations, shift penalties, public holiday rates, and legally mandated superannuation (pension) contributions were entirely scrambled by the new software architecture.
Furthermore, core human resources functionalities collapsed alongside the financial processing. Employees reported that the system’s roster and leave-booking modules malfunctioned entirely, stripping managers of their ability to efficiently deploy technicians to critical infrastructure maintenance tasks across the city. Sydney Water executives were eventually forced to issue an internal apology late on a Friday, formally admitting the transition had not proceeded as planned and warning that stabilization would require significant time.
- The Platform: Dayforce, implemented to replace legacy software, failed upon its first fortnightly pay run.
- The Errors: Zero payments, missing superannuation contributions, incorrect tax withholdings, and broken roster modules.
- The Response: Management acknowledged the catastrophic failure via an internal email, promising manual corrections.
Human Toll: Missed Rent and Mounting Stress
The technological failure immediately translated into severe socioeconomic distress for the utility’s workforce. Operating in Sydney, consistently ranked among the world’s most expensive housing markets, the vast majority of blue-collar technicians rely entirely on punctual, accurate wage disbursements to survive. Missing a single paycheck instantly triggers defaulted rent payments, bounced mortgage direct debits, and restricted access to basic groceries.
Labor representatives highlighted horrific examples of the fallout. One worker reportedly broke down in tears during a 2:00 AM phone call to a union representative, terrified that the lack of wages would prevent them from paying mandated child support, thereby jeopardizing their visitation rights. The psychological toll of navigating high-pressure, dangerous utility maintenance work while facing sudden, unprovoked financial ruin has shattered workforce morale.
Union Backlash and Legal Demands
The Australian Services Union (ASU), which represents a large portion of the affected workforce, has aggressively escalated the dispute. ASU New South Wales secretary Angus McFarland publicly condemned the utility’s executive leadership, revealing that the union had explicitly warned Sydney Water prior to the launch that the Dayforce software was fundamentally incapable of handling the extreme complexities of a 24/7 rotating shift workforce.
McFarland noted that massive discrepancies were clearly identified during the software’s beta testing phase, yet executive management allegedly ignored the red flags and pushed forward with the disastrous hard launch. In response to the crisis, the ASU has officially filed an application with the Fair Work Commission—Australia’s national workplace relations tribunal. The union is demanding an immediate injunction forcing Sydney Water to completely abandon the Dayforce system and revert to the legacy software until accurate payment can be absolutely guaranteed.
- Union Action: The ASU has lodged a formal complaint with the Fair Work Commission.
- Forewarning: Labor leaders assert that pre-launch testing clearly demonstrated the software’s critical flaws.
- The Ultimatum: Workers are demanding an immediate reversion to the old system to stop the financial bleeding.
Digital Transformation Risks for Global Utilities
The Sydney Water debacle serves as a dire warning for government parastatals globally attempting rapid digital modernization. For utility providers in emerging tech hubs—such as Kenya Power (KPLC) or the Nairobi City Water and Sewerage Company—the incident highlights the existential risk of deploying untested enterprise resource planning (ERP) systems onto critical workforces. A minor algorithmic error in a cloud-based payroll suite can instantly destabilize the technicians responsible for keeping a capital city’s water flowing.
As the Fair Work Commission prepares to hear the emergency application, Sydney Water has deployed emergency manual payroll teams to process direct bank transfers to destitute staff. However, with trust fundamentally broken between the executives who purchased the software and the technicians who suffered its failure, the true cost of this digital blunder will extend far beyond the immediate accounting errors.
Published in the Australian Payroll Association, this article sums up the risks
https://austpayroll.com.au/news-and-resources/beyond
By Michelle Lavis | Payroll Consultant, Australian Payroll Association
The project plan says the implementation is on track.
UAT is underway, the issues list is manageable and everyone is working towards the go-live date.
Then someone who has just joined the project asks a seemingly simple question:
“Why did we decide to configure it this way?”
And suddenly, what sounded like a simple question has a six-month history behind it.
Anyone involved in a payroll or HRIS implementation knows far more happens behind the scenes than the project plan suggests. The obvious risks are generally identified early. Data migration, integrations, configuration, testing, timelines and change management all make their way onto the risk register. But some of the challenges that can have the greatest impact are much harder to see at the beginning. And often, they have very little to do with the technology itself.
The people behind the project
Resourcing is a good example. Organisations naturally think about their own project team. Who will provide the payroll expertise? Who will lead testing? How much time will HR, IT and finance need to contribute?
What can be less visible is the resourcing model on the other side of the project. Vendor project managers and implementation consultants are rarely working exclusively with one client. They may be balancing workshops, configuration, testing, defect resolution and go-lives across multiple projects. Through implementation work, we have encountered vendor resources managing significant client portfolios, in some cases up to 10 projects at a time.
That isn’t a criticism of the consultant or vendor. It is simply part of the delivery environment. But it is something organisations should understand when they enter an implementation. For payroll, this can be particularly important.
Payroll configuration is rarely just a matter of selecting a setting on a screen. It can come down to the detail of an Award interpretation, Enterprise Agreement condition, allowance, leave entitlement or working arrangement. That detail then has to carry through configuration, testing and defect resolution. If the people supporting the project are spread across multiple implementations, continuity and access to the right expertise can become important risks. It may also not receive much attention during an RFP, where the focus naturally sits on functionality, timelines and cost.
Questions about the implementation team’s structure, resource availability, continuity when resources change and escalation pathways can become equally important once the project is underway.
What happens when people change?
Of course, vendor-side resources aren’t the only people who change. Payroll SMEs leave. Project managers move on. New employees join halfway through an implementation and inherit months of decisions, workshops, spreadsheets, emails and testing history. Anyone who has joined a project halfway through will know the experience.
You ask what seems like a straightforward question, only to discover there are six months of conversations behind the answer. The challenge isn’t necessarily the change in personnel. It is the knowledge that can disappear with them. This is why good documentation matters so much. Not just the final decision, but the why behind the decision. A configuration choice that makes perfect sense today may be difficult for someone new to the project to understand six months later if the reasoning was never captured.
And it isn’t just people who change. Organisations change too. Policies are updated. Structures move. Enterprise Agreements change. Business processes evolve. New locations or employee groups are introduced. A requirement documented at the beginning of an implementation may still be technically correct, but the business context surrounding it may look very different several months later.
That is why clarification throughout an implementation is normal. Payroll requirements can look relatively simple on paper but become much more nuanced when translated into system configuration. Revisiting a requirement doesn’t necessarily mean the original requirement was wrong. Sometimes the detail simply becomes clearer as the project progresses.
Payroll doesn’t stop for the project
Then there’s the challenge every payroll professional will recognise: business-as-usual doesn’t pause just because UAT has started. Employees still need to be paid. Deadlines still arrive. Queries still need answering. Leave still needs processing, new starters still commence, and employees still terminate. Compliance obligations, month end, year end and everything else in between continue regardless of what’s happening on the project schedule.
And more often than not, the people with the deepest payroll knowledge are the same people being pulled into workshops, configuration reviews, testing and defect discussions. A project can have all the right names on the resourcing plan and still struggle to get enough of those people’s time. This is one of the hidden risks of payroll implementations: the project is competing with the payroll team’s most important job, running payroll.
Testing the system isn’t the same as testing payroll
Testing brings another important lesson. There is a difference between proving that a system function works and proving that payroll works. A system might correctly calculate an ordinary employee’s pay. But what happens when that employee works overtime, takes annual leave, receives an allowance, changes hours, has a retroactive pay increase and then terminates?
Payroll relies on employee data, time and attendance, scheduling, leave, allowances, calculations, approvals, banking, superannuation, statutory reporting and finance all working together. Something can operate perfectly well in isolation and behave very differently once it meets a real employee scenario. And, as most payroll professionals know, employees are very good at producing scenarios that no test script ever imagined. That is why good payroll testing isn’t just about ticking off system functionality. It is about testing the real-world payroll scenarios that the business is actually going to encounter.
The risks between the lines
Perhaps that is one of the bigger lessons from payroll and HRIS implementations. The challenges don’t always sit neatly with the client, the vendor or the technology. They often sit somewhere in between. They sit in competing priorities. In changing people. In knowledge transfer. In different interpretations of a requirement. In a business process that changes halfway through the project. And in the everyday reality of keeping both a project and a payroll moving at the same time.
Not every risk can be predicted or avoided. Complex payroll and HR technology projects involve a lot of moving parts, and things will inevitably change along the way. But recognising these less visible risks early can make them much easier to identify and manage when they emerge. Sometimes the most valuable support isn’t another person ticking off tasks on the project plan. It is having someone who understands payroll look at what is happening between the lines.
If you’re preparing an RFP, considering a new payroll or HRIS platform or already somewhere in the middle of an implementation and could use additional support, get in touch with the Australian Payroll Association.
Frequently Asked Questions
What components are required to be part of the system?
An all-in-one rostering, timekeeping, and timesheet system, including full compliant award interpretation and payroll with API connectors to the HRM system, is the minimum requirement.
How do you test the award interpretation capabilities?
Apart from examples of the most complex interpretation requirements during the sales process, has the vendor committed to the capabilities of their interpretation, including leave accruals and payments, and complex interpretation of award conditions from the timesheet, including:
- Individual engagement of one employee in one shift paid differently for each
- Ability to capture timekeeping for each of the engagements
- Have the multi-engagements joined or not for the purpose of overtime calculations
- Payments and accruals due that may not depend on the time worked, but rather on employee-specific factors
- Leave accruals that are added based on a pre-defined number of day types worked
Any other EBA or award conditions defined by the business applicable in the Australian or New Zealand award conditions
What process is part of the implementation process?
The vendor should be able to demonstrate their implementation project process with the preferred out-of-the-box open system for better documentation, and review of progress for each stage of the project
What pre-go-live validation tests should be included?
All integration and data flows, together with a parallel run of the previous system interpretation to validate compliance with the business needs and award conditions
Should we run the old and new payroll in parallel?
While it’s a complex process, this is a good idea by processing the STP and Payday super components in the new system until you’re fully satisfied, as you can not disrupt your payroll or staff during the transition.