Paul Pester resigned as CEO of TSB on 4 September 2018, five months after an IT migration locked up to 1.9 million account holders out of their finances for weeks. In December 2022 the Financial Conduct Authority and the Prudential Regulation Authority jointly fined the bank £48.65 million for operational resilience failures tied directly to that migration. The penalty, set by the two regulators, ranks among the largest they have ever imposed for such failings. The crisis ended Pester's career at the institution he had helped create from the carve-out of Lloyds Banking Group.
Pester became CEO of TSB in 2013, four years after Lloyds had been forced to sell the branch network as a condition of its 2009 government bailout. The separation, code-named Project Verde, was one of the most complex IT and legal exercises attempted by a UK retail bank. Pester oversaw the creation of a standalone brand with its own banking licence, its own branches, and for a period its own technology stack that still ran on Lloyds' back-end systems. The plan was always to move account holders to a new, fully independent system called Proteo4UK, developed by TSB's parent company, Spain's Banco Sabadell.
The April 2018 Migration and the Immediate Failure
The cutover weekend
TSB scheduled the move for the weekend of 20-22 April 2018. Over those three days the bank attempted to transfer data from the legacy Lloyds system to Proteo4UK. Almost immediately after the cutover, users began reporting that they could not log in to online banking or the mobile app. Some saw other people's account balances. The core banking system was intermittently unavailable, and batch processing of payments failed.
The scale becomes clear
The size of the failure became clear within hours. By the end of the first week, TSB estimated that roughly half its five million account holders were affected. The bank advised people to call a helpline that was itself overwhelmed. Branches saw long queues of individuals who could not access cash or check balances. The outage was not resolved quickly. Some services took weeks to stabilise, and full restoration of all digital channels took months.
What went wrong
TSB later acknowledged that the transfer had caused a database failure that corrupted records, though the bank never published a detailed root-cause analysis of the specific technical fault.
Regulatory and Political Fallout
Parliamentary scrutiny
The UK Treasury Select Committee opened an inquiry into the TSB outage within weeks. In public hearings, committee members pressed Pester on why the bank had not run more extensive testing, why it had not maintained a fallback option to the Lloyds system, and why it took so long to inform people of the severity of the problem. The committee's final report was highly critical of TSB's governance and of Pester's leadership during the crisis.
The joint investigation
The FCA and PRA launched a joint investigation that ran for more than four years. When they announced the penalty in December 2022, the regulators said TSB had failed to take reasonable care to organise and control its affairs responsibly. They found that the bank had not adequately tested the transfer, had not ensured that its systems could handle the data shift, and had not put in place effective contingency plans.
Pester's Departure and the Cost to TSB
Resignation
Pester resigned on 4 September 2018. He had faced sustained pressure from shareholders, users, and politicians since the April outage. TSB's board accepted his resignation and appointed a successor from within the bank's executive team. The bank did not disclose whether Pester received any severance or bonus payments upon leaving, and the brief for this article does not establish his subsequent employment.
Financial damage beyond the fine
The financial cost to TSB went well beyond the regulatory penalty. The bank paid substantial redress to people who had been locked out of accounts, incurred fraud losses when criminals exploited the system's instability, and saw a sharp drop in new account openings. Compensation and fraud losses together ran into the hundreds of millions of pounds, though the exact total is not established here. TSB's market share in current accounts and mortgages contracted, and the reputational damage persisted for years after the migration.
Long-Term Consequences for TSB and the Industry
A cautionary case study
The TSB migration became a case study in how not to run a core banking replacement. Regulators across Europe tightened their scrutiny of large-scale IT change programmes at retail banks. The FCA and PRA revised their operational resilience rules, requiring banks to demonstrate that they can withstand a serious systems failure without disrupting critical services. TSB itself spent years rebuilding trust and stabilising its technology estate under new leadership.
Pester's legacy
For Paul Pester, the episode defined his legacy. He had successfully navigated the separation from Lloyds and built a challenger brand with strong satisfaction scores. The April 2018 migration undid that work in a single weekend. The question this article was written to answer is whether a CEO can survive a systems failure that locks out nearly two million account holders. The answer, from TSB's experience, is no.
Key Facts
- CEO: Paul Pester, appointed 2013, resigned 4 September 2018
- Parent company: Banco Sabadell (Spain)
- IT platform: Proteo4UK, developed by Sabadell
- Migration date: Weekend of 20-22 April 2018
- Customers locked out: Up to 1.9 million
- Regulatory fine: £48.65 million (FCA and PRA, December 2022)
- Outcome: Pester resigned; TSB fined and reputational damage lasting years
