Consolidated SOP V 3 2016 12 22 Post Report Merger PDF

State Bank of India
SBI Group Technology Dept

GITC Belapur
Consolidated Standard Operating Procedure
For all Applications
Post Report Level Merger
Version 3
December, 2016
State Bank of India Composite SOP for all Applications Post Report Merger_v3
Table of Contents
1. Background ............................................................................................................. 5
2. Scope ...................................................................................................................... 6
3. Changes in CBS on Report Merger at Associate Banks ......................................... 7
4. CBS and other Branch Operations & Settlements .................................................. 8
5. Other Applications and Operations & Settlements............................................... 14
5.1. GBSS ...............................................................................................................14
5.2. Exim Bills ........................................................................................................16
5.3. Vendor Payment System (VPS) .....................................................................17
5.4 Financial Inclusion and Government Schemes (FI & GS).............................18
5.5. Loan Origination System (SME & Agri).........................................................19
5.6. New Pension Scheme (NPS) ..........................................................................20
5.7. ATAL Pension Yojana (APY) .........................................................................21
6. Channel Operations & Settlements....................................................................... 22
6.1. Internet Banking .............................................................................................22
6.2. Mobile Banking ..............................................................................................24
6.3. Swayam (Barcode based Passbook Printing Kiosk) ....................................27
7. SOP for Controlling Offices and Corporate Office Units .................................... 29
7.1. Operations - Payments Systems ...................................................................29
7.2. FRT Department..............................................................................................30
7.4. LOS Retail .......................................................................................................31
7.5. LOS Agri / SME............................................................................................32
7.6. LLMS................................................................................................................33
7.7. NPS .................................................................................................................34
2
7.8. APY .................................................................................................................34
7.9. CCDP ...............................................................................................................34
7.10. IFAMS .............................................................................................................37
7.11. Mobile Banking ..............................................................................................40
7.12. POS Business..................................................................................................40
7.13. IDSPM .............................................................................................................42
7.14. HRMS ..............................................................................................................46
7.15. BID ..................................................................................................................47
7.16. Treasury..........................................................................................................48
8. Forbearance Requirement ..................................................................................... 56
9. Customer Notice ................................................................................................... 58
10. Activities to be done at GITC on Report Merger Date ..................................... 60
3
List of abbreviations used in this document

Term Definition
SBI State Bank of India
CBS Core Banking System
BGL Banking General Ledger
UAT User Acceptance Test
SIT System Integration Test
INB Internet Banking
BMB Bharatiya Mahila Bank
ABs Associate Banks of SBI
SBH State bank of Hyderabad
SBBJ State Bank of Bikaner and Jaipur
SBM State Bank of Mysore
SBP State Bank of Patiala
SBT State Bank of Travancore

Report On the date of notification, the financial statements of all the ABs
Merger and SBI will be integrated.
Data Data Merger is a process of merging of the actual data from the
Merger various systems of ABs with SBI. This will be done one AB per week
4
1. Background
1. State Bank of India is in the process of merging the 5 Associate Banks and
Bharathiya Mahila Bank with itself. SBI is proposing to complete the merger
activities before the end of the Financial Year ie 31st March 2017.
2. As per the directives from the Corporate Centre, all the above 6 entities needs
to be merged on a single day with SBI. The notification from Government of
India may require that all these entities are merged on a single day.
3. Merger of all applications and data of all the 6 entities on a single day may
not be possible and hence it has been proposed to do a Report level merger.
4. On the notified date, all the Assets and Liabilities of all the 6 entities will be
merged in SBI and all reports henceforth will be for the combined entity viz
State Bank of India, All 5 Associate Banks and Bharathiya Mahila Bank.
5. Data merger or Merger of all other application data of all the 6 entities with
SBI will be carried over a period of 6/8 weeks after the report merger.
6. In order to have clarity on operations and operating in the interim period

between Report Merger and the Data Merger of all the 6 entities, it was felt
that a comprehensive document be published by individual product owners on
the impact and the operating procedure. The document should also highlight
any procedural changes proposed and impact on reporting or branch
operations.
7. All the application owners have submitted their Standard Operating

Procedures for their respective applications. In order to provide a singular
view to the branches and operational staff, this Composite SOP document is
prepared.
5
2. Scope
8. The scope covers the impacted areas around Core Banking Applications, its
interfaces with other system and all other IT systems which may have impact on
the various stakeholders viz Customers, Staff of the Bank. Further to the CBS,
other IT applications which have interfaces with CBS and customer interface
have also been covered in this document.
9. There are certain IT applications which do not have customer interface but
have regulatory reporting and statutory reporting dependencies. These
applications have also been covered under the scope of this document.
10. Transactions and enquiries are serviced by Core Banking system through
multiple channels / touch points.
a. Branch Tellers
b. Internet Banking
c. Mobile Banking
d. Financial Inclusion
e. InTouch branches
f. Payment Systems Group
g. Trade Finance
h. Mercury FX
i. Murex
j. Vendor Payment System
k. APY/NPS
l. GBSS
m. LoS Per/ LoS Agri / LoS SME
11. Data from CBS flows to many down-stream systems:
a. FinanceOne
b. ALM
c. CCDP
d. CCube
e. CRMD
12. The document attempts to list out the impact and change in processes required
during the interim period.
13. For Bharatiya Mahila Bank (BMB), only the Core Banking system has been
considered for merger with SBIs Core banking system, on the day of
notification.
6
3. Changes in CBS on Report Merger at Associate

Banks
14. Post Report Merger date, all the branches of all the 5 Associate Banks will
function as branches of State Bank of India, despite the fact the data merger
of Core Banking system is pending.
15. To meet the procedural requirements, following changes may have to be done
in the CBS at all Associate Banks:
a. Rate of Interest on Deposits to be aligned with SBI

b. MCLR types and rates to be aligned with SBI
c. Reset dates of MCLR types to be aligned with SBI
d. All AB specific products needs to be closed
e. All live products of SBI to be offered by all ABs
f. AB specific BGLs to be closed
g. All SBI specific BGLs to be opened in all ABs
h. AB specific CGLs or extraneous CGLs as per analysis to be closed
i. SBI specific additional CGLS to be opened in all ABs
j. All NPA parameters to be aligned with SBI
k. Change in BSR Codes
l. Change of Banner (Change of name of the Bank to SBI)
16. Pre-requisites
a. All pending queues on the date of merger to be cleared

b. BGL-CGL Cash to be tallied
c. No unadjusted Balcomp entries
d. No unadjusted CIBA entries
e. No unadjusted CGL Suspense entries
f. No outstanding Clearing differences
17. Assumptions
a. From the date of Report Merger to the Data Merger, all the ABs and SBI
will be handling their respective customers.
b. Membership to clearing houses by the respective ABs will be continued
beyond the Report Merger date and till such time it is administratively
required.
c. All the Departments of the respective Head Offices of ABs will be
functional till the date of Data Merger and till such time it is
administratively required.
d. Income Tax and Service Tax related changes will be effective from the
date of Report Merger.
7
4. CBS and other Branch Operations & Settlements
18. Teller Log-In

Teller of the erstwhile Associate Bank will login to CBS using his own
credentials, as hitherto.
19. Cash Drawer
The teller can access to Cash drawer and if its a BPR branch, will have the
overnight Cash balance restored. For other branches, teller can receive cash
from Cash Officer / Vault Teller
20. Vault Teller
Vault Teller can log-in and perform Cash-in/ Cash-Out normally.
21. Cash Receipts
Cash receipts for the customers of the respective ABs and SBI can be done as
per the existing practice. However, in case of Customers of other ABs or
customers of SBI at ABs, the same is not possible till the date of data
merger. A suitable customer notification to this effect needs to be published.
22. Cash Payments
Cash Payments for the customers of the respective ABs and SBI can be done as
customers of SBI at ABs, the same is not possible till the date of data
merger. A suitable customer notification to this effect needs to be published.
23. Transfers
Transfer between accounts for the customers of the respective ABs can be done
as per the existing practice. However, in case of Customers of other ABs or
customers of SBI, the same is not possible till the date of data merger. A
suitable customer notification to this effect needs to be published.
24. Clearing
Cheques for Clearing can be accepted for the customers of the respective ABs
as per the existing practice. However, in case of Customers of other ABs or
8
25. IOI BC Issue
IOI BC can be issued for branches of the respective Associate Banks and it may
not be possible to issue IOI BCs on branches of other Associate Banks and
State Bank of India, till the date of Data Merger. All the accounting entries
and processes followed till the date of Report Merger will continue till the
completion of the data merger.
26. IOI DD Issue
IOI DD can be issued for branches of the respective Associate Banks and it may
not be possible to issue IOI DDs on branches of other Associate Banks and
State Bank of India, till the date of Data Merger. All the accounting entries
and processes followed till the date of Report Merger will continue till the
completion of the data merger.
27. ABSOT
IOI DDs will continue to be issued between the branches of erstwhile Associate
Banks and State Bank of India as per existing procedure till the date of Data
Merger. The daily settlement for the ABSOT drafts will be continued as it is.
The Centralized off-site Reconciliation Software will be continued with the same
existing activity.
From the next day of Data Merger of first Associate Bank, remaining four
Associate Banks will not issue ABSOT drafts on merged Associate Bank.
Now the branches of remaining four Associate Banks will issue drafts on
the branches of merged Associate Bank through AGCL Scheme.
28. Agency Clearing
Under AGCL Scheme, SBI draws drafts on Associate Banks and in the same
way Associate Banks issue drafts on SBI. The settlement of funds for drawings
amongst Associate Banks and SBI is being made on next working day. With
effect from 17/07/2016, manual funds settlement process is replaced with
Auto Fund Settlement through System. The issue of drafts under AGCL Scheme
will be continued with all existing processes. Branches will use same CBS Screen
for issue of drafts after Report Level Merger Date. The System will
automatically shift the amount of drafts to the BGL Account of Drawee Banks
Branch.
29. Inter-Branch Transaction System (IBTS)
IBTS is being utilized for transfer of funds between the branches of same Bank.
While an entry is passed through CBS, IBTS advice is generated with details of
transactions and name of Originating and Responding branch. This advice is
9
being sent to corresponding branch for responding the entry. This System will
be continued with the same procedure using the same CBS Screen after Report
Level Merger Date by Associate Banks.
30. BCGA (BRANCH CLEARING GENERAL ACCOUNT)
The BCGA System is replaced with IBTS in the year 2011. No originating
entries are being passed under BCGA at SBI as well as in Associate Banks, so
there will be no new entry in BCGA. Responding of entries in BCGA is to be
continued with the same system and procedures using same CBS Screen,
However such entries are to be allowed to be passed in the System only
after getting concurrence from F&A Department of respective Associate
Bank.
31. RTGS Outward
IFS codes of the erstwhile Associate Bank branches may not be changed till the
date of data merger. SBI has already sought permission of Reserve Bank of
India to continue with the existing IFS codes till 30th June 2017. As the CBS
instances of all Associate Banks are functioning, using the new IFS codes will
create problems if the RTGS Outward messages are returned. As all the RTGS
gateways of individual banks are active, the returned RTGS Outward message
may get routed to SBI and may get posted to Suspense account.
32. NEFT Outward
instances of all Associate Banks are functioning, using the new IFS codes will
create problems if the NEFT Outward messages are returned. As all the NEFT
gateways of individual banks are active, the returned NEFT Outward message
may get routed to SBI and may get posted to Suspense account.
33. RTGS Inward
instances of all Associate Banks are functioning, using the existing IFS Codes of
erstwhile ABs will ensure that there are no issues in RTGS Inward.
34. NEFT Inward
10
instances of all Associate Banks are functioning, using the existing IFS Codes of
erstwhile ABs will ensure that there are no issues in NEFT Inward.
35. Group Transfers
Group transfers will be continued till the date of Data Merger. As and when
Banks are merged, the GRPT facility for that entity will be disabled. All
accounting and process will continue as hitherto. However, Fee waiver may be
considered.
36. Inward Clearing
The MICR Codes of all the erstwhile branches of all the Associate Banks will
also be in use till 30th June 2017. It is proposed to continue the CCPC of the
erstwhile Associate Banks till the date of Data Merger or till it is
administratively required. These CCPCs will continue to process the Inward
clearing as hitherto and the settlement process will be handled by the
respective ABs.
37. Outward Clearing
also be in use till 30th June 2017. It is proposed to continue the CCPC of the
erstwhile Associate Banks till the date of Data Merger or till it is
administratively required. These CCPCs will continue to process the outward
clearing as hitherto and where ever CTS operations are live, the same will
continue as hitherto. The settlement process will be handled by the respective
ABs.
AB instruments submitted to SBI for payment shall be routed through

Clearing as is being done at present. Simultaneously, SBI instruments
submitted to ABs shall also be routed through clearing instead of Bank
transfer.
38. Passbook Printing
Passbook printing facility will be restricted to accountholders of the respective

Associate Banks only till the date of data merger.
39. RTGS Settlement
The settlement of RTGS Inward and Outward would be handled by the

erstwhile Associate Banks till the completion of the data merger or till any
date administratively decided. As IFS Codes are not changed till the date of
11
data merger, all the Inward / Outward RTGS messages will be routed through
the respective accounts of the Associate Banks.
40. NEFT Settlement
The settlement of NEFT Inward and Outward would be handled by the

erstwhile Associate Banks till the completion of the data merger or till any
date administratively decided. As IFS Codes are not changed till the date of
data merger, all the Inward / Outward NEFT messages will be routed through
the respective accounts of the Associate Banks.
41. Clearing Settlement
The settlement of Inter-Bank clearing is handled through SBI/ Other Banks at

smaller centers, which are not part of the CTS grids. The settlement accounts
of the Associate Banks have to be maintained till the date of Data Merger or
till any date administratively decided. As the old MICR codes are maintained
till 30th June 2017, Inward / Outward cheque presentment will happen as
hitherto.
42. CTS Settlement
The settlement of Inter-Bank clearing is handled through RBI at various centers,

which are part of the CTS grids. The settlement accounts of the Associate Banks
have to be maintained till the date of Data Merger or till any date
administratively decided. As the old MICR codes are maintained till 30th June
2017, Inward / Outward cheque presentment will happen as hitherto. The
mapping of the erstwhile branches of the Associate Banks to the CCPCs/
Service Branches will continue till the date of Data Merger.
AB instruments submitted to SBI for payment shall be routed through

Clearing as is being done as present. Simultaneously, SBI instruments
submitted to ABs shall also be routed through clearing instead of Bank
transfer.
43. ECS Settlement
The ECS processing and settlement is handled through RBI/ NPCI. The
settlement accounts of the Associate Banks have to be maintained till the date
of Data Merger or till any date administratively decided. As the old MICR
codes are maintained till 30th June 2017, Inward / Outward ECS presentment
will happen as hitherto.
12
44. NACH Settlement
The NACH processing and settlement is handled through RBI/ NPCI. The
settlement accounts of the Associate Banks have to be maintained till the date
of Data Merger or till any date administratively decided. As the old MICR
codes are maintained till 30th June 2017, the NACH/ECS transactions of SBI,
ABs shall be treated by NPCI as received from different Banks. ABs would
continue processing of transactions on them and would continue uploading the
presentations directly to NPCI till further instructions.
The mandates registered on SBI by ABs and vice versa would have to be
routed through the Mandate Management System till the time the systems are
merged
For ECS and NACH transactions between SBI and ABs, the charges would
continue to be collected from corporate customers as is being done at present.
45. Currency Chest Transaction Settlement
The settlement of Curency Chest transactions are done by identified FSLOs of

the Bank as Net settlement on the basis of ICCOMS reports. This may have to
be continued till the date of Data Merger or till any date administratively
decided and the existing mapping of the branches (of erstwhile Associate
Bank) to the FSLOs need to be continued.
46. Cheque Book Issue
Cheque Book issue requests received by the branches of erstwhile Associate

Banks post the Report Merger will be handled as per existing practice. They
will be provided with the cheque books of the respective Associate Banks.
47. TDS Remittance
Deduction and remittance of TDS on Interest Paid, TDS on Salaries, TDS on

Pension payments, TDS on Vendor Payments are to be done as per existing
practice on the Report Merger date. Post Report Merger, all the branches of
ABs will have new TANs allocated and all TDS deducted will have to be
accounted separately.
48. Service Tax Remittance
Deduction and remittance of Service Tax are to be done as per existing

practice, on the Report Merger date. Post Report Merger, all Service Tax
deducted will have to be accounted separately.
49. Prepaid Cards
No impact. Only report level changes.
13
5. Other Applications and Operations &

Settlements
5.1. GBSS
50. GBSS Teller Log-In
Teller of the erstwhile Associate Bank will login to CBS using his own
credentials, as hitherto for accessing GBSS application.
51. Govt. Cash Receipts
Govt. Cash receipts for the customers of the respective Associate Banks can be
done as per the existing practice. However, in case of Customers walks in
with challan of another Associate Bank or SBI, the same will not be
possible to be processed till the date of data merger. A suitable customer
notification to this effect needs to be published.
52. Govt. Cash Payments
Cash Cheque Payments for the customers of the respective Associate Banks can
be done as per the existing practice. However, in case of Customers of other
Associate Banks or customers of SBI, the same is not possible till the date of
data merger. A suitable customer notification to this effect needs to be
published.
53. Govt. Transfers
Transfer between accounts for the customers of the respective Associate Banks
for govt. receipt can be done as per the existing practice. However, in case of
Customers of other Associate Banks or customers of SBI, the same is not
possible till the date of data merger. A suitable customer notification to this
effect needs to be published.
54. IOI for govt. receipts
IOI issued by the branches of the respective Associate Banks will be accepted
in respective Associate Banks only till the date of data merger for Govt.
receipt. All the accounting entries and processes followed till the date of
Report Merger will continue till the completion of the data merger.
55. Govt. Inward Clearing
14
also be in use for a period of 3 months from the date of Report Merger. It is
proposed to continue the CCPC of the erstwhile Associate Banks till the date of
Data Merger for Govt. payment. These CCPCs will continue to process the
Inward clearing for Govt. payment as hitherto and the settlement process will
be handled by the respective ABs.
56. Govt. Outward Clearing
also be in use for a period of 3 months from the date of Report Merger. It is
proposed to continue the CCPC of the erstwhile Associate Banks till the date of
Data Merger for Govt. receipt. These CCPCs will continue to process the
Outward clearing for Govt. receipts as hitherto and where ever CTS
operations are live, the same will continue as hitherto. The settlement process
will be handled by the respective ABs.
57. Govt. CTS Clearing
Govt. CTS transactions for the customers of the respective ABs can be done as
15
5.2. Exim Bills

58. Exim Bills Teller Log-In
Teller of the erstwhile Associate Bank will login to Trade Finance using his own
59. CS Eximbills Application Meta Sync
CS Eximbills Meta data version will be in sync in with SBI in order to have all
necessary parameters as of SBI.
60. GAPI
GAPI components as of ABs will be continued.
61. Interfaces
Interface integration for all 5 Associate Banks to be continued as same. No SBI

interface integration to be done as will have impact on transaction database.
EDPMS, MFx (Mercury), OFAC, DWP, WORKFLOW, SWIFT, SFMS (changes of
SBI to done for all ABs)
62. Advices
Advices to be changed as it will have SBI instead ABs name.
63. SFMS / SWIFT
All ABs SFMS/SWIFT will be updated to have SBI related information to so as

function as part of SBI.
64. Transaction Account Type
Will have to be continued as of ABs.
65. Trade Finance Transactions
All the Trade Finance related transactions (e.g. LC, Export Bills, Import Bills,
etc.) for the customers of the respective ABs can be done as hitherto. However,
such transactions for Customers of other ABs or customers of SBI will not be
possible to be processed till the date of data merger. A suitable customer
notification to this effect needs to be published.
16
5.3. Vendor Payment System (VPS)
66. VPS Teller Log-In

Teller of the erstwhile Associate Bank will login to CBS using his own credentials for
accessing VPS, as hitherto.
67. Vendor Payment Receipts
Vendor payments, for vendors having account in respective Associate Bank or SBI
the payment can be processed as per the existing practice. However, in case of
vendors having account with other ABs or with SBI, the payment processing will not
be possible till the date of data merger. A suitable customer / branch notification
to this effect needs to be published.
68. Access of Vendor IDs
The branches can access the Vendor IDs present in their respective Bank. Accessing
Vendor IDs of other ABs or SBI will not be possible till the date of data merger. A
suitable customer / branch notification to this effect needs to be published.
69. Creation of Vendor Id / Employee Id
While creating an Employee ID / Vendor Id in VPS, the account must be with the
concerned Bank where the ID is being created. The accounts of other ABs or SBI
cannot be used till data merger takes place.
70. Rent payment Processing
Rent payment processing across the banks will happen as per the existing scenario.
71. Cenvat Reports
The cenvat reports that are being submitted will be done as per the current
scenario. The reports will be shared separately for each bank till the date of data
merger.
17
5.4 Financial Inclusion and Government

Schemes (FI & GS)
72. KO, BC and Bank Admin logins
Agent, BCs and Bank admins of the erstwhile Associate Banks will login to their
respective web sites of FI using their own credentials.
73. Financial Services
In FI we are having more than 20 different kinds of services, such as Account

opening, Cash deposit, Cash Withdrawal, Funds transfer, AEPS, IMPS, ATM card
based transactions, etc. These services are available for FI and Non FI customers.
Also some inter banks services are present in FI through which other bank customers
can do financial transactions (AEPS and IMPS).
Post report merger associate banks customers can utilize interbank services of FI
for doing transactions at FI terminal as hitherto. However, till data merger, the
associate banks customers will be considered as other bank customers in FI
application.
74. URLs for Accessing application
SBI and Associate banks are having their own separate URLs for accessing the
application. These URLs will remain same after the report merger. Only logos and
banners will be changed to SBI as per the requirement.
18
5.5. Loan Origination System (SME & Agri)

75. LOS Agri/SME Teller Log-In
Teller of the erstwhile Associate Bank will login to CBS using his/her own
76. CIF Fetch Transaction/ CIF Creation
The CIF details to be fetched from CBS in LOS will be done with the updated
and conflict-free CIF nos.
77. Repayment Schedule Generation Transaction
The repayment schedule will be generated by transmitting the details of the

Repayment with relevant Product Codes of SBI, updated in ABs LOS.
78. Account/Limit Creation/Amendment Transaction
Accounts dependent on the Product Codes (for respective schemes) will be

created for the respective banks taking in consideration the updated product
codes.
79. Collateral Creation/Amendment Transaction
Collateral Creation Transaction will be done in accordance to the security type

(Primary and Security), provided the respective changes in CBS related to the
same have been considered.
19
5.6. New Pension Scheme (NPS)

80. NPS Teller Log-In
Teller of the erstwhile Associate Banks will login to NPS through CBS->Other
apps using his own credentials, as hitherto.
81. Cash Drawer
The teller can access to Cash drawer for NPS cash transactions and if its a BPR
branch, will have the overnight Cash balance restored. For other branches,
teller can receive cash from Cash Officer / Vault Teller.
82. Transfers
Transfer of funds from other associate banks or SBI accounts in case of

registration/ contribution of NPS scheme will not be possible till the date of
data merger. A suitable customer notification to this effect needs to be
published.
83. Registration
Registrations of NPS customers can be done by all the Associate Bank branches
as hitherto. However, registration of other Associate Bank or SBI customers
cannot be processed. A suitable customer notification to this effect needs to be
published.
84. Contribution
Contribution of NPS customers can be done by any branches of SBI and

Associate Banks as hitherto.
85. Subscriber Modification

Subscriber modification has to be done at registered branch only.
86. PRAN Unfreezing

PRAN Unfreezing has to be done at registered branch only.
20
5.7. ATAL Pension Yojana (APY)
87. APY Teller Log-In
Teller of the erstwhile Associate Bank will login to APY through CBS->Other
apps using his own credentials, as hitherto.
88. Contributions
Contributions can be deducted from customers account and can be credited to

Nodal branch BGL account as hitherto.
89. Registrations
Registrations for own customers of the respective Bank can proceed as hitherto.
However, registration for customers of other associate banks and SBI will not
be possible till the date of data merger. A suitable customer notification to this
effect needs to be published.
21
6. Channel Operations & Settlements
6.1. Internet Banking

6.1.1. INB POST-LOGIN CHANGES
90. Associate Bank Websites
As Associate Bank customers will be treated as SBI customers, all Associate

Bank customers will be allowed to login in SBI Online banking site
www.onlinesbi.com. Hence all Associate Banks customer who accesses Associate
bank website will be automatically redirected to www.onlinesbi.com.
91. Associate Bank Login
Presently customers who are logging in www.onlinesbi.com are validated

based on the bank code of the customer. If the customer bank code is SBI code
only then only they are allowed to login in www.onlinesbi.com. For the Report
Level Merger, we will make changes in bank code validation, in order to allow
Associate bank customers to login into www.onlinesbi.com
92. SBI Links and Functionalities
As per Report Level Merger guidelines, Associate Banks will be allowed to

login into onlinesbi.com, however the links and functionalities applicable for the
respective Associate bank will only be made available to Associate Bank
customer(s). New Links and functionalities applicable for SBI will be available
for Associate bank customers only after the Data Merger.
93. Fixed Deposit Product codes
Since the Product codes of Associate Banks will be made in sync with SBI, all
Fixed deposit accounts created post Report Level Merger will be as per the
availability of the product code in Associate Bank. Any exclusive fixed deposit
products (for e.g. SBH Platinum, SBH Double and SBT Special Campaign Days
product) which existed for Associate banks will be discontinued and cannot be
availed by Associate bank customers after Report Level Merger.
94. Inter-Bank Transaction Charges
22
Since SBI and Associate banks will become one entity after Report Level
Merger, Inter-Bank (RTGS/NEFT/GRPT) transaction charges need to be waived
for transactions made between SBI & Associate Banks and vice versa. Inter-
Bank Transaction charges will be deducted as per the policy of SBI. Necessary
approval by business in this regard is taken up separately by PSG.
95. GRPT Funds Transfer
As the Core Banking System (CBS) of Associate banks will continue to function
on Report Level Merger, GRPT Funds transfer option will also continue to
function in INB till the Data Merger of first associate bank.
6.1.2. MERCHANT PAYMENT CHANGES
96. Continuation of Associate Banks links in Payment Gateways
The Associate banks link in Payment Gateways of Merchants and Aggregators

will continue to be displayed separately due to certain challenges in handling
merchant transactions that are enabled exclusively for SBI and not for
Associate banks e.g. EPFO payments by Associate banks. The transaction
amount will be pooled into the respective Associate Bank Pooling account only,
as the CBS of Associate banks will continue to function.
97. Removal of Associate Bank Name and Logo
Though Associate bank customers will login through their respective URL for
merchant payments, the Associate bank name and logo will not be displayed
to the customer when they are landed in the site. We will replace all Associate
Banks name and logo with that of SBI.
6.1.3. OTHER CHANGES
98. INB Branch and Circle Interface
INB Branch and Circle interface is provided to bank staff for INB support and
services to customers through the branches. This interface has been provided
separately for each Associate Bank. Associate Bank branches and Head office
will continue to use their respective branch and circle interfaces.
99. INB Dashboard and Report Interface
Till the actual Data merger of Associate Banks, INB will continue to display
separate figures for SBI and Associate Banks. Consolidated figures of SBI and
Associate Banks can be provided as per the requirement.
23
100. Access to BMB customers
BMB customers will be able to register and access onlinesbi only after they are
on-boarded in CBS with Payment gateway enabled ATM card issued and
mobile number mapping in CBS.
101. INB Charges and Commission
Any commission/charges deducted for INB services availed by Associate Banks

customers will be as per the policy of SBI.
6.2. Mobile Banking

6.2.1. Application Login / Registration
102. State Bank Freedom / SMS Banking
a. Since there is one login for SBI and ABs customers in SB Freedom, no
changes will be required till Data merger. Associate Bank customers can
use the existing user id and password in Freedom application at the time of
report merger and thereafter.
b. At the back end, from the user id, the user bank code will be identified and
based on which the application will fetch information from the respective
ABS CBS.
c. BMB customers will be on-boarded to SBI app on date of report merger.
Such customers will be required to register afresh as per the SOP provided.
d. On data merger the applications will point to SBI CBS and ABs customers
will continue to use the existing credentials for login.
e. The charges, commission and limits will continue AS-IS in Freedom and
SMS Banking for Associate Banks till data merger. On data merger, SBI
business rules will apply.
f. All BGL and Pooling accounts maintained in ABs CBS for Freedom will
continue during the report merger.
103. State Bank Anywhere (SBI) / State Bank Anywhere (ABs)
a. It is proposed to allow AB customers to use SB Anywhere (ABs) till data

merger.
b. The users of ABs will continue to use the ABs anywhere application till data
merger. The bank selection in the app will be removed and named to be
changed as SB Anywhere (Erstwhile ABs users).
c. No change is proposed in State Bank Anywhere (SBI) on report merger.
From the date of data merger all customers of ABs will be able to login
through SBI Anywhere application. ABs application as above will cease to
function from the date of Data merger.
24
d. BMB customers have to register afresh (as per the SOP shared with BMB
team) and can use SBI Anywhere application from the date of report
merger.
e. The customers of ABs will login through ABs Anywhere app and based on
the bank code the app will point to respective ABs Core.
f. Subsequently on the respective bank getting merged under data merger,
on login attempt by ABs customers such bank customers will be identified
and will display proper message giving link to download the application of
SBI for further use.
g. Before the data merger and at least 15 days in advance each customers
will be informed (As per our communication plan shared vide No
GITC/CTO/IT-MB/20160920/MG/681 to Business Unit and confirmed to
Steering Committee).
h. The charges, commission and limits will continue AS-IS in Anywhere for
Associate Banks till data merger. On data merger, SBI business rule will
apply.
i. All BGL, Pooling accounts maintained in ABs CBS for SB Anywhere will
continue during the report merger.
104. SB Anywhere Saral, SB Anywhere Corporate
The SBA Saral application is currently not rolled out for Associate Banks and
hence customers of ABs will not be able to use these applications on report
merger.
6.2.2. Fund Transfer (RTGS/ NEFT/ IMPS/ SBGRPT/ Third Party/ Scheduled
Transactions) and Merchant & Bill Payments
105. State Bank Freedom / SMS Banking / State Bank Anywhere (ABs)
a. All fund transfers will point to the respective ABs core from the date of
report merger to data merger period and also the above applications will
maintain the existing IFSC codes for Fund Transfer.
b. NBIN of Associate Banks for IMPS will also continue to exist till data
merger.
c. All the BGL maintained for RTGS, NEFT, IMPS settlement will continue
during the report merger period in respective ABs CBS. The settlement and
reconciliation activities will be done by existing ABs Settlement team (PSG,
ATM Nodal office) till data merger. On Data merger all BGLs having
balances have to be transferred to the identified BGL in SBI by ABS
Settlement team.
d. The SBGRPT option in SB Anywhere ABs will continue during the report
merger period and will be discontinued on data merger.
e. The RTGS, NEFT, IMPS transfers within State Bank Group (SBI & ABs) will
be treated as inter-bank transactions during the report merger period.
25
f. Beneficiaries maintaining accounts in ABs / SBI will have to be added as

interbank beneficiaries during the report merger period instead of intra
bank beneficiaries.
g. The charges / commission / Limits will be as per ABs business rules during
the report merger period.
h. Billers are common for SBI and ABs. Merchant pooling accounts will
continue AS-IS during report merger period.
i. Merchant pooling accounts of ABs will form part of SBI pooling accounts of
respective merchant on data merger.
j. On data merger the MMID, NBIN, IFSC etc. issues, will be effective as per
the plan action / changes deviation required vide IMPS ref No GITC/DGM
ITMB/20160805/MERGER/02/21/39 duly approved.
k. All scheduled transaction will be take care on data merger without any
user intervention.
106. National Unified USSD Platform (NUUP)
a. The bank selection for Associate Banks will continue with *99# during the
report merger period. At the service level the bank codes are identified
based on the user id and will hit the respective ABs Core during report
merger. Therefore no changes are required.
b. On data merger services will point to SBI CBS and have to use the *99#
code for SBI.
c. MMIDs will not change during report merger, however on data merger ABs
customers to generate new MMID as approved in steering committee note
No GITC/DGM ITMB/20160805/MERGER/02/21/39
107. IMPS
a. The IMPS transaction of ABs will still continue to route through the existing
Ports of ABs to NPCI and will hit the respective ABs CBS during report
merger. During the report merger period, the IMPS transactions within State
Bank Group (SBI & ABs) will be treated as inter-bank transactions.
b. The BGL accounts maintained for IMPS will continue to be used till data
merger. The settlement and reconciliation activities will be done by existing
ABs Settlement team (PSG, ATM Nodal office) till data merger.
c. Existing business rules of ABs will be followed during report merger.
d. On data merger the MMID, NBIN, IFSC issues, the action / changes
deviation required at IMPS ref No GITC/DGM
ITMB/20160805/MERGER/02/21/39 will be followed.
108. SBI Quick Missed Call Banking and Appkart
a. The SBI quick application will continue to fetch information for customers of
ABs from the respective CBS during the report merger period and on data
merger will point to SBI CBS.
26
b. SMS Keywords are different for SBI and Associate Banks. AB customers
will continue to use the existing keywords of ABs during the report merger
period. Post data merger, all requests (all keywords and missed call
banking numbers) will be handled in SBI instance.
c. The appkart will show the links of ABs Mobile app during the report
merger period and on data merger the link will be removed.
109. Functionalities not rolled out to Associate Banks which are in SBI
The following functionalities are currently not rolled out to Associate Banks
customers hence this will not be available to AB customers during the report
merger period.
a. Secure OTP
b. mCAsh
c. mVISA
d. SB Collect
e. Online refunds (mGate)
6.3. Swayam (Barcode based Passbook Printing

Kiosk)
110. Inter-Operability enabled
The customers of SBI as well as Associate Banks will be catered with the Bar
Code Based Pass Book Printing Kiosks (Swayam machines), even before the
data merger, provided the interoperability between State Bank of India and
Associate Banks is enabled at SBI SI End.
The Interoperability enables the following scenario :

