The collapse of Barings Bank in 1995 is a well-known example of how an IT system failure can have catastrophic consequences. The failure of the bank's IT systems was just one of several factors that contributed to the bank's eventual downfall.

In the early 1990s, Barings Bank had a profitable trading operation in Singapore, which was managed by a trader named Nick Leeson. Leeson was responsible for trading on behalf of the bank, but he was also responsible for settling his own trades, a practice known as "back-office processing."

Leeson began to take increasingly risky trades, which ultimately led to huge losses. To cover up these losses, Leeson created a fictitious account known as the "88888" account, which he used to hide his losses from the bank's auditors.

The failure of Barings' IT systems played a critical role in allowing Leeson to cover up his losses. The bank's back-office systems were antiquated and manual, making it difficult to reconcile trades and detect irregularities. In addition, the bank's Singapore office had limited oversight from the head office in London, which made it easier for Leeson to conceal his activities.

When the Asian financial crisis hit in 1995, Leeson's trades began to unravel, and the losses on the "88888" account became too large to conceal. Barings Bank was eventually forced to declare bankruptcy, and was sold to Dutch bank ING for a nominal sum.

The collapse of Barings Bank serves as a cautionary tale about the importance of robust IT systems and proper oversight and controls in financial institutions. The failure of the bank's IT systems made it easier for a rogue trader to cover up losses and ultimately led to the bank's demise.