RSD All Market Segments - Courier Report and Transmittal Slip - v3

BDO Insurance Brokers, Inc.
(BDOI)
Requirements Specification Document
For uploading of:
Courier Confirmation
Transmittal Slip
Version 0.01
Creation Date: January 2015
User of this document is responsible to use only the current version available on HQ and headMine.
The information contained in this document is not to be used for any purpose other than the purposes for which this document is
furnished by GENPACT, nor is this document (in whole or in part) to be reproduced or furnished to third parties or made public
without the prior express written permission of GENPACT.

Uploading requirements 02
Version 0.01
Document History
Version
Date
Author
Description of
Change
Reviewed By
0.01
January 28, 2015
Jeffrey Oliveros
Document creation
Conchita Valena
Approved By
Reference Documents
Document Name
Version
Date Updated
Business Requirement Pipeline Management

Business Systems Proposal of BDOI Online Brokerage System (BBS)
CLG Renewal Module
Requirements Specification Document for Pipeline Management,
Solicitation and Placement
2
1.0
3/4/2014
3/12/2014
0.04
4/3/2014
Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)
Page 2 of 30

Version 0.01
TABLE OF CONTENTS
1. Process Schematic / Process Flow............................................................................................... 4

2. Functional Description................................................................................................................... 6
2.1 RID 1 Extraction of data............................................................................................................ 6
2.1.1 Features.......................................................................................................................... 6
2.1.2 UI Wireframe................................................................................................................... 8
2.1.3 Inputs and Outputs........................................................................................................ 10
2.1.4 Reports Specification..................................................................................................... 11
2.1.5 Business Requirements Mapping..................................................................................11
2.2 RID 2 Uploading of Data to Staging Repository......................................................................12
2.2.1 Features........................................................................................................................ 12
2.2.2 UI Wireframe................................................................................................................. 16
2.3 RID 3 Uploading of Data from Staging to Pipeline..................................................................18
2.3.1 Features........................................................................................................................ 18
2.3.2 UI Wireframe................................................................................................................. 23
Page 3 of 30

Version 0.01
1. Process Schematic / Process Flow

EXTRACTION OF DATA
BDOI
BROKER SYSTEM
Start
Generates
extract file
Broker System
Fills out values

in File
the
Extract
extraction parameter
Saves file to
predefined location
UPLOADING OF DATA TO STAGING REPOSITORY

BDOI
BROKER SYSTEM
Checks and validates file

(Refer to sectionA2.2.1.4 to 6)
C
C
Sends extract file

Passed
to Courier
criteria?
Companies for
confirmation
N
D
C
Uploads file
STAGING
Page 4 of 30

Version 0.01
UPLOADING OF FILE FROM STAGING REPOSITORY TO PIPELINE

BROKER SYSTEM
B
Validates file
(Refer to section 2.3.1.1)
With
exceptions
?
D
C
Y
Generates exception file

consisting of those that did not
pass the criteria. Uploads records
without exception
N
Uploads data
PIPELINE
End
Page 5 of 30

Version 0.01
2. Functional Description
2.1 RID 1 Extraction of data
This function provides a facility in the system that will allow the user to extract data from the broker
system that will be sent to the courier for their CONFIRMATION OR REPLY.
2.1.1 Features
1. System facility to allow user to extract data based on the required parameters. The
following filtering options will be available to the user when extracting data from the broker
system.
FILTER
Start Date
End Date
Line of Insurance
Product Type
Courier Company
Location
2.
DESCRIPTION
Start date to End date may be confined to one month or
several months but should be within the same year.
Extraction of data may be on a per line of insurance (e.g.
Fire Insurance, Marine Hull Insurance, Dental Insurance)
Extraction of data may be on a per product type (e.g.
Under Accident and Health, extraction may confined to
Personal Accident, Medical Reimbursement, etc.)
Extraction of data can be on a per courier company.
However, user has the option to include all the courier
company by not indicating a particular insurer in the
extraction parameter.
Extraction of data may be based on location covered by
the courier company.
System facility to allow the user to extract data (in Excel format) that will be sent to the
COURIER SERVICE PROVIDERS. The following information will be extracted from the
system.
DATA
Transmittal Reference
Number
Courier Company
Date Sent to Courier
Account Reference
Number
Billing Address
Permanent Address
Areas
Assureds Name
VALUES/SOURCE
Reference number generated by the system after creation
of the transmittal
Name of the courier company maintained in the system
and defined during creation of transmittal tasked to send
the letter to the addressee
Date indicated during creation of transmittal when the
letter was forwarded to the courier company that will send
the letter to the addressee
Account Management > View Account Header
Account Management > Basic Information
The data columns below will be part of the extract file where the Courier companies can
indicate their reply, confirmation or comments which will be uploaded to the broker
system. This requirement will be discussed further in the succeeding sections of this
document.
Page 6 of 30

