ORSA - Institute of Risk Management special interest group

Of course while I spent the last couple of months topping up my tan in, errrrr, the Isle of Man, some of the guys in the UK and further afield have been building up an endeavour-flavoured sweat on some of the more malleable elements of Solvency II preparation.


Raining 'Mann' - Glorious Manx summer

The IRM as ever have kept the ball rolling, in particular hosting an ORSA session last month. While you can pick your way through the guest speaker presentations for ideas and comfort (one company specific, one consultant generic, and one which S&ST/RST fans might like as a sense check), I was much more interested in the attendee survey.

A whopping 34 replies came in, via which the attendees have delivered a reasonable ORSA landscape mock-up, which may help some of you get matters shuffled in your priority lists, given where your peers claim to be.

I noted in particular;

• ORSA Process overwhelmingly run by the Risk functions (over 90%)
• Just over half going for annual frequency, the rest (who responded) naturally more frequent - doesn't instinctively feel representative, but not all of the smaller firms would send someone down to this!
• Around two-thirds have their "Reports" at 50 pages or less - if we assume that by "report" we mean Supervisory as well as Internal, the PRA won't be too chuffed with that given their comments at the December industry seminar.
• Only a third have submitted draft ORSA Reports to the PRA and received feedback
• Coverage of emerging risk appears to be an area which not only do respondees think is lacking, but has received critical feedback from the PRA

That half have used external consultants in their ORSA work to-date is certainly no surprise. I'd be worried if that consultancy had more than a year's dust on it though, so think hard before you start submitting your 2014 gear!

ORSA Consultation Paper from EIOPA - bon effort!

As I don't expect everyone had the time, inclination or even the document to see how the pre-consultation team of CEA/AMICE/CRO Forum/CFO Forum etc got on with the ORSA document, I had a cross-cast of the two to see if any substantive changes were made. The following caught my eye in the public consultation paper released yesterday;

• Almost complete removal of the participation of the supervisory authorities in ORSA - this is now being left to Supervisory Review Process guidelines (it was shoehorned in to the pre-consultation in a way that made its removal inevitable sadly).
• ORSA Policy content trimmed down in one respect (removing some actuarial-themed material, which will inevitably end up in the ORSA Report), but added in a section on data quality.
• Made the section on checking SCR assumptions to make sure they fit one's Risk Profile much more confusing by neglecting to state whether "SCR Calculation" in the paper means "Yours" or "Theirs" - it does eventually come out in the wash that they are talking about any mismatch in reality between the assumptions one uses to generate their SCR (whether internal model, partial model, some USPs or full standard formula) and those which would actually fit the business, but it is a poor piece of drafting.
• More rigorous on being able to justify frequency of regular ORSAs
• New section on applying the proportionality principle for methodological complexity, frequency and granularity of ORSA
• Finally had the courage to write the words "ORSA" and "Report" in the same sentence! This was skilfully avoided in the pre-consultation, I guess to enforce the (still legitimate) fact that ORSA is a process, not a boiler-plate report production job
• Having removed the pieces on supervisory participation, they naturally had to lose a piece on how the ORSA output would make its way to the regulator. It was planned to put it in with RSR (and was very convoluted), but now there will seemingly be an opportunity (not guaranteed) to put forward the internal ORSA Report to satisfy regulatory obligations
• More explicit on covering less-than-easily quantifiable risks, and allows for mitigants other than capital to be used in their regard over the business planning period, provided they are not material. I hasten to add here that they have changed the language on reputational and strategic risk from being "less quantifiable" to "non-quantifiable", which is a bit of a cop-out.
• Much more explicit on capital management, both planning and execution over the business planning period - I guess this is a result of pressure from both the SIFI angle as well as Eurozone/Credit Crunch
• Leaves an open ended question on whether the ORSA Process includes or uses the outputs of tests which are associated with ongoing compliance with Articles 120-125, but the option is there for both
• Spectacular typo on page 25 - looks like one of the bullet points has not made the cut, as we jump from A to C!
• Late Psot Script - missed the omission of the requirement to independently assess the ORSA Process - no doubt everyone's internal audit functions are breathing a sigh of relief!

All in all, a good attempt and I feel more than prescriptive enough for the public consultation to drive it further forward. Perhaps a missed opportunity on the regulatory requirements front to iron out what they ought to get out of the industry's ORSA reports from a wide range of stakeholders, but hey, you can't have everything...

Business Innovation and Skills department – “Strategic Report” – anything to borrow for SFCR/ORSA/RSR?

This came out in the week from the Business Innovation and Skills department in the UK - the recommendations clearly impact on the presentation of materials for listed entities, with a "Strategic Report" replacing the various patches of random guff that normally turn up in statutory releases to the market (boiler-plate and pretty offensive in its lack of stakeholder appreciation).

I'm thinking along the lines of Pillar 2&3 in the context of this, particularly if there are some economies of scale which can be generated by sharing information between the Strategic Report and ORSA/RSR/SFCR for insurers - one for your project plans maybe?