Gikonyo, Timothy 21-Jul-20 - Britam - Kenya

Motor Certificate Printing System

Business Requirements Document

Gikonyo, Timothy

21-Jul-20

2

Contents 1 Glossary of Terms .............................................................................................................................. 3

2 Approvals .............................................................................................................................................. 4

3 INTRODUCTION ................................................................................................................................ 7

3.1 Purpose ...................................................................................................................... 7

3.2 Scope .......................................................................................................................... 7

3.3 Assumptions .............................................................................................................. 7

4 Background ......................................................................................................................................... 8

5 CURRENT CHALLENGES ............................................................................................................. 18

6 Functional Requirements ................................................................................................................ 19

6.1 Certificate Requisition & Registering ...........................................................................20

6.2 Certificate Request and Assignment ...........................................................................22

6.3 Certificate printing .......................................................................................................25

6.4 Integration ...................................................................................................................27

6.5 Printer Configurations .................................................................................................28

6.6 User Access and Administration .................................................................................28

7 Non Functional Requirements ........................................................................................................ 30

7.1 User Access/Security Requirements: ..........................................................................30

7.2 Audit and Control: .......................................................................................................30

7.3 Reports .......................................................................................................................30

3

1 GLOSSARY OF TERMS

User User of the system

Approver User of the system that has rights to approve

TIRA Tanzania Insurance Regulatory Authority

Branch An office that is responsible for sharing out certificates to users.

Consumer A user that is consuming the motor vehicle certificates on INSIS

IC Insurance Company

HQ Headquarters

IAM Insurance Association of Malawi

ISSM Instituto de Supervisão de Seguros de Moçambique

7

3 INTRODUCTION

The Sirius upgrade to Pure was completed earlier this year for Malawi, Mozambique and

Tanzania. However, Pure does not have sufficient capability to handle the motor certificate

process. Currently the process of issuing motor certificates is largely manual, which makes it

hard to manage and it makes it susceptible to fraud. In order to overcome the challenges

experienced by manually managing the certificates, a Motor Certificate system is envisioned

to automate all the aspects of the motor certificate process including integrating with Pure

and other third party systems.

3.1 Purpose

The purpose of this document is to detail the Motor Certificate processes requirement for

Malawi, Mozambique and Tanzania. It defines functional requirements and non-functional

requirements to facilitate implementation of Motor Certificate and integration between Pure

and other third party systems

This document will form a common understanding and a point of reference among the

stakeholders who will be involved in the design, development and testing of the envisaged

solution.

3.2 Scope

The following functionality is considered to be in scope of this document:

i. Certificate Requisition & registering

ii. Certificate Request & Issuing

iii. Certificate printing

iv. Reporting

v. User Administration

3.3 Assumptions

Assumption Justification Impact

The motor certificate system

will work together with Pure

and other third party systems

Integration to Pure and other

third party provides will

developed

Integration is expected to

reduce on the turnaround

time

8

4 BACKGROUND

Motor certificates are serialized document issued to a motor insurance policy holder in order

to certify that their car is insured. Motor Certificates (sample below) are issued by the

insurance regulatory authority to insurance companies. Each of the certificates has a unique

serialized certificate number. To issue a certificate an underwriter prints the policy details on

the certificate as shown by the Tanzania sample below.

Tanzania Motor Certificates

Sticker Class

(Tanzania) Sticker

Private Vehicle

Commercial

Vehicle

9

Public Vehicle

Motor Cycle

10

Britam Malawi issues one certificate type as shown by the sample below:

Mozambique

Mozambique has two certificate types, the first is sold by Boarder Agents and the Boarder

Entry points for motorists visiting Mozambique and the second is issued to all other vehicles

buying insurance in Country.

Mozambique Tour Border Certificate

11

12

The below certificate sample is the certificate type issued in Country and it applies to all

types of vehicles in Mozambique:

13

The table below shows the types of certificates (Tanzania).

Classes Class

Groups Vehicle Use

Motor Cycle

A License to drive motor cycles with or without a sidecar and whose capacity exceeds 125cc or 230kg.

A1 Licenses to drive motor cycles without sidecar and whose capacity is less than 125cc or 230kg.

A2 License to drive motor powered tricycles and quadricycles.

A3 Licenses to drive moped whose capacity does not exceed 50cc.

Private Vehicles

B License to drive all types of motor vehicles except motor cycles, commercial, heavy duty and public service vehicles.

