UK Universal Credit income-calculation errors
Errors in how the UK's Universal Credit welfare system calculates monthly income from real-time payroll data have caused thousands of claimants to receive incorrect (often reduced) payments, particularly those paid four-weekly rather than monthly.
The damage was public. The root cause was preventable.
Errors in how the UK's Universal Credit welfare system calculates monthly income from real-time payroll data have caused thousands of claimants to receive incorrect (often reduced) payments, particularly those paid four-weekly rather than monthly.
What the software actually got wrong
The system's automated real-time-information matching software assumes a fixed monthly pay cycle, so claimants paid on a different schedule can be misclassified as having two paydays in a single assessment period, triggering an automatic (and often incorrect) reduction in their benefit.
The system's automated real-time-information matching software assumes a fixed...
The system's automated real-time-information matching software assumes a fixed monthly pay cycle, so claimants paid on a different schedule can be misclassified as having two paydays in a single assessment period, triggering an automatic (and often incorrect) reduction in their benefit.
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.
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.