Version 0.01
COURIER
VALUES
REMARKS
Status
Delivered, Pending delivery or

Return to Sender.
Recipient
Name of the person who received

the letter for the addressee.
Relationship of the receiver to the
addressee of the letter.
Relationship to
the Assured
Date Received
Reason for
unsuccessful
delivery
Receipt
Reference
Number
Date the letter was received

Reason letter was not delivered
Reference number by the courier
report indicating the successful
sending of letter to the addressee
D = Delivered, PD = Pending
Delivery, RTS = Return To
Sender
Free text format
Initial/possible
values
are:
Assured, Spouse, Secretary,
Appointed Contact Person,
Son/Daughter, Father/Mother,
House helper, Guard, Relative
and Other Free Text
MM/DD/YYYY format
Free text format
Free text format
3.
System validation to extract information for confirmation. In order for a record to be

included in the extraction, the user should have created a TRANSMITTAL TRANSACTION
CREATED for the ACCOUNT REFERENCE NUMBER that will be extracted. Otherwise,
said records will be excluded from the data that will be extracted from the system.
4.
System facility to establish the type of extract file. Since the information that will be
extracted will VARY depending on who is the TARGET RECIPEINT of the file, a HEADER
CODE WILL PLACED ON THE CONTENTS OF THE EXTRACT FILE. Uploading will be
through a centralized module but the format of the extract and upload file will differ based
on the data, process or module of the broker system.
Below is the proposed naming convention for the header code.
EXTRACT FILE
HEADER CODE
XYAB
WHERE:
HEADER CODE
X
Y
Z
A
B
5.
DESCRIPTION
C = Courier Confirmation
Date (MMDDYYYY format) of extraction
Count from 01 - 99
Time stamp (HH:MM:SS format)
Number of records extracted
System facility to keep temporary record of files that have been extracted. The system will
KEEP records or logs of HEADER CODE and TOTAL RECORDS per extracted file. These
will be used to validate whether the extract file that will be uploaded back to the system is
valid or not. The term VALID presupposes that the file that will be uploaded to the system
refers to the same file that has been previously extracted. To illustrate:
Page 7 of 30

Version 0.01
There were 200 accounts (e.g. coverage date is from January 3 to January 25, 2015) that
were extracted last January 31, 2015. The system will assign a header code based on the
format mentioned in the preceding. The same will be kept by the system in its database.
When the user uploads back the same file, the system will check the header code and the
number of records of the file versus those logged in its database. .
HEADER CODE
COUNT
RESULTS
CC0131201501:05:00:00-200
200
CC0131201501:05:00:00-300
300
CC0431201501:05:00:00-200
200
Valid. Header code and number of records

in the file matches the systems logged file.
Not valid. Header code and number of
records in the file does not match the
systems logged file.
Not valid. Header code in the file does not
match the systems logged file.
6.
System facility to allow repeated extraction of accounts. The system will allow the user to
extract accounts as many times depending on his needs. This is to accommodate the
possibility that the user will extract records but for some reason does not process or
upload the file to the system.
7.
System facility to automatically save and indicate filename of the extracted file. The
system will store the extract file to a predefined directory maintained in the system.
Filename will also be generated by the system for the user.
FILE
STATUS
Extracted
LOCATION
\\BDOI\Extracted\ Courier Confirmation
FILENAME
XZAB
WHERE:
CODE
X
Y
A
8.
VALUE
CC = Courier Confirmation
Date extracted (MM/DD/YYYY format)
Count from 01 - 99
System facility to prompt system message after records have been extracted. The user
will be prompted of a system message informing him of the following:
o
o
Whether extraction was successful or failed;

If successful,
o Number of records that have been extracted;
o Location where the extract file was saved.
Page 8 of 30

Version 0.01
2.1.2 UI Wireframe
DATA EXTRACTION MENU
DATA EXTRACTION PARAMETERS
Page 9 of 30

Version 0.01
DATA EXTRACTION CONFIRMATION MESSAGE
2.1.3 Inputs and Outputs

DATA EXTRACTION MENU
Page 10 of 30

Version 0.01
DATA ELEMENT
BEHAVIOR
Executable
button
FORMAT
RANGE OF VALUES
REMARKS
Directs the system
administrator to the
DATA
EXTRACTION
PARAMETERS.
DATA EXTRACTION PARAMETERS

DATA ELEMENT
BEHAVIOR
FORMAT
Start Date
Data entry
MM/DD/YYY
End Date
Data entry
MM/DD/YYY
Line of Insurance
Drop down
Product Type
Drop down
Courier Company
Drop down
Area
Drop down
Clear All
Executable
button
Extract
Executable
button
Close
Executable
button
RANGE OF VALUES
o
o
o
o
o
o
REMARKS
All
Particular
All
Particular
All
Particular
o All
o Particular
Area will be based

on the
City/Municipality
Erases all values
in the extraction
parameters
indicated by the
user.
Extracts
data/generates
extract file based
on the parameters
indicated by the
user.
Closes the DATA
EXTRACTION
PARAMETER
WINDOW.
DATA EXTRACTION CONFIRMATION MESSAGE

DATA ELEMENT
Confirmation
Message
Ok
BEHAVIOR
FORMAT
RANGE OF VALUES
REMARKS
Display
Executable
button
Closes the
EXTRACTION
CONFIRMATION
MESSAGE
Page 11 of 30

Version 0.01
2.1.4 Reports Specification

Refer to Annex 1- extract file generated from the broker system.
2.1.5 Business Requirements Mapping

ITEM #
BR REQUIREMENTS
FEATURES
BRM-UP02-RID1-001
User should be able to extract

data listed in section 2.1.1.2
based parameters discussed in
2.1.1.1 of this document.
BRM-UP02-RID1-002
User should be able to generate

and save extracted data based
on the predefined location.
System facility to allow the user to

extract data based on the
requirements mentioned in the
section 2.1.1.1 and 2.1.1.2 of this
document.
System facility to extract and save
data to a predefined repository.
2.2 RID 2 Uploading of Data to Staging Repository

This function provides a facility in the system that will validate the format and completeness of the
uploading files. The uploading files refer the COURIER CONFIRMATION and/or TRANSMITTAL
REPORT. The Courier confirmation upload file refer to extract file that had been submitted to the
courier companies for reply or feedback while the transmittal report are those that have been
prepared manually by BDOI. Unlike the Courier report, contents of the transmittal report were not
extracted from the system. These are new data that will be introduced to the system through
uploading instead of data entry. The upload program will validate the format and contents of the file
to ensure that this complies with the system requirements before this is uploaded to the Staging
Repository.
2.2.1 Features
1. System facility to allow user to upload files. A module will be available to the user to
upload the Courier Confirmation and Transmittal Report. Below are the contents of each
upload file.
COURIER CONFIRMATION
BDOI Module
Transmittal Reference Number
Courier Company
Account Reference Number
Mailing Address
Address
Areas
TRANSMITTAL REPORT
BDOI Module
Slip
Date Sent to Insurer
Date Sent to Client
Date Received Feedback from Insurer
Mode of Transmittal
Page 12 of 30