Customer of bank Swayam Services Result
SBI ABs(any) Success
ABs(any) ABs(any) Success
ABs(any) SBI Success
SBI SBI Success
111. Inter-Operability not enabled
27
If interoperability is not enabled at SBI SI end, the customers of One Associate

Bank(AB) will not be able to use the Bar Code Based Pass Book Printing Kiosks
(Swayam machines) at another Associate Bank/Branch. Moreover the customer
of State Bank of India also will not be able to use the Bar Code Based Pass
Book Printing Kiosks (Swayam machines) at the Bank/Branch of any Associate
Bank and vice-versa. In this scenario, the customers would get uninterrupted
service only after complete data merger happens. In such situation, we will
have to advice the customers through e-Mail, messages, notices at
bank/branches, kiosks, e-lobbies. The notice has to be displayed in English,
Hindi and local language and requires wide publicity.
The possible scenario affecting the customers in this case are as under:
Customer of bank Swayam Services Result
SBI ABs (any) Fail
ABs(SBP) ABs(SBH) Fail
ABs(any) SBI Fail
ABs (SBP) ABs (SBP) Success
SBI SBI Success
28
7. SOP for Controlling Offices and Corporate

Office Units
7.1. Operations - Payments Systems

112. RTGS
Presently SBI Treasury Department has access to ILM and they can instantly
access the fund position as and when required regarding RTGS. Any RTGS
beyond Rs 25.00 cr need to be authorized by Treasury Department in ILM
Application for processing of the transactions. After Report Merger, PSG of
ABs needs to inform SBI Treasury Department on daily basis for arriving at
actual position of the fund and also need to take care for transactions above
Rs 25.00cr.
113. NEFT
SBI Treasury Department has been provided with a portal through which they
can access hourly settlement figures data with regard to NEFT. After Report
Merger PSG of ABs needs to inform SBI Treasury on hourly basis for NEFT
settlement figures to arrive at actual position of the fund.
114. GRPT
These are the transaction originated by ABs on SBI and vice versa. Fund
settlement is done between two entities. PSG of ABs need to report the
settlement of GRPT figures to SBI Treasury.
115. STATUTORY AUDIT
SBI PSG is audited on quarterly basis by Statutory Auditors. After report

merger, PSG of ABs need to provide information to SBI PSG at each quarter
end for consolidated Audit and report purposes.
116. Prepaid Cards
29
As the report data structure for both Associate and SBI is similar therefore, for
report level merger our Prepaid vendor M/s YSE will populate the data in one
table called Report_reportname_SBI.
7.2. FRT Department

117. Elimination entries (Interbank transactions)
a. Elimination entries (Interbank transactions) department of the bank before

report merger. Otherwise post report merger Bank balance sheet will be
distorted.
b. Treatment for Capital, Reserve and Investments accounts to be handled.
7.3. Financial Inclusion & Government Schemes

Department PFMS
118. The PFMS Processing solution is operating at SBI and all the Associate Banks.
The solution is used to process Government subsidy and other payments which
are received through Public Financials Management System (PFMS) an agency
which consolidates the subsidy payments from various Government Agencies
and forwards it to banks who are sponsor banks for the schemes. The entire
process is a back-end process without any customer interaction.
119. Since the input files are received from PFMS and the response files sent back to
PFMS, the file formats of the solution are the same across SBI and its 5
Associate Banks are identical although the processing application software is
developed individually by each Bank.
120. Post-data merger the processing applications of the Associate Banks will be
discarded and only the solution operating at State Bank of India (FI&GS Dept)
will continue to be used. The Report Merger scenario (pre-data merger) will
be as follows:
121. Transaction Processing : There will be no change in the processing modality
of SBI and its Associate Banks / BMBL. Status quo will be maintained until
data merger
122. Notification to External Agencies : The application has integration with (a)
PFMS for receiving transaction files (b) NPCI for sending / receiving clearing
files. Additionally the progress of the processing is tracked by the Office of
the CGA, New Delhi.
30
123. Suitable communication will be sent to all the above advising them of the
impending merger and specific communication to NPCI and PFMS would be
sent advising them of the date of data merger of individual banks, as and
when declared as under :
a. PFMS : Advising them to route the transaction files of the merged AB to the
SBI SFTP for processing
b. NPCI : Advising them to route the Inward processing files of the merged AB
to the SBI SFTP for processing
124. Approvals / Forbearance : No approvals are required from the business units
and no forbearance is required to be sought from any authority.
125. Reporting / Status Tracking: No regulatory / statutory reporting is done in
respect of DBT processing. However, the DFS or CGA Office requests data in
respect of PFMS processing from time to time. Since the PFMS processing
solutions will continue to be operated independently by SBI and Associate
Banks until data merger, as part of the Report Merger exercise, the following
will be obtained from the ABs and BMBL vide email :
a. Daily Report of Transactions Processed
b. Monthly Analysis of Failures in PFMS Processing
7.4. LOS Retail

126. Providing SBI FinnOne LOS (Retail) production access to ABs users
In this activity SBI LOS (Retail) access will be provided to all the ABs users as
per list shared by ABs. In this scenario there will be no need to perform the
logo modification activity also because when user will be doing business with
SBI Production access, all the reports generated via system will automatically
be generated with SBI logo.
127. The following approach is proposed to enable the AB users to access SBI LOS-
PB application:
a. AB users to be redirected from the AB-CBS to SBI LOS-PB application, in
line with the existing pattern of redirection from the SBI CBS to SBI LOS
PB.
b. All the SBI loan products to be aligned in AB-CBS for a/c opening
purpose.
c. The complete branch master of ABs containing circle, module, branch
code, roles, user ids etc. to be shared with LOS-PB for creation of AB
users and branch master in SBI LOS-PB.
d. The user IDs and the branch master for the AB users to be created in SBI
LOS-PB.
31
e. The sourcing, processing, sanction and generation and printing of the Loan
documents to be completed through SBI LOS-PB.
f. The option of loan a/c opening through SBI LOS-PB would not be
available for the AB users till data merger. The loan a/c to be opened
manually in the AB-CBS.
128. It is highly recommended for the Reports Merger activity with given below pre-
requisites and all the required scenarios will be achieved:
a. ABs users list to be provided by ABs
b. CBS access to all the ABs users for which list has been shared.
7.5. LOS Agri / SME

129. Report Level Merger:
On Report Date Merger, SBI products will be available in ABs LOS.

Approaches are as: (Assumptions: CBS Merger and HRMS merger to happen
subsequently on data Merger)
a. ABs users will be logging through ABs CBS as per existing functionality.
b. SBI products will be promoted to ABs LOS region to be used from Report
date Merger. All product features of SBI with MCLR and security documents
will be available in ABs LOS region.
c. CIF/Accounts will open in ABs CBS. ABs CBS will have SBI product codes.
d. Challenges: Baseline is fixed for SBI products (30.11.2016). These
products will be tested in UAT to verify SBI related changes in ABs LOS
region. After successful UAT, the products will be available in ABs LOS
production region.
130. Before Report Level Merger activity at ABs end:
a. All AB specific products need to be closed

b. Change of Banner (Change of name of the Bank to SBI)
c. All pending loan proposals before the date of merger to be cleared.
d. All the transactions in Associate Banks CBS must be aligned with SBI CBS for
the respective transactions (like Account/ Collateral/ CIF creation) to fall in
line with the current sequence of SBI.
131. Data Merger:

CBS and HRMS of ABs will be merged with SBI data.
a. ABs Tellers will be SBI tellers
b. ABs CBS customers and transactions will be SBI CBS customers and
transactions.
32
c. Therefore, ABs users will be using SBI-LOS exactly similar to present SBI
users. Accounts/CIFs will open in SBI CBS.
7.6. LLMS
132. Common application frame work for SBI and Associate Banks has been
developed and implemented in SBI and Associate Banks. Accordingly, a
common application is being used in both SBI and Associate Banks for LLMS
and no changes need to be done from the application view point for the
merger.
133. There will be no report level merger in LLMS. Actual data merger will happen
on report level merger date in LLMS. This is due to the fact that the credit
proposals will flow to the SBI credit committees from the report level merger
date.
134. The data of the associate banks will be merged with SBI data on the report
level merger date except for the data of those entities where SBI is a
consortium member / leader which will be available only for enquiry purpose.
This check will be done based on common PAN numbers.
135. Customer, CMA and CRA data along with documents will be migrated. User
details will be migrated but they will be in deleted state. Fresh users need to
be created in SBI LLMS for the associate bank users after merger. The same
procedure is followed in LLMS when the branches are merged or officials are
transferred. This is due to the fact that on merger, the branches and teams to
which the officials belong to will be different. The users and teams needs to be
created again in LLMS.
136. The following details will be required on the report level merger date (for the
data merger to happen in LLMS on this day):
a. Branch master with the region, module, LHO mapping
b. HRMS data of the associate bank officials
137. In case on the report level merger date, associate banks are treated as virtual
LHOs, either all the credit committees of SBI need to be formed in this virtual
LHO or the mapping of the branches to existing SBI committees need to be
provided.
138. Clarification is also required as to how to treat the CAG / CNW / MCB
branches of associate banks.
33
7.7. NPS
in the NPS at all Associate Banks:
a. Service tax on contribution to be aligned with SBI

b. All AB specific POP/POP-SP numbers should remain same
c. AB specific BGLs should remain same
d. Change of Banner (Change of name of the Bank to SBI)
7.8. APY
in the APY at all Associate Banks:
a. All AB specific NLCC/NLAO numbers should remain unchanged

b. AB specific BGLs should remain unchanged
c. Branch codes will be same
d. Change of Banner (Change of name of the Bank to SBI)
141. Pre-requisites
a. All pending registrations to be uploaded in NSDL on the date of merger to

