Iswitch Payroll System: Document Revision 1.2

iSwitch®
Payroll System
1.0
CR
for
RCBC
Document Revision 1.2
Batch Upload for RCBC
Confidentiality Statement
Copyright © 2000-2010 Interblocks Ltd. All Rights Reserved. No part of this publication may be
reproduced or transmitted in any form or by any means, mechanical, electronic, photocopying,
recording, or otherwise, without prior written permission of Interblocks Ltd. The Interblocks logo
is a trademark of Interblocks Ltd.
Document Details
Document ID : RCB-IC-14_BatchUpload_r1.2
Document Revision: 1.2
Revision date: 4th January 2010
Author: Rajeeva Nonis
Reviewed by: Anupama Weerabahu
Release date: 4th January 2010
Interblocks Limited
240, High Level Road
Colombo 6
Sri Lanka
Telephone: +94 11 5415415
Facsimile : +94 11 4513386
www.interblocks.com
Table of Contents
Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 2 of 46

Document Version 1.2 4th January 2010
1. INTRODUCTION.............................................................................................................................. 6
1.1 PURPOSE.............................................................................................................................................6
1.2 INTENDED AUDIENCE.............................................................................................................................6
1.3 SCOPE OF THE DOCUMENT......................................................................................................................6
1.4 DOCUMENT CONVENTIONS.....................................................................................................................6
1.5 REFERENCES.........................................................................................................................................6
1.6 OTHER RELATED DOCUMENTS..................................................................................................................7
1.7 TERMS, ABBREVIATIONS AND CONVENTIONS..............................................................................................7
2. PRODUCT SCOPE............................................................................................................................ 8
2.1 SOLUTION OVERVIEW............................................................................................................................8

2.2 FUNCTIONAL EXCLUSIONS.......................................................................................................................9
2.3 USER DOCUMENTATION..........................................................................................................................9
2.4 ASSUMPTIONS AND DEPENDENCIES........................................................................................................10
3. PAYROLL FILE CAPTURE................................................................................................................ 11
3.1 REQUIREMENT – CAPTURE PAYROLL FILE................................................................................................11

3.1.1 Description.............................................................................................................................11
3.1.2 Stimulus and Response...........................................................................................................11
3.1.3 Functional Requirement – Description...................................................................................11
3.1.4 Exclusions...............................................................................................................................12
3.2 REQUIREMENT – VIEW PAYROLL FILE STATUS..........................................................................................13
3.2.1 Description.............................................................................................................................13
3.2.4 Exclusions...............................................................................................................................13
3.3 REQUIREMENT – ICARD OLTP SERVER RESPONSE.....................................................................................14
3.3.1 Description.............................................................................................................................14
3.3.4 Exclusions...............................................................................................................................14
3.4 REQUIREMENT – VIEW ICARD OLTP SERVER STATUS................................................................................15
3.4.1 Description.............................................................................................................................15
3.4.4 Exclusions...............................................................................................................................15
4. EMAIL ACCOUNT ADDITION.......................................................................................................... 16

4.1 ADD EMAIL ACCOUNT..........................................................................................................................16

4.1.1 Description.............................................................................................................................16
4.1.4 Exclusions...............................................................................................................................16
4.2 DELETE EMAIL ACCOUNT......................................................................................................................17
4.2.1 Description.............................................................................................................................17
4.2.4 Exclusions...............................................................................................................................17
4.3 VIEW EMAIL ACCOUNT.........................................................................................................................18
4.3.1 Description.............................................................................................................................18
4.3.4 Exclusions...............................................................................................................................18
5. REQUIREMENT – REPORTS............................................................................................................ 19
5.1 BRANCH ACCOUNT DAILY TRANSACTION JOURNAL....................................................................................20

5.1.1 Description.............................................................................................................................20
5.1.2 Selection Criteria - Input.........................................................................................................20
5.1.3 Report Field Definitions - Output...........................................................................................21
5.2 BRANCH POSTED ONLINE TRANSACTIONS (SERVICING BRANCH)..................................................................24
5.2.1 Description.............................................................................................................................24
5.3 ACCEPTED AND REJECTED ICARD PAYROLL TRANSACTIONS.........................................................................28
5.3.1 Description.............................................................................................................................28
5.4 ACCOUNTS PAYABLE BALANCES PER BRANCH..........................................................................................31
5.4.1 Description.............................................................................................................................31
5.5 ICARD PAYROLL UPLOAD POSTED TRANSACTIONS (SERVICING BRANCH).......................................................33
5.5.1 Description.............................................................................................................................33
5.6 ICARD PAYROLL UPLOAD POSTED TRANSACTIONS (MAINTAINING BRANCH)..................................................36

5.6.1 Description.............................................................................................................................36
5.7 ICARD – GL INTERFACE SUMMARY.........................................................................................................38
5.7.1 Description.............................................................................................................................38
5.8 REVERSAL OF BATCH CREDIT TRANSACTION REPORT...................................................................................40
5.8.1 Description.............................................................................................................................40
5.8.2 Selection Criteria – Input........................................................................................................40
6. EXTERNAL INTERFACE REQUIREMENTS......................................................................................... 42
6.1 USER INTERFACES................................................................................................................................42

6.2 HARDWARE INTERFACES.......................................................................................................................42
6.3 SOFTWARE INTERFACES........................................................................................................................42
6.4 COMMUNICATION INTERFACES..............................................................................................................42
7. NON FUNCTIONAL REQUIREMENTS.............................................................................................. 43
7.1 PERFORMANCE REQUIREMENTS..............................................................................................................43

7.2 SAFETY REQUIREMENTS........................................................................................................................43
7.3 SECURITY REQUIREMENTS.....................................................................................................................43
7.4 SOFTWARE QUALITY ATTRIBUTES............................................................................................................43
7.5 LOOK AND FEEL / USABILITY REQUIREMENTS...........................................................................................43
7.6 MAINTAINABILITY AND PORTABILITY REQUIREMENTS..................................................................................43
7.7 LEGAL, CULTURAL AND POLITICAL REQUIREMENTS.....................................................................................43
8. APPENDICES................................................................................................................................. 44
8.1 PAYROLL FORMAT...............................................................................................................................44

8.2 EMAIL CONFIRMATION FORMAT............................................................................................................45
9. SIGN-OFF FOR DOCUMENT........................................................................................................... 46
10. DOCUMENT REVISION HISTORY................................................................................................ 47

1. Introduction
1.1 Purpose
This document intends to present a solution for the problem of payroll file processing,
which would also consist of Email confirmation and report generation.
1.2 Intended Audience
The document is intended for the implementation and project teams of RCBC and
Interblocks.
1.3 Scope of the document
Current scope of this document is for payroll file processing, email confirmation and
generation of specific reports.
1.4 Document Conventions
The document is compiled according to the Interblocks standards in developing Software

Requirement Specifications for projects. Each requirement is discussed under four
separate sections:
I. Description: a brief description of the requirement.

II. Stimulus and Response: the activities which trigger the need and the response from
the system.
III. Functional Requirement: the detailed functional requirement.
IV. Exclusions: any functional exclusion is documented here.
1.5 References
N/A

1.6 Other related documents
CRF-Batch Upload Mode.doc
1.7 Terms, Abbreviations and Conventions
CR – Change request
Servicing Bank – Branch who initiated the transactions
PBS – Platform Banking Systems

This would be the RCBC system which is deployed in different branches.
FTP – File Transfer Protocol
Up loader – A program used to get and read the payroll files from the FTP folder
CA/SA – Current/ Savings
RC – Regional Centre

2. Product Scope
2.1 Solution Overview
Figure 2-1: Solutions overview diagram

1. RCBC Branch will upload the Payroll File in Platform Banking System (PBS).
[Payroll file format is given in Appendix 8.1]
2. PBS will send Debit request to the banks backend. Wait for the response, if
successful, then the Payroll File will be put by PBS to a known FTP Folder. If rejected,
then it will provide necessary error message to the Branch.
3. The Up loader program then will pick up the Payroll File uploaded by PBS.
4. The Up loader program then will process the payroll file one by one by sending
credit transaction request to iSwitch (iCard OLTP Server).
5. After the processing, iCard system will automatically send e-mail notification to
branches of all successful and rejected credits. All relevant online and offline reports
would be generated.
a. Processing Time,
o RCBC processes 1,400 Payroll Files per payday
o 1 Payroll File contains 2,000 records
o Acceptable transaction volume for the iCard OLTP Server to be 10
transactions per second.
o Scheduled execution/frequency of payroll credits run in a day would
be maintained in the system for 5 times a day, which would be at
9am, 11am, 1pm, 3pm and 5.30pm.
o Up loader must handle sending of multiple requests [maximum of 20] to the
OLTP server.
2.2 Functional Exclusions
N/A
2.3 User documentation
1. A copy of the SRS for future reference.
2.4 Assumptions and Dependencies
None

3. Payroll File Capture
3.1 Requirement – Capture Payroll File
3.1.1 Description
Use this function to capture the required payroll file.
3.1.2 Stimulus and Response

Once the Payroll file for the day has been added to the PBS, the up loader program will
capture the file for the respective day and process the file. The successfully processed
transaction details would be sent to iCard.
3.1.3 Functional Requirement – Description
1. Scheduled execution will happen 5 times a day at 9am, 11am, 1pm, 3 pm and 5.30 pm
to check whether a file has been added to the FTP INBOX folder, added files would
be validated to check if it matches with the current date, if it does the data would be
inserted into a table.
[Default upload file format name would be “TBBBCCCDD.ixN”]
2. Also if the payroll file name reads as “ TBBBCCCDD-00.ixN” it will skip the
validation checks [Forced uploading] and will be moved to outbox.
3. After reading, up loader will move the file, from INBOX FTP folder, into OUTBOX
FTP folder for all successfully read files.
4. In case, file is corrupted, from the INBOX FTP folder, up loader should move it to
REJECTED FTP folder.
5. Up loader will automatically send a file which contains the corrupted files name and
corresponding details to the uploading branch, further the same file will be stored in
the ‘Rejected’ section of the FTP folder.
6. In case, certain records in the file are not readable, the up loader will process the
successful transactions and the unprocessed transactions would be flagged and
written to a separate file containing the default file name for the day with the
addition of ‘unprocessed’. [E.g. - TBBBCCCDD_Unprocessed.ixN]

7. Unprocessed reasons would include;

Branch Crediting - unprocessed due to ‘Closed account’, ‘Invalid account’, ‘Not
found account’, ‘Processed and NOT credited’ and ‘iCMS replied and incomplete’.
Reprocessing - ‘Unreadable file’, ‘Cannot send to iCMS’.
8. A file will be sent to the uploading branch which contains the details of the
unprocessed transactions and the same file will be stored in the ‘Rejected’ section of
the FTP folder.
9. Same payroll file once successfully uploaded will not be accepted by the system on
the same day or on another, unless a Force upload has been initiated.
10. The Up loader program will process the payroll file by sending individual credit
transaction requests to iSwitch (iCard OLTP Server).
[Default upload file format name would be “TBBBCCCDD.ixN”]
3.1.4 Exclusions
None

3.2 Requirement – View Payroll File Status
3.2.1 Description
Use this function to view the status of a required payroll file.

User enters the payroll file name and submits. System would extract the current status of
the payroll file and display.
1. Customer will have to enter the payroll file name in the “File Name” field.
2. Click on the ‘Submit’ button.
3. The current status of the payroll file will be retrieved from the system and would be
displayed.
Statuses would be as below;
 Processed – The payroll file has been successfully processed and sent to
the iCard OLTP server.
 Rejected – The payroll file has not been processed, due to the file being
corrupted.
 Unprocessed – The file contains transactions which were not processed.
 Branch Crediting - unprocessed due to ‘Closed account’, ‘Invalid
account’, ‘Not found account’, ‘Processed and NOT credited’ and ‘iCMS
replied and incomplete’.
 Reprocessing - ‘Unreadable file’, ‘Cannot send to iCMS’.
3.2.4 Exclusions
None

3.3 Requirement – iCard OLTP server response
3.3.1 Description
This function will allow the iCard OLTP server to receive the message sent by the up
loader program which in turn would be processed.

iCard OLTP server receives the request and credits the respective branches. iCard
system will also initiate Email messages for all successful and rejected credits.
1. iCard OLTP server will receive the credit request which in turn would credit the
required amount to the corresponding recipient, which would be the initiating bank.
2. iCard system will trigger a message which in turn will prompt the ‘Lotus Email
server’ to send a confirmation email to the initiating branch for all successful and
rejected credits, the email addresses of the recipients would be extracted from the
system.
3. Aside from e-mail notification, iCard system will create required reports as shown in
Section 5 – Reports.
3.3.4 Exclusions
None

