Skip to main content
GullySystem
Financial services

Multi-Branch Consolidation for Cooperative banks

Combine branch records while retaining each branch's operational view.

Platform

Does this function belong in your operation?

Use when several branches need consistent records and a combined management view.

Management needs reporting across several operating locations.

Each branch posts its own deposits, loans and cash. Head office sees the combined position of share capital and advances across branches. Inter-branch transfers are matched on both sides.

Bring the records the workflow depends on.

  • Branch list
  • Shared master data
  • Consolidation rules

Outputs to check

  • Branch and combined reporting views
  • Shared master-data register
  • Inter-branch reconciliation list

Follow the multi-branch consolidation workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define branch boundaries

    Separate branch-owned records from shared master data.

  2. 2. Align identifiers

    Resolve item, account and reporting-definition differences.

  3. 3. Collect branch activity

    Import or connect each agreed reporting period.

  4. 4. Reconcile internal movements

    Match transfers and other cross-branch entries.

  5. 5. Publish combined views

    Show group totals, branch detail and any incomplete source data.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Branch manager

Reviews their branch records and resolves source-data differences within the authorised access scope.

Owner

Compares reconciled branch totals and investigates incomplete submissions or inconsistent definitions.

Accounts assistant

Books branch sales and collections into one set of books.

Storekeeper

Records transfer dispatch and receipt and investigates quantities still shown in transit.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Duplicate shared customer

Agree the common identifier before combining balances.

Branch reports arrive late

Show the missing period or branch instead of presenting a complete group total.

Inter-branch transfer unmatched

Keep the sending and receiving difference visible until both sides reconcile.

Can this work independently?

Consolidation needs consistent branch identifiers and source data. Branch systems can remain separate if their imports reconcile. Operational consolidation is distinct from statutory group accounting; separate entities, intercompany entries and currencies need accountant-approved treatment rather than simple addition.

Systems and records it connects with

  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Stock: Item-location quantities and authorised stock movements.
  • Roles and permissions: Named user access and action-level authority.
  • Dashboards and KPIs: Defined operational measures with traceable source totals.

Configure, test and introduce the workflow.

  • You list outlets, warehouses and who runs them. You get a written structure showing what is shared and what stays local.
  • Item lists from each branch are compared. You get a trial merge to correct before anything is combined. A pair of branches bill and transfer on the trial. You hear where the routine differs and the settings are adjusted. Real counters teach fast.
  • Other outlets join in turn. Managers are trained on the screens for their branch and on cross-branch stock. The combined figures are shown beside each branch’s own books. The owner and accountant confirm they agree.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Group totals reconcile with branch totals.
  • Branch users see their permitted scope.
  • Inter-branch activity follows the agreed treatment.
Cooperative banks

How the business operates.

A cooperative bank serves a membership that knows its staff by name. Account holders are also owners, so a share certificate, a savings book, a recurring deposit and a loan guaranteed by a neighbour can all belong to one person. The board is elected from the members. Reports go to the general body and to the supervisory authority, each in a different format and on a different date.

Member register and share capital

Hold each member once, with share holdings, nominee, occupation and linked accounts, and record allotments, transfers and withdrawals.

Savings and current accounts

Post deposits and withdrawals by branch, keep passbook and statement history, and flag dormant accounts for follow-up.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Member register and nominees. One person, one record. Address, occupation, nominee, joint holders and every linked account are held together, with each change dated and attributed to the clerk who made it.
  • Share capital ledger. Record allotments, transfers and refunds on withdrawal. Paid-up capital is then compared against the ceiling in the bye-laws and the limits the registrar has set for the bank.
  • Savings and current accounts. Post deposits and withdrawals, print passbook lines, record cheque leaf issues and produce statements. Accounts untouched beyond the dormancy period you set are listed as inoperative for the manager to review.
  • Term and recurring deposits. Lien marks. A deposit that backs a loan carries one on its receipt. Maturity, auto-renewal and premature closure are tracked, and interest is worked on the compounding cycle your scheme offers, quarterly or at maturity.

Operational bottlenecks to check

Share capital sits apart from accounts

Shares sit in a ledger, savings in a core system and the loan in a file. One question needs three lookups.

Daily collections reach the books late

Agents hand in a sheet at the end of the beat. Entries are keyed the next morning, so a member’s balance shows yesterday’s figure.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Membership

    Enrol first. A new member is entered with a nominee, any joint holder and an opening share allotment, then a savings account is opened and linked to that person.

  2. 2. Deposits

    Counter or agent. Deposits arrive at the teller window or through an agent, and each fixed or recurring deposit receipt prints the maturity date and the renewal instruction.

  3. 3. Loan application

    Members apply. They name sureties and offer a plot, a vehicle or a pledged deposit as security. The officer files the valuation, the income papers and a note on repayment capacity.

  4. 4. Committee decision

    The committee reads the file. Approval, conditions and directors present are recorded in one entry, and the sanction letter prints from those terms with no retyping of the amount or the security clause.

  5. 5. Repayment

    Instalments reach the counter or an agent and are set against principal and interest. Accounts that miss a due date fall onto the loan officer’s follow-up list, ranked by age.

  6. 6. Day-end and year-end

    Each branch closes cash and books daily. Year end brings the interest posting. Dividend proposals, auditor schedules and the board pack are all drawn from the ledger entries that the branches already closed.

Industry reports to connect with

  • Deposit position by scheme and branch
  • Fixed and recurring deposits maturing in the next month
  • Overdue loans by age band and asset classification
  • Sureties with combined exposure per member

Questions before implementation.

When should cooperative banks consider multi-branch consolidation?

Use when several branches need consistent records and a combined management view. Management needs reporting across several operating locations.

What should we bring to the requirements discussion?

Bring anonymised examples of Branch list; Shared master data; Consolidation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Combine branch records while retaining each branch's operational view. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Separate legal entities, currencies and accounting consolidation require additional rules.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Group totals reconcile with branch totals. Use this check when reviewing the first working version.

Talk to us

Discuss multi-branch consolidation for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

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