Guide
Anatomy of a loan application, from submission to disbursement
9 min read
Every lender describes their process differently, but underneath the vocabulary the shape is remarkably consistent. An application arrives, the applicant is identified, their ability to repay is assessed, someone with authority decides, a contract is signed, and money moves.
This guide walks through that chain one step at a time. For each step it describes what has to happen, what the manual version costs, and what is left for a person to do once the step is automated.
The shape of the flow
Before automating anything, it helps to write the process down as a sequence of states rather than a list of tasks. A task list describes what your team does today. A state machine describes what has to be true before an application can move forward, which is the thing software can enforce.
01
Submitted
The applicant has provided enough information to be identified and contacted. Nothing has been verified yet.
02
Verified
Identity has been confirmed against a document, and screening has either come back clear or has been reviewed and cleared by a person.
03
Assessed
Affordability and risk have been evaluated from bank data, declared information, and whatever scoring you apply.
04
Decided
An accept, decline, or counter-offer has been recorded by someone authorised to make it, with the reasoning attached.
05
Contracted
The agreement has been issued, signed electronically, and stored with the case.
06
Disbursed
Funds have left, the repayment schedule exists, and the loan has moved from origination into servicing.
Identity and screening
The first gate is establishing that the applicant is a real, identifiable person you are permitted to do business with. That means document verification, a liveness check, and screening against sanctions, politically exposed person lists, and adverse media.
The mistake to avoid here is treating every screening hit as a blocker. Matching on names is imprecise, so a workable configuration sets a sensible threshold, routes matches to a review queue, and records who cleared each one. A system that blocks too readily gets overridden informally, and informal overrides leave no trail.
- Verification runs in the applicant's own session, not by email attachment
- Structured data comes back and populates the case automatically
- Screening hits create review tasks with a named owner
- Every clear or confirm is timestamped against the case
Affordability, in evidence rather than declaration
A declared income figure is a claim. A connected bank account is evidence. With open banking consent, you see salary credits arriving on a rhythm, existing loan repayments leaving, and the behavioural markers that predict trouble better than any self-reported number.
The strongest signal in most portfolios is not how much someone earns. It is how steadily they already meet obligations.
This is also the step where applicants drop out, so the connection flow deserves attention. Explain what is being read, for how long, and why refusing means a slower manual route rather than an automatic decline.
The decision, and who is allowed to make it
Scoring produces a recommendation. Your credit policy decides what happens with it: auto-accept below a threshold, auto-decline above another, and a review band in between where a human decides. The important part is that the boundaries are configuration, not code, so they can move on a Tuesday afternoon without a release.
Approval levels belong in the same place. A junior analyst approving within limits and a committee approving above them are the same mechanism with different thresholds, and both should produce the same kind of record.
Contract and payout
Once a decision exists, the agreement is generated from the case data, sent for electronic signature, and stored with the signing evidence attached. Disbursement follows from the signature rather than from someone noticing that a signature arrived.
From there the loan crosses into servicing: a schedule exists, collections are attempted on it, and the exceptions — failed payments, early settlement, restructuring — become the work. That half of the lifecycle is longer, quieter, and where most operational cost actually lives.
What to automate first
If you are starting from spreadsheets and email, resist the urge to model the whole lifecycle before going live. Pick the segment with the highest volume and the least discretion, run it end to end, and let the exceptions teach you what the configuration is missing.
- Highest-volume product first; the rare complex one last
- One decision path live and working beats five half-configured
- Keep a manual override, and watch how often it is used
- Treat every override as a question about the configuration
Have a system exactly as you envision it
Let's talk. It's time to make a better version of your business.