3.4 Requirement – View iCard OLTP server Status
3.4.1 Description
Use this function to view the status of the message sent to the OLTP server.

User enters the payroll file name and submits. System would extract the current status of
each transaction pertaining to the respective payroll file and display.
1. Customer will have to enter the payroll file name in the “File Name” field.
2. Click on the ‘Submit’ button.
3. The current status of the transactions pertaining to the payroll file will be shown.
This would contain the “First Name”, Last Name”, “Branch Name”,” Transaction
status”.
Statuses would be as below;
 iCard received and processed – messages which have been successfully

received by the iCard OLTP server and processed
 Amount Credited – Transactions for which the payroll amount has been
successfully credited.
 Email confirmation Sent – Payroll file transactions for which the Email
confirmation has been sent.
3.4.4 Exclusions
None

4. Email Account Addition
4.1 Add Email Account
4.1.1 Description
Use this function to upload the required Email address to the system.

User enters the required Email address and submits the request; the system passes the
details to the database where the email details would be copied to the database.
1. User enters the “First Name”, “Last Name”, “Branch Name” and the “Email” in the
provided fields.
2. User submits the entered details.
3. System will copy the provided details to the database.
4. A confirmation message would be prompted.
4.1.4 Exclusions
N/A

4.2 Delete Email Account
4.2.1 Description
Use this function to delete the required Email addresses from the system.

User enters required details of the email address to be searched in the search field’s
provided, system extracts the details and displays on the screen. User deletes the email
address; the details of the respective email will be removed from the system.
1. User enters either of the fields “Branch Name”, “Email Address”.

2. Click on the ‘Search’ button.
3. System will extract the details and display.
4. User selects the record and clicks on the ‘Delete’ button.
5. The details of the respective branch will be removed from the system.
4.2.4 Exclusions
None

4.3 View Email Account
4.3.1 Description
Use this function to view all active email addresses in the system

User enters required details of the email address to be searched in the search field’s
provided, system extracts the details and displays on the screen.
1. User enters either of the fields “Branch Name”, “Email Address”.

2. Click on the ‘Search’ button.
3. System will extract the details and display on the screen.
4.3.4 Exclusions
None

5. Requirement – Reports
This function will allow authorised users to view the;
 Branch Accounts Daily Transaction Journal

 Branch Posted Online Transactions
 Accepted and Rejected iCard Payroll Transactions
 Accounts Payable Balances per Branch
 iCard Payroll Upload Posted Transactions (Servicing Branch)
 iCard Payroll Upload Posted Transactions (Maintaining Branch)
 iCard GL interface summary
 Batch credit transaction report

5.1 Branch Account Daily Transaction Journal
5.1.1 Description
This report shall be used by the branch of account to verify transactions posted to all
accounts maintained at the branch.
Every successful transaction shall be posted in this report.
It shall be made available to users online via ICMS > REPORTS> Branch Reports as
printable or downloadable file.
5.1.2 Selection Criteria - Input

Any of the following:
o Transaction Date
o Transaction Type
o Card Number
o Branch Code (for branch 999)
o Retention period : 1 year
o Recipient of report : Branch of Account
o Frequency and schedule of generation : Online, real-time

5.1.3 Report Field Definitions - Output
Field Name Field Description Field Definition
Bank Displays numeric and alpha Get from Bank table. Could be
character of the Bank where 001 : RCBC and 002 : RSB
accounts are maintained.
Currency Displays numeric and alpha Get value from currency table.
character of the accounts’ currency Currently, the Bank only has Php
currency.
Branch Displays numeric and alpha

character of the Branch derived from
the branch ID of the user generating
the report.
Page No Page number of the document
Transaction Date Date when the transactions were In MM/DD/YYYY format

posted on the account
Run Date Date report is generated In MM/DD/YYYY hh:mm:ss
format
Card Number Card number where the transaction In 16-digit numeric format
is posted
Account Number Account reference number attached In 10-digit numeric format
to the card number where
transaction is posted
Account Name Account name of the card number Text format
where transaction is posted
Product ID Product ID corresponding the card Get value from product table.
number
Transaction Code Displays the code of the transaction
TR Time Time when transaction was posted In hh:mm:ss format
Tran Amount Displays amount of the transaction
Type Displays type of transaction May be :

