General Information & Client Services
  • Americas: +1.212.553.1653
  • Asia: +852.3551.3077
  • China: +86.10.6319.6580
  • EMEA: +44.20.7772.5454
  • Japan: +81.3.5408.4100
Media Relations
  • New York: +1.212.553.0376
  • London: +44.20.7772.5456
  • Hong Kong: +852.3758.1350
  • Tokyo: +813.5408.4110
  • Sydney: +61.2.9270.8141
  • Mexico City: +001.888.779.5833
  • Buenos Aires: +0800.666.3506
  • São Paulo: +0800.891.2518

7.3%
Banks’ IT expenses equal 7.3% of their revenues – nearly twice as much as other industries.
120
In the US, more than 120 banking organizations are subject to resolution planning requirements.
$50m
Large banks are increasing their spending on stress testing – an estimated $10 million per year on operating costs, and $30-$50 million on top of that on technology.
59%
In a recent financial services survey, 59% of respondents stated that improving their general knowledge of the industry would be the most helpful way of improving the resilience of their firm.
25%
An estimated 25% of banks still rely heavily on obsolete technology, such as Excel spreadsheets and email systems, to provision their stress testing.
77%
77% of DFAST banks have a roadmap for improving stress testing over the next few years.
10-14
The average insurer has 10 to 14 core systems installed. One multinational insurer has more than 80 core systems.
75,000
In Europe, more than 75,000 validation rules are specified by the EBA on COREP reports to check for consistencies.
79%
In a 2013 CEB Tower Group poll of Commercial Banking, 79% of executives reported that it is critical or highly important to maximize their credit application, approval, and booking rates.
7-10%
Efficiently managing data in banks is such a problem that it can take up to 7-10% of a bank’s operating income.
60%
A study conducted by the Everest Group estimates that the cost savings from offshoring research and analytics is typically anywhere between 30% to 60%.
$1b
Airbus’ problem took almost two years to fix and cost more than a billion dollars – highlighting the risks of using siloed software systems.
As Published In: