One record of each customer, application, approval and complaint across every branch.
Manage customer records, account and credit applications, identity documents, collateral files, approvals, service requests, complaints and overdue follow-up across branches and back offices. Each customer is held once. Every request carries its documents, its approvers and its dates. Branch managers, credit officers, tellers, operations staff and compliance teams work from the same trail. Your core banking provider keeps the ledger.
- Branch structure, approval levels and limits entered the way your bank works
- Customer lists, open applications and open complaints migrated
- Edits to forms and approval rules handled by GullySystem staff when asked
Bank Management Software holds customer records, applications, approvals, service requests and complaints, configured by GullySystem to your branch and approval structure. Each customer is held once, and each request carries its documents, approvers and dates. Branch, credit, operations and compliance teams read one trail. Your core banking provider keeps the ledger.
What goes wrong before the software.
How the work flows through it, step by step.
- 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
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
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
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
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
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.
What is inside.
Every module can be switched on, left out or changed to match how your team already works.
The business modules it is built from.
Each one is also available on its own, or inside a system built for you.
- Contact & Account Management
People and businesses are separate records linked to their accounts and nominees, so a branch, a loan desk and a complaints team read one page.
- Lead Management
Each enquiry about an account, card or term loan is logged with its channel, then followed until it becomes an application or goes quiet.
- Document Management
Identity, address, income and specimen signature papers are filed against the customer with the verifier’s name, and approaching expiry dates appear on a list.
- Workflow and Approvals
Applications travel to the officer or committee their amount requires, and each sanction is written down with the approver, tenor, date and reason.
- Ticket Management
A cheque book request, a passbook reissue, an address change or a complaint becomes a numbered ticket with an owner and a promised reply date.
- Collections and Payment Follow-Up
Accounts past due are listed by age, calls, promises and moratorium requests are noted, and the next action lands on the responsible officer’s list.
- Multi-Branch Consolidation
Every branch keeps its own teller queues and customers on one system, while head office reads the combined position without collecting separate sheets.
- Audit Trail
Every view, change and sanction is logged with the staff member and time, so a reviewer can follow one customer case end to end.
How we would put it in.
Setup, data migration, integrations and anything built on top.
One system, each person sees their part.
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.
The numbers the owner asks for.
- 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
Who this is built for.
- Community and regional banks with several branches and a central operations team
- Savings and commercial banks that want one record of each customer across tellers, lending desks and back office
- Banks that run lending desks and need a clear trail behind each sanction and covenant
- Complaints, compliance and audit teams that answer questions about past decisions
- Smaller and newer banks that still manage requests through email and shared folders
When it is not the right choice.
- 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.
Adapted to your business before it goes live.
You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.
Works alongside
- Core banking system
- SMS
- WhatsApp or other messaging
- Document and cheque scanners
- Identity verification services
- SWIFT remittance exports
Questions owners ask before a demo.
Does it replace our core banking system?
No. The ledger, card switch and payment rails stay with your core provider. This holds the customer, sanction and service work around them, and the first workshop settles the connection between the two.
Can approvals follow our own limits and levels?
Yes. Amounts, products and approving roles are entered once, a request above a limit moves to the next approver, and each sanction is kept with a name, a date and a note.
Can several branches share one system?
Yes. Each branch works from its own queue and customers, while head office sees every branch together. What a branch may see is a permission set per role.
How are identity documents handled?
Papers are attached to the customer, and the person who checked each one is recorded. Documents near expiry are listed, so a renewal can be requested before the account turns dormant and the file goes cold.
Can customers submit requests themselves?
Requests that arrive by email, phone or in a branch are logged by staff. A customer-facing channel can be added as a scoped extra, agreed in the first workshop.
How are complaints tracked?
Each complaint becomes a ticket with a category, an owner and a reply date. Open and late tickets show on one list, and every reply is kept against the customer, including any ombudsman referral.
Can existing customers and open cases be moved across?
Yes. Your present customer lists, applications in flight, complaints, collateral files and overdue accounts are brought over, and operations staff read through the imported cases before the switch.
Does it meet our regulator’s requirements?
Rules vary with the country and with the type of licence a bank holds. Record-keeping and reporting rules are reviewed with your compliance team during implementation, and nothing here replaces their advice.
Who owns the data?
You do. The proposal states in plain terms how a full copy of your records is handed back. That is settled before work starts.
What does it cost?
No price is published. It moves with the number of users, the branch count and how much configuration your products need. Tellers, loan officers and head office staff see a live walkthrough before any quotation.
Wondering what it costs? Six questions give you a written scope and the buckets any quote should separate.
Businesses that use this.
Related products.
See Bank Management Software with your own data.
Tell us how you run things today. We’ll show you the parts that matter to you and say plainly what would need changing.
- 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