DR for debit transaction
CR for credit transaction

Seq Displays sequence number of the

transaction. Should be unique per
transaction across all channels
Terminal ID Displays the terminal ID where
transaction is initiated
Channel ID Displays the channel where Shall have the following
transaction is initiated. convention
NNNXXX
Where NNN = channel which
can be:
RTR – RCBC Teller
STR – RSB Teller
RTM – RCBC ATM
STM – RSB ATM
BTM – Bancnet ATM
BPS – Bancnet POS
VTM – VISA ATM
VPS – VISA POS
RIB – RCBC Internet Banking
BIB – Bancnet Internet
Banking
MRT – MRT/OMI
ICS – ICARD
XXX = branch code
Summary Displays the summary of Type of transaction shall be

Other Branch transactions posted on branch’ derived from the transaction
accounts but are processed by other code.
branches
Debits Displays summary of debits per type
of transaction
Credits Displays summary of credits per
type of transaction
Count Number of posted transactions 6 digit numeric


5.2 Branch Posted Online Transactions (Servicing Branch)
5.2.1 Description
This report shall be used by the servicing branch for verification of transactions
processed by the branch; this report would only be available to branch 999.
Every successful transaction shall be posted in this report.

o Transaction Date
o Transaction Type
o Card Number
Branch Code (for branch 999)

Retention period: 1 year
Recipient of report: Servicing Branch
Frequency and schedule of generation: Online, real-time

Bank Displays numeric and alpha Get from Bank table. Could be
character of the Bank where 001 : RCBC and 002 : RSB
accounts are maintained.
currency.
Branch Displays numeric and alpha

the report.
Page No Page number of the document In XXX format
Transaction Date Date when transactions were posted In MM/DD/YYYY format

on the account
Run Date Date report is generated In MM/DD/YYYY hh:mm:ss
format
Transaction Code Displays the code of the transaction

sorted according to type of
transaction i.e. Credit then Debit
Tran Amount Displays amount of the transaction
FROM Source Card number or Deposit In 16-digit numeric format for

Card Number Account Number of the posted ICARD accounts
transaction In 10-digit numeric format for
CASA accounts
FROM Displays the branch code of the

Maintaining RC source account derived from the
account number
FROM Product ID corresponding the card Get value from product table.
Product Type number
TO Receiving Card number or Deposit In 16-digit numeric format for
Card Number Account Number of the posted ICARD accounts

transaction In 10-digit numeric format for

CASA accounts
To Displays the branch code of the

Maintaining RC destination account derived from the
account number
To Product ID corresponding the card Get value from product table.
Product Type number
TR Time Time when transaction was posted In hh:mm:ss format
Seq. No. Displays sequence number of the

Terminal ID Displays the terminal ID where
transaction is initiated
Channel ID Displays the channel where Shall have the following
transaction is initiated. convention
NNNXXX
Where NNN = channel which
can be:
RTR – RCBC Teller
STR – RSB Teller
RTM – RCBC ATM
STM – RSB ATM
BTM – Bancnet ATM
BPS – Bancnet POS
VTM – VISA ATM
VPS – VISA POS
RIB – RCBC Internet Banking
BIB – Bancnet Internet
Banking
MRT – MRT/OMI
ICS – ICARD
XXX = branch code
Summary Displays the summary of branch Type of transaction shall be

On-Us Transactions own accounts transactions derived from the transaction

code.
Other Branch Displays the summary of other Type of transaction shall be

Transactions branch transactions processed by the derived from the transaction
servicing branch code.
Debits Displays summary of debits per type

of transaction
Credits Displays summary of credits per
type of transaction

5.3 Accepted and Rejected iCard Payroll Transactions
5.3.1 Description
This report shall be used by the servicing branch for verification of uploaded ICARD
payroll transactions every successful and rejected transaction shall be posted in this
report.

o Filename
o Source Account Number

Recipient of report: Servicing or Uploading Branch
Frequency and schedule of generation: After processing of payroll file
Frequency and schedule of generation: Online, real-time

Filename Icard payroll filename. Derived Text file

from payroll file generated by PBS
during upload.
Source Account CASA account number debited for
funding of payroll
Servicing RC Displays the responsibility center
(RC) of the uploading branch
Terminal ID Displays terminal ID of the PBS
where payroll is uploaded
Transaction Date Date when payroll is uploaded for
posting
List of Posted ICARD Displays all successful payroll
Accounts credits
List of Rejected ICARD Displays all rejected payroll
Accounts transactions
Card Number ICARD card number where payroll 16-digit
credit amount is posted
Depository RC Depository RC corresponding to the
card number. Derived from account
number reference linked to the card
Transaction Amount Payroll amount posted
Seq No. Displays sequence number of the

Time Time when transaction was posted In hh:mm:ss format
Count Number of payroll credit posted
Remarks
Processed by Displays the user ID who uploaded

the ICARD payroll file
Approved By Displays the user ID of branch

officer who approves the iCard

payroll upload

5.4 Accounts Payable Balances Per Branch
5.4.1 Description
This report shall be used by the branch of accounts for verification of card balances
sorted per Accounts Payable (AP) type for the day. Though in batch, data should be
taken from ICARD online transactions and not from EOD file.
Only those card numbers issued by the branch should be listed in this report. Card
numbers should be sorted in ascending order. This report should be made available to
users via ICMS > REPORTS> Branch Reports as printable or downloadable file.

o AP type or <blank> for all
o Transaction Date

Recipient of report: Maintaining Branch
Frequency and schedule of generation: As needed

currency.
Maintaining Branch Displays numeric and alpha

the report.
Page No Page number of the document In XXXXX format

on the account
AP Type/Card Displays the Accounts Payable Type Card Numbers should be in
Numbers and card numbers linked to this AP ascending order
type
Count Total count of linked cards per AP
type
Previous Balance Card ending balance as of previous
day (Day 0). Should have total per
AP
Debit Total amount debited on cash card
account for the day. Should have
total per AP
Credit Total amount credited on cash card
account for the day. Should have
total per AP
Ending Balance Ending card balance for the day.
Should have total per AP
Total AP Balance for Total amount of card balances issued
Branch by the concerned branch.

5.5 iCard Payroll Upload Posted Transactions (Servicing Branch)
5.5.1 Description
This report shall be used by the servicing branch to verify GL posting of uploaded
ICARD payroll transactions per filename.
Report shall only capture successful PAYROLL UPLOAD transactions
Card numbers should be sorted in ascending order. This report should be made available
to users via ICMS > REPORTS> Branch Reports as printable or downloadable file.
Selection criteria for generating this report are:

o Filename
o Transaction Date

Recipient of report: Servicing Branch
Frequency and schedule of generation: A day immediately after batch.


Transaction Date Date when payroll is uploaded for
posting
Filename Icard payroll filename. Derived Text file
from payroll file generated by PBS
during upload.
Source Account CASA account number debited for
funding of payroll
Terminal ID Displays terminal ID of the PBS
where payroll is uploaded
Transaction Code Displays transaction code
DR GL Code Displays the debit GL code of

payroll upload
Debit Amount Displays the amount debited for
certain payroll transaction
CR GL Code Displays the credit GL code of
payroll upload
Credit Amount Displays the amount credited for
Depository RC Depository RC corresponding to the
card number. Derived from account
number reference linked to the card
Transaction Status Displays the transaction status. Status can be :
1. Valid
2. Switch Back-End Time
Out
3. Incomplete

Total Total amount for debit/credit

5.6 iCard Payroll Upload Posted Transactions (Maintaining Branch)
5.6.1 Description
This report shall be used by the maintaining branch to verify GL posting of ICARD
payroll upload transactions credited to accounts of the branch.
Report shall only capture successful PAYROLL UPLOAD CR transactions
Card numbers should be sorted in ascending order. This report should be made available
to users via ICMS > REPORTS> Branch Reports as printable or downloadable file.

o Transaction Date
o Servicing RC

Recipient of report: Maintaining Branch
Frequency and schedule of generation: A day after ICARD payroll is uploaded

Maintaining RC Displays the responsibility center

(RC) of the branch of accounts
Transaction Date Date when payroll credit is posted
Transaction Code Displays transaction code
DR GL Code Displays the debit GL code of

payroll upload
Debit Amount Displays the amount debited for
CR GL Code Displays the credit GL code of
payroll upload
Credit Amount Displays the amount credited for
Transaction Status Displays the transaction status. Status can be :
1. Valid
2. Switch Back-End Time
Out
3. Incomplete
Total Total amount for debit/credit