Version 0.01
Assureds Name
Status
Recipient
Relationship
Date Received
Reason for unsuccessful delivery
Receipt Reference Number
Name of Receiver
Relationship to the Assured
Date Received from Insurer
Date Received from the Bank
Date Sent to the Bank
TAT
2. System detection on the type and location of files to be uploaded. The system will detect
the type and location of files to be uploaded to the broker system through the UPLOAD
FILE MAINTENANCE MODULE in the BDOI Brokerage System.
FILE
Courier
confirmation
Courier
confirmation
Courier
confirmation
Transmittal
Report
Transmittal
Report
Transmittal
Report
WHERE:
CODE
X
Y
Z
STATUS
For uploading
FILENAME
XZAB
Uploaded
LOCATION
\\BDOI\For uploading\Courier
Confirmation
\\BDOI\Uploaded\Courirer Confirmation
Rejected
\\BDOI\Rejected\Courirer Confirmation
XZAB
For uploading
\\BDOI\For Uploading\Transmittal Report
XZAB
Uploaded
\\BDOI\Uploaded\Transmittal Report
XZAB
Rejected
\\BDOI\Rejected\Transmittal Report
XZAB
XZAB
VALUE
C = Courier Confirmation, TR = Transmittal Report
Date of target upload
Count from 01 to 99
AND
FOLDER
FOR UPLOAD
UPLOADED
REJECTED
DESCRIPTION
Location where files that will be uploaded to the system will be
placed by the user.
Location of files after these has been uploaded to the system. Files
that have been processed will be automatically MOVED by the
system from the FOR UPLOAD folder to the UPLOADED folder.
Locations of files that have not been uploaded to the system due to
non-compliance with the conditions prior to uploading (e.g. incorrect
header code, incorrect number of records in the file).
Page 13 of 30

Version 0.01
3. System detection on the files due for uploading. Based on the date indicated in the
filename of the upload files, the system will prompt or display to the user (through the
upload screen) regarding files that should be uploaded. User will also be allowed to upload
files whose date is not equal to the current system date provided that upload date
(indicated in the filename) is prior and not beyond the system date.
Below is an illustrative example:
Let us assume there were several upload files for courier confirmation in the upload
directory. These are listed as follows:
CC0105201501
CC0106201501
CC0107201501
CC0108201501
CC0109201501
DATE
January 5, 2015
January 6, 2015
January 7, 2015
January 8, 2015
January 9, 2015
If the system date is January 7, 2015, the user will be prompted of the following files that
should be uploaded to the system.
FILE
CC0105201501
CC0106201501
CC0107201501
REMARKS
Date is prior to the current system date
Date is prior to the current system date
Date is equal to the current system date
4. System checking on the validity of the upload files. In the case of the COURIER
CONFIRMATION, the system will check if an upload file is valid for uploading based on the
LOGS OF HEADER CODE STORED IN THE SYSTEMS DATABASE AND THE TOTAL
NUMBER OF RECORDS VERSUS THE HEADER CODE AND THE ACTUAL RECORD
COUNT OF THE UPLOAD FILE. In case there is a matched, the system will upload the
file. Otherwise, the system will REJECT the ENTIRE upload file. To illustrate:
In the systems database, the following are the logs of the extract files generated by the
system.
Page 14 of 30

Version 0.01
EXTRACT FILE
CC0105201501
CC0106201501
CC0107201501
CC0108201501
CC0109201501
HEADER CODE
CC0105201501:03:04:00-100*
CC0106201501:03:04:00-150*
CC0107201501:03:04:00-300*
CC0108201501:03:04:00-250*
CC0109201501:03:04:00-180*
COUNT
100
150
300
250
180
* - Please note that in section 2.1.1.5 of this document, it was discussed that when a file is
extracted, the system automatically assigns a header code and forms part of the contents
of the extract file. The same will be saved by the system to its database.
The system will compare the header code on the extract file versus those that were logged
in its database when the user uploads the above files on a particular date (e.g. January
16, 2015).
UPLOAD FILE
CC0116201501*
CC0116201501*
CC0116201501*
CC0116201501*
CC0116201501*
EXTRACT FILE
HEADER CODE
COUNT
CC0105201501:03:0
100
4:00-100*
CC0106201501:03:0
150
4:00-150*
CC0107201501:03:0
300
4:00-300*
CC0108201501:03:0
250
4:00-250*
CC0109201501:03:0
180
4:00-180*
SYSTEM
HEADER CODE
CC0105201501:03:04:
00-100*
CC0106201501:03:04:
00-150*
CC0107201501:03:04:
00-300*
CC0108201501:03:04:
00-250*
CC0109201501:03:04:
00-180*
COUNT
100
150
300
250
180
* - It was explained in the section 2.2.1.2 that the filename of the upload file will be based
on the type of extract file and the date it will be uploaded to the system.
In the above example, if the header code of any of the upload file does not match the
system records, it will be rejected by the system. One of the possible causes of the
Page 15 of 30