be cleared
b. BGL to be tallied
7.9. CCDP
142. CCDP program versions (especially Back-End business logic implementation) for
Associate Banks and State Bank of India are same as far as rule
implementation is concerned. However, there are mismatches may exists at any
point of time due to variety of products/other way of
implementation/situational differences in Associate Banks vs. SBI. In this case,
sometimes any changes happened due to change in logic goes as per the rule
of logic, but due to data related gaps may hinder/pose a large difference co-
exists resulting data aberrations between quarter to quarter within a bank.
These discrepancies would be resolved once the actual Abs CBS data merger
completed with SBI CBS data. Till such time the following process would help in
consolidation of the SBIs CCDP data with Associate Banks CCDP data.
143. A scenario is envisaged during the initial discussions for merging of the
Associate Banks with parent Bank SBI, in which case, a common date (i.e.
34
Merger Date) would be common for all the Associate Banks and as far as
actual CBS data merger of the respective Associate Bank would be of different
dates. In such case, this standard operating process document may be used to
consolidate the reporting to statutory requirement as well as internal
consumption.
Solution Approach
144. Associate Banks already have their separate CCDP server for processing as
well as CBS servers and Golden Gate server. They would continue the same
processes as before the merger date till the respective associate Banks actual
data merger happens in SBIs CBS. However, once the Date of Merger
declared, these associate banks do not report on its own as before and CCDP
at SBI would take over the control from Date of Merger. Each individual
Associate Bank would be referred in CCDP at SBI with a separate Circle/LHO
code ( eg:16-SBH 17-SBBJ 18-SBT 19-SBP 20-SBM ).
145. On any reporting date consolidation would follow the approach enumerated
below.
Step 1: On a reporting Date (i.e., Quarter End date) respective CBS
generates the extracts required for CCDP at each Associate Bank as well as
SBI as usual.
Step 2: The data would be loaded in the Associate Banks CCDP server by
respective Associate Bank. Process the data till Error generation completion
needs to be completed.
Step 3: For each Associate Bank prepares relevant information to be
extracted by using the following queries at each interval and provide the data
in excel sheet for initial reporting consolidation.
146. 1. AFTER INITIAL IIMEDIATE UPLOAD OF THE CIS DATA
SELECT B.CIRCLE_CD, B.CIRCLE_NM, A.SEGMENTCD, A.ASSETCD, SUM

(OUTAMT) TOTADV, SUM (CASE WHEN A.ASSETCD > 'IR00003' THEN
OUTAMT ELSE 0 END) TOTNPA FROM CUST_POST A JOIN BRMASTER B ON
A.BRCD=B.BRCD WHERE A.FACCD<= 'FC00011' AND OUTAMT >0 GROUP
BY B.CIRCLE_CD, B.CIRCLE_NM, A.SEGMENTCD, A.ASSETCD;
147. 2. AFTER DEFAULT VALUE REPLACEMENT

148. 3. AFTER ONE A/C NPA ALL A/CS NPA BEFORE STAMPING
35
SELECT A.CIRCLE_CD, A.CIRCLE_NM, B.SEGMENTCD, B.NEW_IRAC ASSETCD,

SUM (OUTAMT) FROM BRMASTER A JOIN SYSCHNG B ON A.BRCD=B.BRCD
WHERE FRESH_NPA='Y' AND EXEMPT='N' GROUP BY A.CIRCLE_CD,
A.CIRCLE_NM, B.SEGMENTCD, B.NEW_IRAC;
149. 4. AFTER BORROWER-WISE STAMPING COMPLETED

150. 5. AFTER PROVISION CALCULATION COMPLETED
SELECT A.CIRCLE_CD, A.CIRCLE_NM, ASSETCD, B.SEGMENTCD, SUM

(OUTAMT), SUM (B.PROV_TOTAL) FROM PROVISION B JOIN BRMASTER A
ON A.BRCD = B.BRCD WHERE FACCD <= 'FC00011' GROUP BY
A.CIRCLE_CD, A.CIRCLE_NM, B.SEGMENTCD, ASSETCD;
Apart from the above excel sheets data the following table dumps are also to
be provided to SBI after error generation program completion.
SLNO TABLE NAME Remarks
1. CUST_POST Main Master
2. PROVISION Main Master
3. BRMASTER Branch Master
4. SYSCHNG Borrower Wise NPA stamping dump
Step - 4: Once the loading of SBI data is over at SBI CCDP end, SBI would
also take the above dumps into their database for consolidation.
Step 5: At this juncture, Associate Banks can release their CCDP for their
branches for corrections. At this point onwards, GOLDEN GATE at SBIs end
would start replicating the following tables ongoing basis till the respective
Associate Banks CCDP activity is over i.e., these Associate Banks are acts as a
LHO at SBIs point of view and practical consideration.
SLNO TABLE NAME Remarks

1. CUST_POST
2. CUST_MOC
3. PROVISION
4. PROVISION_MOC
5. BRMASTER For changing finalised/ locked like status
36
updation.
151. Assumptions /Presumptions:
a. Approach adopted as described above due to Code differences in the

respective Associate Banks CBS as well as non-matched product codes vis-
-vis with SBI database.
b. All the CCDP programs as exist in SBI are synced with the relevant
Associate Banks provided any discrepancy preventing to do so.
c. Date of Merger for all the Associate Banks would be same, but DATA
Merger date would be different for each Associate Bank.
d. All Associate Banks works in coordination and continuous consultation with
the SBI CCDP team while preparing CCDP for each quarter falls after Date
of Merger till final DATA merger (CBS) with SBI.
e. Branch Codes of SBBJ might have changed well before Date of Merger as
these branch codes would clash with SBI.
f. Discrepancies with Customer Numbers as well as Account Numbers have
been already addressed before Date of Merger.
g. All associate Banks might have changed their parameters of CCDP from
Branch-Wise borrower-wise NPA stamping to Bank-Wide Borrower-Wise
NPA stamping as exists in SBI.
h. All the CBS NPA parameters of the relevant products to be as exist in SBIs
CBS for better explanation to the Statutory Audits subsequent to the Date
of Merger.
152. The following Circle Codes have been allotted to all the Associate Banks for
practical consolidation in CCDP reporting.
SLNO ASSOCIATE BANK CIRCLE_CODE
1. State Bank of Patiala-SBP 16
2. State Bank of Travancore SBT 17
3. State Bank of Mysore SBM 18
4. State Bank of Bikaner & Jaipur SBBJ 19
5. State Bank of Hyderabad SBH 20
7.10. IFAMS
153. After the merging, all the branches of all the 5 Associate Banks (ABs) and
Bharatiya Mahila Bank (BMB) will function as branches of State Bank of India
154. To meet the procedural requirements, following changes may have to be done:
37
a. The data is required for 14 master tables and 12transaction tables

b. The tables are listed below,
S. No Table Name Type

1 IFS_ADM_BRANCH_MST Master
2 IFS_ADM_CIRCLE_MST Master
3 IFS_ADM_DISTRICT_MST Master
4 IFS_ADM_GROUP_MST Master
5 IFS_ADM_HRMS_MST Master
6 IFS_ADM_ITEM_MST Master
7 IFS_ADM_LOCATION_MST Master
8 IFS_ADM_NETWORK_MST Master
9 IFS_ADM_OFFICER_MST Master
10 IFS_ADM_REGION_MST Master
11 IFS_ADM_STATE_MST Master
12 IFS_ADM_USER_MST Master
13 IFS_ADM_VENDOR_MST Master
14 IFS_ADM_ZONE_MST Master
15 IFS_DEP_DEPRCALC_DTL Transaction
16 IFS_FAM_ASSET_DTL Transaction
17 IFS_FAM_INVOICE_DTL Transaction
18 IFS_FAM_LEASEASSET_DTL Transaction
19 IFS_FAM_PREMISE_DTL Transaction
20 IFS_FAM_PUCFINALITEM_DTL Transaction
21 IFS_FAM_PUCPROJECT_DTL Transaction
22 IFS_FAM_PUCPROJITEM_DTL Transaction
23 IFS_FAT_FATRANSFER_DTL Transaction
24 IFS_FAT_PREMISETRANSFER_DTL Transaction
25 IFS_MOC_ASSET_DTL Transaction
26 IFS_MOC_INVOICE_DTL Transaction
c. In the main tables, Invoice ID, from Unique ID, FA ID, Premise ID, and PUCID
will be generated accordingly to the branches by IFAMS during migration.
d. The database over which the migration is to be made must be maintained
under separate schema for each and every banks-
e. BMBL users will manually feed their transactions to IFAMS at AB-UAT
environment and after verification the same data will be migrated to
respective Production database.
f. If the database is to be maintained as the same schema which is used by
the SBI currently, then the following constraints are to be handled.
The End Users PF ID should be unique.

Master Table records should align with that of SBI
38
The Branch ID, Region ID, Zone ID, Circle ID which is to be created new
should not be the same as currently used in SBI
g. Branch IDs and PF IDs should be unique in all the combined Associate Bank
AB & BMB Database.
h. Initially there will be 7 schemas in the database for 7 banks (SBI, 5 ABs &
BMB) and once it is completed for 2 branches in a bank for testing purpose.
Once the migration test is completed. All remaining data will be migrated.
After the merger notification, all AB Databases as well as BMB Database
would be merged on the SBI IFAMS Database.
i. Detailed Technical Steps can be found in the detailed SOP
155. Pre-requisites
a. All the branches which are to be merged should be fully reconciled.

b. Reconciliation will be done by the 5 Associated Banks& BMB themselves.
c. The data should be provided to SBI IFAMS team only on the following
format
csv file
The data must be separated with each fields by || (pipe symbol)
The date should be only in the following format (dd-mm-yy)
d. The Opening balance, Closing balance and the Schedule 10 data is to be

received from the entities initially before migration and the same is to be
verified after completion of the data migration
156. IFAMS Branch Operations
Define Circles, Zones, Regions, Branches, Define

Branches with PUC Premises and Fixed Assets
Lock Branches
1. Special Admin Corporate Level Define Account heads
Define Items
EOD/ SOD
All Reports including Schedule -10
Define Branches, Define Branches with PUC,
Premises and Fixed Assets within the Circle
Can create newly opened branch with the help of
2. Circle Admin LHO
mandatory Branch details
Can create IFAMS End Users(Maker, Checker)
All Reports
3. Branch Admin
Can create IFAMS End Users (Maker / Checker)
or Branch Level
Level 9 User Branch related Reports
39
Creates/ Makes Transaction

4. Maker Branch Level
View Branch related Reports
Authorizes / Rejects Transaction(s) created by
5. Checker Branch Level Maker
View Branch related Reports
7.11. Mobile Banking
157. The approval is required to continue with existing business rules of ABs for
velocity check during the report merger period. On data merger SBI business
rule will apply.
158. BMB customers will have to register afresh on the date of data merger.
159. MIS and Dashboard
a. The MIS and Dashboard will continue to provide report with Bank wise
break-up during the report merger period. From data merger date,
consolidated reports will be generated.
7.12. POS Business

160. Pre-Merger, Report Merger, Day of Data Merger & Post Merger
Sr No Activity By whom
1 Pre-Merger: From ABs and
i. Preliminary information from ABs and BMB regarding BMB
(received)
the present MAB activities, Vendor, terminal base etc.
ii. Once the date of Merger is finalized, updated branch SBI and
master to be uploaded at MAB Workflow Software as Hitachi
well as Vendor MMS Payments(HPY)
iii. Change of the linked branch / Circle of the effected SBI and
terminals Hitachi
iv. To reconcile parking account(s) used for Merchant Payments
Payment/Chargeback/Refund etc. by 7th October,
2016 and the Reconciliation Statement (entry-wise Abs and BMB
40
outstanding details) to be submitted to MAB IT Ops

