LIVE
Finacle EOD — End of Day Process, Common Failures & What to Do · Finacle SOD / BOD — Start of Day Process Explained Step by Step · Finacle Common Error Codes — What They Mean & How to Fix Them · Bank Staff Loan vs Market Loan — When the Concessional Scheme Beats the Market (and When It Does Not) · CAIIB Salary Increment 2026 — 2 Extra Increments, Promotion Impact & Career ROI · Which CAIIB Elective Should You Choose? 2026 Role-Wise Decision Guide · CAIIB BRBL Complete Guide 2026 — Banking Laws, RBI Regulations & Legal Framework · CAIIB ABFM Complete Guide 2026 — Financial Statements, Valuation & Emerging Business · CAIIB BFM Complete Guide 2026 — International Banking, Forex, Treasury & ALM · CAIIB ABM Complete Guide 2026 — Syllabus, Strategy & Module-wise Breakdown · Finacle EOD — End of Day Process, Common Failures & What to Do · Finacle SOD / BOD — Start of Day Process Explained Step by Step · Finacle Common Error Codes — What They Mean & How to Fix Them · Bank Staff Loan vs Market Loan — When the Concessional Scheme Beats the Market (and When It Does Not) · CAIIB Salary Increment 2026 — 2 Extra Increments, Promotion Impact & Career ROI · Which CAIIB Elective Should You Choose? 2026 Role-Wise Decision Guide · CAIIB BRBL Complete Guide 2026 — Banking Laws, RBI Regulations & Legal Framework · CAIIB ABFM Complete Guide 2026 — Financial Statements, Valuation & Emerging Business · CAIIB BFM Complete Guide 2026 — International Banking, Forex, Treasury & ALM · CAIIB ABM Complete Guide 2026 — Syllabus, Strategy & Module-wise Breakdown ·

Finacle Common Error Codes — What They Mean & How to Fix Them

Last updated by Jai on June 26, 2026

Quick Lookup — Finacle Error Codes
Error Message Cause Fix
Transaction not permitted — BOD pending BOD batch hasn’t run Check HSSI → call data centre
Balance not sufficient Actual balance low Verify balance with CI command
Lien amount exceeds available balance ALM lien blocking withdrawal Check ALMI → escalate to BM
Account frozen — debit not allowed AFSM freeze active Do not process → refer to BM
Customer ID not verified CUMM verification pending Supervisor verifies via CUMM
Clearing zone not open HOICZ not run today Supervisor runs HOICZ
Teller cash account not balanced Cash mismatch in teller vault Check HCASHPND → report to BM
Value date cannot be less than BOD date Back-value transaction Manager override required
Transaction pending verification Maker done, checker pending Checker uses HFTI to verify
Account inoperative / dormant No transactions for 2+ years Reactivation process via BM
Stop payment registered Stop payment on this cheque leaf Do not override → inform customer
SI failed — insufficient balance Standing Instruction execution failed Check SIETR and CFLM

It’s 10:30 AM and a customer is standing at your counter. You enter the transaction and Finacle throws an error you’ve never seen before. You stare at the screen. The customer stares at you. Your supervisor is busy.

This guide is for exactly that moment. Below are the errors that appear most often at branch counters — explained in plain English, with the exact fix for each. Bookmark this page. Share it with every new joiner in your branch.

1. “Transaction Not Permitted — BOD Pending”

What you see on screen: “Transaction not permitted” or “Transaction not permitted — BOD pending” or “SOL not open for transactions”

Beginning of Day (BOD) has not run for your SOL (branch). Finacle works on a daily cycle — EOD closes the books at night, BOD opens the system for the new business date the next morning. Until BOD completes, all counter transactions are blocked.

BOD runs automatically at the data centre, usually between 8:00–9:00 AM. It can be delayed by high system load, an overnight patch, or a partial EOD failure the previous night.

What to do:
1. Check HSSI (SOL Status Inquiry) — enter your SOL code and look at the current business date. If it shows yesterday’s date, BOD is pending.
2. Call your data centre helpdesk immediately. Give them your SOL code and the exact error message.
3. While waiting: account inquiry (CI), statement printing (STMTPR), and CUMM Inquire still work — do whatever non-transactional work you can in the meantime.
What NOT to do: Do not try transactions from a different user ID — same result. Do not ask a colleague to “try from their login.” BOD is a system-level batch. No branch user can override it.

2. “Balance Not Sufficient” vs “Lien Amount Exceeds Available Balance”

These look like the same problem on screen but they are completely different — and treating the second one like the first can create a legal issue.

“Balance Not Sufficient” / “Insufficient Funds”

The account’s actual balance is lower than the withdrawal amount. Use CI (Customer Inquiry) or ACLI (Account Level Inquiry) to verify the current balance. Tell the customer their available balance and ask them to adjust the withdrawal amount.

“Lien Amount Exceeds Available Balance” / “Transaction Blocked Due to Lien”

The account has enough money in it, but part of the balance is locked by a lien marked through the ALM command. The available balance after the lien deduction is less than the withdrawal amount.

Example: Account balance ₹1,00,000. A lien of ₹80,000 has been marked for an income tax attachment. The customer wants to withdraw ₹50,000. Finacle blocks it — only ₹20,000 is free of lien.

What to do: Use ALMI (ALM Inquiry) to see the lien details — who marked it, the amount, the reason, and when it expires. Do not release the lien yourself. Escalate to BM.
Legal note: If the lien was marked for a court attachment or income tax order, releasing it without proper authority is a serious compliance breach. The BM will need to consult legal or compliance before any release.

3. “Account is Frozen — Debit Not Allowed”

What you see: A freeze message blocking debit transactions, credit transactions, or all transactions on the account.

An authorized officer has placed a freeze on the account using AFSM (Account Freeze Setup Menu). There are three types of freeze in Finacle:

  • Debit freeze: Withdrawals blocked, deposits allowed. Used when a court order restricts outflows while allowing salary or pension credits to continue.
  • Credit freeze: Deposits blocked, withdrawals allowed. Less common — used in specific regulatory or escrow situations.
  • Total freeze: No transactions at all. Used for deceased accounts, court-ordered full attachment, or active fraud investigation holds.
What to do: Do not process the transaction. Politely inform the customer that their account has a bank-imposed restriction and they need to speak with the Branch Manager. To check the freeze details yourself: AFSM → Function: I (Inquire) → enter account number.
Do NOT disclose the reason for the freeze to the customer — especially if it is related to a court order or fraud investigation. That conversation belongs with the BM, not at the counter.

4. “Customer ID Not Verified” / “Customer Profile Inactive”

What you see: “Customer not active” or “CIF not verified” or “Customer ID not verified” when trying to open a transaction.

The customer’s CIF (Customer Information File) profile — maintained through CUMM (Customer Maintenance Menu) — has been created but the verification step has not been completed. In Finacle’s maker-checker model, creating and verifying a customer profile are two separate steps. Until the checker verifies the CIF, no transactions are permitted on that customer’s accounts.

This most often happens with newly opened accounts where the checker was busy and missed the verification step. It also happens after a KYC update (address change, mobile number update) that was entered but not yet approved by a supervisor.

What to do: An authorized officer (checker role) opens CUMM → Function: V (Verify) → Customer ID → complete verification. This is a 2-minute fix once the right person logs in. The account is active for transactions immediately after verification.

5. “Clearing Zone Not Open” / “Clearing Zone Closed for Transaction”

This error appears when you try to process clearing transactions — inward cheques, NACH credits, ECS debits — and the clearing zone for the day has not been opened yet.

Clearing in Finacle operates in time-bound zones that must be opened each morning by an authorized supervisor using HOICZ (Host Open/Close Clearing Zone). This is a daily task that occasionally gets missed during shift handovers or when the clearing officer is absent.

What to do: Stop retrying the clearing transaction — it will keep failing. Go to your Clearing In-charge or Branch Manager. They need to run HOICZ → select the relevant clearing zone → Open. All clearing transactions will process normally once the zone is open.

6. “Teller Cash Account Not Balanced” / “Cash Mismatch”

Finacle tracks your teller cash position in real time. If the total of your cash received minus cash paid out doesn’t match your declared physical cash, the system flags a mismatch. In some configurations, this blocks further transactions until it is resolved.

