E Kuber

When one investor moves government securities from one SGL account to another, the transfer has to actually happen inside a system RBI itself operates.

That system is called E Kuber. It is RBI's own core banking platform, and it is where the real movement of book-entry government securities takes place, underneath whatever forms the DP and depository handle on the investor's side.

When securities are being brought into a depository's account from another SGL entity, the counterparty on the other side is the one who actually starts the transfer, and it does so inside E Kuber.

To transfer government securities held in book-entry form with another SGL-eligible entity into a depository account, the client submits 1 DRF-GS, together with an SGL credit advice and a request letter for "Value Free Transfer", to the DP. The DP checks the SGL account being transferred from, confirming it is registered with PDO Mumbai — identifiable by the prefix "BY" on the account number — then fills in ISIN and Loan Code details, and the depository system generates a DRN.

The DP provides the demat request details to the depository's G-Sec cell, which emails the SGL counterparty, requesting it to initiate the transfer in RBI's system. The SGL counterparty then initiates the transfer request in the RBI E Kuber system, and intimates the depository.

The depository then confirms the request in the RBI E Kuber system, after which the balances are credited to the depository's own Constituent SGL account. Only after this E Kuber confirmation does the demat request get confirmed in the depository system itself, with the electronic balance finally credited to the holder's demat account.

Mr Malhotra holds Rs 25,00,000 of government securities in an SGL account with a bank, and wants to move them into his depository demat account instead. He submits a DRF-GS, an SGL credit advice and a request letter for Value Free Transfer to his DP.

The DP verifies the bank's SGL account carries the "BY" prefix confirming PDO Mumbai registration, fills in the ISIN and Loan Code, and the depository system generates a DRN. The depository's G-Sec cell then emails the bank — the SGL counterparty — asking it to begin the transfer. The bank initiates the transfer request inside RBI's E Kuber system and tells the depository it has done so.

The depository confirms the request within E Kuber, RBI credits the depository's Constituent SGL account with Rs 25,00,000 of securities, and only then does the depository confirm the demat request in its own system, crediting Mr Malhotra's demat account with the same amount.

Chapter 11, section 11.4.1, walks through the "Procedure for Transferring Government Securities in SGL Form to Depository account" step by step, naming E Kuber as the specific RBI system in which the SGL counterparty and, later, the depository each confirm the transfer.

Expect a question on who initiates the E Kuber transfer request — the SGL counterparty, not the depository or the DP — and on what the depository must do afterwards, which is confirm the same request in E Kuber before its Constituent SGL account is credited.

• The SGL counterparty initiates the E Kuber transfer, not the depository or the DP. The depository only confirms it afterwards.
• E Kuber sits inside RBI, not inside the depository system — it is the underlying settlement platform for G-Secs, distinct from the depository's own DP system where the DRN and demat request live.
• The "BY" prefix on an SGL account number confirms PDO Mumbai registration, a check the DP must make before the transfer can proceed at all.
• Do not confuse this route (transfer between two SGL entities) with a plain dematerialisation of a physical G-Sec certificate, which uses a different form — DRF-GS with a Form of Transfer, not an SGL credit advice.