INFORMATION SYSTEMS

FUNCTIONAL SPECIFICATION

Bill payment Remittance System- (BRS)

Document: DA-FS-BRS-020404 Version: 1.2 Date: April 2, 2004

Table of Contents
INTRODUCTION....................................................................................................................................................................3 CHANGE RECORD..............................................................................................................................................3 ...................................................................................................................................................................................................3 .....................................................................................................................................................................3 SYSTEM ARCHITECTURE..................................................................................................................................................4 DATABASE DESIGN..............................................................................................................................................................7 TABLES AND FIELDS.........................................................................................................................................8 DIAGRAM OF RELATIONSHIPS............................................................................................................................11 APPLICATION DESIGN......................................................................................................................................................12 OVERALL PROGRAM FLOW................................................................................................................................12 GUI (GRAPHICAL USER INTERFACE) DESIGN.....................................................................................................13 Main Process Screen........................................................................................................................................................13 Processing Options Screen...............................................................................................................................................14 Merchant Settings Screen.................................................................................................................................................15 Reports/Printers Options Screen......................................................................................................................................16

61610255.doc

Page 2 of 16

June 26, 2011

INTRODUCTION
The ATM End of Day system (ATM EOD) is an application built in the mid 1990s running on a Windows NT workstation using Microsoft Access as the programming language. One of the functions of the ATM EOD application is to collect payments made by customers to Bank credit cards or local merchants from the ATM, Telephone and Internet Banking delivery channels, and send remittances to those merchants. As part of the Alliance Programme ATM/POS/TB Interfaces Project, this functionality is to be replaced with a new Bill Payment Remittance System (a.k.a. BRS) that will be built using software and hardware technology that is in line with the Banks technology road map. At a scheduled time each business day, BRS will accept an extract file of all payments authorized by Bankmaster and produce the remittances to be sent to each merchant or institution. These remittances can be in the form of a report delivered via email or fax, or by a file delivered via email or transmitted over the internet, or any combination thereof. The remittances will be prepared for FDR (Bank credit card payments), Bank of Bermuda and Capital G (Off-us payments/transfers), American Express (Amex payments) and various local merchants that we have contracts to accept payments for.

Change Record
Version 1.0 1.1 1.2 Change Initial Version with DB Design Added GUI Design Updated GUI Design Date March 19th, 2004 March 26th, 2004 April 2, 2004

61610255.doc

Page 3 of 16

June 26, 2011

SYSTEM ARCHITECTURE
During the design stage, it has been agreed that: 1. 2. BRS will communicate with BANKMASTER by the way of accepting the daily import file from it and than processing that file (BANKMASTER will send this file every afternoon Phase II) Current ATM_EOD will be modified to provide this very same import file in place of BANKMASTER, which will not be functional yet at a time this application is ready (Phase I). This will allow BRS to get implemented well before BANKMASTER is in place to start sending files. BRS will be developed as a .NET solution (VS.NET Integrated Development Environment will be used for the purposes of development, .NET Framework 1.0 will be installed on the production server) It is envisioned to be a 2-tier system, having the front end developed in VB.NET and the database developed within MS SQL Server 2000 The front end will perform an import function, produce output files, created and send merchant remittance information and provide maintenance tools. The database side will include several look-up tables, accommodate import data and store it for at least three months and include all the business logic (mostly through stored procedures) BRS application will be installed on BRBNTAPP02 server and the database will reside on BRBNTSQL08. The development and test environments will reside at the same server: BDSQLTEST BRS System will communicate with several different key elements, as shown in the Slide 1 (System Architecture) BANKMASTER from where the import file will come daily in a final Phase II Current ATM_EOD which will provide an import file on the Phase I Network server for data backup storage Several different printers, mostly located in Card Services Department Merchants Fax machines, E-Mail servers and FTP servers

3. 4. 5. 6. 7. 8. 9.

61610255.doc

Page 4 of 16

June 26, 2011

BANKMASTER

Phase II

Phase I

INPUT FILE
ATM_EOD (Current)

