Ireland's PPARS health-service payroll system failure
Ireland's national health service suspended the rollout of its new payroll and personnel system after years of delays and cost overruns, including one employee mistakenly paid over 1 million euros in a single transfer.
The damage was public. The root cause was preventable.
Ireland's national health service suspended the rollout of its new payroll and personnel system after years of delays and cost overruns, including one employee mistakenly paid over 1 million euros in a single transfer.
What the software actually got wrong
The SAP-based payroll software, intended to unify pay for over 100,000 health-service staff, was rolled out to only a fraction of its target users after years of development, still could not correctly handle basic functions like sick pay and annual leave, and its error went undetected by the system itself until the overpaid employee reported it.
The SAP-based payroll software, intended to unify pay for...
The SAP-based payroll software, intended to unify pay for over 100,000 health-service staff, was rolled out to only a fraction of its target users after years of development, still could not correctly handle basic functions like sick pay and annual leave
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.
Its error went undetected by the system itself until...
its error went undetected by the system itself until the overpaid employee reported it
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
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.
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.
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.