Version 0.01
discrepancy is due to manual or accidental alteration made by the user on the header
code of the extract file. Unless, corrections will be made on the code, the user will be
barred from uploading the file. In the same manner, if there is a matched in the header
code but the total number of records differs, the system will reject the upload file.
The above validation will NOT APPLY to TRANSMITTAL REPORT because the contents
of this document were not extracted from the system. These are new information that will
be introduced to the system. Thus, validation pertaining to the header code is not
necessary.
Apart from the above validations, the system will also check for the completeness (e.g. If
extract file has 10 columns, the upload file should also consist of 10 data columns) of the
DATA COLUMNS (not the contents of each column). If this does not tally with the
prescribed count, the system will reject the entire upload file. This will APPLY to both
Courier Confirmation and Transmittal Report
5. System validation on the number of records in the Staging repository versus number of
records uploaded. Validation regarding the total number of records in the raw file versus
those that have been uploaded to the Staging repository. Raw file refers to the contents of
the excel/upload file that have been uploaded by the user. These will be compared to the
contents of the Staging repository to ensure that the data (after undergoing data
management procedure (e.g. concatenate)) have been completely accounted for. To
illustrate:
UPLOAD FILE COUNT
200
300
100
STAGING COUNT
200
150
120
ACTION
Upload
Reject
Reject
In the preceding example, the second and third files were rejected because there was a
discrepancy in the total number of records between the raw file and the record count in the
Staging repository.
6. System checking on the readability of the data. The system will validate the readability of
the data below before these are uploaded to the Staging repository. Please note that not
all of the data columns in the upload were included in the list below because some of
these are no longer feasible and practical to undergo validation (e.g. Reason for
unsuccessful delivery a free text field that may contain any value)
BDOI Module
Courier Company
Areas
Assureds Name
Status
Recipient
Relationship
Date Received
REMARKS
Data will be saved in the system
Data will be used a unique reference
Page 16 of 30

Version 0.01
TRANSMITTAL REPORT
BDOI Module
Date Sent to Client
Date Received Feedback from Insurer
Mode of Transmittal
TAT

Data will be used a unique reference
To illustrate:
DATA
DESCRIPTION
3/12/2015
45670A123
VALIDATION
Readable
Non-readable
7. System checking on the contents of the upload file. The system will validate the following
entries prior to uploading in the broker system.
REMARKS
BDOI Module
There should be no NULL values
Courier Company
Mailing Address
Address
Areas
Assureds Name
In the case of the Transmittal Report, the system will NOT check for NULL values because
as it will be explained in the succeeding section, the completeness of the data fields of the
upload file will be the basis of the system to save the contents to the Pipeline database.
2.2.2 UI Wireframe
DATA UPLOADING MENU
Page 17 of 30

Version 0.01
DATA UPLOADING WINDOW

DATA UPLOADING MENU
DATA ELEMENT
BEHAVIOR
Executable
button
Transmittal Report
Executable
button
FORMAT
RANGE OF VALUES
REMARKS
Directs the user to
the DATA
UPLOADING
WINDOW
Directs the user to
the DATA
UPLOADING
WINDOW
Page 18 of 30

Version 0.01
DATA UPLOADING WINDOW

DATA ELEMENT
BEHAVIOR
File
Display
Location
Display
Select
Check box
Select All
Check box
Upload
Executable
button
Close
Executable
button
FORMAT
RANGE OF VALUES
REMARKS
Shows file for
uploading per
product type.
Shows location of
files for uploading.
If checked,
includes the file for
uploading.
If checked, selects
all file for
uploading. If
unchecked,
deselects all data
for uploading.
Uploads the file
selected by the
user to the system.
Closes the DATA
UPLOADING
WINDOW

N/A
Page 19 of 30

Version 0.01