BRS (Bill Remittance System)

E-Mail

Printer(s) FAX CARD SERVICES Network Storage Drive

Slide 1 - System Architecture

BACKUP
61610255.doc

FTP Transfer

Page 5 of 16

June 26, 2011

MERCHANTS

61610255.doc

Page 6 of 16

June 26, 2011

DATABASE DESIGN
Production Server: BRBNTSQL08 Test Server: BDSQLTEST Database Name: BillRemittSystem

CONSIDERATIONS: The database has been designed in a manner to allow a maximum flexibility in terms of Merchants having clear choices on how do they want their remittance info presented and which mean of communication they prefer. Also, another major aspect in this design stage was our attempt to design a user friendly system, having in mind that there is a good potential this app will be used by Operations people to maintain all the merchants information and some other system resources information as well. All relevant static, service type of information will be stored in look-up tables. Since this is a 2-tier system, all of the business logic will reside within stored procedures. Hard-coded information shall be avoided by all means. Comparing to the current ATM_EOD system, BRS system will allow merchants to choose which types of files they would like receive and how would they like them to be delivered. Previously, only data files could have been ftp-ed and only reports e-mailed. Every request which differed from this rule, had to be handled in a way of hard-coding. In addition, each merchant will be able to specify multiple fax numbers and multiple ftp sites where they want to receive their remittance info. Another improvement in this new system will be in the way reports and printers are handled. Each report will have a printer associated with it and the system will not keep changing the default printer on the server itself, which proved inefficient in the current ATM_EOD. It is envisioned that all the different formats of data files will also be stored in this database to allow easy modification and addition. Setup table will contain all the system resources and merchant unrelated information. All the data from import files will be stored in the Transaction table and will be kept for at least three (3) months. A Clean-up routine will be developed to delete the data older than that. If this timeframe proves to be insufficient, it will be extended. To accomplish that, another table, for statistic and historic purposes might be introduced at later date.

61610255.doc

Page 7 of 16

June 26, 2011

Tables And Fields

