New Zealand Novopay teacher payroll failure
A new payroll system for New Zealand's roughly 110,000 state school teachers caused widespread under- and overpayments, leaving many teachers unpaid or incorrectly paid for months and ultimately costing well over NZD 45 million to fix.
The damage was public. The root cause was preventable.
A new payroll system for New Zealand's roughly 110,000 state school teachers caused widespread under- and overpayments, leaving many teachers unpaid or incorrectly paid for months and ultimately costing well over NZD 45 million to fix.
What the software actually got wrong
The Novopay software was rolled out without sufficient testing against New Zealand's complex, variable teacher pay and leave rules, and the system's error-handling could not keep pace with the volume of payroll discrepancies once it went live.
The Novopay software was rolled out without sufficient testing...
The Novopay software was rolled out without sufficient testing against New Zealand's complex, variable teacher pay and leave rules
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.
The system's error-handling could not keep pace with the...
the system's error-handling could not keep pace with the volume of payroll discrepancies once it went live
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.