Dept.
v. To settle all issues of Chargeback/Refund/Pending
amount of Merchants/Payment to Vendors-Position to ABs and BMB
be given fortnightly starting from 15/10/2016
vi. To settle Complaints on day to day basis and
Statement of Pending Complaints to sent on monthly ABs
base to IT MAB Ops Dept(devender.verma@sbi.co.in,
pushkard.mgmt@sbi.co.in)
2 Report Merger:
i. Vendor starts sharing combined MIS as per updated HPY
branch master.
ii. SBI and Vendor to effect changes due to branch
master at their respective ends. HPY and SBI
iii. ABs can create users for MAB Workflow now.
However, they are not to use the same for new
ABs
requests till date of data merger.
iv. Vendor and ABs start pasting SBI stickers on the HPY and ABs
terminals
2 Day of Data Merger:
i. Vendor shares the record of existing terminal holders HPY and SBI
via one off data for uploading in MAB Workflow
Software. This can take 10-12 days
ii. Vendor starts sharing the transaction, merchant credit HPY and MAB
files with SBI. Crediting for the transactions done on the DAU
date of merger will be done through SBI MAB DAU (
we presume that CBS would have merged by then)
iii. Users of ABs start using MAB Workflow for new
applications. Approvals to be done in line with SBI Circle/RBOs to
guidelines. As of now, Branch Managers in SBI take care
branches are the approving authority.
iv. Vendor starts sharing information related to suspicious,
on hold , chargeback transactions of the combined HPY
entity with SBI
v. Current accounts being used by ABs should be zeroed
ABs
or reconciled. The balance, if any, should be
identifiable for the out standings.
vi. Credits which have failed due to incorrect account ABs
number or other reasons and lying in sundry or other
accounts, will have to be transferred to SBI MAB DAU
along with details.
3 Post-Merger:
i. There would be a change in terminal application of the HPY
ABs terminals. Vendor will initiate uploading the same
41
through RTM (Remote Terminal Management). Success

rate of RTM is very low, say less than 10%. The
remaining terminals will have to be upgraded with SBI
application manually i.e. it would warrant field visit.
This can take 3-4 months SBI
ii. Combined purchase orders for new terminals as per
requirement
iii. All parking accounts (for merchant ABs
Payments/Chargeback etc.) to be closed within FIVE
working days after system merger
7.13. IDSPM
161. Changes in IDSPM:
SN Report Sour Frequenc Rela SBI Only/ Constraints

Name ce y ted Consolida
Data BU ted/
1+5
1 LCR CBS Monthly ALM 1+5 BU needs to validate of ABs
Reports
2 IBS CBS quarterly IBG 1+5
3 Liberalised Merc Monthly NRI 1+5 BU needs to validate of ABs
Remittance ury Cell Reports
Scheme, Data
ADF- 90
4 Details of Merc Monthly NRI 1+5 BU needs to validate of ABs
remittances ury Cell Reports
made by Data
NRO +
account, CBS
ADF-91
5 CIC Data CBS Monthly Exter SBI Only, Product, Activity code, scheme
nal ABs need code Org code, Industry code
CIC to provide based. Mapping required from
the data O&TS. Since above mentioned
as they parameters will not be aligned
providing with SBI till data merger, so it is
presently
not possible to give this data of
42
till data ABs.

merger.
6 Statement CBS Quarterly BOD 1+5 BU needs to validate of ABs
on Reports
reconciliati
on of
clearing
differences
ADF-156
7 Statement CBS Quarterly BOD 1+5 BU needs to validate of ABs
on the Reports
position of
balancing
of books,
ADF-157
8 Statement CBS Quarterly IM& 1+5 BU needs to validate of ABs
on quick A Reports
special
audit of
sundry
deposits/
suspense
account,
ADF-158
9 RBS CBS Monthly Com 1+5 Murex data will be of merged
plian SBI(consolidated) and CBS data
ce will be of SBI only.
10 No. of ATM ATM Quarterly ATM Consolidat Product, Activity code, scheme
Data INS ed code Org code, Industry code
based. Mapping required from
O&TS. Since above mentioned
parameters will not be aligned
with SBI till data merger, so it is
not possible to give this data of
ABs. BU need to take ABs data
from respective ABs.
11 No. of Crds ATM Monthly ATM Consolidat
& Txn Data INS ed
12 SMR-6 CCP Monthly CPP SBI Only, Product, Activity code, scheme
D+C D ABs need code Org code, Industry code
BS to provide based. Mapping required from
43

presently not possible to give this data of
till data ABs. BU need to take ABs data
merger. from respective ABs.
13 SIBC F1+ Fortnightl CPP SBI Only, Product, Activity code, scheme
CBS y D ABs need code Org code, Industry code
to provide based. Mapping required from
14 GLC CBS Monthly SBI Only, Product, Activity code, scheme
ABs need code Org code, Industry code
15 PSA CCP Quarterly SME SBI Only, Product, Activity code, scheme
D+C /Annual /AG ABs need code Org code, Industry code
BS RI to provide based. Mapping required from
16 Form - A NW Weekly GM SBI Only, BU need to take ABs data from
SA + U ABs need respective AB. Murex data will
Mure to provide be of merged SBI(consolidated)
x the data and CBS data will be of SBI
Wee as they only.
kly+ providing
Man presently
ual till data
Data merger.
17 Long Term CBS Quarterly FRT SBI Only, Product, Activity code, scheme
44
Finance to provide based. Mapping required from

18 DEAF CBS Monthly CBS SBI Only, Product, Activity code, scheme
19 SHG CBS Monthly SBI Only, Product, Activity code, scheme
20 Income Tax CBS Monthly SBI Only, Product, Activity code, scheme
Data ABs need code Org code, Industry code
21 Statement BCG Monthly CIBE SBI Only, BU need to take ABs data from
on A+D R/C ABs need respective AB.
reconciliati raft ompl to provide
on of inter- + ianc the data
branch e as they
RTC
accounts, providing
+IBT
ADF-155 presently
S+I
OI+ till data
merger.
45
CBS
7.14. HRMS
BACKGROUND
162. State Bank of India is in the process of acquisition of all the 5 Associate Banks
and Bharatiya Mahila Bank Limited (BMBL). As per advice of the Corporate
Centre effective date of acquisition of all the 6 entities will be same and it will
be Report Level Merger w.e.f. that date because, CBS Data Merger will take
place in phased manner with in two months of Report Level Merger.
PROCEDURE FOR HANDLING ACTIVITIES BETWEEN REPORT LEVEL MERGER AND

CBS DATA MERGER
163. There will not be any impact of various reports to be generated from HRMS
Data Base in case of all the 5 Associate Banks (ABs) because, these are
already on HRMS Platform.
164. Salary to the employees of BMBL can only be paid through HRMS System after
migration of BMBL to SBI CBS because, the same is required for effecting
financial transactions (debits and credits). However, if the migration of BMBL to
SBI CBS will take place after 1st of the month then salary to the employees of
BMB will be paid w.e.f. next month. Various Reimbursements are to be paid
manually to the employees of BMBL till 31.03.2017 in terms of approval of the
Steering Committee. Hence, there will not be any issue between Report Level
Merger and CBS Data Merger in case of BMBL.
165. In HRMS System all the 5 ABs are having different Company Code and
Payroll as per details given below:-
COMPANY
NAME OF THE ASSOCIATE BANK PAYROLL
CODE
STATE BANK OF BIKANER & JAIPUR (SBBJ) 1000 BJ
STATE BANK OF HYDERABAD (SBH) 2000 HY
STATE BANK OF MYSORE (SBM) 4000 MY
STATE BANK OF PATIALA (SBP) 5000 Y1
STATE BANK OF TRAVANCORE (SBT) 7000 TV
46
166. All the reports relating to ABs can be generated from HRMS Department, CC,
Navi Mumbai. But, the work relating to payment of Salary, Allowances and
various Reimbursements/Perquisites to ABs employees including debits and
credits is being handled by HRMS Team of respective AB centrally at their
Head Office Level based on the above mentioned Company Code and Payroll.
Hence, till CBS data merger this work will be handled by the same teams at
Head Office Level of respective AB because, the DAU of HRMS Department,
CC, Navi Mumbai will not be in position to effect debits & credits relating to
ABs employees, having accounts at their respective Bank.
167. However, on Salary Slip and reports generated from HRMS System name of
State Bank of India will appear in case of all the employees (including those of
ABs) w.e.f. Report Level Merger date.
168. If there will be any difference between ABs and SBI in regard to payment of
Salary, Allowances and various Reimbursements/Perquisites the same will be
controlled as per existing system i.e. through Company Codes of ABs between
Report Level Merger and CBS Data Merger.
169. After CBS Data Merger the difference between ABs and SBI in regard to
payment of Salary, Allowances and various Reimbursements/Perquisites will be
handled through Tables in which data of employees of ABs will be maintained
along with ABs Company Code. The required Tables have already been
created in HRMS System.
170. Presently in SBI salary is being paid on 25th of every month and in ABs it is
paid on 26th (SBP) and 27th (all other ABs). After CBS Data Merger of AB(s), 5
to 6 days period will be required for processing and payment of salary to
ABs employees along with SBI salary. Accordingly, if CBS Data of one/more
AB(s) will be merged after 20th then either the respective AB(s) should pay the
salary at their end before CBS Data Merger or the SBIs salary will require to
be postponed taking into consideration the above mentioned processing time
and the date of payment of salary will be decided at the material time.
7.15. BID
P-Report: Merger of Associate Banks
171. Background: The granular data of the P Report is being sent to BID by O&TS
department and same is loaded in BID server and various reports required by
PPR and other CC departments are generated.
47
172. The two important reports namely, Part-1 & Part-2 are prepared by BI
Department at every month end and provided to PPR Department, Corporate
Centre for preparation of CENMAC, and other presentation. This report
contains data from March 2014 related to Business (Advance & Deposits) and
P&L (income and expenses).
173. In order to prepare these two reports we will require Business & P&L figures of
Associate Banks w.e.f. March 2014. In the meeting held at GITC, Belapur on
21-09-2016, TCS showed their inability to provide last 36 months (from Mar-
2014) data in the P-Report format. So, it was decided that TCS will provide
branch-wise CGL-wise bid-code-wise data for all the months along with the
latest CGL-bid mapping, and BI department will convert this into the required
format to load into their system and provide the reports to PPR Department.
174. It was also discussed that updated Branch Master (with SBI Branch Codes
assigned to Associate Banks will be provided along with Associate Banks P-
Report generated for 30-September to generate P-Report and provide to
associate banks for checking and confirming the CGL-bid codes mapping used.
If P-Report generated for 30-Sep found to be correct than historical data can
be extracted and provided to BID by using the confirmed CGL-bid mapping. In
case of any discrepancies respective associate banks will look into the CGL-bid
code mapping and ensure that it is correct.
175. It is observed that detailed Government Business Table related data will not be
available in the historical data. However total government commission will be
available as part of miscellaneous business income.
176. It is also observed that as on report merger date, all P&L related fields data
will be initialized (i.e. zero) and on this report merger date, P-Report extract
will be provided to BID before initializing these fields, and BID will preserve
this data and will add it to the respective heads of each branch to generate
the post report merger date reports.
7.16. Treasury
177. Considering the low volume of Bharatiya Mahila Bank (BMB) the outstanding
deals will be inserted into manually into Murex which will avoid the time delay
and cost in development of STP interface. Steering committee on merger of
associate banks has proposed two approaches for the merger of 5 associate
banks with SBI. The first approach is the merger at report level in which case
database of all ABs will not be merged at a single instance as it requires huge
downtime, instead the reports of SBI and 5 Associate Banks will be
consolidated from 6 instances to generate reports as a single entity.
48
Considering the complex nature of treasury operations and volume of reports,

the merger at reports level is not a feasible approach.
178. The second approach proposed is the merger at database level. In this
approach the CORE databases of SBI and CORE databases of 5 Associate
Banks will be merged at later date but the treasury databases of 5 Associate
Banks will be merged at a single instance and the outstanding deals will be
imported into Murex on the cut-off date. Since the versions of the Mercury-Fx
application used at AB branches and SBI branches are different, it will create
many problems in operations. Therefore, the forex enabled branches of ABs
will stop using their version of Mercury-Fx application from day one after cut-
off date and will start using the Mercury-Fx application of SBI. They will call
dealers of SBI for Dealer Rates whenever required and also can access Card
Rates published by SBI. This will bring all the forex enabled branches of SBI
and ABs on a single application platform. The proposed architecture is
presented in next page.
179. SBI Mercury-Fx has interfaces with SBI CBS/Exim Bills and Murex but there is no
interface between SBI Mercury-Fx and Associate Bank CBS and Exim Bills,
which Credence has promised to develop the interface and release for UAT by
20th October 2016.
Vertical/Section wise approaches for the merger of Associate Banks are described
below:
180. Merchant Desk: As described above all the forex enabled branches of the
Associate Banks will start using Mercury-Fx version of the SBI and will obtain
forex rates from the Dealers of SBI and report transactions to them since day
one of merger.
181. SPOT DESK: Open positions of the ABs will be imported into Murex through
the interface developed for the purpose. For facilitating merger and
reconciliation of positions, we will be creating five new portfolios for each
portfolio of the SBI depending upon the open positions of ABs.
Existing Portfolios New Portfolios for 5 ABs

IN-MU-CVR-SPOT-IB IN-MU-CVR-SPOT-IB-sbbj
IN-MU-CVR-SPOT-IB-sbh
IN-MU-CVR-SPOT-IB-sbm
IN-MU-CVR-SPOT-IB-sbp
IN-MU-CVR-SPOT-IB-sbt
IN-MU-CVR-SPOT-MER IN-MU-CVR-SPOT-MER-sbbj
49
IN-MU-CVR-SPOT-MER-sbh
IN-MU-CVR-SPOT-MER-sbm
IN-MU-CVR-SPOT-MER-sbp
IN-MU-CVR-SPOT-MER-sbt
182. FORWARDS DESK maintains their positions in

IN-MU-CVR-SWP-IB IN-MU-CVR-CVR-IB- sbbj
IN-MU-CVR-CVR-IB-sbh
IN-MU-CVR-CVR-IB-sbm
IN-MU-CVR-CVR-IB-sbp
IN-MU-CVR-CVR-IB-sbt
IN-MU-CVR-SWP-MER IN-MU-CVR-CVR-MER-sbbj
IN-MU-CVR-CVR-MER-sbh
IN-MU-CVR-CVR-MER-sbm
IN-MU-CVR-CVR-MER-sbp
IN-MU-CVR-CVR-MER-sbt
183. CROSSES DESK has no separate folders but they use above folders with
different currencies hence no new requirement for creation of portfolios.
184. Structured Products Desk/Derivatives Desk: ABs do not have any open
position in Derivatives deals and hence no new requirement during migration.
185. EQUITY & MUTUAL FUND DESK: Security wise outstanding deals or one deal
per security (as provided) can be imported into Murex as on the date of
merger.
MU-INEQ-AFS MU-INEQ-AFS_sbbj
MU-INEQ-AFS_sbh
MU-INEQ-AFS_sbm
MU-INEQ-AFS_sbp
MU-INEQ-AFS_sbt
MU-INEQ-AFS-NQ MU-INEQ-AFS-NQ_sbbj
50
MU-INEQ-AFS-NQ_sbh
MU-INEQ-AFS-NQ_sbm
MU-INEQ-AFS-NQ_sbp
MU-INEQ-AFS-NQ_sbt
MU-INEQ-HFT MU-INEQ-HFT_sbbj
MU-INEQ-HFT_sbh
MU-INEQ-HFT_sbm
MU-INEQ-HFT_sbp
MU-INEQ-HFT_sbt
MU-INEQ-HTM-PRS MU-INEQ-HTM-PRS_sbbj
MU-INEQ-HTM-PRS_sbh
MU-INEQ-HTM-PRS_sbm
MU-INEQ-HTM-PRS_sbp
MU-INEQ-HTM-PRS_sbt
MU-INEQ-AFS-STG MU-INEQ-AFS-STG_sbbj
MU-INEQ-AFS-STG_sbh
MU-INEQ-AFS-STG_sbm
MU-INEQ-AFS-STG_sbp
MU-INEQ-AFS-STG_sbt
MU-INEQ-DEST/DURATION MU-INEQ- DURATION_sbbj
MU-INEQ- DURATION_sbh
MU-INEQ- DURATION_sbm
MU-INEQ- DURATION_sbp
MU-INEQ- DURATION_sbt
MU-INMF-LQD-T01 MU-INMF-LQD-T01_sbbj
MU-INMF-LQD-T01_sbh
MU-INMF-LQD-T01_sbm
MU-INMF-LQD-T01_sbp
MU-INMF-LQD-T01_sbt
MU-INMF-EQY-T01 MU-INMF-EQY-T01_sbbj
MU-INMF-EQY-T01_sbh
MU-INMF-EQY-T01_sbm
MU-INMF-EQY-T01_sbp
51
MU-INMF-EQY-T01_sbt
186. Reports to be modified to take effect of deals imported on account of ABs

merger.
R7-Equity Blotter,
R11-AFS Buy,
R11-HFT Buy,
R13-AFS Sale,
R13-HFT Sale,
R-7 Trade Blotter (MF)
Equity Holding Summary Report in HFT.
187. PRIVATE EQUITY DESK: The outstanding deals in each security of the private
equity will be imported into respective portfolios.
IN-MU-INVC-AFS-CA IN-MU-INVC-AFS-CA-sbbj
IN-MU-INVC-AFS-CA-sbh
IN-MU-INVC-AFS-CA-sbm
IN-MU-INVC-AFS-CA-sbp
IN-MU-INVC-AFS-CA-sbt
IN-MU-INVC-VC-AFS IN-MU-INVC-VC-AFS-sbbj
IN-MU-INVC-VC-AFS-sbh
IN-MU-INVC-VC-AFS-sbm
IN-MU-INVC-VC-AFS-sbp
IN-MU-INVC-VC-AFS-sbt
IN-MU-INVC-VU-HTM IN-MU-INVC-VU-HTM-sbbj
IN-MU-INVC-VU-HTM-sbh
IN-MU-INVC-VU-HTM-sbm
IN-MU-INVC-VU-HTM-sbp
IN-MU-INVC-VU-HTM-sbt
Reports Needs to be changed: R9 Holding Report.
188. IRM DESK:
52

MUSLR-HTM-T01 MU-HTM-sbbj
MU-HTM-sbh
MU-HTM-sbm
MU-HTM-sbp
MU-HTM-sbt
MU-SLR-AFS-T01 MU-SLR-AFS-sbbj
MU-SLR-AFS-sbh
MU-SLR-AFS-sbm
MU-SLR-AFS-sbp
MU-SLR-AFS-sbt
MU-SLR-HFT-T01 MU-SLR-HFT-sbbj
MU-SLR-HFT-sbh
MU-SLR-HFT-sbm
MU-SLR-HFT-sbp
MU-SLR-HFT-sbt
MU-NSLR-AFS-T01 MU-NSLR-AFS-sbbj
MU-NSLR-AFS-sbh
MU-NSLR-AFS-sbm
MU-NSLR-AFS-sbp
MU-NSLR-AFS-sbt
MU-NSLR-HFT-T01 MU-NSLR-HFT-sbbj
MU-NSLR-HFT-sbh
MU-NSLR-HFT-sbm
MU-NSLR-HFT-sbp
MU-NSLR-HFT-sbt
MU-NSLR-HTM-T01 MU-NSLR-HTM-sbbj
MU-NSLR-HTM-sbh
MU-NSLR-HTM-sbm
MU-NSLR-HTM-sbp
MU-NSLR-HTM-sbt
MU-MM-CD-INV MU-MM-CD-INV-sbbj
53
MU-MM-CD-INV-sbh
MU-MM-CD-INV-sbm
MU-MM-CD-INV-sbp
MU-MM-CD-INV-sbt
MU-MM-CP-T01 MU-MM-CP-sbbj
MU-MM-CP-sbh
MU-MM-CP-sbm
MU-MM-CP-sbp
MU-MM-CP-sbt
MU-TRIR-VAN-OIS MU-TRIR-VAN-OIS_sbbj
MU-TRIR-VAN-OIS_sbh
MU-TRIR-VAN-OIS_sbm
MU-TRIR-VAN-OIS_sbp
MU-TRIR-VAN-OIS_sbt
MU-TR-IR-IRF MU-TR-IR-IRF_sbbj
MU-TR-IR-IRF_sbh
MU-TR-IR-IRF_sbm
MU-TR-IR-IRF_sbp
MU-TR-IR-IRF_sbt
MU-MM-CBLO-T01 MU-MM-CBLO-T01-sbbj
MU-MM-CBLO-T01-sbh
MU-MM-CBLO-T01-sbm
MU-MM-CBLO-T01-sbp
MU-MM-CBLO-T01-sbt
MU-MM-CALL-T01
MU-MM-R-LAF-T01
MU-MM-R-MKT-COR
MU-MM-R-MKT-T01 These are short duration deals which will
be inserted into Murex, outstanding if
MU-MM-R-MSF
any.
MU-MM-REFIN-T01
MU-MM-RR-LA-T01
MU-MM-RR-MK-COR
MU-MM-RR-MK-T01
54
Elaboration/action plan in the following areas are expected to be provided

by respective units/verticals.
189. P&L Desk: Valuation of Securities
190. SECURITY SERVICES BRANCH: To ensure the correctness of the data like rate
convention, RICs, data related to RBI tranche1, all masters related to Bonds and
Equity will be created by officials at SSB based on the master creation forms
provided by ABs. The formats for master creation (Part1 & Part 2) will be
provided by SSB to ABs).
191. Reports required by SSB will be modified by IT-TSS to include the newly
created portfolios of ABs and reflect the deals related to ABs. Therefore, list
of all reports to be forwarded by SSB at the earliest.
192. GLOBAL MARKETS UNIT KOLKATA (GMU-K): Reports related to

NOOP,AGL-IGL etc. will be modified by IT-TSS to take effect of merger of
ABs. Banking book related data for ABs will be provided CBS of ABs on daily
basis. Therefore, list of all reports to be forwarded by GMU-K at the earliest.
193. MID-OFFICE: Counterparty limits may have to be reviewed to avoid breach.
194. MARKET RISK MANAGEMENT DEPARTMENT: VaR related reports will be

revised to take effect of merger of ABs. VaR numbers as on 30.09.2016 data
will be calculated from Murex system for test purpose. Credence Analytics will
extract all deals data from their system and provide the outstanding deals
which will be imported into Murex and VaR will be calculated.
195. Other Issues:
a. After merger of the ABs, a few officials will be absorbed into Global
Markets dealing room as well as in the back office. Since they will not be
conversant with Murex Application, Global Markets Department need to
identify such officials and arrange for their training in advance.
b. The obtaining licenses from Murex for the new users, Global Markets need
to provide the count of such officials to IT-TSS for further action.
c. Indemnity from customers if any, needs to be obtained.
d. Legacy system need to keep operational for a few more years for
reference of data, SLA agreements need to be renewed if required.
55
8. Forbearance Requirement
196. Report level merger will ensure that all the 5 Assoiate Banks are amalgamated
with State Bank of India. Reporting to Reserve Bank of India and to other
Statutory Bodies will be made for the single amalgamated entity ie State Bank
of India.
197. Due to the tehnical challenges in Data Meger of all 5 Associate Banks on the
same day, the Data Merger of the various Associate Banks are scheduled over
a period of 6-8 weeks from the date of Report Merger. Due to this there may
be challenges in complying to various reporting requirements as the data for
submission may have to be amalgamated from the various source systems and
reported. This may result in delay or non-submission of certain statutory
infomation to the vaious regulators.
198. Due to the deferred Data Merger schedule there may be challenges in
Settlement of various Payment Systems related transactions, Clearing
Transactions as the Settlement Accounts of the erstwhile Associate Banks may
have to be continued well past the Report Meger date, which may require
regulatory approvals / forebearance.
199. We give below the details of various functional areas which may require such
regulatory forebearance:
a. Continuation of RTGS Gateways of the various Associate Banks for a period of

6-8 weeks from the date of Report Merger or any other date adminsitratively
decided.
b. Continuation of NEFT Gateways of the various Associate Banks for a period of
6-8 weeks from the date of Report Merger or any other date adminsitratively
decided.
c. Continuation of Settlement Accounts with Reserve Bank of India of the various
Associate Banks for a period of 6-8 weeks from the date of Report Merger or
any other date adminsitratively decided.
d. The settlement with RBI/NPCI shall continue to be separate to avoid problems
in bank wise settlement. SPOC from ABCD shall take up the matter with
RBI/NPCI for extensions for continuation of Bank wise settlement.
e. If RBI continues to do the settlement with respective ABs in their accounts with
RBI, no change would be required in any CTS operations. SPOC from ABCD
shall take up the matter with RBI/NPCI for extensions for continuation of Bank
wise settlement.
f. Continuation of Settlement Accounts with State Bank of India / Other
Settlement Banks of the various Associate Banks for a period of 6-8 weeks
from the date of Report Merger or any other date adminsitratively decided.
56
g. In case of change of existing TAN number of branches of Associate Banks after

Report Merger, multiple remittances under 2 TANs and filing of 2 returns under
2 TANs.
h. In case of change in Service Tax number of the various Associate Banks after
Report Merger date, the process and remittance changes required.
i. Business Department to decide on waiver of service charges or otherwise, for
RTGS / NEFT / GRPT transactions from SBI to ABs and vice-versa, and
communication to be given to branches).
j. The commission / charges currently applicable to ABs customers will continue
during the report merger period and on data merger SBI charges will be
applicable.
57
9. Customer Notice
200. Report Level Meger will be an well published event, there may be issues with
regad to Customer Service. In order to address the needs of the customers and
also to streamline the opeations post Report Meger, following Customer
notification may be issued:
===============================================
201. To All Customers of erstwhile Associate Banks of State Bank of India
We Welcome you to State Bank of India.
All the Associate Banks of State Bank of India have been merged with State Bank
of India effective DD/MM/YYYY. However the technical meger of these Banks
with State Bank of India is likely to be completed with in next 6-8 weeks. Till then,
all customers of erstwhile Associate Banks are requested to continue to transact
with their respective Bank branches only. Please do not drop your Cheques for
clearing at any other Associate Banks or State Bank of India branches till further
notice.
OUR VALUABLE CUSTOMERS ARE HEREBY ADVISED TO USE THE Bar Code
Based Pass Book Printing Kiosks IN swayam MACHINES OF RESPECTIVE BANK
ONLY TILL FURTHER NOTICE.
Transfer / Remittances between State Bank of India and erstwhile Assocaite Banks,
between estwhile Associate Bank branches will be handled FREE OF COST.
We seek co-operation from the esteemed customers of erstwhile Associate Banks.
===============================================
202. Customer notice Mobile Banking
203. As approved in the action taken report no GITC/CTO/ITMB/

20160920/MG/681, the customer will be communicated 15 days in advance
to the customers in the form of SMS message, Message through ATM and
suitable message will be shown through the application which will guide the
customers to download the SBI app from the play store.
204. On Report Merger :
a. Customers to continue using SB Anywhere Associate Banks app till further
notice.
205. On Data Merger :
58
a. Customers to download the SBI Anywhere app from respective play

stores and login using existing credentials.
b. Service charges for IMPS transaction have been revised, Refer FAQs
section of mobile app for details.
206. Mode of communication

a. SMS notification : to be sent by respective ABs HO to their customer 15
days prior to the report merger
b. Electronic / Print Media: to be arranged by Customer Service Dept. as part
of consolidated notice to the customer.
207. The approved mobile application SOP on customer notice shall be provided to
customer service dept for customer notice and awareness.
208. NOTIFICATION TO ASSOCIATE BANK CUSTOMERS Internet Banking:
209. SMS notification and Pre-login Scroll message for Merchant Payments: Since
there will not be any change in Merchant/Aggregator Payment gateway page
for Associate Banks on Report Merger, customer may get confused on which
bank to select for merchant payment. Hence, SMS will be sent to all Associate
Bank customers to their INB registered mobile number to continue selecting their
respective Associate Banks for merchant payments till further notice.
210. Similar Pre-login informative scroll message will also be displayed in

www.onlinesbi.com Home page as informative to Associate Bank customers.
211. SMS notification on Data Merger: After the Data Level Merger of every
Associate Banks, SMS will be sent to the merged Associate Bank customers to
select the State Bank of India option on the payment gateway while doing
merchant payments.
59
10. Activities to be done at GITC on Report

Merger Date
212. All activities relating to Data Level Merger date are tabulated hereunder:
a) BGL MAPPING ACTIVITY:

Sr. Name of BGL Account Mapping Activity Time of By
No. Office Account No. to be Activity Whom
mapped
1 AGCL Drafts i) 98617 The outstanding amount in Data Data
Old Scheme (AGCL these BGL accounts is to be Merger Merger
General mapped to same BGL Date Team at
Account) accounts in SBI with same GITC
place (No movement of
ii)98618
amount from existing
(AGCL Draft
location)
Paid Account)
2 AGCL Drafts i)3199931- The outstanding amount in Data Data
New Scheme (Agency these BGL accounts is to be Merger Merger
Clearing mapped to same BGL Date Team at
General accounts in SBI with same GITC
Account-New) place (No movement of
ii)3199932 amount from existing
(Agency location)
Clearing Draft
Payable A/c-
New)
iii)3199933
(Agency
Clearing Draft
Cancellation
A/c New)
3 IBD (Drafts) 98627 (Draft The outstanding amount in Data Data
Account) this BGL account is to be Merger Merger
mapped to same BGL Date Team at
account in SBI with same GITC
location)
4 IOIs (Drafts) i)98602 (IOI The outstanding amount in Data Data
Old) these BGL accounts is to be Merger Merger
ii)3199492
accounts in SBI with same
60
(IOI New) place (No movement of GITC

location)
New BGL Account NO. Before O&TS
98932 is to be created in Data Dept. /
SBI Merger of Data
1st Merger
Associate Team at
Bank GITC
5 ABSOT(Drafts) 98932 The outstanding amount in Data Data
this BGL account is to be Merger Merger
account in SBI with same GITC
location)
6 IBTS i)2399776 The Outstanding amount in Data Data
(IBTS Non- these BGL Accounts is to be Merger Merger
DTL if Debit) mapped in same BGL Date Team at
accounts in SBI with same GITC
ii)2399775 amount from existing
(IBTS Non- location)
DTL if Credit)
iii)2399774
(IBTS DTL if
Debit)
iv)2399773
(IBTS DTL if
Credit)
v)2399778
(IBTS
Suspense
Account)
vi)2399777
(IBTS Sundry
Account)
7 BCGA 98605 The Outstanding amount in Data Data

these BGL Accounts is to be Merger Merger
98611
mapped in same BGL Date Team at
accounts in SBI with same GITC
location)
61
- - - - End of Document - - - -
62

Consolidated SOP V 3 2016 12 22 Post Report Merger PDF

Загружено:

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

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

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

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

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

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

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

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

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

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

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

Consolidated SOP V 3 2016 12 22 Post Report Merger PDF

Загружено:

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

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

State Bank of India

SBI Group Technology Dept

Consolidated Standard Operating Procedure

For all Applications

Post Report Level Merger

3. Changes in CBS on Report Merger at Associate Banks ......................................... 7

4. CBS and other Branch Operations & Settlements .................................................. 8

5. Other Applications and Operations & Settlements............................................... 14

5.1. GBSS ...............................................................................................................14

5.2. Exim Bills ........................................................................................................16

5.3. Vendor Payment System (VPS) .....................................................................17

5.4 Financial Inclusion and Government Schemes (FI & GS).............................18

5.5. Loan Origination System (SME & Agri).........................................................19

5.6. New Pension Scheme (NPS) ..........................................................................20

5.7. ATAL Pension Yojana (APY) .........................................................................21

6. Channel Operations & Settlements....................................................................... 22

6.1. Internet Banking .............................................................................................22

6.2. Mobile Banking ..............................................................................................24

6.3. Swayam (Barcode based Passbook Printing Kiosk) ....................................27

7. SOP for Controlling Offices and Corporate Office Units .................................... 29

7.1. Operations - Payments Systems ...................................................................29

7.2. FRT Department..............................................................................................30

7.4. LOS Retail .......................................................................................................31

7.5. LOS Agri / SME............................................................................................32

7.7. NPS .................................................................................................................34

7.8. APY .................................................................................................................34

7.9. CCDP ...............................................................................................................34

7.10. IFAMS .............................................................................................................37

7.11. Mobile Banking ..............................................................................................40

7.12. POS Business..................................................................................................40

7.13. IDSPM .............................................................................................................42

7.14. HRMS ..............................................................................................................46

7.15. BID ..................................................................................................................47

8. Forbearance Requirement ..................................................................................... 56

9. Customer Notice ................................................................................................... 58

10. Activities to be done at GITC on Report Merger Date ..................................... 60

List of abbreviations used in this document

SBI State Bank of India

CBS Core Banking System

BGL Banking General Ledger

UAT User Acceptance Test

SIT System Integration Test

INB Internet Banking

BMB Bharatiya Mahila Bank

ABs Associate Banks of SBI

SBH State bank of Hyderabad

SBBJ State Bank of Bikaner and Jaipur

SBM State Bank of Mysore

SBP State Bank of Patiala

SBT State Bank of Travancore

6. In order to have clarity on operations and operating in the interim period

7. All the application owners have submitted their Standard Operating

11. Data from CBS flows to many down-stream systems:

3. Changes in CBS on Report Merger at Associate

a. Rate of Interest on Deposits to be aligned with SBI

a. All pending queues on the date of merger to be cleared

4. CBS and other Branch Operations & Settlements

18. Teller Log-In

19. Cash Drawer

20. Vault Teller

Vault Teller can log-in and perform Cash-in/ Cash-Out normally.

21. Cash Receipts

22. Cash Payments