5.7 iCard – GL Interface Summary
5.7.1 Description
This report shall be used by all branches and head office units to verify GL posting of all
iCard transactions in summarized format per GL account per RC.
GL accounts shall be classified as follows:
CASH
CLEARING ACCTS
SUNDRY DR – INTERFACE
ACCOUNTS PAYABLE
ACCOUNTS RECEIVABLE
RET CHECKS & OTHER CASH ITEMS
OVERAGES
SHORTAGES
CHARGES/FEES
GL codes should be sorted in ascending order per classification. This report should be
made available to users via ICMS > REPORTS> Branch Reports as printable or
downloadable file.

Selection Criteria: Transaction Date

Recipient of report: Branches, ATM Centre, Electronic Banking Support Dept
Frequency and schedule of generation: After batch
character of the accounts’ currency. Currently, the Bank only has Php
currency.
Maintaining Branch Displays numeric and alpha

the report.
on GL accounts
GL Description Displays description of GL account
GL Code Displays the corresponding GL code
Debit Total amount debited from the GL

account
Credit Total amount credited to the GL
account
Total Total debit/credit amount

5.8 Batch Credit transaction report
5.8.1 Description
This report will be a system generated report after the credit transactions have been
processed, which allows the user to view the successfully posted and rejected
transactions.
5.8.2 Selection Criteria – Input
Selection Criteria: Successfully posted and successfully rejected transactions

Recipient of report: Branches
Frequency and schedule of generation: After batch

SUCCESSFULLY POSTED ICARD ACCOUNTS

Depository Transaction
Regular Card Number RC Amount Trace Time Remarks Count
00000 11:41:1
6019-7058-0000-0001 109 15,757.25 1 0 1
00000 11:41:1
6019-7010-0000-0001 109 9,242.75 2 1 1
00000 11:41:1
6019-7010-0000-0002 109 7,400.00 3 2 1
00000 11:41:1
6019-7058-0000-0003 318 41,500.00 7 6 1
00001 11:42:1
4215-8558-0000-0001 322 7,200.00 4 0 1
00001 11:42:1
4215-8558-0000-0002 322 3,500.00 5 1 1
00001 11:42:1
4215-8558-0000-0003 162 8,612.58 6 2 1
00001 11:42:1
4215-8558-0000-0004 249 10,865.22 7 3 1
00001 11:42:1
4215-8558-0000-0005 411 21,347.40 8 4 1
Total Amount & Count of Successful Credits 125,425.20 9
REJECTED CREDITS TO ICARD ACCOUNTS

Depository Transaction Reason of
Regular Card Number RC Amount Trace Time Reject Count
00000 11:41:1
6019-7058-0000-0004 411 50,001.00 8 7 Hot Card 1
00000 11:41:1 Invalid
6019-7010-0000-0005 411 110,000.00 9 8 Number 1
00001 11:41:1
6019-7010-0000-0006 365 37,800.00 0 9 Time out 1
00001 11:41:2
6019-7010-0000-0007 179 41,295.00 1 0 1
00001 11:41:2
6019-7058-0000-0006 523 71,691.12 2 1 1
00001 11:42:1
4215-8558-0000-0006 965 200,000.00 9 5 1
00002 11:42:1
4215-8558-0000-0007 250 91,565.11 0 6 1
Total Amount & Count of Rejected Credits 602,352.23 7

Grand Total 727,777.43 16

Processed by USERID
Approved by USERID
6. External Interface Requirements
6.1 User Interfaces
There will be stand alone interfaces provided for viewing of ‘iCard OLTP server status’,
‘Payroll file status’ and ‘Reports’.
6.2 Hardware Interfaces
None
6.3 Software Interfaces
None
6.4 Communication Interfaces
None
FOR REVERSAL EXIT

7. Non Functional Requirements
7.1 Performance requirements
N/A
7.2 Safety requirements;
1. In order to safeguard the solution we recommend the client to implement a DR

