>...exceptions in which the automated process doesn't terminate someone for being >115
You gave a several good explanations about why the current automated processes don't mark the records as deceased. But those are excuses. Just because the design of the system is flawed, that doesn't mean the system isn't in error because the code implements the design.
All those sound like it needs to be fixed to me. As somebody that deals with data for large enterprises that are nowhere near, obviously, as the government, but definitely companies with 100k employees and several in the Fortune 20. It's rudimentary to:
- have a data staging area before data gets into any financial system intended for payment transactions. Those staging systems can be used for analytical, reporting, and especially data cleaning.
- No use one record to represent the obligations to a completely different records of the same type. i.e. overloaded corrupt master data.
Uncurated data systems should be treated completely differently than systems that actually impacts financial transactions. Just because it's taxpayer money, they shouldn't be able to avoid criticism because they're wasting the money. If anything they should be more accountable.