Public

C

License to drive public service vehicles with seating capacity of 30 and more passengers in addition to the driver, Vehicles in this category may be combined with a trailer having a maximum authorized mass of not more than 750kg. Applicants must have held Class CI or E license for a period of not less than three years.

C1

License to drive public service vehicles with a seating capacity of 15 but less than 30. Passengers in addition to the driver. Vehicles in this category may be combined with a trailer having maximum authorized mass of not more than 750kg. Applicants must have held Class D license for a period of not less than three years.

C2

Licenses to drive public service vehicles with seating of four but less than fifteen Passengers. Vehicles in this category may be combined with a trailer having maximum authorized mass of not more than 750kg. Applicants must have held Class D license for a period of not less than three years.

C3

Licenses to drive public services vehicles with a seating capacity of four or less passengers inclusive the driver. Vehicles in this category may be combined with a trailer having a maximum authorized mass of not more than 750kg. Applicants must have held a Class D license for not less than three years.

Commercial

D Commercial Light Duty Vehicles: License to drive all types of vehicles except motor cycles, heavy duty and public service vehicles.

E Commercial Heavy Duty Vehicles: License to drive all types of vehicles except motor cycles and public serves vehicles. Applicants must have held Class D License for not less than three years.

The Table below shows the vehicle usage classification for Malawi

Class Vehicle Usage Britam Malawi Rates

Motor Private Private Cars K80,000.00

Fleet K80,000.00

Car Hire/Taxis N/A

Trailers 50% of Basic TP

Pass/Liability K 10,000/Pass

Motor Commercial Own Use K 120,000.00

Fleet N/A

Trailers 50% of Basic TP

Omnibus (Own Use) K200,000.00

Hire & Reward K150,000.00

14

Fleet N/A

Trailers 50% of TP premium

Special Types K 60,000.00

Buses N/A

Mini Buses N/A

Pass/Liability K 10,000.00/Pass

Motor Cycle K 40,000.00

Motor Traders (Internal) K 50,000.00

Motor Traders (External)

K 75,000.00

Motor Contingent K 50,000.00

TP Limits of Liability TP Death and bodily injury TP Property Damage Loss of Use

D/I–K5,000,000.00 PD–K1,000,000.00, Corporates K3,000,000.00 LU – K 50,000.00 Corporates K100,000.00

Pass Liability Limits K250,000.00/Pass K1,000,000.00/event

Comprehensive

Private vehicles Sum insured between K2m – K5m rate 7%

Sum Insured K5m+ and fleet rate 6%

Commercial vehicles Fleet

Rate 12.5%

Rate 10%

Motor Cycle Rate 4%

The Table below shows the vehicle usage classification for Mozambique

Class Vehicle Usage Britam Mozambique Limits

Tour / Boarder Heavy Commercial Vehicles, Buses 3,000,000.00 MT

Trailers for HCV 3,000,000.00 MT

Motor Vehicles Sedan/SUV/LDV 3,000,000.00 MT

Caravanas/Motorcycles, Trailers for Private Vehicles; Specials & Caravans

3,000,000.00 MT

Legal Assist 122,500.00 MT

Class Vehicle Usage Britam Mozambique Limits

Motor Private Comprehensive 15,000,000.00 MT

Third Party Theft and Fire 15,000,000.00 MT

Third Party Only 5,000,000.00 MT

Motor Commercial

Comprehensive 15,000,000.00 MT

Third Party Theft and Fire 15,000,000.00 MT

Third Party Only 5,000,000.00 MT

15

The Current process for managing certificates is largely manual. Certificates are received

from TIRA Office; the details are recorded in HQ. An underwriter then assigns certificates

numbers to the various branches and intermediaries and dispatches the physical copies to

those branches and intermediaries.

1. Branches

Tanzania Mozambique Malawi

a. HQ Branch

b. Mlimani City Branch

c. MIC Branch

d. Mwanza Branch

e. Dodoma Branch

f. Arusha Branch

g. Mbeya Branch

h. Mtwara Branch

a. Maputo

b. Chimoio

c. Beira

d. Nampula

e. Tete

a. Blantyre

b. Lilongwe

c. Kasungu

d. Mzuzu

2. Intermediaries such as Broker, Agent, Bank Assurance (Intermediary Name)

(Tanzania)

In the branches and intermediaries, for each policy issued by the underwriter, they print a

