Hidden costs of outdated banking systems
Sponsored content. This article was supplied by a third party and Business Money has been paid to publish it.
Most banks know what their old core system costs to license and run. The bigger costs are harder to spot. They show up as slow launches, extra staff, outages and fines, and they rarely get added up in one place.
The running costs nobody tracks
Old systems need old skills. Many legacy cores were built decades ago, and the people who know them well are getting harder to find. Banks end up paying specialists, or a supplier, to keep things ticking over.
Then there is the work around the system. When the core can’t do something, teams build a workaround. Spreadsheets, overnight batch jobs and manual checks fill the gaps. Each one takes time, and each one is a place where mistakes can creep in.
Slow change costs you customers
On a legacy core, a small product change can take months. A new savings rate has to pass through layers of old code and testing. By the time it goes live, a rival may have already taken the customers you wanted.
This cost never appears on an invoice. It shows up as growth you didn’t get.
Outages are expensive
When old systems fail, the bill can be huge. The best-known UK example is TSB. In April 2018, its move to a new platform went badly wrong, hitting a large share of its 5.2 million customers. Problems carried on until December 2018. The FCA and PRA fined the bank £48.65 million, and it paid £32.7 million in redress to customers.
Smaller outages add up too. The Treasury Committee found that nine UK banks and building societies reported at least 158 IT incidents between January 2023 and February 2025, totalling 803 hours. Barclays alone said it could pay up to £12.5 million in compensation for outages in that period.
The regulatory burden keeps growing
Since 31 March 2025, UK banks must meet the FCA and PRA operational resilience rules in full. They need to map their important business services, set limits on how much disruption they can accept, and prove they can stay within them.
On a tangled legacy core, that proof is costly. Teams spend weeks tracing how data moves and testing scenarios on systems few people fully understand. Reporting often relies on data that is a day old.
Data you can’t easily use
Old cores tend to lock data away. Getting a clear, current view of a customer or an account can mean pulling reports from several systems and stitching them together. That slows down risk checks, fraud work and any plans to use AI or personalisation.
What a modern core changes
A modern core banking platform tackles many of these costs at the source. SaaScada’s platform, for instance, is cloud native and event-sourced. It streams every event in real time to your own tools, keeps an immutable audit log and is designed to remove manual reconciliation. Product features are shared but kept apart, so changing one product doesn’t break another.
A few areas where the savings tend to show:
- Fewer workarounds and manual checks
- Faster product launches, measured in days or weeks
- Compute that scales up only when you need it
- Simpler audit and resilience evidence
Counting the real cost
List every cost your current system creates. Include the workarounds, the delays, the incident clean-ups and the compliance hours. The licence fee is only the start. Once the full picture is on paper, the case for change is often much clearer than it first looked.