WEBVTT

1
00:00:10.228 --> 00:00:18.623
We are an insurance that offers all types of insurance, life insurance pensions but also P&C and accident and health, 

2
00:00:18.624 --> 00:00:28.020
both the regulatory and the market environment is a real changing environment, in terms of regulatory for instance 

3
00:00:28.021 --> 00:00:37.416
we implemented Solvency II a couple of years ago and we are now in the process of implementing IFRS 17. Two main things

4
00:00:37.417 --> 00:00:46.813
are expected from a financial Risk department, the first thing is that we need to have efficients low-cost highly 

5
00:00:46.814 --> 00:00:56.209
compliant processes, so the license to operate for a financial institution is to have good quality reporting tool

6
00:00:56.210 --> 00:01:05.606
for regulatory reports. We use CCH Tagetik for consolidation, regulatory reporting and Solvency II, Tax, 

7
00:01:05.607 --> 00:01:15.002
cost allocation: CCH Tagetik is one of our core system. The confidence in CCH Tagetik was the main reason  

8
00:01:15.003 --> 00:01:24.399
to also choose CCH Tagetik for the IFRS 17 solution. Another reason that was that the IFRS17 solution in the CCH Tagetik environment

9
00:01:24.400 --> 00:01:33.795
is a relatively simple and small solution whereas other providers designed larger and 

10
00:01:33.796 --> 00:01:43.192
full scale solution and in our current finance risk architecture and we believe that adding another heavy system

11
00:01:43.193 --> 00:01:52.588
would not be a smart thing to do, so both the confidence on the one side but also the type of solution that is provided on the other side 

12
00:01:52.589 --> 00:02:01.985
drove the decision to implement the IFRS 17 of CCH Tagetik. In terms of the implementation phase, the benefits that we've seen

13
00:02:01.986 --> 00:02:11.381
in working together with CCH Tagetik is the fact that we were able to really give our own input and working on a solution together,

14
00:02:11.382 --> 00:02:20.778
seeing our own ideas in the new system and so we are very happy with that. In terms of

15
00:02:20.779 --> 00:02:30.174
implementation time I think all in all we will end up with working on it for about a year and for an IFRS 17 solution I think that is very 

00:02:30.175 --> 00:02:33.556
fairly quickly. Based on our experience so far we are very happy.