Skip to main content
GullySystem
Financial services

Workflow and Approvals for 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 application moves from branch to credit officer to committee, with each limit of authority set by amount. A rejection returns it with a reason. Sanction letters issue only after the last approval.

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

See the full industry workflow, reports and implementation plan →

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.

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.

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

Industry reports to connect with

  • Applications by product, branch and stage
  • Sanctions by level, approver and turnaround
  • Complaints open, closed and past ombudsman date
  • Collateral valuations due for renewal

Questions before implementation.

When should 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