Minnesota State payroll problems grew after Workday launch, auditors say

Steven

Minnesota State payroll problems grew after Workday launch, auditors say

Summary

An audit from the Office of the Legislative Auditor found that a Workday-based HR rollout across Minnesota State colleges and universities likely increased payroll errors and late payments for faculty and staff. Sample testing of 202 faculty members identified 19 with incorrect payments; further checks found another 38 affected. Auditors estimate a lower-bound error rate of around 9%, which could mean roughly 1,278 staff were impacted. The system still relies on a mix of Workday, a legacy payroll system and SEMA4 to produce pay records.

Key Points

  • Audit sampled 202 faculty: 19 were inaccurately paid; additional testing found 38 more cases.
  • Auditors estimate at least a 9% error rate, potentially affecting about 1,278 employees.
  • Workday did not incorporate faculty payroll calculation; Minnesota State continues to use legacy and SEMA4 systems alongside Workday.
  • Interface and data-transfer issues between ISRS (legacy) and Workday worsened problems after go-live.
  • Project budget rose from $151.1m to $242.7m and later to $290.4m (Nov 2024) due to scope changes and delays.
  • Implementation timelines were pushed: HR/payroll and finance moved to July 2024; full student component delayed to autumn 2029.
  • Other US/Canadian public-sector Workday implementations have encountered setbacks (Iowa, Maine, Washington University), indicating a broader trend of costly, complex rollouts.

Content Summary

The audit traces how Minnesota State began replacing its legacy ISRS ERP in 2019 and contracted Workday in 2020. Because Workday lacked a built-in capability to calculate faculty payroll, the institution retained legacy processes and SEMA4 to produce pay distributions, creating multiple hand-offs and interfaces. Auditors found pre-existing payroll issues but concluded errors and late payments increased after the Workday launch, citing interface failures and integration shortcomings. Costs and timelines have grown substantially as scope increased.

Context and Relevance

This matters to anyone tracking large public-sector IT transformations. Workday projects are high-cost, high-risk undertakings for institutions replacing legacy systems across many campuses or departments. The Minnesota State case joins a series of troubled rollouts—highlighting integration risk when new SaaS platforms do not fully replace specialised legacy payroll logic, and the fiscal and operational pain that follows for staff and students.

Author style

Punchy: The report lifts the lid on a costly, messy rollout that had real-world impacts on pay and trust. If you care about digital transformation, public-sector accountability or ERP risk, the audit is worth a close read.

Why should I read this?

Look — payroll getting borked is about more than red tape. Folks missed pay, budgets ballooned and the fix is messy because the new system didn’t cover faculty payroll properly. If you work in IT, HR, finance or run change programmes, this is a cautionary tale that could stop you repeating the same mistakes.

Source

Source: https://go.theregister.com/feed/www.theregister.com/2026/04/08/minnesota_workday_payroll/