CBS- CSI General Ledger (GL) Integration | FAQ • Version 1.0

CBS- CSI GENERAL LEDGER (GL) INTEGRATION

Frequently Asked Questions

1. Daily account and LOT are not tallying after GL Integration.

Logic of LOT is based on Transaction sol ie wherever the transaction is done. But logic of Daily account is based on Account SOL ie wherever the account stands.

2. Whether Voucher Posting has to be done for CBS transactions post GL Integration?

No Voucher posting is to be done for CBS transactions either through F-02 or through ZFB07. All CBS transactions done in Finacle will reflect in daily account which can be generated on next day.

3. Whether Voucher Posting are to be done for Branch office transactions?

No voucher posting is to be done for Branch Office transactions

4. Branch Office transactions done through Non RICT mode is reflecting in Daily account of account office.

CBS transactions done through RICT device will reflect in BO Daily account. But transactions done through Non RICT mode will reflect in Daily account of account office.

5. CBS transactions are not reflected in the daily account on same day after completion of transaction.

Post GL Integration, CBS transactions will be reflected in same day’s daily account but this daily account can be generated only on next day.

Eg: CBS transactions done on 18/10/2019 will reflect in Daily account of 18/10/2019 only. But this daily account can be generated on 19/10/2019 only.

6. Whether Counter PA should login to Finacle only through POS after GL Integration?

Yes. CPA should login to Finacle through POS for updation of cash correctly in POS.

7. Whether Supervisors/Postmaster/System Admin role users should login to finacle through POS?

Only CPA can login to Finacle through POS. Other role users must login to Finacledirectly and not through POS.

8. Whether transactions done outside POS will reflect in Daily account?

Yes. All transactions in Finacle (either through POS or direct login) will reflect in Daily account.

9. What are the office accounts in finacle which are mapped to POS CASH GL?

Only Teller cash and Vault office accounts are mapped to POS CASH GL.

10. What are the office accounts in finacle which are mapped to DOP CASH GL?

Only BO Cash office account and Branch settlement account office account are mapped to DOP CASH GL.

11. Whether POS cash will be affected for CBS transactions if logged into finacle directly and not through POS?

Yes. Teller cash and Vault office accounts inFinacle are mapped to POS cash. Hence transactions done in finacle through teller will affect POS cash of the office.

12. Standing Instructions (SI)  - MIS to SB, SCSS to SB, SB to RD is not reflecting in daily account

CBS Transactions will reflect in daily account only if ATLEAST ONE POS CASH GL or DOP CASH GL is hit on that day. In other words, if the Post office has not done any transactions in finacle which is affecting POS CASH GL or DOP CASH GL ,although if there arecertain channel transactions like ATM, E Banking, IPPB, M Banking, etc, Daily Account will not be generated and hence Automatic Credit, Maturity credit to POSB accounts , InterSOL (RSAO)will not reflect in the daily account.

13. What is the document type to be used during creation of Cheque Liability for payment of Savings Bank closures?

Document Type “PB” to be used while creating liability.

14. Whether cheque liability request to be created before closure of account or after closure of account?

Cheque liability request is to be created before closure of account based on the maturity amount shown in Trial closure option.

15. Whether cheque liability request will reflect in daily account immediately after creation of request?

Cheque liability request will not reflect in daily account. It will be reflected only during receipt of cheque.

16. What is the change in cheque liability request post GL Integration?

Old Process	New process after GL Integration
Debit Scheme (KVP) Credit One Time customer	Debit Postmaster cheque account(4200030013) Credit One time customer

17. CBS Transactions done by TNF CSI location ie CBS rolled out but one particular post office is not rolled out to CSI is affecting POS CASH of that TNF CSI post office.

Since Teller cash and Vault are linked to POS CASH GL, finacle transactions (involving POS CASH/DOP CASH GL) will affect POS CASH of the TNF CSI LOCATION. POS cash has to be made zero by moving to DOP CASH by accesing DAP through nearby CSI post office.

18. Whether HTTUM menu can be used post GL Integration?

HTTUM menu can be used post GL Integration. But GL mapped to the DEBIT OFFICE ACCOUNT will reflect in Daily account.

19. DBT Upload is reflecting in Payment side while uploading Bonus/DA/GDS salary in HTTUM.

Office account (0410) is DBT Upload account. This office account is for crediting NREGA credits. If this office account is used for Bonus/DA/GDS salary credits through HTTUM , DBT UPLOAD will reflect in payment side of daily account.

20. Whether any separate claim office account is available in finacle?

Office account - SOL ID + 0407 – Claims(Salary/Pension) - GL Sub Head Code – 45145 which is mapped to 10 digit code 4200039997 to be used. This claims office accounts is available in all HOs and in DAP sols.

21. How will Non CSI locations account CBS transactions in Daily account post GL Integration?

Separate SOP is provided in SB ORDER 09/2019 for accounting of CBS transactions in Daily account. CBS transactions should be accounted only based on GL DAILY TRANSACTION – SUMMARY report and not based on LOT or Consolidation.

22. Reason for non reflection of CBS Transactions in daily account even after GL extract file generation in Finacle?

CBS transactions hitting Unmapped GLs or Invalid/Incorrect facility ID or Unbalance GL extract will move to Error Report in CSI and hence no CBS transactions are reflected in daily account.

23. Whether all CBS transactions will be moved to error folder if there is unbalancing entry in one GL?

CSI will not consume entire GL extracts of that facility id even if there is unbalancing entry in one GL. Entire GLs of that facility id (including BO facility id) will be moved to error report.

