Core Banking System FAQ

8/18/2019 Core Banking System FAQ

1/38

India Post

FINACLE CBS – FAQs & User Guide


2/38

FAQ – User

2

Finacle CBS FAQ’s & User Guide

Table of Contents

1.1. ( , , .)..................................... 4

1.2. ( A ) ............................................................................................................... 4 1.3. A A AA ................................................................................. 4 1.4. A A A ............................................................................. 4

1.1. A ......................................................................................................................... 5 1.1.1. AE F E FFCE E CE ADDE BEG ED G AB .................................. 5 1.1.2. AB EABED A E ACC EE .......................................................................................... 5 1.2. A A ................................................................................................................... 5 1.2.1. GAE E E DE DE EG E ..................................................................... 5 1.2.2. GAE E E DE ACCE DED ................................................................................. 7 1.2.3. GAE/GA E E ........................................................................................................ 7 1.2.4. GAE E E E DEF E EAC E ........................................................................ 8

1.3. A ........................................................................................................................... 9 1.3.1. C/ ACC FECED ........................................................................................................... 9 1.3.2. CEFCAE AAABE FACE ( ECD GAED) ................................................................ 10 1.3.3. E DG DCAGE F CEFCAE .............................................................................................. 10 1.3.4. ABE CEFCAE ............................................................................................................ 10 1.4. A A ................................................................................................................... 11 1.4.1. AGE D CEA EBAG ......................................................................................................... 11 1.4.2. ACC BE F E AGE .................................................................................................. 11 1.4.3. AGE D AA CEAED FACE CA ACE AD D. .......................................................... 12 1.4.4. ABE G E AGE D AD DED. .............................................................. 12 1.5. ............................................................................................................................ 12 1.6. . ............................................................................. 12

1.7. A ............................................................................................................................... 14 1.7.1. AD CEAG E DCAE E .................................................................................. 14 1.7.2. E DAED ................................................................................................................... 15 1.7.3. E E AD F CEE................................................................................................. 16 1.7.4. CAGE F BGE BC F A CEE ACC AD GAED A BGE AD EE AAABE BA CEE BE? ............................................................................................................... 17 1.7.5. AD CEAG E CDE EE F A ACA BA AD BAC CBA ...... 17 1.7.6. CE F ADG B CCA AG AB A E BA & BAC: ........................................ 19 1.7.7. ADE A CEE FACE? .................................................................................. 19


3/38

FAQ – User

3


E E AD F BE EED E: .......................................................................................... 19 1.7.8. A E CEDE F A ' A A' CEE. F EE D F CEE ECE CAGEA BE CECED) ............................................................................................................................................ 20 1.7.9. CAG CD BE DE DE CEE E . .............................................................................. 20

1.8. AA A A A ........................................................................... 21 1.9. A ...................................................................................................................... 22 1.9.1. A ACC CE E ............................................................................................................... 24 1.9.2. EAE CE E .................................................................................................................. 25 1.9.3. DA B ACC CE E .................................................................................................... 27 1.10. A/ A A ......................................................................................... 28 1.10.1. D A ACC AFF DE G CA ECE ........................................................................... 29 1.10.2. AAC GEG ED C/ E .......................................................................... 30 1.11. A A A............................................................. 31 1.12. AAA AA ...................................................................................... 31 1.13. A A A A .......................................................................... 32 1.14. AA A A . ............................................................. 32 1.15. ........................................................................................................... 32

1.16. ...................................................................................................................................... 32 1.16.1. E EE A FA ED ................................................................................................................ 32 1.16.2. E E ED BCG ADA. ........................................................................................ 33 1.17. A AAA A .................................................................................. 33 1.17.1. C F E A FFCE ................................................................................................ 33 1.17.2. C F 1 .............................................................................................................. 37 1.18. A .......................................................................................................... 37 1.19. A A . ................................................................................... 38

1.1. A ..................................................................................................................... 38 1.2. AA A ............................................................................................................................. 38


4/38

FAQ – User

4


1.1. ( , , .)

For the Finacle CBS application, the configuration details are specified in the belowattached zip file.

