Minnesota State's Workday-based HR platform rollout left over 1,000 faculty and staff with incorrect payments, with auditors finding increased errors after implementation despite prior awareness of payroll issues.
Minnesota State's ambitious Workday implementation has run into significant payroll problems, with auditors finding that over a thousand faculty and staff received incorrect payments after the new HR platform went live.
According to a report from the Office of the Legislative Auditor, sample testing revealed troubling accuracy issues. Out of 202 faculty members tested, 19 were paid incorrectly, with an additional 38 identified through further testing. Even using the conservative nine percent error rate from this sample, the auditors estimate that approximately 1,278 staff members across Minnesota State's 54 campuses may have been affected.
The payroll problems appear to have worsened after Workday's introduction, despite Minnesota State being aware of existing faculty payroll issues beforehand. The auditors specifically cited "interface issues with transferring data between ISRS and Workday" as a contributing factor to the increased errors.
Minnesota State's payroll system now operates as a complex patchwork, combining Workday with its legacy payroll system and a Statewide Employee Management (SEMA4) system to create pay distribution records. This hybrid approach emerged because the state realized it "might not be able to find one system that could provide all of the desired functionality," particularly the capability to calculate faculty payroll.
The financial implications have been substantial. What began as a $151.1 million project budget ballooned to $290.4 million by November 2024, with implementation dates pushed back from the original 2023-2026 timeline to 2024-2029. The project aims to replace the Integrated Statewide Record System (ISRS) with a unified platform combining finance, HR/payroll, and student components across Minnesota State's network of 54 campuses serving 270,000 students and employing over 14,200 faculty and staff.
These issues mirror challenges faced by other institutions implementing Workday systems. Washington University's Workday project has reached $266 million, or approximately $16,000 per student, over a seven-year rollout replacing 80 legacy systems. Iowa terminated its Workday finance software contract in 2024 after encountering "implementation issues" that could impact multiple business processes, though it continues using Workday's HR system. Maine suspended its $54.6 million Workday project in 2021 after missing two go-live dates, citing "significant gaps in configuration and testing" and laying off contractors.
Workday CEO Carl Eschenbach, who left his position in February 2025 following job cuts and share price volatility, previously claimed that "more than 90 percent of the vendor's rollouts are a success" and that "95 or 90 percent of our implementations are on-time and on-budget." However, the Minnesota State experience suggests that even successful vendors can face significant challenges when implementing complex enterprise systems across large educational systems.
The Minnesota State case highlights the risks inherent in large-scale ERP implementations, particularly when integrating new cloud-based systems with existing legacy infrastructure. As educational institutions and state governments continue to modernize their administrative systems, the balance between innovation and operational stability remains a critical challenge.
The auditors' findings raise questions about project management, testing procedures, and the decision to proceed with implementation despite known issues. For the thousands of affected faculty and staff, the payroll errors represent not just administrative inconvenience but potential financial hardship and erosion of trust in institutional systems.

The Register has reached out to both Minnesota State and Workday for comment on the audit findings and their plans to address the ongoing payroll issues.

Comments
Please log in or register to join the discussion