[Account_Type] ( [Account_Type] [char] (2) [Accont_Type_Description] [varchar] (50) [EMail_Info] ( [ID] [int] IDENTITY (1, 1) [Merchant_ID] [int] [Active] [char] (1) [EMail_To] [varchar] (50) [EMail_CC] [varchar] (50) [File_Type] [int] [File_Zipped] [char] (1) [File_PwdProtected] [char] (1) [File_Pwd] [varchar] (12) [SendIfNoPmts] [char] (1) [User_ID] [char] (12) [LastChangeMade] [datetime] [Fax_Info] ( [ID] [int] [Merchant_ID] [int] [Active] [char] (1) [Fax_Number] [varchar] (12) [Attention] [varchar] (30) [SendIfNoPmts] [char] (1) [User_ID] [char] (12) [LastChangeMade] [datetime] [FTP_Info] ( [ID] [int] [Merchant_ID] [int] [Active] [char] (1) [File_Type] [int] [FTP_Address] [varchar] (30) [FTP_ID] [varchar] (30) [FTP_Pwd] [varchar] (30) [FTP_Directory] [varchar] (50) [User_ID] [char] (12) [LastChangeMade] [datetime] [Merchant] ( [Merchant_ID] [int] IDENTITY (1, 1) [Merchant_Code] [char] (3) [Merchant_Name] [varchar] (50) [Merchant_Active] [char] (1) [Fee_Amount] [money] [Fee_Account] [char] (30) [Fee_StartDate] [char] (10) [Report_Name] [char] (30) [DataFile_Name] [char] (10) [File_Counter] [int] [LastChange_User_ID] [char] (12) [LastChange_Date] [datetime]
61610255.doc Page 8 of 16 June 26, 2011

[Monthly_Stats] ( [Merchant_ID] [int] [MonthOfDate] [char] (8) [Account_Type] [char] (2) [Transaction_Number] [int] [Transaction_Amount] [money] [FeeAmount] [money] [Output_File_Type] ( [File_Type] [int] [Type_Description] [varchar] (50) [Printer] ( [ID] [int] [Printer_Name] [varchar] (12) [Printer_NetWorkName] [varchar] (50) [Printer_Primary] [char] (1) [Printer_Location] [varchar] (50) [Report] ( [ID] [int] NOT NULL , [Report_Name] [varchar] (30) [Report_Print] [char] (1) [Default_Printer] [int] NOT NULL , [EMail_Active] [char] (1) [EMail_ID] [int] [Fax_Active] [char] (1) [Fax_ID] [int] [SetUp] ( [Input_Dir] [varchar] (50) [Input_File] [varchar] (12) [Output_Dir] [varchar] (50) [Reports_Dir] [varchar] (50) [Backup_Dir] [varchar] (50) [Last_Import_Date] [datetime] [EMail_ErrorMsg] [varchar] (50) [Fax_Enabled] [char] (1) [EMail_Enabled] [char] (1) [FTP_Enabled] [char] (1) [DataBackup_Enabled] [char] [PrintReport_Enabled] [char] (1) [PrintPreview_Enabled] [char] (1) [Source] ( [Source_Type] [char] (3) [Source_Description] [varchar] (50) [Transaction] ( [Transaction_ID] [bigint] [CIF_Number] [char] (10) [Customer_Name] [varchar] (50) [Merchant_ID] [int] [Source_Type] [char] (3) [Account_Type] [char] (2) [AccountNumber] [varchar] (16) [Transaction_Amount] [money]
61610255.doc Page 9 of 16 June 26, 2011

[Transaction_Currency] [char] (10) [Transaction_Date] [datetime] [Transaction_Time] [datetime] [Transaction_Description] [varchar] (50) [Source_Ref_Num] [char] (12) [Load_Date] [datetime] [Load_Time] [datetime] [User_ID] [char] (12) [Transaction_Rejected] ( [Transaction_ID] [bigint] [CIF_Number] [char] (10) [Customer_Name] [varchar] (50) [Merchant_ID] [int] [Source_ID] [int] [Transaction_Type] [char] (10) [AccountNumber] [varchar] (16 [Transaction_Amount] [money] NOT NULL , [Transaction_Currency] [char] (10) [Transaction_Date] [datetime] [Transaction_Time] [datetime] [Transaction_Description] [varchar] (50) [Source_Ref_Num] [char] (12) [Load_Date] [datetime] [Load_Time] [datetime] [User_ID] [char] (12)

61610255.doc

Page 10 of 16

June 26, 2011

Diagram of Relationships
The diagram of tables and their relationships is shown below.

61610255.doc

Page 11 of 16

June 26, 2011

APPLICATION DESIGN
Overall program flow
BRS (Bil Remittance Info) SERVICE

File Monitoring Object

Is Import File Present

EX IT

Error Handling

File Already Imported

N
IM O P RT VERIFICAT ION P CE S RO S

EX IT

Error Handling

Import Reports Creation

Import Verification S cce e u dd

Y
IM O P RT P CE S RO S

Store Import Data

CREATE FILES FILE BACKUP SEND FILES BACK-UP FILES OUTPUT FILES

CRE T AE

RE O S P RT S ND E RE O S P RT B CKUP A RE O S P RT

O P UT UT

RE O S P RT

O P UT UT M RCHA S E NT REMITTANCE INFO E T CT XRA REMITTANCE INFO CRE T AE RE IT A M T NCE FILES S ND E RE IT A M T NCE INFO B CK A UP RE IT A M T NCE

61610255.doc

Page 12 of 16

June 26, 2011

GUI (Graphical User Interface) Design Main Process Screen

61610255.doc

Page 13 of 16

June 26, 2011

Processing Options Screen

61610255.doc

Page 14 of 16

June 26, 2011

Merchant Settings Screen

61610255.doc

Page 15 of 16

June 26, 2011

Reports/Printers Options Screen

61610255.doc

Page 16 of 16

June 26, 2011