Finacle Desktopsetting version1 1.zi

1.2. ()

For the proper printing of the passbook, the Passbook Printer needs to be configured asper the below specified document.

Passbook_printer_settings.zip

1.3. A

Please see below the word document for the complete ATM Process and its PINmanagement.

Creation ofPlaceholder ATM S

Interim process ofhandling ATM oper

1.4. Please see below the word document for the complete E-Banking password and PIN

printing.

Finacle EbankingProcedure-Passwor

Ebanking-pin.pdf


5/38

FAQ – User

5


1.1.

1.1.1. Name of the office or the customer address being printed wrongly in Passbook

Issue Reported : For.e.g It is reported by the counter PA at Srikakulam HO, thename of the PostOffice in the passbook front page is showing as SRIKALAHAS,ANDHRA PRADESH, INDIA, 532001. instead of SRIKAKULAM, ANDHRAPRADESH, INDIA, 532001.

Solution: Check the city code linked to the address of the Post office or thecustomer address. Then validate the city code description in the menu HRRCDM.Either the HRRCDM city code in the customer's address / Post office address has tobe changed in the address details or the description of the particular code has to bechanged in HRRCDM menu.

HRRCDM access is given to DOP Operations team to maintain the details.

1.1.2. Passbook not enabled at the account level

Solution: The passbook is not enabled at the account level. The same has to bemodified at the account level for passbook printing.

For PPF account, the menu HACM has to be used for modification of the field A/Cstatement in the General Details tab.

For SCSCC accounts, the menus CSCAM/SCSSMAV to be used

For MIS accounts, the menus CMISAM/MISAMAV to be used

1.2. 1.2.1. Signature view issues due to desktop settings not proper


6/38

FAQ – User

6


Solution: Please check the desktop settings and then try viewing the signature.


7/38

FAQ – User

7


1.2.2. Signature view issues due to access not provided

Solution: The issue is present due to the access not provided to the particular user.The changes have to done in the user creation by modifying the USER GROUPNAME to ADMIN

User to contact the DOP Operations team to get the issue rectified.

1.2.3. Signature/photograph view issue

Error Screen shot

Solution


8/38

FAQ – User

8


Check for the signature view from other user id and other location, preferably DOPOperations Team. Issue may be with the desktop settings. The above issue is not occurringfor the below user id as per the screenshot attached.

Solution Screenshot

1.2.4. Signature view issues - Steps to identify the exact issue

Issue Reported : Signature is not displayed

Solution: The signature not displayed might be due to several factors like

• Desktop Setting not done properly ]

• Access not given to the user. ] Explained in 1.2.1 ,1.2.2 and1.2.3 above

• Signature not uploaded properly

If signature is not uploaded in Finacle, system will show the belowdetails:


9/38

FAQ – User

9


• Signature not migrated due to huge size.

Any signatures present in Sanchay Post database which is above 30kb size shall bedropped while migrating in Finacle. After the data upload, as a part of the recon details,Infosys shall provide the details of signatures dropped during upload. POs need to ensurethat when the customer whose signtaure is dropped comes to the PO, fresh signaturemandate is captured using a new 'account opening form' and customer's transaction isallowed based on the fresh signature mandate. POs to ensure that the account openingform is clearly identified by writing 'Signature mandate' on top of first page of the form .They should also clearly mention the CIF id and account number on the form. The formshall be sent to CPC for scanning and upload of signature in Finacle.

1.3.

1.3.1. NSC/KVP accounts not fetched

Error Screen shot


10/38

FAQ – User

10


Solution

The input criteria provided in the Registration No. field is incorrect. R has to be suffixedfor Registration number.

1.3.2. Certificate not available in Finacle ( record not migrated)

Issue Reported : At NSC Counter, A NSC is presented by Customer Of Rs.10000/-In the name of Shri Harish R Jakhete with Regn No. 80537 dated 21.10.2005Certificate No.69EE265815 . But while Discharging the certificate, the error shown isas "No records fetched". Hence it is not possible for us to discharge the certificates.Solution: There is a possibility that the certificates are not migrated. Please checkre-conciliation report if NSC was avilable in Sanchay Post or check data digitizationsign off report if NSC were issued manually. Approach DMCC.

1.3.3. Issues during Discharge of Certificates

Whenever the Certificates are discharged, the cash transactions are done by the user

for paying out the proceeds to the customer. At the same time, the NSC/KVP accountneeds to be closed by the teller in Finacle.

1.3.4. Not able to print Certificates

1. The certificate should not be actually printed till orders issued fro Directorate.


11/38

FAQ – User

11


2. When certifcate is manually written, before handing over the same tocustomer - a dummy print needs to be executed in Finacle using HDRP. Ensure that"printed succesfully" radio button is ticked during executing the menu HDRP.

3. The critical point is certificate inventory should be moved from DL (doublelock) to EM (Employee Location) as and when printing is required.

4. There Should never be a case where a customer is given a hand written certificateand print command is pressed later. This would lead to mismatch of certificatenumber.

5. In case certificate is wrongly printed and the customer has returned or the postoffice is in possetion of the wrong certificate - a duplicate certificate needs to beprinted using HDUDRP menu option.

1.4. A

1.4.1. Agent ID Creation in e-Banking

Issue Reported : Please create Agent ID in e-banking as it was not part of migratedagents.Solution: The Agent ID should be first created in Finacle using the menu HDSAMMby the post office . After that, the Agent ID should be shared with Help Desk forcreating the Agent ID in e-banking as well.

1.4.2. Accounts not visible for the Agents

Possible reasons for ACCOUNTS NOT VISIBLE FOR AGENTS

Same Agent might have SAS and MPKBY agency.

Duplicate agent ids are present. While renewal instead of correcting theexisting ID, new agent ID has been created resulting in Duplicate IDs. Furtherin many post offices it is seen that SB account number is linked even to theseduplicate agent IDs.

If multiple IDs are present to same agents, PO should refer to correct MPKBYID from the excel sheet provided during Data Migration Transformation andcheck whether the RD accounts are linked to this ID.

When the agent logs in, accounts are not visible. Please link the accounts.

Solution: The account linkage for the Agent has to be done in Finacle by the PO userby going to account modification menu for each account.


12/38

FAQ – User

12


1.4.3. Agent IDs manually created in Finacle contains space and dot.

Issue Reported : Agent IDs manually created in Finacle contains space and dot.

Solution: Agent IDs created in Finacle should not contain space or a dot. AgentsPortal will not allow creation of such agent id’s.

1.4.4. Not able to login with the Agent ID or Password provided.

Issue Reported : Not able to login with the Agent ID or Password provided.Solution: Passwords are case sensitive i.e. lower case and upper case charactersshould be entered as is. If the agent enters password wrongly 10 times, the Agent IDgets disabled.

1.5.

F E, A 0008079307

.

338/ . . 344/F

. 6/ .

:

A/C :

A/C : 0008079307

: 49500/

: 23122011

Solution:

The MIS accounts interest is applied during EOD by the batch job GEN18. Steps to find outthe reason for difference in interest amount

1. Check the SOL id of the account.

2. In the EOD reports of the interest run of the account, this account will also be present.

3. The .SUC report shows the total interest calculated amount till date. System deducts thelast interest applied amount (migrated data) and then applies the rest of the amount.

1.6. .

Issue Reported : Screenshot


13/38

FAQ – User

13


Solution :

This issue occurs when there is a lien placed at the account which is being closed. This liencan be seen in the menu HALM. The lien has to be removed by making the expiry date as

System Date and then the closure should be done.


14/38

FAQ – User

14


1.7. 1.7.1. Inward clearing issues – Duplicate instrument


15/38

FAQ – User

15


Solution

In all such cases, the instrument has to be modified or marked as reject in the inward

clearing process. Attaching the document with the step by step process.

Inward Reject.docx

1.7.2. Instrument is post dated


16/38

FAQ – User

16


Solution

In such cases, the below step by step process has to be followed

1. C , ' '

2. C , G.

3. A

4.

.

