Photo of Mark Hoban

Mark Hoban (Shadow Minister, Treasury; Fareham, Conservative)

I welcome you to the Chair, Mr. Illsley, for today’s proceedings.

We had quite a full debate on this group on Tuesday afternoon and I want to reflect a little on the Minister’s response to it. Before I do so, I should like to refer to the comments that my hon. Friend the Member for Gosport made about who should pull the trigger. He made them in the context of the debate about the code and we will pick up on that in clause 7. My hon. Friend and I share the same viewpoint on this. For a variety of reasons we believe that the best body to pull the trigger is not the Financial Services Authority but the Bank of England.

My hon. Friend gave a clear elucidation of those reasons on Tuesday. If we concentrate on the efficiency of the regulatory system, there is a danger that we forget about its effectiveness. The responsibilities of the tripartite authorities are so clearly delineated in each other’s minds that sometimes there is no overlap or any form of check or scrutiny or engagement in other aspects of their arrangements. That is why giving the Bank of England the power to pull the trigger will give it a much greater role in the supervision of the banking system.

We need to get the balance right. We do not want to have two regulators, but we need to ensure that there is an effective check and there is no risk of regulatory forbearance by one regulator. My party’s policy is that the Bank of England should pull the trigger but, as the Minister knows, in the interests of passing the Bill speedily, my right hon. Friend the Member for Witney (Mr. Cameron) indicated that we would not be pursuing this matter now. We will leave this one for another time. It is very much on our agenda to look at this.

I want to go back to the Minister’s remarks on Tuesday afternoon and to focus on two points. The first is about flexibility. We appreciate the need for flexibility in the code and the way in which the powers are operated. The Minister talked about flexibility in the context of making a statement on the use of powers and my amendment on “comply or explain”. I understand the point he makes, but there is a risk attached to flexibility that we need to bear in mind. The code is being put out to consultation today and will be redrafted. If it is too vague or opaque, or the need to comply with it is too lax, it will undermine confidence in the way in which it is meant to circumscribe the exercise of powers in the Bill. I will come back to the comments made by the hon. Member for South-East Cornwall about the benefits of that circumscription.

The second point is on the threshold conditions. The Minister indicated that the FSA, in the light of the Bill, will look again at the threshold conditions to ensure that the two things dovetail. When will the FSA consult on a revision of the threshold conditions? Will there be fewer conditions? I mentioned a couple of the conditions on Tuesday. Will the adequate resources condition be the key condition in the context of the Bill, and how much guidance will the FSA give on the conditions? One concern is that too much opacity on how the conditions can be met or, indeed, breached, will undermine confidence in the use of powers in the Bill.

I should like to go back to the central purpose of having the code in the Bill and why the code is important. The Bill includes some quite invasive powers: it gives the tripartite authorities powers to interfere with the rights that creditors and investors would normally enjoy. For example, it gives the tripartite authorities the right to take control of the bank and to transfer part of its assets into a bridge bank. The code is meant to provide confidence to creditors and investors about how the powers will be exercised. Increased uncertainty about that means that there is high risk in the eyes of investors and creditors. Higher risk means an increase in the cost of capital, which will make it harder for banks to raise capital, which will have an impact on the wider economy. If the cost of capital of a bank increases, so will the cost of the loans it makes to households and families.

I believe that the Government recognise that, which is why they have accepted that it is important that the code sets out the limitations on the exercise of powers in the Bill. However, to give confidence to the sector, the code needs to be explicit about the circumstances in which, and when, the powers will be exercised. The Government must therefore produce a much more detailed code if they are to allay any fears about the use of the powers. They need to provide clear guidance to the tripartite authorities rather than produce a rewrite of the explanatory notes, and to set out, in the context of clauses 10, 11 and 12, the hierarchy of the stabilisation options, and what is the preferred option.

Not only the code but the threshold conditions need to be more specific to avoid the sense that they can be used in an arbitrary fashion. The Government will argue that they need flexibility; that an overly restrictive code will constrain the freedom of action. However, if the use of invasive powers in the Bill is perceived to be unconstrained, markets will make their own judgments on whether they should invest in British banks. If the code as redrafted does not provide significantly greater detail on how and when the powers will be used, there will be demand for the constraints to be in the Bill rather than the code.

The Government need to reflect on the tension between flexibility and reassurance. At the moment, the code errs on the side of flexibility. If that continues, the cost of capital will rise, and families will pay the price through higher interest rates. Moving forward, the Government need to think carefully about how the code should be redrafted to give confidence to banks and their investors and creditors. Certainly, conversations that I have had in the past few days with external parties suggest that the code as currently drafted does not do the job that people expected it to do.

Annotations

No annotations

Sign in or join to post a public annotation.