Skip to main content
GullySystem
Financial services

Workflow and Approvals for Cooperative banks

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

A loan file moves from the loan officer through surety verification to the committee. Every step is stamped with the person and date. Rejected files return with the committee’s remark.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals 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 authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

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

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

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.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

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.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
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 workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation 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. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

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. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Talk to us

Discuss workflow and approvals 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