It’s a mystery why this keeps happening and only to the same banks 
From what I understand, some of the software they’re running is pretty old and given the experiences of TSB when it moved away from the Lloyds platform I can understand the hesitancy to make big changes. Most banks simply tinker with the periphery rather than making necessary root and branch reform. Some are moving to cloud platforms but for most it’s a gradual process.
1 Like
If you think that’s old, I gather that the UK state pension system is still running on the same software that went live in the early 1990s!
Which is probably going to need a major upgrade when the state pension exceeds the basic tax free allowance in, probably, 2026 or perhaps 2027 depending on the triple lock raises.
Oh, and don’t forget the ATMs still running on Windows XP.
1 Like
The TSB migration was rushed - Lloyds started charging TSB (Sababell) a sizable premium for not migrating off their systems when contractually agreed plus problems mounted with the new owners prescribing Sabadell’s in-house IT platform and services to migrate TSB.
Lot’s of the DWP systems are legacy ones but what makes you think their pension systems can’t deal with new tax codes?
When I was working it, it had no tax functionality at all. Worryingly, my understanding is that it’s essentially the same system in operation now which is why they may have rather a large problem about to arise either in 2026 or 2027, depending on how the upcoming triple lock raises work out.
It can deal with tax codes and deductions so the drones at DWP can find a workaround if it’s even needed.