ITEM #
BRM-UP02-RID2-001
BRM-UP02-RID2-002
BR REQUIREMENTS
FEATURES
The
system
should
automatically show or prompt
the user regarding files to be
uploaded.
The system should be able to
validate if the upload file is valid
for uploading to the Staging
repository.
System facility to detect and

prompt the user due for uploading
based on the predefined location in
the system.
System facility to check if:
o The format and contents
conforms to the system
requirements
o The upload file has a
corresponding extract file
through the header code
validation (applies only to
Courier Confirmation).
2.3 RID 3 Uploading of Data from Staging to Pipeline

This function provides a facility in the system that will upload the COURIER CONFIRMATION and/or
TRANSMITTAL REPORT. This stage presumes that the file have already confirmed to be valid for
uploading based on the validation procedure and criteria discussed in the preceding section.
2.3.1 Features
1. System facility to upload files. The following data from the courier confirmation and
transmittal report upload file will be compared and matched if (pre-maintained) in the
system. Otherwise, the record with non-existing values will be rejected by the system.
COURIER CONFIRMATION/
TRANSMITTAL REPORT
BDOI Module
Courier Company
Status
Relationship
REMARKS
Initial/possible values are: Quotation, Proposal,
Renewal, Placement, Booking and Submitted.
This should exist in the Pipeline
This should exist in the Pipeline
All courier company data defined in the system
Initial/ possible values are: D = Delivered, PD =
Pending Delivery, RTS = Return To Sender
Initial/possible values are: Assured, Spouse,
Secretary, Appointed Contact Person,
Son/Daughter, Father/Mother, House helper,
Guard, Relative and Other Free Text
Page 20 of 30

Version 0.01
After checking the above values, the system will validate if ALL the data columns listed
below have contents. Otherwise, the system will NOT upload the record to the Pipeline.
STATUS
Status
Recipient
Relationship
With contents
With contents
With contents
Date Received
With contents
Reason for unsuccessful delivery

Receipt Reference Number
With contents
With contents
TRANSMITTAL REPORT
STATUS
BDOI Module
Slip
With contents
With contents
With contents

Date Sent to Client
Date Received Feedback from
Insurer
Mode of Transmittal
With contents
With contents
With contents

Name of Receiver
With contents
With contents
With contents

TAT
With contents
With contents
With contents
With contents
With contents
REMARKS
Validation will NOT apply if

Status = RTS (Return to
Sender) and PD (Pending
Delivery)
Delivery)
Delivery)
REMARKS
This should exist in the system
Values will depend on the
BDOI module.
Initial/ possible values are:

Email, Courier, Fax, via Bank
AO or BDO Branch.
Free text
Initial/possible values are:
Assured, Spouse, Secretary,
Appointed Contact Person,
Son/Daughter, Father/Mother,
House helper, Guard, Relative
and/or Other Free Text.
Page 21 of 30

Version 0.01
If the ALL of the above conditions are present, the system will upload the information to the
broker system. The data from the upload file will be uploaded based on the Account
Reference Number.
In the uploading the contents of the upload file to the target data fields that have contents,
below will be the procedure:
FILE
PROCEDURE
o The system will validate if the Account Reference Number of

the upload file is the same with the Account Reference
Number of the target data fields. If yes, the system will upload
the data. Otherwise, the system will generate an exception
report for the record;
o The system will always overwrite the contents of the target
data fields in correlation to the provision mentioned in the
section 2.1.1.3. 2.2.14 and the validation procedure mentioned
in the same section. Below is an illustrative example:
Scenario: User extracts and uploads data. Previously
uploaded will be superseded by a recent upload file)
Transmittal Report
o In January 2015, user A extracts data (template);

o User A sends data (template) to insurer;
o Insurer fills out template and sends accomplished
template to user A;
o Use A uploads data;
o In February 2015, user A extracts again the same
record for confirmation of the Insurer. Reconfirmation
from the insurer is required is the information
previously given is preliminary and not yet final (e.g.
Return to Sender, Pending Delivery, etc.)
o If user A uploads again the same information, the
system will overwrite contents of the target data
fields to accommodate the recent data.
o The system will validate if the Account Reference Number of
the upload file is the same with the Account Reference
Number of the target data fields. If yes, the system will upload
the data. Otherwise, the system will generate an exception
report for the record;
o The system will always overwrite the contents of the target
data fields subject to the validation mentioned in section
2.2.1.4 and preceding paragraph of this same section.
2. System generation of exception report. In cases that the unique reference data in the
upload file does not match the record in the Pipeline, an exception report will be generated
by the system. Below is the list of reports specification:
Page 22 of 30

