Skip to main content
GullySystem
Finance and insurance · Software for banks

Keep each customer, application, approval and complaint on one branch-wide trail.

Banks run customer information files, loan applications, sanction letters, collateral, service requests, complaints and delinquent accounts across branches and back offices, often in separate tools. The bank management software holds each customer once and carries every request, decision and document against that record. Branch managers, credit officers and operations teams read the same trail. The core ledger stays where it is.

At a glance

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.

Bank management software sits beside the core ledger and holds the work around it. Loan files, KYC papers, approvals, complaints and dunning follow-up are kept per customer and per branch. Start with the process your teams find hardest to evidence. Then add the next.

How the work runs today

Branch staff open accounts, take loan applications and collect KYC documents. Relationship managers look after business customers, their working capital limits and renewal dates. Credit officers appraise each application against policy and pass it to a credit committee when the amount needs one. Every step needs a name against it: who asked, who checked, who sanctioned and on which date. Without a shared record, a branch manager answers an audit query by phoning three desks.

Operations teams process service requests such as a cheque book, a debit card replacement, a standing instruction or a change of address. Customer service logs complaints and promises a reply date. Collections staff work through accounts past due, ring the borrower and note each promise to pay. Compliance asks for lists at short notice. Head office wants branch figures on one screen. It does not want seven spreadsheets.

Where it breaks

What goes wrong for banks without a proper system.

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.

What the software does

What we would build for banks.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

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, delinquency 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.

Before you talk to a supplier

A requirements checklist for banks.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for banks.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

Bank Management Software

Customer records, loan applications, collateral files, approvals, complaints, overdue follow-up and branch reporting for banks with several branches and back offices.

See the product
Solutions inside

The business modules banks use most.

Each one is also available on its own, or inside a system built for you.

How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, Tally reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions banks ask before they call.

Does it replace our core banking system?

No. The core ledger, card switch, SWIFT messaging and payment rails stay where they are. This holds the customer-facing and back-office work around them. The connection to your core is agreed during implementation.

Can approvals follow our own limits?

Yes. Levels, amounts and approving roles are set up with you. Anything over a limit passes to the next sanctioning authority, and each decision is stamped with the approver’s name and date.

Will it fit a small community bank?

Often, yes. A community bank with a few branches and one operations team can begin with customer files, complaints and loan approvals. Other parts follow later.

How are staff permissions handled?

Each role sees only what its work needs. A teller, a credit officer and an auditor open different screens, and every change is logged. Access rules for each role are agreed with you at the start.

What happens in the free technology audit?

We look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough to start. You get a report ordered by priority, and there is no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. The audit settles the scope, and the cost goes into a written proposal before any work starts.

Category

Part of a wider group.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements