Skip to main content
GullySystem
Financial services

Business solutions for Banks

Explore software for work such as “Savings and current accounts”. Review each business function below, including when it fits and what to check before implementation.

Banks

How the business operates.

A bank serves people and businesses through branches, relationship managers, call centres and digital channels. Each channel keeps its own notes, yet the customer expects one institution. Records built around the account number rarely show who the customer is, which sanction is pending or what was asked last month.

Customer records

Hold each person or business once, with linked accounts, guarantors, contacts, relationship manager and branch, so every team in every department starts from the same customer file.

Applications and approvals

Take account opening and loan applications, route them by amount and role, and keep each decision with the approver’s name, date, covenants and note.

Documents and identity checks

Store identity and address proofs against the customer, record who verified them, and flag documents near their expiry date or a due KYC refresh.

Service requests and complaints

Every request and complaint, from branch counter to email, becomes a numbered ticket that names its owner and the date a reply is due.

Overdue accounts and follow-up

List accounts past due by age bucket, record each call and promise to pay, and put the next reminder or notice on the officer’s own list.

Branch and management reports

Compare branches. Applications, sanctions, complaints, overdue accounts and dormant account counts come straight from the records, with no spreadsheets collected from branch managers by email at month end.

Roles and audit trail

Give each role its own screens. Keep a log of who viewed or changed a record, so that an auditor can follow a case from application to closure without asking anyone.

Collateral and lien register

Property papers, gold ornaments and deposit receipts pledged against a loan are recorded with valuation date and custodian. Credit officers see what covers each limit. Release needs approval from a named officer.

Dormancy and account closure

Closure requests, dormant accounts and unclaimed balances are tracked with dates and the officer handling each. Branch managers see accounts nearing dormancy. Nothing closes without a name, and customers receive a written closure note.

Locker and safe deposit register

Every locker has a holder, a nominee, a rent due date and an access log. Branch staff note the time of each visit against the locker. Rent arrears show beside the number.

The records that hold the operation together.

  • Customer records. Hold each person or business once. Linked accounts, nominee details, contacts, relationship manager and home branch sit on one page that every team opens.
  • Enquiries and product applications. Record every enquiry with its channel and product, carry it forward to an application, and spot the enquiries that have stopped moving after a rate quotation went out.
  • Documents and identity checks. Store identity, address, income and specimen signature papers against the customer. Note who verified each one, and flag documents close to their expiry date.
  • Credit applications and approvals. Route each application by amount and role, and collect the reviewer’s notes on collateral and covenant terms. The final sanction stays with the approver’s name, tenor and date.
  • Service requests and complaints. Raise a numbered ticket for every request, chargeback dispute or complaint from any channel, and give each one an owner, a type and a promised reply date.
  • Overdue accounts and recoveries. List accounts past due by age. Record each call, promise, moratorium request and visit, and place the next action on the responsible officer’s own list so nothing waits on memory.
  • Branch operations. Run several branches on one system. Each sees its own customers and teller queues, while head office sees them all together without chasing a single sheet.
  • Customer notices. Email, SMS or other messaging carries instalment reminders, requests for papers and confirmations of a reply, and each message is pulled from the customer’s own record.

Operational bottlenecks to check

Customer details sit in several tools

The branch, the loan desk and the complaints team each keep their own notes. A new mobile number given at one teller counter never reaches the other two desks, and statements and calls go to the old one.

Approvals leave a thin trail

A sanction given by email or in a committee meeting is hard to find later. The file shows the outcome but not the reviewer, the limit applied, the collateral taken or the reason. Audits need all four.

Identity documents are collected and then lost

Passports, utility bills and proof of address are taken at the counter and scanned later, when nobody is watching the clock. Expiry dates sit in nobody’s diary. A KYC refresh passes unnoticed.

Complaints have no single list

