October 7, 2026 · Guides

Core Banking Modules: Deposits, Loans and General Ledger

Core banking modules are the separate parts of a CBS, and knowing what each does makes a demo far easier to judge. For a society or Nidhi the three that matter most are deposits, loans and the general ledger, joined by branch and control features that keep the day orderly.

In this guide

The deposit module
The loan module
The general ledger module
Branch and control features
How the modules connect
Common mistakes
What to check in a demo
Related reading
FAQs

The deposit module

This is where a member's money is recorded. The Core Banking System Software page lists savings and current accounts, fixed deposits, recurring deposits and MIS deposits, with interest slabs, maturity and TDS. In practice a clerk opens the account, takes the cash, issues a receipt, and the system works out interest as the product rules say. Whether you may offer a given deposit at all depends on your Act or Rules, so check the current provisions before you switch a product on.

The loan module

The page names gold loans, property loans and loans against deposits, along with sanction processing, disbursement, loan schedules, overdue tracking and penal interest calculation. A loan clerk records the sanction, releases the amount, and the schedule is generated. A month later the manager asks for the overdue list and expects it without calling the field staff. If you want the narrower view of lending-only software, core banking vs loan management software sets out the difference.

The general ledger module

The ledger is the module accountants care about. The page lists the day book, trial balance, P&L statements, balance sheet generation, and member, account and loan ledgers. Every entry made in deposits or loans should land here by itself. Ask what the accountant can still enter by hand, and where that is logged, because the auditor will ask the same question. Audit reports your society software should produce goes through what to expect at year end.

Branch and control features

Branch-wise accounts, so each office sees its own books and head office sees all.
Day-begin and day-end controls, which stop a branch working on yesterday's open items.
Multiple users with different rights, a holiday calendar and IP binding.
User activity logs, which show who did what and when.
Customizable print forms and receipt generation for the counter.

These are not glamorous, but they decide whether a CBS survives a busy month end.

How the modules connect

Take one example. A member repays a loan instalment in cash. The loan module reduces the dues, the deposit module is untouched, and the general ledger gets a cash debit and a loan credit, all from one entry. Now repeat it with a loan against that member's fixed deposit. A good CBS shows the lien in the deposit and the loan in the ledger without a second entry. If you must key the same figure twice, you are not using a core system, only two programs sitting side by side.

The same logic is why a society or Nidhi should read core banking software for societies and Nidhis alongside this guide. The software records your business; it does not change what the law lets you do.

Common mistakes

Buying every module on day one, then using half.
Setting up deposit products before confirming they are permitted.
Leaving the accountant's manual entry rights wide open.
Skipping the day-end test with a deliberate mismatch.
Not asking how opening balances will come in. See migrating to core banking software.

What to check in a demo

Open a fixed deposit and find its entry in the day book and ledger.
Sanction a loan, generate the schedule and mark one instalment overdue.
Show the penal interest working and where its rule is set.
Print the trial balance and balance sheet from the same data.
Open the user activity log and find your own actions.
Add a user who can see one branch only, and test it.

Want to see this working on your own data? See the Core Banking System Software, ask for a live demo on +91 93117 95484, or write to mail@taxhint.in.

FAQs

What are the main core banking modules?

Deposits, loans and the general ledger are the heart of it, supported by branch management, user controls and print forms. Each should post into the same set of books.

Do I need every module?

Not usually. Start with the ones that match the products you are permitted to run, and add others when the work needs them.

How does the general ledger module help at audit time?

It holds the day book, trial balance and ledgers produced from the entries already made, so the auditor works from one source. Your CA will still review the figures.

Can one module work without the others?

They can be switched on in stages, but the benefit comes from the shared books. A deposit module that does not post to the ledger leaves you reconciling by hand.