What to do:
1. Run HCASHPND — shows all pending cash transactions that have been entered by the maker but not yet committed by the checker. A transaction stuck in this state often explains the mismatch.
2. Run HSCWRPT (Scroll Write Report) for your teller ID for today — gives a full transaction-by-transaction breakdown of your cash position.
3. Recount your physical cash carefully.
4. If the mismatch is confirmed and genuine, report to your BM immediately — do not wait until EOD.
Do NOT enter a fictitious offsetting transaction to force-balance your till. This is a serious audit finding and makes the investigation much harder. Report the excess or short to your BM — it is documented, investigated, and closed properly through the cash excess/short process.

7. “Value Date Cannot Be Less Than BOD Date” / “Invalid Value Date”

You are trying to post a transaction with a value date earlier than today’s BOD (business) date. Standard teller roles in Finacle do not have permission to post back-value transactions — Finacle rejects the entry at the date validation step.

This comes up when posting a cheque that needs to carry yesterday’s value date, correcting a missed transaction from a holiday, or entering any adjustment that needs an earlier date stamp.

What to do: You cannot fix this at the teller level. The transaction must be entered by a manager-level user who has the back-value override permission in their role profile. Explain to your BM what the transaction is and why it needs a prior value date.

Back-value transactions are flagged in Finacle’s audit trail. There should be a valid documented reason — bank holiday, system downtime, late instrument receipt. These entries are scrutinized in internal and RBI audits.

8. “Transaction Pending Verification” / “Maker-Checker Pending”

What you see: The transaction appears to have been entered but nothing has posted. The customer’s account hasn’t changed, yet Finacle shows the transaction in “Entered” or “Verification Pending” status.

Finacle uses a maker-checker system for certain transactions: the maker (teller or officer) enters the transaction; a second authorized user (the checker) must approve it before it actually posts to the account. The transaction is waiting at the checker stage.

Transactions that commonly require checker verification: RTGS/NEFT initiations, DD issuance (DDISSUE), account opening (CUMM add), large-value cash transactions above your branch’s internal authorization limit.

What to do: Use HFTI (Host Financial Transaction Inquiry) → enter the transaction reference number → confirm its status. An authorized checker then opens HFTI → Verify function → locates and approves the transaction. If you are the maker, call your supervisor immediately — don’t leave the customer waiting.
Do NOT enter the same transaction again thinking it didn’t go through. You will create a duplicate — and reversing duplicate transactions creates an audit trail that is difficult and time-consuming to sort out.

More Errors You Will See Regularly

Error What it means & what to do
Account inoperative / dormant No customer-initiated transactions for 2+ years. All transactions blocked until reactivation. Process: customer submits a written request with KYC documents → BM approves → account status updated in Finacle via the account modification command. The customer cannot reactivate over the counter — it requires a formal request and verification.
Account does not belong to this SOL The account exists but is registered at a different branch (SOL). Use CI with the full 15-digit account number to confirm. Depending on your bank’s CBS configuration, the account may still be transactable from any SOL — check with your BM or the account-holding branch.
Stop payment registered A stop payment instruction is active on this specific cheque leaf number. Do not override it. Tell the customer the cheque cannot be paid. It may be a stop payment request placed by the account holder themselves, or it may be a court order. Either way, do not force it through.
SI failed — insufficient balance A Standing Instruction attempted to execute at BOD or during SIE but the source account did not have enough funds. Check SIETR (SI Executed Today Report) to see all SIs and their statuses for the day. Failed SIs are tracked in CFLM (Carry Forward List Maintenance) and may be attempted again or flagged for manual action.

The One Rule for Any Finacle Error

Stop → Read the error carefully → Match it to this list → Escalate if needed.

Do not click around trying things. Most Finacle errors are informational — the system is telling you something specific. Read the exact message, match it to this guide, and take the right action. When in doubt, stop and call your supervisor. It takes 30 seconds to ask and can save hours of reversal work later.

Bookmark this page. If you know a new joiner at your branch who just started on the counter — share it with them. It is the guide you wish you had on Day 1.

Categories: Articles

Preparing for Bank Promotion Exam? Enrol Now →