Finacle EOD — End of Day Process, Common Failures & What to Do
- Close teller cash for the day:
HCCST(Host Close Cash Transactions) - Verify teller cash balance:
HCBR(Hard Cash Balance Report) - Check pending cash transactions:
HCASHPND - Check SOL status / EOD progress:
HSSI(SOL Status Inquiry) - SOL Closure of Day (branch trigger):
HSCOD - Scroll Write Report (full day transaction list):
HSCWRPT - Teller balance report:
EOBR(End of Business Report)
It is 6:15 PM. The last customer left 20 minutes ago. The guard wants to lock up. You try to run EOD and Finacle throws an error. The data centre helpline is busy. Your BM is asking for an update every five minutes.
This is the moment every branch banker knows. EOD failure at end of day is one of the most stressful situations in branch banking — not because it is technically complicated, but because the fix is time-sensitive and the cause is rarely obvious when you are panicking.
This article covers the complete EOD process in Finacle: what the system actually does, what you must complete before EOD can run, the command sequence, what commonly blocks it, and exactly what to do when it fails. For the morning side of this cycle, see the companion article: Finacle SOD/BOD — Start of Day Process Explained.
What EOD Actually Does in Finacle
EOD (End of Day) is the batch process that closes the current business date in Finacle and prepares the system for the next working day. It is the accounting equivalent of closing the books at the end of a trading session. Until EOD completes, the business date does not advance — the system is still “today.” After EOD, the system is in a closed state until BOD opens the next business date the following morning.
During EOD, Finacle runs several processes automatically:
- Interest calculation — calculates interest earned and due on all accounts for the day.
- Standing Instructions marked ‘A’ — SIs with EOD execution type are triggered. These are typically transfers that should happen at the end of the business day.
- GL reconciliation — general ledger entries are balanced across all modules.
- Report generation — day-end reports, exception reports, and audit logs are generated for the day.
- Account status updates — accounts crossing thresholds (inoperative status, maturity flags) are updated in batch.
- Date advance preparation — the system prepares the next business date so BOD can open it the next morning.
EOD is run at the data centre for most banks — branch staff do not trigger the central batch. But in many CBS implementations, the branch must close its SOL (through HSCOD or a similar command) before the central EOD picks it up. What you do at the branch in the hour before EOD determines whether it runs cleanly or gets stuck.
The Pre-EOD Checklist — What Must Be Done Before EOD Can Run
Most EOD failures are not caused by the EOD batch itself. They are caused by something left open or unbalanced at the branch level that the batch cannot proceed past. Run through this checklist before 5:30 PM — do not wait until the last minute.
1. All Tellers Must Close Their Cash — HCCST
Every teller who opened cash in the morning using HOCST must close it at the end of the day using HCCST (Host Close Cash Transactions). This signals to Finacle that the teller’s counter is done for the day and their cash position is final.
If even one teller has not run HCCST, EOD may be blocked at the teller cash closure step. Check that every teller ID that ran HOCST in the morning has a corresponding HCCST by end of day.
2. Verify Teller Cash Balances — HCBR
After closing cash, run HCBR (Hard Cash Balance Report) for each teller. The system balance and the physical cash count must match. Any mismatch must be resolved before EOD — a cash excess or short must be documented and reported to the BM, not hidden.
Also run EOBR (End of Business Report) — this gives the full teller summary for the day: total cash received, total cash paid, net position. This is your final teller reconciliation before sign-off.
3. Clear All Pending Transactions — HCASHPND
Run HCASHPND and check for any pending cash transactions — entries that have been made by the maker but not yet verified by the checker. These transactions are in limbo: the customer may have left, the cash may have been given, but the entry is not committed in the system.
Every pending transaction must be either verified (committed) or deleted before EOD. EOD cannot run cleanly with transactions stuck in “Entered” state. If a pending transaction should not be committed — for example, a duplicate entry — delete it properly rather than leaving it hanging.
4. Ensure No Unverified Non-Cash Transactions
RTGS/NEFT initiations, DD requests, account opening entries, and other transactions that require checker verification must all be verified before EOD. Use HFTI (Host Financial Transaction Inquiry) to search for any transactions in “Entered” or “Verification Pending” status for today’s date. Verify or delete each one.
5. Check Clearing Status
Ensure all inward and outward clearing for the day has been processed. Any clearing transaction left open can block EOD in banks where clearing and day-end are tightly integrated. Check with your Clearing In-charge that all clearing files have been submitted and that HOICZ has been closed for the day’s clearing zones.
The EOD Command Sequence
In many banks, the BM or designated officer must close the SOL before the central data centre batch picks it up. The exact commands and sequence vary by bank and CBS configuration, but the typical flow is:
| Step | Command | What it does | Who runs it |
|---|---|---|---|
| 1 | HCASHPND | Verify no pending cash transactions remain open | BM / Supervisor |
| 2 | HCCST | Close each teller’s cash for the day | Each Teller |
| 3 | HCBR / EOBR | Verify teller cash balance; generate end-of-business report | Each Teller / BM |
| 4 | HSCOD | SOL Closure of Day — marks the branch SOL as ready for EOD. In banks where this is branch-triggered, the BM runs this. The central EOD batch then processes the SOL. | BM |
| 5 | HSOLCOP | SOL Copy — data centre step that copies the day’s transaction data for processing. Usually a batch step, not triggered from the branch. | Data Centre |
| 6 | HSCOLD | SOL Close Day — the final step that closes the business date for the SOL. After this, the SOL is in EOD state and no transactions can be posted until BOD the next morning. | Data Centre |
In banks where EOD is fully centralised, steps 4–6 happen automatically at the data centre once a cut-off time is reached. Your branch role ends at step 3. In banks where the BM triggers HSCOD, you need to run it before the data centre’s EOD window closes — typically by 6:00–6:30 PM. Check your bank’s specific EOD cut-off time.
Reading HSSI — What the Status Codes Mean
HSSI (SOL Status Inquiry) is your real-time window into where EOD stands. Run it when you need to know if EOD has started, is in progress, or has completed. Enter your SOL code and read the SOL Status field:
| Status shown in HSSI | What it means |
|---|---|
| Open / Active | Normal working state. BOD has run, business date is current, transactions are allowed. |
| Closed | EOD has run (or HSCOD has been triggered) and the SOL is closed for the day. BOD has not yet run for the next date. No transactions possible. |
| EOD In Progress | The EOD batch is currently running for this SOL. Do not try any transactions — wait for it to complete. |
| EOD Completed | EOD has finished successfully. The SOL is now waiting for BOD the next morning. |
| EOD Failed / Error | EOD attempted but encountered an error. Call the data centre immediately with your SOL code and the exact status shown. Do not attempt any transactions. |
What Blocks EOD from Running
If EOD fails or won’t start, one of these is almost always the reason. Work through them in order.
| Blocker | How to diagnose | Fix |
|---|---|---|
| Teller cash not closed | Check which teller IDs ran HOCST but not HCCST | Each unclosed teller runs HCCST. If the teller has left, a supervisor may need to close it with appropriate authority. |
| Pending / unverified transactions | HCASHPND for cash; HFTI for non-cash pending entries | Verify genuine transactions; delete duplicates or erroneous entries. Every open entry must be resolved. |
| Teller cash balance mismatch | HCBR shows system balance ≠ physical cash | Recount physical cash. Check HSCWRPT for transaction-level detail. Report excess/short to BM and document it — do not create fictitious entries. |
| Open clearing zone | Check with Clearing In-charge; use HOICZ to view zone status | Close today’s clearing zone using HOICZ before EOD is triggered. |
| System / batch issue at data centre | All branch-level checks clear but EOD still won’t proceed | This is now a data centre issue. Call helpdesk. Give your SOL code, HSSI status, and confirm you have completed all branch-side closure steps. |
When EOD Fails Mid-Way — What to Do
EOD starting and then failing mid-process is the worst scenario — the SOL is in a partially processed state, you cannot post transactions, and the cause is not visible from the branch. Here is how to handle it.
1. Check HSSI immediately — note the exact status shown and the business date. Screenshot or write it down.
2. Do not attempt any transactions — the SOL is in a partial state. Any action you take could complicate the recovery.
3. Call the data centre helpdesk — give them: your SOL code, the HSSI status, the time EOD was triggered, and what the last successful step was if you know it.
4. Tell your BM immediately — this is now an escalation. The BM should be aware and available to authorise any recovery steps the data centre may ask for.
5. Wait for data centre confirmation — they will either restart EOD from the last successful checkpoint or advise on a recovery procedure. Do not guess.
— Do not try to re-run HSCOD or any EOD commands yourself. Running batch commands on a partially-processed SOL can cause data corruption.
— Do not log off and back in hoping it resets. It won’t.
— Do not ask the data centre to “just run BOD for tomorrow” to get transactions moving. BOD on a failed EOD creates a date mismatch that is very difficult to recover.
— Do not tell the branch staff to go home without confirming with the data centre that EOD is being handled.
What to Tell the Data Centre When You Call
Data centre teams handle dozens of calls during EOD time. The faster you give them the right information, the faster they can help. When you call, have this ready:
- Your SOL code (branch code in Finacle)
- Current HSSI status — exact text on screen
- Business date shown in HSSI
- Time EOD was triggered (or time you first noticed the issue)
- Pre-EOD steps completed — confirm you have run HCCST for all tellers, HCASHPND is clear, no pending transactions
- Whether this is a recurring issue or a first-time occurrence
This information lets the data centre team go directly to the relevant log without asking you five follow-up questions.
Traditional EOD vs EODMU (24×7 Model)
If you work at a large public sector bank, you may have heard that “EOD doesn’t block transactions anymore.” That is because some banks have moved to the EODMU (End of Day Multi-User) model in Finacle.
| Traditional EOD | EODMU (24×7 Model) |
|---|---|
| Hard cut-off: no transactions after EOD starts | EOD runs in the background; transactions continue through the night |
| Branch must close (HSCOD) before data centre runs EOD | Business date advances automatically; no branch trigger needed |
| EOD failure = branch stuck, no transactions possible | EOD failure is isolated; most branch operations can continue |
| “BOD pending” error is common at branch level | “BOD pending” error is rare; system self-advances |
Most regional offices, smaller PSU branches, and co-operative banks still run traditional EOD. If you regularly experience the 6 PM EOD window and “BOD pending” errors the next morning, you are on the traditional model. The pre-EOD checklist and procedures in this article apply fully to you.
EOD Checklist — Print and Keep at the Counter
- ☐ HCASHPND — confirm no pending cash transactions
- ☐ HFTI — confirm no unverified non-cash transactions
- ☐ All RTGS/NEFT entries verified or cancelled
- ☐ Clearing zone confirmed closed with Clearing In-charge
- ☐ HCCST — every teller closes their cash
- ☐ HCBR / EOBR — teller balances verified; any excess/short documented
- ☐ HSCOD — BM runs SOL closure (if your bank requires branch trigger)
- ☐ HSSI — confirm EOD status is progressing normally
- ☐ Data centre confirmation received that EOD completed
The branches that never panic at EOD time are the ones that start the pre-EOD checklist at 5:30 PM, not 6:15 PM. Build the habit of clearing pending transactions throughout the day — not in a rush at close — and EOD will become the routine it is supposed to be.
For a list of the exact error messages you will see when something goes wrong during EOD or BOD, and the fix for each one, see: Finacle Common Error Codes — What They Mean & How to Fix Them.