certificate for that policy. At the end of the day the underwriter consolidates a list of used

certificate numbers along with their matching debit number and sends this HQ for

reconciliation. The list also contains certificates that were spoiled (e.g. misprinting of physical

damage). This list is meant to inform HQ of the certificates that have been utilized and those

that have been damaged. It also helps head office to keep an inventory of available certificate.

A sample of the list is shown below.

16

The motor certificate management and administration for Malawi process starts with the

underwriting manager together with the motor certificate officer, making a formal requisition

to the finance manager to allocate funds towards the purchase of motor certificate serial

numbers. The Motor Certificate serial numbers are purchased from the insurance

association of Malawi which sells and tracks ranges of motor certificate serial numbers sold

and allocated to the various insurance companies.

In order to ensure that motor certificates are tracked and usage monitored, a few checks are

put into place to aid this.

Motor Certificate Requisition form

Motor certificate register (manual)

Motor certificate declaration report (system generated)

Motor Certificate Distribution Report

Spoiled/Spoilt Certificate Declaration Report

The Current process for managing certificates is done through the MotorCert system. An

underwriter assigns certificates numbers to the various branches and dispatches the physical

copies to those branches. At the branch, for each policy issued by the underwriter, a

certificate is printed for that policy. Once a batch is close to full utilization the motor certificate

officer generates a motor certificate declaration report together with a list of spoiled

certificates and sends to HQ for reconciliation. This list is meant to inform HQ of the

certificates that have been utilized and those that have been damaged. It also helps head

office to keep an inventory of available certificate. A sample of the list is shown below.

17

Mozambique currently manages its Motor certificates through a manual system. Motor

certificates in Mozambique are privatized with each insurance company producing its own

branded and serialized certificates. The Motor certificate is one type which serves for all

Motor Vehicle classes. The Management of certificates is at two levels, Administration and

Underwriting. Underwriting must produce a usage report which is submitted to

Administration before being allocated the next batch. The Underwriting Manager is then

responsible to distribute/ allocate to the individual users and branches.

18

5 CURRENT CHALLENGES

1. Motor certificate management is a manual process where there’s a high risk of fraud

and misplacement as well as accountability issue.

2. Motor certificate are a manual handbook which are received from the insurance

regulator to the insurers where the insurer can then provide to clients upon receiving

premium.

3. For Tanzania, the motor certificates are received in a given range from the insurer

which then is being distributed to branches and intermediaries.

4. The process of managing certificates is manual and sometimes cumbersome to

track the utilization per BU including damaged stickers.

5. Spooling of certificates takes too long

6. Errors in allocation (Both actual allocation of invoice to a motor certificate

transaction & auto allocation of invoices by the system)

7. The system does not detect errors in issuance of wrong Insurance Period

8. The system does not detect that a certificate for the stated period has already

been issued

9. The system lacks control for managing Fraud (one can easily edit client or

cover details before printing the disk)

10. The system lacks the Intelligence in setting out a guideline for inserting data

uniformly.

11. The system sometimes duplicates transactions

12. The system usually hangs when issuing certificates ( Kasungu )

13. The system does not generate client details where an apostrophe is used in the

client name

19

6 FUNCTIONAL REQUIREMENTS

The proposed system should offer the following functions;

Certificate Requisition & registering: process of requisitioning, receiving and

registering certificates.

Certificate Request & Issuing: processes of assign certificates to the branches and

intermediaries.

Certificate printing: utilization of the certificates.

Reporting: The following reports will be necessary at both branch level, intermediary

and at head office level. The report specification details will be provided separately

o Utilization reports: showing the usage of the certificates for a select period

o Certificate inventory reports.

o Compliance report: showing reports certificate usage does not comply with the

define rules (defined in the following requirements section.

User Administration

Validation Requirements (Malawi, Tanzania & Mozambique)

The Proposed system should not permit editing of certificates after being processed

in the system

The system should deny issuing of a certificate where the period is more than 365

days

The system should provide alerts where certificates are issued out but no invoice

has been raised for a period of time

The system should deny issuing of a certificate where the registration number is not

entered uniformly

20

There should be an approval matrix before a certificate is spoiled or recalled in the

system

The system should not allow a certificate to be edited once it has been processed in

the system

The system should not allow an invoice to be edited once it has been generated as

the same can be manipulated

The system should be able to produce alerts that a registration number has been

issued to a particular certificate to avoid duplication

The system should be able to deny allocating an invoice for a previous period of

insurance

The system should be able to detect that a particular invoice does not belong to a

particular client

The system should deny issuing a certificate where he period stipulated is more than

365 days

The system should deny auto generation/ auto allocation of invoices to transactions

which are outside the system

The following section details the envisaged system process and details the requirements

6.1 Certificate Requisition & Registering

The proposed system should allow the creation of a certificate requisition from TIRA.

Requisition is done by;

Tanzania Malawi Mozambique

Selecting the certificate

category/type of certificate to be

requested.

Print a requisition letter

Print a requisition letter

(Internally)

Once the certificates have been received the system should allow for the registration of the

certificates. The flow chart below illustrates the certificate registry process.

21

Certificate Registering

Un

de

rwri

tin

g

Ma

na

ge

rp

ort

al

Phase

Start Login Creates

Registration batch

Capture batch start and end

serial

Validate the new batch

Create certificate numbers

Confirm certificate

number generation

End

The process as depicted above beings by the underwriter or Underwriting Manager receiving

the physical certificate copies. The underwriter then logs into the system and performs the

following steps.

1. Create a registration batch. A registration batch represents a list of certificates that

have been received and registered together, the registration batch will contain the

following information;


Registration Batch ID Registration Batch ID Registration Batch ID

Registration Date Registration Date Registration Date

Reception Date Reception Date Reception Date

Certificates Type Receiver Receiver

Receiver

Field Description

22

Registration Batch ID A system generated ID to uniquely identify the batch.

Registration Date A system Time stamp of the registration date

Reception Date Date the received by the underwriter

Certificates Type

(Tanzania only)

This indicates the type of certificates being registered.

There are Four types of certificates, Motor Private,

Motor Public, Motor Commercial and Motor Cycle,

certificates.

Receiver The user registering the certificates

2. The underwriter then proceeds to register the certificates under the batch. To

register the certificates, the underwriter defines the following;

Field Description

First serial number The first number of the certificates received

Last serial number The last number of the certificates received

3. The system will then use the submitted first and last number to generate the list of

certificates. E.g. if the first and last serial number are 1001 and 1011 respectively, the

system will generate 11 certificates number starting with 1001 and ending 1011.

4. Validation of the first and last serial number needs to be done by the system before

generating the certificates. The systems validate that indicated serials/certificate

number are not already register, that is, the certificate numbers should not be

overlapping. All newly registered certificates will have a status ‘Available’.

6.2 Certificate Request and Assignment

Once underwriters receive and register certificates, they can then assign them to the

branches and intermediaries for usage. Assignment of certificates is based on a request from

a branch and intermediary. An underwriter in the branch or an intermediary requests for more

certificate when the stock in the branch is low. The system should allow the underwriter and

intermediary to create a request by;


23

Selecting the type of

certificate needed

Select the number of

certificate needed


certificate needed


certificate needed

Branch Submitting the request

Branch/Intermediary Name Submitting the request

Intermediary Type

Submitting the request

The process flow below Illustrates the process of assignment of certificate once the request

has been received from the branches and intermediaries.

Validation: The system should give pop up messages when an underwriter requests

certificates if they have unused certificates. “You have 12 unused certificates, are you sure

you want to request for more certificates?). It should proceed to allow the request.

Certificate Assignment

Un

de

rwri

ter

Ma

na

ge

rB

ran

ch

/U

nd

erw

rite

r

Phase

Start Login Creates

Assignment batch

Capture batch start

and end serial

Confirm Receipt of

Assignment Batch

Assign the batch to the

branch

Notify branch/intermediary of assignment

end

The assignment process starts by the underwriting Manager creating an assignment batch

and follows the following steps

1. The underwriter creates an assignment batch and captures the following batch

details.


24

Assignment Batch ID Assignment Batch ID Assignment Batch ID

Assignment Date Assignment Date Assignment Date

Branch

Intermediary

First serial number First serial number

Select Intermediary Last serial number Last serial number

Certificate type (Tanzania) Branch Branch

First serial number

Last serial number

Field Description

Assignment Batch ID A system generated ID to uniquely identify the batch.

Assignment Date A system Time stamp of the registration date

Branch

Intermediary

Branch being assigned

Intermediary being assigned

(Broker, Agent, Bank Assurance)

Select Intermediary (Drop Down list of Intermediaries)