Version 0.01
SPECIFICATION
Data columns
Contents
Manner of uploading
Format
Filename
REMARKS
The same data columns of the upload files, Courier
Confirmation and Transmittal Report.
The same contents of the upload file except those data
columns listed in section 2.3.1.1 (both Courier Confirmation
and Transmittal Report). Records that will be included in
the exception report are those findings listed in section
2.3.1.1 and the Account Reference Number indicated in the
upload file does not match the account number of those
that have been previously uploaded or those with existing
values. For those that have been uploaded, these columns
will have NO values signifying to the user that there is no
need to upload again the values previously indicated.
The user will use the same upload file (containing same
header code and record count. This presupposes that the
same extract file will be used. The contents of the
exception report file will undergo the same upload
validation procedure mentioned in this document.
Excel file
The system will automatically assign a filename (XYZAB)
where X = CC (Couriers Confirmation) or TR (Transmittal
Report), Y = Date (DD/MM/YYYYY format), Z = Timestamp
(HH:MM:SS format), A = E (Exception) and B =count from
01 to 99.
The exception report will be saved in:
Insurers Confirmation = \\BDOI\Exception\Courier
Confirmation
Transaction Diary = \\BDOI\Exception\Transmittal Report
When the user uploads this file, he will apply the prescribed
naming convention and file location as discussed in section
2.2.1.2 of this document.
3. System procedure in uploading the contents of the upload file. Below is a summary of
procedure the will be performed by the system before it uploads the contents.
PROCESS
The system will prompt files for uploading
based on the filename and location.
The system will validate the upload based
on the criteria mentioned in sections 2.2
and 2.3.
The system will upload the contents of the
upload file to the target destination.
OBJECTIVE
To ensure that only those files intended to be
uploaded will be prompted to the user in the
upload module.
To ensure that the upload file is based on the
prescribed system format and requirements.
To remove the task of manually encoding
each information to the Pipeline.
o Courier Confirmation = Transmittal

Facility
o Transmittal Report = Transmittal
Facility
Page 23 of 30

Version 0.01
4. System capability to generate message regarding status of the uploading. The user will be
prompted of the following system message depending on the outcome of the uploading
process:
UPLOAD STATUS
Successful
Unsuccessful (entire file

was rejected by the
system)
With Exceptions (File

was accepted by the
system. However, the
contents were partially
uploaded. Others were
not uploaded due to
errors detected by the
system).
CONTENTS
o File uploaded
o Status of the
upload;
o Number of
records
uploaded
o Filename;
o Reason/s
for
the
unsuccessful
uploading (e.g.
incorrect
header code,
incomplete
data
column,
incomplete
record count,
duplicate/null
account
reference
number,
null
user Id.)
PROPOSED MESSAGE CONTENTS

200 records from CC0116201501 have
been successfully uploaded to the
system.*
o Filename;
o Number of
record
uploaded;
o Number of
records that
were not
uploaded;
o Exceptions in
the upload file
(e.g. Required
field has no
value or Value
is not existing
in the system)
100 records from CC0116201501 were

successfully uploaded to the system. 100
were not uploaded due to non-existing
Account
Reference
Number,
Relationship, Mode of Transmittal) in the
broker system. Exception report was
generated
and
saved
to
\\BDOI\Exception\Courier Confirmation *
File CC0116201501 cannot be uploaded

to the system due to incorrect header
code.*
Page 24 of 30

Version 0.01
* - Message will vary depending on the outcome of the upload process.

5. System display of history of uploaded files. User will be able to VIEW records of previous
files that have been uploaded to the system. Below are the proposed parameter and data
columns that will be available to the user.
DATA
Parameter
Data columns
Format
DESCRIPTION
o By user
o Month
o Year
o Date (uploaded) From
o Date (uploaded) To
o Filename
o Date uploaded
o Uploaded by
o Total number of record
Open office or excel
Page 25 of 30

