Skip to main content
GullySystem
Financial services

Workflow and Approvals for NBFCs

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 branch to credit officer to the approver whose limit fits the amount. Each step shows who holds it and for how long. Sanction conditions must be cleared before disbursement.

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

How the business operates.

A small NBFC may run several products at once: used vehicle loans, gold loans, loans against property and unsecured business loans. Each has its own documents, approval levels and collection rhythm. A gold loan hinges on purity and net weight, while a property loan waits on a legal opinion and title search.

Applications and KYC checklist

Keep a document checklist per loan product, with scanned identity proof, bank statements, signed agreements and the bureau report stored against the application.

Appraisal and sanction levels

Record income, existing obligations, bureau score and a risk note, then route the file to the approver set for that amount or product. Disbursement waits for sign-off, and the log shows who gave it.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and leads. Log every enquiry with its source and a follow-up date. Report on which enquiries became applications.
  • Borrower and group records. Keep one record per borrower with loans, guarantors and interaction history. For group lending, members sit inside their group so group totals and member dues agree.
  • Loan applications and ID documents. Track a checklist per loan product. Store scanned ID papers, tax documents, bank statements and agreements against the application.
  • Appraisal and credit notes. Record income, existing loans, credit history and a risk note. The approver reviews the same page as the officer.

Operational bottlenecks to check

The loan book lives in three places

The loan system, Excel and the books each hold a different figure for outstanding principal. Month end starts with matching them line by line, before anyone can quote an overdue-loan figure.

Field receipts reach the office late

Collectors bring cash and handwritten receipt books back at night, and the loan account updates the next day. Borrowers who already paid still get reminder calls and a bruised relationship.

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 and application

    Log the enquiry with its source, such as a walk-in, an agent or a referral. When the borrower applies, attach ID papers, income proof and guarantor details to the application.

  2. 2. Appraisal and sanction

    The loan officer records the appraisal, credit history and collateral. The file goes to the approver for that loan size, and each approval carries a name and a time.

  3. 3. Disbursement

    Record the release with date, mode and reference. The instalment schedule is generated from the rate, the tenure and the start date.

  4. 4. Collection

    Collectors open their route or groups and see who is due. Each receipt is entered against the borrower with the collector’s name, and the office sees it the same day.

  5. 5. Overdue follow-up

    Accounts move into overdue buckets when an instalment is missed. Reminders go out, visits are assigned, and promises to pay are recorded on the loan.

  6. 6. Closure and renewal

    The loan closes when the last instalment is received, and collateral is marked for release. Eligible borrowers can be offered a renewal or top-up from the same record.

Industry reports to connect with

  • Demand versus collection for the day, week or month, by collector and by branch
  • Overdue ageing by bucket, with the borrower list behind each figure
  • Disbursements by product, officer and month
  • Group-wise outstanding and member-wise repayment history

Questions before implementation.

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