Show Summary Details
Page of

(p. 231) 6. UK banking supervision and regulatory architecture 

(p. 231) 6. UK banking supervision and regulatory architecture
(p. 231) 6. UK banking supervision and regulatory architecture

Iris H-Y Chiu

and Joanna Wilson

Page of

PRINTED FROM OXFORD LAW TROVE ( © Oxford University Press, 2018. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Law Trove for personal use (for details see Privacy Policy and Legal Notice).

date: 25 May 2020

This chapter addresses the UK bank supervision and regulatory architecture. Although banking business has existed in England since the seventeenth century, banks enjoyed no formal system of regulation until the introduction of the Banking Act of 1979. Over the years, the scope and intensity of regulation increased. After the global financial crisis, further changes were made to bank regulation as well as the regulatory architecture in the UK for bank regulation. The regulatory architecture introduced in April 2013 is characterised as ‘twin peaks’, that is, having two main agencies that are responsible for different regulatory objectives. The Prudential Regulation Authority (PRA) is responsible for ‘prudential’ objectives—that is, the solvency and financial soundness of financial institutions—while the Financial Conduct Authority (FCA) is responsible for conduct of business and market regulation, including promoting competition. The PRA and FCA enjoy a wide berth of rule-making and enforcement powers.

Access to the complete content on Law Trove requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access code, please see the information provided with the code or instructions printed within the title for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.