Approval workflow

An approval workflow is a defined sequence of reviews and authorisations that a request must pass through before it takes effect. It specifies who reviews what, in what order, under what conditions, and what happens when a reviewer approves, rejects, or sends the request back for correction.

In lending, the most common example is the loan approval workflow: an application moves from the officer who captured it, through one or more levels of review, to the person or committee holding the authority to commit funds at that amount. The same mechanism governs other irreversible actions — disbursements, write-offs, fee waivers, restructures, journal entries and refunds.

The defining feature of an approval workflow is that the person who initiates an action is not the person who authorises it. That separation is the control. Everything else — routing rules, thresholds, escalation timers — exists to make the separation practical at scale.

Why approval workflows matter

Fraud prevention. The single most effective control against internal fraud is that no one person can both create and approve a value-moving transaction. A fictitious borrower, an inflated disbursement or a quiet write-off all require collusion rather than a single bad actor.

Credit discipline. Approval limits force large exposures upward to more experienced reviewers. Without them, credit standards drift toward whoever is most optimistic.

Regulatory compliance. Prudential guidelines in most jurisdictions require documented delegated lending authority, board approval for insider and large exposures, and evidence that the approval hierarchy was actually followed rather than merely written down.

Auditability. An approval trail answers the question auditors and supervisors always ask: who authorised this, on what basis, and when.

Speed, when designed well. A workflow that auto-approves small routine requests and escalates only exceptions is faster than one where a manager signs everything.

Core components of an approval workflow

Trigger. The event that starts the workflow — an application submitted, a write-off proposed, a payment above a threshold entered.

Roles, not individuals. Steps are assigned to roles so the workflow survives staff turnover, leave and transfers. A named person as an approval step is a single point of failure.

Routing rules. Conditions that determine the path. The most common are amount, product type, borrower risk grade, branch, whether the exposure is unsecured, and whether the borrower is a related party.

Approval limits. The maximum amount each role may authorise, also called delegated lending authority or approval thresholds.

Sequence. Whether steps run one after another, simultaneously, or only when a condition is met.

Outcomes. Approve, reject, or return for amendment. A return should reopen the request for edit and restart the affected portion of the chain, not silently approve.

Escalation and time limits. What happens when a step sits untouched. Options include reminders, automatic escalation to the next level, or reassignment to a delegate.

Audit trail. An immutable record of every action: actor, role, timestamp, decision, comments, and the version of the request at the moment of decision.

Stages of a loan approval workflow

1. Capture and submission

A loan officer records the application, borrower details, requested amount, purpose, security offered and supporting documents. Submission locks the record from further edits by the originator.

2. Completeness and eligibility check

An automated or clerical screen confirms mandatory fields, valid identification, KYC status, and that the product parameters requested fall within policy. Incomplete applications are returned rather than escalated.

3. Credit assessment

Affordability, repayment capacity, credit bureau history, existing exposure and, where relevant, group standing are assessed. Any collateral is valued and its loan-to-value ratio tested against policy.

4. First-level approval

Typically the branch manager or supervisor. If the amount sits within their delegated limit and no exception applies, the decision ends here.

5. Escalation for amount or exception

Requests above the first-level limit, or carrying a policy exception such as an out-of-range rate or a waived requirement, route upward — to a credit manager, a credit committee, or in the largest cases the board.

6. Final authorisation and disbursement release

Approval authorises the commitment. Disbursement is usually a separate control, released only once the offer is accepted, security is perfected and documentation is signed. Treating approval and disbursement as one step removes a control point.

7. Handover to servicing

The approved terms become the boarding record for loan servicing. Anything approved but not carried across accurately is a servicing error waiting to happen.

Sequential, parallel and conditional workflows

• Sequential: Each approver acts in turn; the next is notified only after the previous decides. Best suited to: Credit decisions where each level builds on the last.
• Parallel: Several approvers review at the same time. Best suited to: Independent checks such as legal and credit, where neither depends on the other.
• Conditional: A branch of the chain activates only if a rule is met. Best suited to: Exception handling, related-party lending, large or unsecured exposures.
• Unanimous: All assigned approvers must approve. Best suited to: Committee decisions with no single owner.
• Quorum: A defined subset must approve. Best suited to: Committees that must function when members are unavailable.