Site for the main application and the database.
7.3 Security requirements
1. All users of this system will need to be authorized using appropriate user
authentication features.
2. After specified number (configurable) of consecutive wrong password tries, the
user will be automatically locked.
7.4 Software quality attributes
1. Both internal QA personnel and client’s audit team will test the solution.
2. The Solution developed will be deemed accepted by client following a
comprehensive UAT.
7.5 Look and Feel / Usability requirements
None
7.6 Maintainability and portability requirements
None
7.7 Legal, Cultural and political requirements
None

8. Appendices
8.1 Payroll Format
The branch code will be used in determining the Source CASA RC.
Current file name convention - TBBBCCCDD.ixN
Where;
T = account type (valid values are S for Savings and C for Current Account)
BBB = branch code
CCC = company code
DD = day of the month
N = sequence of upload (valid values are 1 to 9

8.2 Email Confirmation Format

9. SIGN-OFF for Document

Date: 4th January 2010
We hereby agree to the Terms and Conditions herewith;
RCBC Interblocks
........................ ........................
Lilian Cruz Carlo P Castillejo
Department Head Project Manager
........................ ........................
JohnnA Go Rajeeva Nonis
IT Project Lead Business Analyst
10. Document Revision History

Revision Date Name Reference
Original : Author : According to the new requirements

th
28 July 2010 Rajeeva Nonis corresponding to the payroll system and
1.0
review comments included.
Reviewed : Reviewed :
26th July 2010 Anupama Weerabahu
Original : Author : According to the review comments from

th
5 August 2010 Rajeeva Nonis the bank.
1.1
Original : Author : Additional Reports

th
4 January 2010 Rajeeva Nonis
1.2


Iswitch Payroll System: Document Revision 1.2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Iswitch Payroll System: Document Revision 1.2

Uploaded by

Copyright:

Available Formats

iSwitch®

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 2 of 46

2.1 SOLUTION OVERVIEW............................................................................................................................8

3. PAYROLL FILE CAPTURE................................................................................................................ 11

3.1 REQUIREMENT – CAPTURE PAYROLL FILE................................................................................................11

4. EMAIL ACCOUNT ADDITION.......................................................................................................... 16

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 3 of 46

4.1 ADD EMAIL ACCOUNT..........................................................................................................................16

5.1 BRANCH ACCOUNT DAILY TRANSACTION JOURNAL....................................................................................20

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 4 of 46

6. EXTERNAL INTERFACE REQUIREMENTS......................................................................................... 42

6.1 USER INTERFACES................................................................................................................................42

7. NON FUNCTIONAL REQUIREMENTS.............................................................................................. 43

7.1 PERFORMANCE REQUIREMENTS..............................................................................................................43

8.1 PAYROLL FORMAT...............................................................................................................................44

9. SIGN-OFF FOR DOCUMENT........................................................................................................... 46

10. DOCUMENT REVISION HISTORY................................................................................................ 47

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 5 of 46

1.2 Intended Audience

1.3 Scope of the document

1.4 Document Conventions

The document is compiled according to the Interblocks standards in developing Software

I. Description: a brief description of the requirement.

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 6 of 46

1.6 Other related documents

CRF-Batch Upload Mode.doc

1.7 Terms, Abbreviations and Conventions

Servicing Bank – Branch who initiated the transactions

PBS – Platform Banking Systems

FTP – File Transfer Protocol

CA/SA – Current/ Savings

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 7 of 46

2.1 Solution Overview

Figure 2-1: Solutions overview diagram

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 8 of 46

2.2 Functional Exclusions

2.3 User documentation

1. A copy of the SRS for future reference.

2.4 Assumptions and Dependencies

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 9 of 46

3. Payroll File Capture

3.1 Requirement – Capture Payroll File

3.1.2 Stimulus and Response

3.1.3 Functional Requirement – Description

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 10 of 46

7. Unprocessed reasons would include;

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 11 of 46

3.2 Requirement – View Payroll File Status

3.2.2 Stimulus and Response

3.2.3 Functional Requirement – Description

Statuses would be as below;

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 12 of 46

3.3 Requirement – iCard OLTP server response

3.3.2 Stimulus and Response

3.3.3 Functional Requirement – Description

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 13 of 46

3.4 Requirement – View iCard OLTP server Status

3.4.2 Stimulus and Response

3.4.3 Functional Requirement – Description

Statuses would be as below;

 iCard received and processed – messages which have been successfully

Document ID: RCB-IC-14_BatchUpload_r1.2 Confidential Page 14 of 46

4. Email Account Addition