8/12/2019 Bordya

1/5

This document contains details of the outstanding RI Bordereau requirements.

This initial version has been formed out of high level requirements which have been filled out byRebus to describe a possible working solution and to come up with estimates for the work involved.All parties must review this document with this in mind and respond with any concerns and/or

omissions it is felt eist.

!election by R/I "articipant

This requirement has arose from the #I $% branch& though maybe used by any branch once set up.'or the #I $% branch this change is needed to enable them to report policies incepting on or after()/()/** only and not to pick up earlier policies).This is because #I $% will continue to processthose policies before that date& while +itodurum will process policies after that date. "olicies ceded to+itodurum will be set up with a different ,ame -ode for the participant. This will allow a Bordereaurun to be selected which will only contain policies which are being processed through +itodurum.

!election by "rogram ,umber

This requirement replaces that raised earlier which stated that it must be possible to select a numberof R/I "olicies/Inwards risks for a single bordereau run. After further discussions it was found that themain reason this would be required would be to enable all the policies belonging to a specific "rogramto be report in the one bordereau run.

It will be far more straightforward to add the selection by single "rogram ,umber than to set up thismultiple select option. 'urthermore the chances of missing out a policy would be removed and allpolicies stamped with the entered "rogram ,umber would be reported.

-ession "ercentage rounding

As the -ession "ercentage is calculated for reporting on the Bordereau& based on the amounts

posted& rounding errors occur which do not look neat on the report and could lead to confusion. Alsowhen data is sent via RI,T the transactions will be reected since the RAI! system will check thepercentage against one held on RAI!& and there is no built in tolerance level.

It has been stated that the percentages used are a maimum of 0 decimals. The suggestion has beenmade to round the four decimal. This has been confirmed as acceptable by 1arkus Baier.

#ritten/"aid Reporting Basis

A requirement was also raised to be able to run the bordereau on a paid basis to add etra fleibility tothe bordereau reporting to allow local reports or 2pre3bordereau4 5Ad3hoc6 +itodurum reports to onlyreport those items where the associated gross amount has been fully paid.

7ive Run -onfirmation

A request has been raised to ensure that a warning message is sent when a user selects a 27ive4bordereau run. This should also prevent the function processing until a second requested to proceed isreceived by the function.

)These policies will be dealt with locally using R/I Broker statements which are currently beingspecified. his will include any local/direct reinsurers.

8/12/2019 Bordya

2/5

8atabase -hanges

Bordereau 'ile !uite

The main bordereau control file which holds the details of run request must be changed to include a

,ame code to hold the R/I "articipant ,ame code entered and a field to hold the "rogram ,umber ifentered.

These two fields will be printed on the top of the bordereau run audit reports.

1ain 9enius 'ile changes

-urrently when premium and claim transactions are reported on the Bordereau 5as part of a liverun6& they are flagged so that they are not reported again. This flagging of transaction must be movedto a different file to allow the selection by participant.

1ain Bordereau !elect function

The main select screen for the bordereau will be changed as shown.

CWIC01 Bordereau Production - Select 4/12/98 14:19:55Type detail! pre "nter#

Bordereau Type$Pre%iu% # # # : B &/' Pre%iu% (er) : B &/' Tec*nical +/C : B &/'Clai% # # # # : B &/' Clai% (eer)e : B &/' (eport Bai #: B ,,,,,,,

Select ,ption$

ro% Period # : 99999 To Period # : 99999Co%pany # # # : BBBBBBBB ,,,,,,,,,,,,,,,,,,,,,,,,,Branc*# # # # : BBBBBBBB ,,,,,,,,,,,,,,,,,,,,,,,,,(/I Particpnt#: BBBBBBBB ,,,,,,,,,,,,,,,,,,,,,,,,, Br./Inurer# #: BProra% 'o# # : BBBBBBBBBBBBBBB(/I Policy # : BBBBBBBBBBBBBBB ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,Inard (i. : BBBBBBBBBBBBBBB ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,Inard Clai% : BBBBBBBBBBBBBBB ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Control ,ption$i)e (un # # : B Pre-+lloc la: BB ,,,,,,,,,,,,,,,(eprint (e3 # : 999999999

"6it 4Pro%pt 12Pre)iou 15"n7uiry

+alidation

To reduce the possibility of someone accidentally running bordereau for a full company and branch&the new R/I "articipant field will be made mandatory& ensuring the user is forced to enter a specificreinsurer. 'or those occasions where a full branch run is required& the participant name code 2:All4 ;will be ecepted but not used as part of the actual selection processing.

The Brk/Insurer field will initially default to 2I4.

If a "rogram ,umber is entered& it will notbe valid to also enter an R/I policy& inwards risk orinwards claim.

If "articipant is specified& it will be valid to also enter a "rogram ,umber

8/12/2019 Bordya

3/5

Basis Type will default to 2#4 for #ritten. This can be changed to 2"4 for "aid. This field will bemandatory and valid values are only 2#4 or 2"4

!elect by "rogram ,umber

The standard select function below will be available on the new "rogram ,umber field. This functionis currently used to select policies via the eternal reference field on the underwriting select screen.

The ,ame Involvement type will default to 2A4 for 1aor Assured so only references for these nameinvolvement4s will be shown0.

The 2!electing for option4 shows the description of the option and transaction code combination thatwould be entered when this program is called from the underwriting maintenance select function.These will be defaulted to 2)/(=4 within the functions which will result in the description& 2nquire on"olicy4>.

P89 ;;;;;;;;;;;;;;;;;Select Policy;;;;;;;;;;;;;;;; 4/12/98 1:iplay C%d ,pt,p "6ternal ater In)ol)e In) +ured Incept

(e3erence (e3erence 'a%e Tp >ate

;; ?P(,(+'B"(? I'WI+B/9This is soft coded and will show the description as set up at #interthur.

8/12/2019 Bordya

4/5

A standard select function will be available from the R/I "articipants field. This screen will show allnames for the usage types ) and ; with values controlled by the 2Broker/Insurer4 flag descibed above.+alues used will be (;/(= for Reinsurers& and (;/() for Brokers.

D''+4@ ;;;;;;;;;;;;;;;Select 'a%e;;;;;;;;;;;;;;;; 4/12/98 14:04:55

ae Type 1 : 02 "6pert ae Type 2 : 05 (einurerType option! pre "nter#1Select

,p 'a%e it 'a%e Typ ;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;; ; ;;; ;

; + +! r o*n P (I '; ++CE0001 +ac*ner (uc. C (I '; ++CE0002 +ac*ner (uc.)eric*erun C (I '; +T;0002 +ent 'u%Fer 2 C (I '; +T;000 +ent 'u%Fer C (I '; +T;0004 +ent 'u%Fer 4 C (I '; +T;0005 +ent 'u%Fer 5 C (I '; +T;000@ +ent 'u%Fer @ C (I '; +I(0001 +I (I Bro.er 1 C (I '; +S>000< ad33d33da3 C GE '

; +DI'T +llianH international C (I '; >D(C001 >D Tet (/I Co%pany C (I '; "P "P Inurance Co%pany C (I '; ,+0001 oarty! od Carl P (I

"6it 5(e3re* 11>iplay/Eide +ddre 12Pre)iou Pp P>n

If the name code is entered directly into the field& it will be validated to ensure it has a validBroker/Insurer name usage as defined above. ,o checks will be performed against policies.

#ritten/$npaid Basis

8/12/2019 Bordya

5/5

Audit Reports

Both audit reports will be updated to show the "articipant/"rogram ,umber if entered and whichbasis the reports were run under.

stimates

"rogram ,umber !electReinsurer !elect#ritten/"aid Basis