← Back to the 100 Software Failures Timeline
Case Study #44 — Top 100 Software Failures

Queensland Health payroll system failure

Tens of thousands of Queensland Health staff were overpaid, underpaid, or not paid at all after go-live; the eventual cost to fix and support the system exceeded AU$1.2 billion, against an original budget of about AU$6 million.

2010
When it happened
Government / Healthcare
Sector
#44 of 100
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

Tens of thousands of Queensland Health staff were overpaid, underpaid, or not paid at all after go-live; the eventual cost to fix and support the system exceeded AU$1.2 billion, against an original budget of about AU$6 million.

Government
Sector affected
2010
Date of the event
#44
Rank in the Top 100 Software Failures
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

The new SAP-based payroll system was rushed live without adequate testing, training, or business-process alignment, so it could not correctly process the many complex award and shift-pay rules of the health workforce.

01Root Cause

The new SAP-based payroll system was rushed live without...

What Happened

The new SAP-based payroll system was rushed live without adequate testing, training, or business-process alignment, so it could not correctly process the many complex award and shift-pay rules of the health workforce.

How Requs AI Catches This

Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.

03 — How This Gets Caught Before It Happens

Beyond code coverage and "shall" testing

Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.

Requs AI Edge Case

Surfaces this before code exists

Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.

Requs AI Software FMEA

Connects the failure mode to the hazard

Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.

Find the overlooked root causes before they ship.

Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.