24. What is the T Code to access CSI Error Report?

T Code: ZFSI_ERROR.

25. Which role users can access this T Code?

YS:FA_CBS_PLI (Delegation of Role in SAP has to be designated by concerned R.O/C.O).

26. What errors can be corrected using this T Code?

Incorrect facility ID and Unmapped GL can be corrected using this T Code.

27. Whether Unbalancing error can be corrected using T Code ZFSI_ERROR?

FI/CO interface: Balance in transaction currency is the error description for Unbalanced error. Amount cannot be modified using this T Code. Hence unbalancing error can be corrected using ZFSI_ERROR if the difference amount is listed as separate line item by modifying the facility id.

28. How to modify the Unmapped GL in ZFSI_ERROR report?

In case if the transaction is hitting unmapped GL, entire CBS transactions of that sol will move to error table.

Unmapped GL has to be corrected using proper G.L description depending upon the type of G.L Subhead code (tabular column as given below).

29. How to identify the unbalancing error?

Reasons

1. BO Code tagged and BO cash new account debited are different

1. Download ZFSI_ERROR in excel format for a particular date
2. In ZFSI_ERROR excel report, sort based on Facility ID. Select one facility id. BOs if available will be listed in this selection
3. Unbalancing can be between 2 BOs or 1 BO and its Account office ie PO facility id
4. If the unbalancing is between 2 BOs, Both BOs will be available under this selection
5. Check the totals of Amount Debit and Amount Credit for these 2 BOs or BO and its account office to arrive at the difference amount
6. Generate GL Daily Transaction Report – Summary for this particular SOL (sol id will not be available in ZFSI_ERROR report. SOL ID is to be identified from mapping table or concerned Circle/PO will know their corresponding sol ids)
7. Check for the discrepant amount in the identified BO code in the summary report. If the discrepant amount is listed as separate row, it would be easy to identify the particular TRAN ID by generating GL Daily transaction report - Detailed
8. If the  discrepant amount is not listed as separate transactions, generate the detailed report for the GL sub head of the BO where debit amount is more.
9. Identify the particular tran id , account number from the detailed report
10. Check the Tran ID in HTI to find out the debit account details.
11. Once details of the transaction is identified, it could be observed that BO code tagged is different and BO cash new account debited is different
12. Suitable instructions to be given to that facility id to ensure that BO code tageed and BO cash new account debited is same.
13. Data in error table can be correct by replacing the BO FACILITY ID in ZFSI_ERROR if this discrepant record is listed as single line item without getting clubbed with some transactions.

30. What is the office account to use for PLI maturity credits through POSB account?

Finacle Office account SOL ID + 0104 which is mapped to 4200030014 to be used for all type of closures. This 10 digit code will be nullified when Mccamish transactions are updated in corresponding GL codes.

31. While discharging certificates in Bulk, Repayment account was not given; instead cash payment was made to the customer. At a later point of time, it was noticed that the closure proceeds were actually transferred to 0340 A/c?

The above issue is due to usage of Bulk closure(CNSBCV) menu for closures below Rs.20000/-. Maturity credits for the accounts closed through CNBCV menu will be credited into Postmaster cheque accounts (0340) if POSB account is not given. Cash Closures cannot be done through CNSBCV menu.

32. A BO has generated two RICT unique ref. no.s in place of one, for opening of a new account. How to reverse one ref no.?

Transfer the amount from BO cash new account (SOL ID + FSI BO Code + N) to BO cash account (SOL ID + FSI BO Code) of BO through HTM by providing additional transaction details such as duplicate reference number. This can be done only by SU users. Currently this is impacting cash of account office. Patch will be deployed soon for affecting BO cash balance .Necessary error book entries to be made.

33. Some commonly used G.L Codes held in S.O/RICT enabled BO’s

GL Subhead Code	BO Receipts (Credit)	GL Code Credit	BO Payments (Debit)	GL Code Debit
10004	BO Cash A/c	4867100010	BO Cash A/c	4867100010
10005	BO Cash New A/c	4200030009	BO Cash New A/c	4200030009
30001	SB Deposit	8800100010	SB Withdrawal	4800100010
30042	SSA Deposit	8800100020	SSA Withdrawal	4800100020
54041	SSA Default Fee (SOL ID+SSA04)	8800800030	NIL	NIL
30010	RD Deposit	8800100030	RD Withdrawal	4800100030
54039	RD Default Fee (SOL ID+0384)	8800800030	NIL	NIL
76001	NIL	NIL	RD Rebate (SOL ID+0327)	4800800120
30011	1 YR TD Deposit	8800100040	1 YR TD Withdrawal	4800100040
30012	2 YR TD Deposit	8800100050	2 YR TD Withdrawal	4800100050
30013	3 YR TD Deposit	8800100060	3 YR TD Withdrawal	4800100060
30014	5 YR TD Deposit	8800100070	5 YR TD Withdrawal	4800100070

34. Whether data in error table ZFS_ERROR can be posted after period closure

No

35. Whether manual voucher posting is to be done for offices which are available in ZFSI_ERROR report

Corrections can be done only in GL Sub Head and addition/deletion of Facility ID in ZFSI_ERROR report. Entire transactions will get posted during next batch job if credits and debits are balanced. Corrections involving amount could not be modified in ZFSI_ERROR. Manual voucher posting only should be done for these offices as per the instructions of circles (either at Circle/Region/Division

Share this

Share on FacebookPlus on Google+