Most real lending workflows combine these: sequential by default, conditional above a threshold, quorum-based at committee level.

Approval limits and delegated authority

Delegated lending authority is the schedule setting out how much each role may approve. A simplified example:

• Loan officer: Nil (recommends only) for both unsecured and secured loans. Escalates to branch manager.
• Branch manager: Small individual loans (unsecured); moderate secured loans. Escalates to credit manager.
• Credit manager: Moderate exposures (unsecured); larger secured exposures. Escalates to credit committee.
• Credit committee: Large exposures for both unsecured and secured lending. Escalates to board.
• Board: Insider, related-party, and single-obligor limit breaches.

Three principles govern a sound limit schedule. Limits are set against total exposure to the borrower, not the individual loan, so a borrower cannot be kept below a threshold by splitting one request into several. Limits are lower for unsecured lending than secured. And related-party and insider exposures escalate regardless of amount, because the risk is conflict of interest rather than size.

Maker-checker and segregation of duties

Maker-checker, also called the four-eyes principle, requires a second person to verify a transaction before it commits. It is the minimum viable approval workflow: one step, two people.

Segregation of duties is the broader principle that no single role should control more than one of: initiating a transaction, authorising it, recording it, and holding custody of the related asset. In a lending business this means the officer who originates a loan should not release the disbursement, and the person posting a write-off should not be the one who approves it.

Small institutions often struggle here because one person genuinely does hold several roles. The usual compensating controls are mandatory dual authorisation on cash and disbursement, periodic independent review of exceptions, forced leave, and rotation of officers across branches or portfolios.

Approval workflows beyond lending decisions

The same mechanism protects any irreversible or value-moving action:

• Disbursements — releasing funds after approval
• Write-offs — removing a non-performing asset from the books
• Fee and penalty waivers — a common route for concealed fraud when uncontrolled
• Restructures and reschedules — which can mask arrears if approved by the same officer whose portfolio benefits
• Journal entries and adjustments — particularly manual entries affecting income or provisions
• Refunds and overpayment releases
• User access and role changes — the workflow that protects all the others
• Interest rate or product parameter changes

Approval workflows in microfinance

Institutions delivering microfinance face specific design pressures:

Volume versus scrutiny. Thousands of small loans cannot each receive committee attention. The workable answer is a low auto-approval or single-approver band for standard small loans, with escalation reserved for size, exceptions and repeat restructures.

Field-based origination. Officers capture applications away from the branch. Workflows must function on mobile devices and tolerate intermittent connectivity, queueing submissions until they sync.

Group lending. Approval may operate at two levels: the group guarantees and endorses members, and the institution approves the group limit and the individual allocations within it.

Multi-branch structures. Routing must respect branch boundaries so a manager approves only their own portfolio, while regional and head office roles retain oversight across branches.

Turnaround expectations. Borrowers often choose lenders on speed. Escalation timers and delegate assignment during leave matter as much as the hierarchy itself.

Common failures

• Rubber-stamping. Approvers with no time or no information approve everything. The workflow exists but the control does not.
• Limits set too low. Everything escalates, the top of the hierarchy becomes a bottleneck, and approvals get batched without review.
• Named individuals as steps. The workflow stalls whenever that person is on leave.
• No return-for-amendment path. Approvers reject outright or approve flawed requests because the only alternative is to start again.
• Splitting to avoid thresholds. Limits tested per loan rather than per borrower invite structuring.
• Approval and disbursement merged. Removes the check that security and documentation are in place before funds move.
• Editable after approval. If terms can change post-approval without re-triggering the workflow, the approval record is meaningless.
• Weak audit trail. Recording only the final decision, not each step, leaves no evidence the hierarchy was followed.

Frequently asked questions

What is the difference between an approval workflow and an approval hierarchy? The hierarchy is the ranked structure of roles and their limits. The workflow is the operating process that routes a specific request through that structure, including conditions, escalation and outcomes.

How long should approval records be kept? For at least the statutory record retention period applying to the underlying transaction, which in most jurisdictions runs for several years after the account closes.