Certificate type This indicates the type of certificates being registered.

There are two types of certificates, motor private and

motor commercial certificates.

First serial number The lowest available/unassigned certificate number. This

generated by the system, the underwriter is not allowed

to pick any other value.

Last serial number The last number of the certificates to be assigned

2. Once the range of serials / certificate numbers has been selected the system should

validate that the defined range exists and is in the available status.

3. The underwriter will then submit the assignment batch.

4. A branch underwriter/intermediary of the assigned branch is required to acknowledge

receipt of the assignment batch once they receive and verify the physical certificates.

They do this by changing the status of the assignment batch to ‘received’.

5. A branch underwriter/intermediary can revert the assignment batch if they don’t

receive the physical certificates. In this case batch can be reassigned by the head

25

office underwriter to another branch/intermediary. Though the indicated range of serial

number cannot be changed.

6. Once the branch underwriter/intermediary acknowledges receipt of the assignment

batch the batch status will be changed to assigned.

Validation: The underwriting manager should check certificates requested from specific

branches/intermediaries and how many are not utilized. The underwriting manager will then

decide to assign more certificates or revert.

6.3 Certificate Printing

The proposed system will integrate with Britam’s policy administration system to allow

printing of certificates for covered vehicles and policy issued in the policy

administration system. Underwriters are allowed to print certificates that have been

assigned to their branch and have not been utilized. Printing process proceeds as

follows;

1. Underwriters search for a vehicle by inputting the policy number or a debit note

number (a debit note number is an invoice number that is generated from

Sirius on policy issue)

2. The system will then retrieve the following information to be printed on the

certificate

3. The motor Certificate should indicate the Class whether Motor Cycle, Private,

Public or Commercial Class.

The Table Below shows the information for Tanzania

Field Description

Certificate Number Certificate Number issued by TIRA

Vehicle Number Vehicle registration/Number plates

Make The Vehicle Make e.g. Toyota

Model The Vehicle Model

Color Vehicle Color

Insurer The issuing company

Commencement Date Policy cover start date

Expiry Date Policy cover end date

The Table Below shows the information for Malawi

Field Description

26

Debit Note number Invoice number generated by Pure

Policy number Policy number generated by Pure

Commencement Date Policy cover start date

Expiry Date Policy cover end date

Registration Number Vehicle registration/number plates

Issued by The issuing company

Name of Issuer Name of Underwriter e.g. Initials

Type of cover Comprehensive or Third Party

The Table below shows the information for Mozambique

Field Description (Tour Certificate)

INSURED Name of the Owner

RIGISTRATION Registration Number

MAKE AND MODEL Vehicle Mark and Model

TIME Time of the created policy

PERIOD Cover Dates

CURRENCY Currency

COVER TYPE Type of Cover

Field Description (Motor Certificate)

TRANSACTION REF. Debit Note Number

CLASS Product Type

TYPE Cover type (Comprehensive, FTF&T, Third Party Only)

POLICY NUMBER Policy Number

THIRD PARTY LIMIT Cover Limit

INSURED The Insured Name

VEHICLE The Make/Brand of the Vehicle (e.g: Mazda BT50)

REGISTRATION Registration Number of the Vehicle

ENGINE No Number of the Engine

CHASSIS No Number of the Chassis

PERIOD Cover Period

27

OWN DAMAGE SUM INS Sum Insured

BANK INTEREST Bank Interest

TERRITORIAL LIMITS Countries covered by the policy

4. In case of multiple vehicles with the same debit note or policy, the underwriter

will be prompted to select the correct details/vehicles.

5. The system will then allocate a certificate number to the vehicle selected. The

following validations are necessary during allocation.

a. The vehicle has no certificate already allocated. In case an underwriter

wants to allocate a certificate to vehicle that already has another

certificate, they need to invalidate the current allocation first. To

invalidate/unallocated the current certificate the underwriter follows the

steps;

i. Find/search for the relevant vehicle.

ii. Input the reason for un-allocation/Invalidated e.g. accident

damage, printer damage, lost, etc.

iii. Action the un-allocation

6. The Underwriter is then allowed to modify the following information before

printing.

a. The start date. If this is modified, the date should be the current date or

in the future but within the cover period (between cover start date to

end date) defined.

b. The cover end date. Should be proportional to the prorated premium

paid. If 50% premium is paid, the certificate can only be generated for

50% of the period. If the underwriter requires to generate a long period,

