Showing posts with label Implementing Technical Standards. Show all posts
Showing posts with label Implementing Technical Standards. Show all posts

Tuesday, 4 November 2014

EIOPA's Implementing Technical Standards on Internal Model Approval - ready to "submit"?

EIOPA have kicked into life at the end of October like Freddy Krueger on laughing gas, releasing a swarm of consultation papers and summaries. While the releases on Colleges of Supervisors or the calculation of the risk-free interest rate will be of interest to some, my own interest was in a subset of their draft Implementing Technical Standards on Solvency II Approval Processes

I have tried to cover the distinction between ITS and the other weaponry in the hands of EIOPA and legislators here. The aggregated feedback received by EIOPA on the suite of Solvency II approvals covered by ITS is neatly summarised in this doc, with EIOPA adding dollops of proportionality into the summary, to effectively remind supervisors not to treat the applications of giants and pygmys with the same vigour. Given the audience reaction to the UK regulator's industry event a couple of weeks ago, I think 'proportionality' may need to become the PRA's middle name (though it probably works better as its first name...)

Clearly, two big moans have been common threads in the responses received, and both have been rebuffed. The concept of supervisory requests for supplementary information "stopping the clock" on one's approval window has been retained, while the idea of "no answer in 6 months equals approval" has been firmly rejected.
Internal Model approval
- "Easy, Easy"
Of more interest to me than the other approvals covered by the consultation is the Big Daddy himself, Internal Model Approvals. From a UK perspective I have covered this in multiple posts previously (here, here, here and here for a start) , and was interested to see if any more whistles and bells had been added to what is already an area causing serious fatigue within the UK's potential applicants, not to mention a few dozen corpses from the c.100 interested parties back in 2011 (slide 4 here).

I thought the following was worth highlighting;
  • Given that the Delegated Acts are already loaded with granular Documentation requirements for IM applications (articles 243 & 244), the ITS insists on a few more pieces! Having cross-referenced between the DAs and the ITS, I reckon the items listed in Article 3 d, h, j, p, q and r are all new requirements, though none would be a stretch to produce.
  • Expectations that your model has been in use prior to application (Art 2 (3 a ii)), and is integrated into your current system of governance (Act 2 (c)) - perhaps this is the effort which firms with capital add-ons will be compelled to do in 2016 & 2017 in advance of model applications?
  • Results of your "last" Validation Process must be submitted in a Model application (Art 2 (m)) - again, suggests there will need to be a year's worth of "live" modelling in advance of making an application
  • The supervisors have 30 days to assess the "completeness" of an application - this feels weirdly generous, given those 30 days count towards the overall 6-month assessment window (provided the application is complete).
  • Despite the PRA's firm assertion on Oct 17th (slide 8) that conditional approval for Model applications is not available, Articles 3 (8) and 5 (4 b) both suggest otherwise, namely that proposed "adjustments" or "terms and conditions" can be accounted for in their decision. 
  • As much prominence being given to Model Change process and Model Change policy as the initial Model Application process - applications can actually be rejected on the strength of the change policy (Art 5 (2)). Despite that, the articles designated for these areas (Arts 7 & 8) are relatively straightforward.
There is no real reason why these ITS for IM approval won't sail through at the Commission, so best to prepare accordingly. However, UK applicants with 2016 modelling ambitions will of course need to wait further for EIOPA's Common Application Package before they can finalise this montagne de papier.

Wednesday, 2 April 2014

EIOPA's Implementing Technical Standards on Approval Processes - Cut and Paste?

EIOPA have at last commenced their work on "Level 2.5" regulation in the Solvency II world, and with it being something of a trip into the unknown (only their sister body ESMA world appear to have performed a similar exercise to-date), their consultation papers will no doubt be getting torn apart like a parking ticket by Insurers and NCAs alike.

Open until the end of June with a view to presenting this particular batch to the European Commission for endorsement by the end of October, the ITS cover how the following approvals should be applied for and administered, with definitions and rationale provided in this cover note.
  • Use of Matching Adjustment
  • Use of Internal Model, "Major" changes to that model, and changes to the Model Change Policy (phew!)
  • Use of a Group Internal Model
  • Use of Undertaking-Specific Parameters (USPs)
  • Use of Ancilliary Own Funds for SCR
  • Use of Special Purpose Vehicles for risk transference

For this post, I wanted to concentrate on the Internal Model-themed ITS (emboldened), specifically things which introduce something new to the table (i.e. not already in the thoughts of UK firms/regulators through the Directive, Delegated Acts, Preparatory Guidance or indeed the existing IMAP structure in the UK).

Therefore in the interests of recyclability, UK firms will be delighted by the requirements within this particular ITS - you will recognise the text as part of the Self-Assessment Template "tabs" which you would have been populating as part of IMAP over the last 2 years!

That text was of course co-opted from the Draft Implementing Measures from October 2011 (specifically Article 203 IM1 for the application requirements, IM2-IM8 for the model change and administrative process elements). These articles had disappeared from the latest version of the Delegated Acts, only to find its way into this ITS almost verbatim.

Elements which therefore show noteworthy change from that old text (other than semantics) include

  • The addition of a requirement for a (year-end 2014?) P&L Attribution to be submitted as part of the application.
  • Withdrawal of some of the ceremony around applying for a change to the Model Change Policy, which was a little more elaborate in the October '11 text (AMSB explanation and justification text, 6 month turnaround time for NCAs to make a ruling).
  • The same for an application for a Model Change itself, now seemingly less formal
  • Giving room for terms and conditions and transitional plans to be factored in to an NCA's decision on model approval
  • That more detail should be published on the NCA's website regarding the approval (namely that the scope of the IM should be disclosed, as well as risk categories and business units covered, which feels a touch commercially sensitive to me!)

I'm guessing this isn't the only ITS which is going to use this approach (i.e. ripping text directly out of the Oct 2011 Draft Implementing Measures where it has been seemingly jettisoned), so a bit of cross checking might help you second guess what is going to appear in the rest of the ITS!

Now I'm off to have a look at the others...


Wednesday, 26 February 2014

"Implementing Measures" to "Delegated Acts", "RTS" and "ITS" - Unsporting Lisbon...

How to make sense of post-
Lisbon legislative processes
OK, I have finally broken. I think it was a paragraph that had the words "acts" "delegated" "implementing" "regulatory" "measures" and "standards" strewn around like the gin-soaked occupants of a broken carousel that got to me.

The transition of Solvency II-relevant terminology from pre-Lisbon to post-Lisbon, and the lack of clear supporting material to aid the understanding of an idiot prole like me, has led me to have a stab at clarifying it myself, in the lead up to the Omnibus II vote in a couple of weeks.

The fundamentals are easy enough - the 2009 Treaty of Lisbon aimed to put Parliament and Council on an even keel in the decision making process, and get things done quicker. Lisbon was enacted around the same time that the original Solvency II Directive was coming in to land, so naturally any Lisbon-inspired changes in how EU legislation is made and maintained would need to be factored in to the wording of the Solvency II Directive when convenient.

Coupled with this was the European Union's decision (post-credit crunch) to develop a new architecture of financial supervision, which allowed EIOPA to rise in 2010 freshly armed from the embers of CEIOPS with new legislative drafting powers, changing the comfort blanket of the existing 4-level Lamfalussy process into something much trickier to fathom.

There was therefore plenty to factor in when Omnibus II, the tidying-up vehicle, was first envisaged  (covered nicely in this blast from the past from Freshfields), most prominently;
  • EIOPA's ability to draft and recommend "technical" standards which could become law without Parliament and Council having a blocking vote - as CEIOPS, they would have only had an "advisory" capacity.
  • The EU Parliament now being in a position to suggest that certain "technical" matters were actually "political", thus bringing some of the granular mathematics (specifically, Long Term Guarantee-related) back into their sphere of influence during the trilogues - without co-decision making, this would have been much trickier.