5.

6. C .

7. C ' ' ' '

8. C

9. C

1.7.3. Instrument type is invalid for scheme


17/38

FAQ – User

17


Solution

The account 0025387513 belongs to the scheme code SBGEN, hence the issue. Theinstrument type CHQ is not valid for this scheme code. If the cheque number in invalidthen also this error is thrown. The account entered here should belong to the schemetype SBCHQ.

1.7.4. How to change from SBGEN to SBCHQ if it is a cheque account and migratedas SBGEN and how to enter available blank cheque numbers?

Transfer the account to SBCHQ using the menu HACXFRSC and issue the cheques via

HICHBA menu.

HACXFRSC Menu Screen shot.


18/38

FAQ – User

18



19/38

FAQ – User

19


1.7.5. Outward Clearing Issue - Sort code not present for a particular bank andbranch combination (For DOP CBS IT OPration Team only)

Issue Reported : When we lodge the Outward Cheques for clearing the sortcodes related to

the concerned cheques ( Nasirabad Bank Branch Codes ) are not being accepted by thesoftware.So How will we enter the Bank Branch related sortcodes without having any Bankcode in search option for that particular Branch of Bank. Kindly arrange the all Bank relatedCodes Or some other solution for feeding.

Solution

Sort code means MICR Code.

1.The cheque can be lodged under the sort code of the 'service branch' of the same bank, ifthat code is available in Finacle

is it mandatory to select Service Branch Code? Can any other branch code of same bankavailable in data base be selected?

Answer: Any valid sort code can be selected.

2.If the sort code of the service branch ( main branch that participates in clearing for that

bank ) is not available, then please use the menu HBRTM to add the missing sort code as

per the attached document.

Steps to add theSort code in HBRTM

3. Once the above is done, cheques can be lodged in outward clearing.

1.7.6. Process of handling RBI Circular intimating about a new Bank & Branch (ForCBS IT Operatioan Team only):

Circular from RBI intimating about any new bank shall be received at the local SO/HO.The SO/HO need to forward the said circular to the DOP Operations team which shall

create the new Bank code in the menu option HBKTM and the new branch code inHBRTM. The MICR city code bank code and branch code as entioned in the RBI

circular shall need to be input during branch code creation.

In case the Bank is already is in Finacle CBS (by confirming through Inquiry mode in

HBKTM) - a branch code has to be created in HBRTM.

The naming convention of the bank / branch code is to have the MICR branch code

itself.

1.7.7. How to handle Outstation Cheque in Finacle?

Use HIRM menu and follow below mentioned steps:-

1. Invoke the menu HIRM.


20/38

FAQ – User

20


2. The details of the cheque and the account number has to be keyed in using the Lodge

option.

3. Finacle will automatically collect the collection charges.

4. Verification should be done for the lodged cheque.

5. Send the cheque physically to the outstation location.

6. If the cheque is cleared - intimation coming from outstation location - the Realize function

needs to be invoked in HIRM menu and submitted.

7. If the cheque is dishonoured - the dishonour function to be invoked and submitted in HIRM

menu option.

1.7.8. What is the procedure for outstation ' AT PAR' cheques.

Solution : At Par cheques should be treated as loacl cheques and entered in the outward

clearing zone with other cheques. No outstation charges should be collected fro At Par cheques.

1.7.9. Carving could not be done due to scheme errors.

Issue Reported : Error Screen shot


21/38

FAQ – User

21


Solution

Please always click on the Show exception button to get the issue description.

If the cheque / instrument is not issued/ passed /stopped then this message comesup. Even other errors are also listed related to exceptions like Insufficient availablebalance , etc.

1.8.


22/38

FAQ – User

22


Solution

There is no write permission for the role id of the user who is trying to post it , hence the

issue. In HRPM menu, for the scheme code to which the above account in the screenshotbelongs should be given write permission. Contact DOP CBS IT Operation Team, Chennai.

1.9. A


23/38

FAQ – User

23


Solution

This issue occurs if the account being closed is the interest credit account for some other

account e.g MIS or SCSS or TD account. To check to which account this is linked, the user

can check the transactions in the account being closed in the menu HACLI. The interesttransactions will show the account number to which the account being closed is linked asshown below

If the closure account is Interest Credit Account, go to Account Modification menu for thatlinked account. Change the Interest Credit Account to some other account and then proceed

closing this account.


24/38

FAQ – User

24


1.9.1. Loan account closure issue

Error Screen shot


25/38

FAQ – User

25


Solution

The above error occurs when the balance is not zero for the loan account. This means thatpayoff has not been done for the account. Please complete the payoff process and thenclose the loan account

1.9.2. Premature closure issues

Error Screen shot


26/38

FAQ – User

26


Solution

The above screenshot is not an error actually. It is showing the messages as part of userinformation during premature account closure. If unsure of the closure proceeds, please do atrial closure, check the report and then proceed with actual closure of the account.


27/38

FAQ – User

27


1.9.3. Dormant SB account closure issue

Dormant means Silent

Issue Reported : Since the SB account being closed is dormant, the account

closure transaction is not verified and gives the below error


28/38

FAQ – User

28


Solution

The closure process has to be cancelled and the account status to be modified to Live beforeclosing it.

Steps

• Cancel the closure operation in HCAAC menu. While cancelling an user info will beshown that the transaction has to be manually reversed. After the cancel operationin HCAAC, the transaction has to be deleted in HTM.

• If the account has to be closed , then after cancelling the transaction in HTM menu

by selecting Modify function.

• Modify the account status of the SB account in CASBAM menu from Silent to Liveand verify it

• Close the account now in HCAAC and verify it.

1.10. /


29/38

FAQ – User

29


1.10.1. RD loan account payoff done through cash receipt

This error will be thrown in offices migrated in the middle of the month. (ie on or after 2nd)

In case of Loan Disbursement or Loan Repayment the value date will be automaticallychanged to 01st of the month as interest is calculated from the 1st of the month for loans. AsCash account of that office will not be available as on 1 st (since the office has migrated in the

middle of the month) this error is thrown in Supervisor while verification. This error will bethrown only in the month of migration and from 2nd month cash be used for repayment ordisbursement.

Workaround to overcome this error

“In case of Loan disbursement – Instead of Cash (even if it is below Rs.20,000) selectTransfer and show RD Loan Disburement office account (Account number ending with 323)and pay by cheque or cash from this office account. ( CTM menu is to be used for this )

In case of Loan repayment – Instead of repaying through cash accept loan repaymentthrough Transfer. Transfer can be from RD Loan Repayment office Account (Account numberending with 323) or SB account of customer (if available) (CTM Menu to be used for this).


30/38

FAQ – User

30


1.10.2. Transaction not getting posted in CTM/HTM menu

Solution :

The user who is trying to do the operation doesn’t have a teller account linked to his

employee id, hence the issue.

Either the teller should be posting the transaction or the user trying to post thetransaction should be getting a teller account attached to his employee id.


31/38

FAQ – User

31


1.11.

Solution:

The above error occurred when during account opening, only instrument date has

been entered and no other instrument details entered

In such cases, the transaction will not be posted and has to be deleted in HTM

menu. Once the transactions are deleted , the accounts opening has to be cancelled

and then new accounts have to be opened again with proper data entry.

1.12.

Issue Reported : When the user tried to invoke any menu, an error is displayed as MenuNot avaialble for the user.


32/38

FAQ – User

32


Solution : Please contact DOP Operations Team at Chennai for the required access to begiven to the specified user for the particualr menu id.

1.13. A A A

Issue Reported : When the user tried to invoke HAGTXP menu in Modify mode, an error isdisplayed as Inavlid Agent Type and Scheme Code Combination.

Solution : SAS type of Agents do not have access to post RD bulk posting. The Agent Typefor that particular Agent ID needs to be modified as either PRS or MPB in HDSAMM menu.

Post this modification, user will be able to do posting in HAGTXP menu. Appropriate AgentID need to be modified as the commission structure differs for both.

1.14. A .Issue Reported : When the user tried to close the browser with out proper logout, again onloggin in, it gives error message as User Already logged in.

Solution : Please contact DOP Operations Team at Chennai for the unlocking the user id.

1.15. Issue Reported : When the user tried to login and invoke any menu, it gives an errormessage as User_Menu_ID is undefined.

Temporary Solution : Logout from Finacle Application. Make Internet Browser as yourdefault browser. Press F-12, Clear all cookies and history. Then try to Login through default

browser i.e (Internet Explorer)

1.16.

1.16.1. Steps to ensure a fast EOD

Identify all the transactions which are in Entered Status and un-Posted/Partiallyposted status.

These Transactions needs to be verified in each post office by using relevantmenu at the earliest and before the EOD starts.

If still any transaction is not getting posted then use HTM to post thattransaction.

If still transaction is not getting posted, contact FSI Helpdesk immediately.


33/38

FAQ – User

33


1.16.2. Steps to Inquire EOD blocking validations.

• Pending Transactions, Unposted, unverified transactions – HFTI menu shouldbe used.

• Pending inward Zone to be closed - HIMCZ / HICTM menu should be used.• Pending Unverified Accounts – HAFI menu should be used

• Pending Unverified Inventory Transaction List – HIMC/HICHB• HSVALRPT report can be invoked to view the blocking validation for each sol

• For each sol/set the same can be viewed in a custom report in HPR menu.Report Name is EOD – Blocking Validation Report – Under development

1.17. A 1.17.1. Instructions for Users at Post Office

The below list of instructions is for the users at the Post offices to raise ahelpdesk request during CBS-Finacle connectivity issues ( Finacle notaccessible)

1) The IncidentReporting.jsp page has to be typed in the browser, the

complete path of which can be like

http://DOPFSIHELP/.....incidentReporting.jsp (to be provided once the

page is made active)

2) The below page appears with the details of the user’s computer on the left

panel and a section to enter the user details on the right panel.

The fields which are marked with an asterisk (*) are mandatory.


34/38

FAQ – User

34


3) The city of the user can be chosen from the dropdown provided

4) On selection of a city, all the pin codes under the city are shown in the Pin Code

dropdown


35/38

FAQ – User

35


5) On selection of a pin code, all the post offices under the pin code are shown in

the Post Office Name dropdown with the first one selected

6) On entering all the mandatory fields and a valid 10 digit contact number , the

submit button has to be clicked


36/38

FAQ – User

36


7) On successful submission of the page with the user computer details and the

user details, the confirmation page appears


37/38

FAQ – User

37


1.17.2. Instructions for L1 Support i.e IFOSYS HELP DESK (Not for Post Offices)

The below list of instruction is for the L1 support personnel to view the list of problemslogged by the post office users

1) The CBS_Support.jsp page has to be typed in the browser, the complete path of

which can be like http://10.122.97.69:8082/CBS/CBS_Support.jsp. The below page

appears with today’s date in yyyy-mm-dd format as default and the list of issues

logged

2) The date range can be changed in yyyy-mm-dd format to view the list of issues for

that date range

1.18. A Issue Reported : Initially 2 systems are connected with Finacle. Later onwhen 2 new system are connected, they are not working properly.Solution : For the newly added two systems, desktop configuration is notdone. Once the configuration is completed as per the provided PDF, it startedworking fine.


38/38

FAQ – User

1.19. .Issue Reported : When one menu is continuously used for long time,application is getting locked. User needs to log out and login again.

Solution : Need to analyze.If solution is not ready, please remove this issue.

1.1. Before raising the defect or while lodging the defect, the below specified worddocument needs to be updated by DOP and the same uploaded by the HD team inMeops, so that the issue resolution time is reduced.

Template_For_Lodging_the_defect.doc

1.2. PFB the excel sheets for the escalation matrix.

FSI-CBS_Escalation_Matrix_for_FSI_-_Fin

FSI-CBS_Escalation_Matrix_for_Non-Sev

FSI-CBS_Escalation_Matrix_Apps_Infra_S

Core Banking System FAQ

Documents

Transcript of Core Banking System FAQ