there should be an approval process in place.

7. Once the certificate number has successfully been allocated. The underwriter

then selects available printer and prints the certificate. The system will then

ask the underwriter to confirm if the printing was successful. On a successful

confirmation the system updated the certificate’s status to printed.

6.4 Integration

The propose system will have the following Integrations.

28

1. The proposed system will need to integrate with Sirius Pure - Britam’s policy

administration system to access policy and vehicle information and perform the

validations described in the functional requirements section above. Policy details such

as New Business, Renewal and vehicle details such as Vehicle Reg. Number, Make,

Model, Vehicle Color. This is the requirement for Malawi, Mozambique and Tanzania

2. The system will integrate with government portal for managing motor certificate –

TIRAMIS so to avoid duplication of tasks to register again in TIRAMIS. The duplication

of tasks is when underwriters post in Sirius and then have to enter vehicle registration

again to government portal TIRAMIS, this is duplication of tasks. The motor certificate

management should integrate with TIRAMIS and Sirius to avoid duplication of tasks.

The fields for integrations should be the same as captured on the Motor Certificate

and Sirius such as Vehicle Reg. Number, Make, Model, Vehicle Color, Policy number.

3. The system will be integrated with active directory to provide single sign on through

windows authentication.

4. The system should integrate with the Malawi Road traffic Directorate. fields to be

accessed include Registration Number and Chassis number

5. The system will be accessed through Britam’s Intranet portal through an Iframe.This

means the system need to be a web –based system that can be imbedded through on

an HTML Iframe. Sign-on credentials will be passed through the URL.

6.5 Printer Configurations


Tanzania we do not print certificates but manually write them. However this should remain option until further confirmation from the regulator as it was hinted Tanzania is moving to digital certificates and not paper certificates.

In Malawi the printer used to print out certificates is an Epson LQ-690 & Epson LX-350. This printer prints 4 certificates.

The printer used to print out certificates is an Epson LQ 2190. This printer prints 3 certificates in triplicate.

6.6 User Access and Administration

We propose the system to be rights based where we have the following roles

Super User: Creates Branches/Users/Assign roles to branch users

Senior Underwriter/ Administrator: Assign Certificates to branches and

intermediaries’/ Void certificates/ Reassign certificates from one branch to another.

29

Branch Administrator: Receives the certificates from the Senior Underwriter.

Underwriters: Print certificates based the certificates that have been approved.

30

7 NON FUNCTIONAL REQUIREMENTS

7.1 User Access/Security Requirements:

i. Access of system should be based on the user’s role

7.2 Audit and Control:

i. There should be logs for audit trail and for error identification/resolution.

7.3 Reports

Certificate Assignment Reports:

This report should show the certificates that have been assigned to the group during specific

periods of time e.g. Monthly/Weekly and also query the duration he/she would like to query.

Fields to be captured here include


Certificate Type (Motor Private/Motor Commercial)

Duration(Monthly)

Duration(Monthly)

Duration(Monthly) Branch

Certificate Range Assigned

Branch Certificate Range Assigned

Certificate Range Assigned

The report should show certificate distribution to intermediaries such as Brokers and Agents

Utilization Report

This report should to be able to list the certificates at that have been utilized during a specific

period of time. The following field will be required:


Certificate Type Certificate Number Certificate Number

Certificate Number Policy Number Policy Number

Branch Posted Date Posted Date

31

Policy Number Debit Note Number Debit Note Number

Posted Date Status (Printed/Spoilt) Status (Printed/Spoilt)

Debit Note Number Cover type Cover type

Status (Printed/Spoilt) Branch Branch

Cover type

Spoilt Certificate Report:

This report should display the spoilt reports per branch. Fields here include


Certificate number Certificate number Certificate number

Policy Number Policy Number Policy Number

Registration Number Registration Number Registration Number

Branch Start Date Start Date

Intermediary Name/Type End Date End Date

Start Date Posted Date Posted Date

End Date Branch Branch

Posted Date

Cover type (Motor Commercial/Motor Private)

Available certificate report:

This report should display the total number of available certificates. The Fields to be included

here are listed below


Certificate number Certificate number Certificate number

Branch Branch Branch

Certificate Type

Intermediary Name/Type

The report should include reports to show utilization and premium generated for each at Intermediary, Branch and Company level.

Gikonyo, Timothy 21-Jul-20 - Britam - Kenya

Documents