To supplement any confusion that might arise in the Lisbonising of the Solvency II Directive, there has been an opportunistic replacement, recycling or bastardisation of terms from pre-Lisbon over to the current day, without an effective mapping (this is by far the best offering I've seen, from Herbert Smith Freehills). Therefore for my own benefit, I have broken it down, and any benefit you can derive you are most welcome to!

Old Term - Implementing Measures (or "Level 2 Text")

New Term (part 1) - Delegated Acts

Why New - Comitology was the process of the Council and Parliament leaving Commission-led "committees" to deal with the development of secondary legislation to sit alongside core legislation (Solvency II Directive in our case). For years, Parliament was largely out of the loop of its drafting, receiving a Yes/No vote on such legislation only as late as 2006.

The post-Lisbon move from implementing measures to Delegated Acts gave Parliament the right to veto and amend drafts of secondary legislation. The European Council have the same powers. The delegated powers can also be revoked if either co-legislator doesn't like the Commission's tone.

The Commission, who remain responsible for developing Delegated Acts, have the drafting powers delegated, via article 290 of the TFEU. They continue to receive assistance from expert committees to create this material, with EGBIP assembled last summer to advise on the Delegated Acts side of things.

What does it really mean - not much on its own, however the new process is proving to be just as opaque and convoluted as it was previously (covered nicely here). It evidently means that influencing the content of Solvency II's Delegated Acts remains in the hands of a chosen few, for example, when Dr Wiedner noted (in AOB) that 'Member States' will get to see draft Delegated Acts before they are finalised in trimester 2 of this year, I think he meant the representatives in the room, not us!

This shadowy future was nicely predicted here back in 2011 - a less efficient process, less formality, less visibility of legislative influencers, and more horsetrading than bank holiday barbeque weekend at Tesco.


Old Term - Implementing Measures ("Level 2 Text")

New Term (part 2) - Implementing Acts

Why new - The concept of "Implementing Measures" has effectively been cut in half, with Implementing Acts very much a sideshow in the context of Solvency II - the Herbert Smith Freehills paper referenced above states that implementing acts are only referenced in one article of the Directive.

These are drafted by the Commission through powers delegated via article 291 of the TFEU, and the distinction between Delegated and Implementing Acts is shown here.

What does it really mean - nothing of consequence it would appear!


Old Term - N/A

New Term (part 3a) - Regulatory Technical Standards/RTS/
"Level 2.5"

Why New - EIOPA were empowered through the 2010 "EIOPA Legislation to draft technical standards on behalf of the Commission which would ensure consistent harmonisation of Solvency II across the Union. These kick in formally as soon as Omnibus II gets through.

A huge step up from their previous guise as CEIOPS, where they were little more than a sparsely staffed lobbying aggregator, Regulatory Technical Standards (RTS) are directly enforcable in Member State law once approved.

RTS may only be for technical matters and "shall not imply strategic decision or policy choices". These are published for public consultation, then submitted to the Commission, who can adopt, reject or amend them.

Both the Council and Parliament receive the draft RTS at the same time as the Commission, and have limited windows in which to object to their content. A specific "sunrise clause" has also been added to Omnibus II which allows the Commission (for a limited period) to circumvent the RTS process entirely and deal directly with certain matters without EIOPA involvement.

What does it really mean - For both RTS and ITS (below), EIOPA, as pen-holders, have had a significant amount of influence placed in their hands with respect to what "uniform conditions" are, and how they should be enforced.

As we have seen in recent consultations, EIOPA do not tend to change their minds, which may perversely make life easier (or at least more certain)!

Ultimately, the reality of "Level 2.5" is that the co-legislators have lost much of their ability to influence or veto acutely technical material, further distancing Solvency II's amendment and approval from Parliament and Council, into the hands of unelected, quasi-autonomous technocrats. Which can only be a good thing...


Old Term - N/A

New Term (part 3b) - Implementing Technical Standards/ITS/"Level 2.5" text

Why New - As with RTS, Implementing Technical Standards (ITS) are directly enforcable in Member State law once approved, and follow the same drafting process. EIOPA's scheduled work in the "Level 2.5" space is of course ITS, not RTS, in the run up to 2016.

Risk.net have tried to cover the distinction between RTS and ITS Standards here (subscription required), but it is not even massively clear from the Regulations which empower EIOPA!

The crucial difference is that ITS, once adopted by the Commission, receive no further scrutiny, unlike RTS, where the co-decision makers can still object after the Commission adopts.

What does it really mean - The reality of the legislative process means that even in the sticky-beaker's paradise of Solvency II, Parliament and Council do not have the time or inclination to argue the toss over this material, so will hopefully leave EIOPA and the Commission to it.


Hard to conclude this post really. For sure we have been unlucky to have bridged the Lisbon divide, as well as the genesis of EIOPA and the realisation midway through proceedings that some of the "technical" matters had immense political significance.

That said, the legislative path we have set Solvency II down for the last few years has made a mockery of the best laid preparation plans within the Union's insurers. Andrew Tyrie MP really hit the nail on the head...

Tuesday, 25 February 2014

Omnibus II and Delegated Acts - state of play summary (before it gets interesting!)

Unless you've been hiding in a cave since last summer, you shouldn't find anything new in this post, but I wanted to accumulate all relevant materials into one place for the run up to Omnibus II D-Day for my own convenience, and you're welcome to share.

At the moment we have;

European Parliament
European Commission
  • I'll cover the fineries of this on a separate post, but worth noting that the Commission's "draft implementing measures" document, which have been circulating for over 2 years, is now referred to as "Delegated Acts", after being Lisbonised.
  • A revised draft of these rebadged Delegated Acts, on the assumption that Omnibus II gets through Plenary, will be delivered like an impatient baby in the deuxieme trimestre of this year (p21). 
  • It apparently not be made available to the proles for public consumption beforehand (reported here and here). Still plenty of time for the faceless exponents of dark arts and back-room shenanighans to influence its content, so the lack of formal consultation is not necessarily a calendar breaker, though it is exceptionally poor form. 
  • The Commission's advisers now come in the form of EGIBF (for Delegated Acts) and EIOPC (for Implementing Acts). EIOPC are evidently a garage without a car at the moment, having not published a scrap of material in 15 months while Omnibus II dragged its heels. 
EIOPA
Obviously as a practitioner in the Risk field who doesn't want to wallow in the details of European Union lexicon, the forthcoming spurt of activity is considerably murkier than it would have been pre-Lisbon. Virtually every relevant term or participating body in the Solvency II hemisphere has had a name or remit change in the interim, and I'm not seeing anyone offer a mapping between "Pre" and "Post"-Lisbon terms.

I'll have a stab on a separate post, for my own sanity if nothing else.




Tuesday, 21 June 2011

ABI Solvency II Newsletter for June - clear words (and nice pictures!)

The ABI have pushed out their June industry newsletter, and it's a beauty. Highlights;
  • Compromise for long-term products appears to be palatable (to the ABI's working group at least). Final proposals in their 'package deal' will be discussed tomorrow at the Commission's Solvency II experts group
  • Clear "that some of the Level 3 guidance will not be available, nor imminent by go-live date
  • This will require regulators to "cede some autonomy" to the industry over implementation techniques
  • Asking for 1 year grace period between presentation of Implementing Technical Standards and actual application (indeed the ABI seems a little anxious on developments in this area)
  • Nice piece on justifying their approach on contract boundaries
  • Some good schematics on legislative timelines and Implementing Technical Standards due dates