A complaint arrives by phone, letter and branch visit, and nobody holds the full list. Replies run late. The customer explains the same matter twice to different staff, and the ombudsman letter that follows surprises the manager.

Overdue follow-up depends on memory

Collections staff keep their own call notes. A promise to pay on the fifteenth is remembered by one officer and missed by the next, and a legal notice goes out too soon.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Enquiry

    A person asks about a savings account, a card or a term loan at a branch, on the phone or online. The enquiry is logged against the customer and the product asked for.

  2. 2. Application and documents

    The application is entered once. Identity, address and income papers are attached, a collateral valuation is added for secured lending, and each paper is marked as checked with the verifier’s name.

  3. 3. Review and approval

    The request routes to the officer or committee its amount requires. Each sanction is recorded with the approver, the tenor, the covenant terms, the date and the reason for the decision.

  4. 4. Servicing

    Service requests become tickets. A cheque book, a card replacement, a passbook reissue or an address change each gets an owner and a promised date.

  5. 5. Follow-up

    Complaints are answered by their reply date. Accounts past due are listed by age, and every call, promise and moratorium request is noted against the account for the next officer to read.

  6. 6. Reporting

    Branch managers and head office read the same counts of applications, sanctions, complaints and arrears, taken straight from the records, so nobody rebuilds them from sheets at month end.

Roles and responsibility boundaries.

For branch staff

Open the customer’s record, take applications, attach documents, log passbook and cheque requests, and see at a glance what is still waiting for the customer.

For credit officers

Review applications in the queue. Read the collateral papers and notes, then record a sanction or refer the file up to the next level, with covenant checks beside each file.

For operations and customer service

Work through service requests, remittance queries and complaints by due date. Each reply is recorded against the customer.

For compliance and audit

Search a customer or a sanction, read the trail behind it, and list records by approver, date or branch when an examiner asks.

For management

Compare branches on applications, sanctions, complaints and arrears. Open any figure down to the records behind it without asking a branch for a sheet, a call or an email.

Reports your managers need.

  • Applications by product, branch and stage
  • Sanctions by level, approver and turnaround
  • Complaints open, closed and past ombudsman date
  • Collateral valuations due for renewal
  • Accounts past due by age and officer
  • Dormant accounts by branch
  • Branch comparison for management

Connections to scope

  • Core banking system
  • Email
  • SMS
  • WhatsApp or other messaging
  • Document and cheque scanners
  • Identity verification services
  • SWIFT remittance exports

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Branches and approval levels

The first entries are your branch list, staff roles, lending limits, overdraft ceilings and approval levels, laid out exactly as the bank applies them now. Nothing is retyped later.

Forms and document lists

Application forms, required documents and request types follow the products you offer. A mortgage file and a passbook account carry different paper lists, and each is set with you.

Customers and open cases migrated

Customer lists, open applications, open complaints, collateral files and arrears are loaded from your current records. Each load is checked before go-live.

Currency, language and local rules

Your operating currency, the languages customers read and the wording of notices are fitted to the country you serve. Local record-keeping duties are walked through with your compliance team as the work proceeds.

Connection to your core

The first workshop decides how the system talks to your core banking platform. Customer numbers, account numbers and cheque clearing references then agree in both places, and nobody keys them twice.

Hosted by GullySystem

The platform runs on GullySystem servers, so each branch and department reads one set of records. When a form or an approval rule needs to change, GullySystem staff make the edit.

Limitations to settle before implementation

  • A bank looking for a core ledger, card switch or payment engine needs a core banking platform. This sits beside one.
  • A lender whose whole business is loans may find Loan Management System closer. A member-owned society may prefer Credit Union Management Software.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Savings and current accounts
  • Fixed and recurring deposits
  • Personal loans
  • Home loans and loans against property
  • MSME and business loans
  • Agricultural and Kisan credit
  • NRI banking
  • Credit and debit cards
  • Digital and UPI banking adoption
  • Insurance and mutual fund cross-sell
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements