Finacle Inoperative / Dormant Accounts — How to Activate, Commands & RBI Guidelines
- View / modify customer profile:
CUMM(Customer Maintenance Menu) - Account inquiry — check account status:
ACLI(Account Level Inquiry) - Savings account modification:
CASBAM(or bank-specific equivalent) - Current account modification:
CABAM(or bank-specific equivalent) - Customer inquiry — all accounts:
CI - RBI unclaimed deposit portal: UDGAM (udgam.rbi.org.in)
A customer walks in after three years. They want to withdraw money from an account they haven’t touched since their posting to another city. Finacle shows the account as inoperative. The balance is there. The customer is there. But the system won’t let you process the withdrawal without a reactivation — and reactivation isn’t a one-minute fix.
Inoperative accounts are one of the most common counter situations in branch banking and one of the most mishandled. This article covers how Finacle classifies accounts as inoperative, how reactivation works step by step, the GL sub-head issue that causes balance mismatches in CBS, and what happens to accounts that reach the unclaimed deposit stage under RBI guidelines.
How Finacle Classifies Accounts as Inoperative
RBI defines an inoperative (dormant) account as a savings or current account in which there have been no customer-initiated transactions for a period of two years. System-generated credits — interest credits, bank charges, tax debits — do not count as customer-initiated transactions. The two-year clock runs only on transactions initiated by the account holder.
Finacle identifies and flags inoperative accounts through a quarterly batch process that typically runs in January, April, July, and October. At each quarterly run, the system identifies accounts that crossed the two-year threshold during that quarter and changes their status from operative to inoperative. The status change also triggers a GL sub-head code change — the account’s balance moves from the operative GL bucket to the inoperative GL bucket in the bank’s books.
Once an account is marked inoperative in Finacle, all customer-initiated transactions — deposits, withdrawals, transfers — are blocked until the account is formally reactivated. The balance remains in the account; it is not transferred anywhere at this stage. The block is operational, not a balance movement.
The GL Sub-Head Change — Why It Matters
When an account is marked inoperative, Finacle changes the GL (General Ledger) sub-head under which the account balance is classified. In your bank’s books, operative savings account balances sit under one GL sub-head; inoperative savings account balances sit under a different GL sub-head. The total liability is the same — only the classification changes.
This matters for two reasons:
- Balance tallying: When branch staff or auditors run GL reports, inoperative account balances appear under a different code. If a reconciliation compares the operative savings GL to the total savings balance, it will show a shortfall — the difference being the inoperative pool. This is normal, but branch staff who don’t know about the GL sub-head split will flag it as a discrepancy.
- Audit finding — GL mismatch: The most common audit finding in this area is accounts that have been operationally blocked as inoperative but whose GL sub-head was not correctly updated by the batch (a batch failure or configuration gap). These accounts show as inoperative on ACLI but still sit under the operative GL code. The fix requires a manual GL correction through the data centre — it cannot be done from the branch.
If you encounter a balance reconciliation issue involving inoperative accounts during an audit, the first question to ask is: did the quarterly batch run correctly for all affected accounts? Check with your data centre if you suspect a GL sub-head mismatch.
The Reactivation Process — Step by Step
Reactivating an inoperative account is a branch-level process that requires customer action, KYC verification, and a Finacle account status change. It cannot be done over the phone or by the customer alone — they must visit the branch.
| Step | Action | Details |
|---|---|---|
| 1 | Customer submits written request | A signed letter or standard bank form requesting reactivation. Some banks have a printed form; others accept a plain letter. The request must be signed by the account holder (all joint holders if joint account). |
| 2 | KYC re-verification | Collect fresh KYC documents — current address proof and identity proof. Per RBI guidelines, reactivation of an inoperative account requires KYC re-verification even if the existing KYC on record is within the normal validity period. Check whether the existing CKYC ID needs to be refreshed as well. |
| 3 | Update CUMM | Update the customer profile in CUMM with any changed address, mobile number, or email from the fresh KYC. Verify the CUMM modification (checker must approve). This step establishes a refreshed, verified customer record before the account is opened for transactions. |
| 4 | Change account status in Finacle | Open the account modification command for the account type (CASBAM for savings, CABAM for current, or your bank’s equivalent). Locate the Account Status field and change it from Inoperative / Dormant to Operative / Active. Commit and verify (checker approval required). |
| 5 | BM authorization | In most banks, reactivation of an inoperative account requires BM-level authorization — not just officer-level. The BM signs the request form, confirms KYC documents have been verified, and authorizes the Finacle status change. Keep all documents in the account file. |
Inoperative vs Unclaimed Deposits — the 10-Year Rule
An account becoming inoperative at 2 years is only the first classification. RBI has a second, more serious classification: unclaimed deposits.
If an account remains inoperative for 10 years — meaning no customer contact, no reactivation attempt, no response to the bank’s outreach — the balance is transferred to the Depositor Education and Awareness (DEA) Fund maintained by the RBI. This transfer is mandatory under Section 26A of the Banking Regulation Act. In Finacle, this transfer is handled through a batch process and the account balance is remitted to the RBI.
After the transfer to DEA Fund, the customer is not permanently barred from their money. They can still claim it — but the claim process now goes through the UDGAM portal (udgam.rbi.org.in), which is RBI’s centralised unclaimed deposit search and claim portal. The customer searches for their account, identifies the unclaimed balance, and files a claim which the bank then processes.
At the branch level, your role is to direct customers who come asking about very old dormant accounts to check UDGAM first if more than 10 years have passed since the last transaction. The branch may still facilitate the claim process — but the balance is no longer in your CBS; it is with the RBI.
RBI’s Outreach Requirement Before Transfer
RBI requires banks to actively reach out to customers before transferring their balance to the DEA Fund. Specifically, banks must:
- Inform the customer at the 1-year mark (before the account becomes inoperative) that their account will be classified as inoperative if there is no transaction in the next year
- Send a notice to the customer when the account is actually classified as inoperative
- Make a renewed attempt to contact the customer before the 10-year mark when the balance would be transferred to the DEA Fund
This outreach is typically handled through your bank’s CBS-driven letter generation and SMS systems — not manually at the branch. But if a customer comes in saying they never received any notice about their account going dormant, check whether the communication was sent to the current mobile number and address on record in CUMM. Outdated contact details in the CIF are the most common reason customers miss these notifications.
Common Audit Findings — and How to Avoid Them
| Audit finding | Root cause & fix |
|---|---|
| Accounts marked inoperative but GL sub-head still shows operative | Quarterly batch did not process correctly for some accounts. Raise with data centre for manual GL correction — cannot be done from the branch. |
| Inoperative accounts reactivated without KYC re-verification | Branch officer changed account status in Finacle without collecting fresh KYC. RBI requires KYC at reactivation — no exceptions. Ensure the process always includes KYC documents before status change. |
| Reactivation done without BM authorization | Account modification done by an officer without BM sign-off on the request form. Most bank policies require BM authorization. Check your bank’s specific SOP and follow it — do not short-circuit the process because the customer is in a hurry. |
| Customer contact details not updated at reactivation | Account was reactivated (status changed) but CUMM was not updated with the fresh KYC address and mobile number. The next outreach will still go to the old details. Always update CUMM as part of every reactivation. |
Inoperative account management is a recurring audit theme because it sits at the intersection of operational compliance (KYC), GL accuracy (sub-head classification), and customer rights (unclaimed deposit protection). The branches that handle it cleanly are the ones that follow the full process — customer request, KYC, CUMM update, BM authorization, status change — without skipping steps because the transaction looks simple.