Background<br />Zions Bancorporation originated as Keystone Insurance and Investment Co., a Utah Corporation, in April 1955. In April 1960, Keystone, together with several individual investors, acquired a 57.5 percent interest in Zions First National Bank from the LDS Church. In 1965, the name of the company was changed to Zions Bancorporation. (However, it operated as Zions Utah Bancorporation from 1966 to 1987.) The first public offering of shares in Zions Bancorporation was made in January 1966. There continued to be some minority shareholders until April 1972, when the company exchanged the remaining minority shares for common shares.<br />Zions Bancorporation's common stock is traded on NASDAQ under the symbol ZION. The company is a member of the S&P 500 Index and the NASDAQ Financial 100 Index.<br />
Challenge<br />As a financial services company that operates six bank charters across the western United States, Zions Bancorporation have the diverse, broad services that it offers. It cause a complicated risk profile. One of the main questions of management was what type of technology system would fit the company’s needs and facilitate meeting Sarbanes-Oxley Section 404 requirements.<br />
ERM Component<br /> Below is Zions Bancorporation COSO’s component founded on report source :<br />Internal Environment<br />Zions Bancorporation has diverse and broad services that it offers. It’s services come with a complicated risk profile to search a type of technology system that would fit the company’s needs.<br />Objective Setting<br />Zions Bancorporation has 3 objective to reach :<br /><ul><li>Allow Zions to effectively manage risk and cut losses
Increase shareholder value and customer service
Meet regulatory requirements of Sarbanes-Oxley Section 404 requirements.</li></ul>Event Identification<br />Zions Bancorporation deals with banks, it worked closely with theFederal Reserve Bank , the U.S. Office of the Comptroller. And also with the Internal Audit department (who provided feedback on many areas such as functionality, methodology, and user guidelines).<br />
ERM Component (cont.)<br />Risk Assessment<br />Zions Bancorporation using a system for online certifications and for management approvals on controls and actions. Those system spesification :<br /><ul><li>Automated ERM system
Data feeds from multiple system</li></li></ul><li>ERM Component (cont.)<br />Risk Response<br />The response to the new system has been positive across the company. <br /><ul><li>It effectively allows Zions to manage existing issues and plan for future issues.
It allows for better disclosure to its auditors in a more timely manner, as well as providing focus to its Internal Audit department.
Zions has been able to combine multiple risk tools into one common system, providing the company a more effective way to manage its risk and increase its customer service. </li></ul>Control Activities<br /> In this new system, the business-line users determine the objectives and identify the risks associated with those objectives. This system then calculates the inherent risk score for analysis (this step helps with the evaluation of the company’s risk levels). <br /> The business-line users then populate the system with controls(preventive or detective) and ratings. This system then calculates control and residual risks scores to identify risk exposures. <br />
Source<br />Using Technology to Support ERM: A Case Study : URL Link<br />Zions Bancorporation Homepage : URL Link<br />