Version 0.01
2.3.2 UI Wireframe
DATA UPLOADING MESSAGE WINDOW
TRANSMITTAL FACILITY
Page 26 of 30

Version 0.01
VIEW UPLOADED FILES MENU
VIEW UPLOADED FILES SCREEN
Page 27 of 30

Version 0.01

DATA UPLOADING CONFIRMATION MESSAGE
DATA ELEMENT
BEHAVIOR
Message
Display
Closes
Executable
button
FORMAT
RANGE OF
VALUES
REMARKS
Closes DATA
UPLOADING
CONFIRMATION
MESSAGE
VIEW UPLOADED FILES MENU
Page 28 of 30

Version 0.01
DATA ELEMENT
View uploaded files
BEHAVIOR
FORMAT
RANGE OF
VALUES
Executable
button
REMARKS
Directs the user to the
VIEW UPLOADED
FILES SCREEN
VIEW UPLOADED FILES SCREEN

DATA ELEMENT
BEHAVIOR
FORMAT
RANGE OF
VALUES
Per user
All user
User
Dropdown
Month
Dropdown
January to
December
Year
Dropdown
Year (e.g. 2015,

2016, 2017, etc.)
Date (uploaded)
From
Date (uploaded) To
Data entry
MM/DD/YYYY
Data entry
MM/DD/YYYY
Clear All
Executable
button
View
Executable
button
Close
Executable
button
REMARKS
Shows users that
have access to
upload files.
Limited to one
month per viewing
Limited to one year
Clears parameters
indicated by the
user.
Display data based
on parameters
defined by the
user.
Closes the VIEW
UPLOAD FILES
SCREEN.

Refer to Annex 1 and Annex 2 for the upload file of Courier Confirmation and Transmittal Report
respectively.

ITEM #
BRM-UP02-RID3-001
BR REQUIREMENTS
FEATURES
User should be able to upload

the following to the broker
Facility to allow the user to upload

the following to the broker system:
Page 29 of 30

Version 0.01
BRM-UP02-RID3-002
BRM-UP02-RID3-003
BRM-UP02-RID3-004
system:
o Courier Confirmation
o Transmittal Report
The system should be able to
match and validate target data
fields versus source data fields
in the upload file and broker
system respectively.
The user should be able to
upload
records
in
the
exception report that have
been corrected.
User should be able to view
files that have been uploaded
to the system.
o
o
Transmittal Report
System facility to match and

validate target data fields versus
source data fields in the upload file.
System facility to allow the user to
upload corrected upload file.
Facility to allow the user to view
files that have been uploaded to
the system.
Page 30 of 30

RSD All Market Segments - Courier Report and Transmittal Slip - v3

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RSD All Market Segments - Courier Report and Transmittal Slip - v3

Загружено:

Авторское право:

Доступные форматы

BDO Insurance Brokers, Inc.

Requirements Specification Document

January 28, 2015

Business Requirement Pipeline Management

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

1. Process Schematic / Process Flow............................................................................................... 4

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

1. Process Schematic / Process Flow

Fills out values

UPLOADING OF DATA TO STAGING REPOSITORY

Checks and validates file

Sends extract file

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

UPLOADING OF FILE FROM STAGING REPOSITORY TO PIPELINE

Generates exception file

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Delivered, Pending delivery or

Name of the person who received

Date the letter was received

System validation to extract information for confirmation. In order for a record to be

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Valid. Header code and number of records

Whether extraction was successful or failed;

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

DATA EXTRACTION PARAMETERS

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

DATA EXTRACTION CONFIRMATION MESSAGE

2.1.3 Inputs and Outputs

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

DATA EXTRACTION PARAMETERS

Area will be based

DATA EXTRACTION CONFIRMATION MESSAGE

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

2.1.4 Reports Specification

2.1.5 Business Requirements Mapping

User should be able to extract

User should be able to generate

System facility to allow the user to

2.2 RID 2 Uploading of Data to Staging Repository

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

\\BDOI\For Uploading\Transmittal Report

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Data will be saved in the system

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)