Denmark tax debt-collection system failure
Denmark's automated tax debt-collection system (EFI) failed to collect the vast majority of outstanding tax debts it was built to recover and had to be scrapped, at a cost estimated in the hundreds of millions of dollars and years of lost tax revenue.
The damage was public. The root cause was preventable.
Denmark's automated tax debt-collection system (EFI) failed to collect the vast majority of outstanding tax debts it was built to recover and had to be scrapped, at a cost estimated in the hundreds of millions of dollars and years of lost tax revenue.
What the software actually got wrong
The debt-collection software could not correctly calculate which debts were still legally collectable, incorrectly writing off or mishandling large volumes of debt, and repeated attempts to patch the system failed to bring it up to a workable standard.
The debt-collection software could not correctly calculate which debts...
The debt-collection software could not correctly calculate which debts were still legally collectable, incorrectly writing off or mishandling large volumes of debt
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.
Repeated attempts to patch the system failed to bring...
repeated attempts to patch the system failed to bring it up to a workable standard
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.