Loan approval process flowchart
A worked example to adapt. Rename steps, add branches and owners to match how your team actually works.
Mermaid source for this diagram
flowchart TD
s(["Applicant submits application"])
docs["Collect income and ID documents"]
d1{"Documents complete?"}
req["Request missing documents"]
kyc["Identity and KYC checks"]
cr["Pull credit report"]
uw["Underwriter reviews risk"]
d2{"Decision?"}
dec(["Send decline notice with reasons"])
cond["Issue conditional approval"]
d3{"Conditions met?"}
fund["Sign agreement and disburse funds"]
e(["Loan funded"])
s --> docs
docs --> d1
d1 -->|No| req
req --> d1
d1 -->|Yes| kyc
kyc --> cr
cr --> uw
uw --> d2
d2 -->|Decline| dec
d2 -->|Approve| cond
cond --> d3
d3 -->|Yes| fund
d3 -->|No| uw
fund --> ePaste into any Markdown tool that renders Mermaid, such as GitHub.
About this loan approval process flowchart
Lending processes are usually drawn in BPMN because several roles touch each application: the applicant, a loan officer, compliance and an underwriter. This example shows the sequence and decision gates; generate a swimlane version to place each step in its role's lane.
It is an illustration of a typical consumer or small-business loan flow, not a compliance procedure. Your lending policy and regulators decide the actual checks and notices.
Step by step
- Application. The applicant submits the application and supporting documents; incomplete files loop back.
- Identity checks. KYC and identity verification run before credit is pulled.
- Credit and underwriting. An underwriter reviews the credit report, income and risk against policy.
- Decision. Declines get a notice with reasons; approvals may carry conditions.
- Funding. Once conditions are met, the borrower signs and funds are disbursed.
How to make it in flow-chart.io
- Start from the example. Edit the text in the generator box above so it names your own loan product and checks, then press Generate. The free preview needs no sign-up.
- Add the branches. Add the decision points that matter for you, for example manual review needed? or collateral appraisal. Each decision becomes a diamond with labeled outcomes.
- Assign owners. Save the diagram to the editor (free account) and rename steps to show who does what: applicant, loan officer, compliance and underwriter lanes.
- Share or export. Share a read-only view link: people with the link can view the diagram but not edit it. Downloads as PNG, SVG or PDF are part of Flow Pro (see pricing).
Tips
- Use lanes per role; BPMN reviewers expect to see who owns each task.
- Show the conditional-approval loop explicitly; it is where files wait longest.
- Keep adverse-action notices as their own step so they are not forgotten.
Frequently asked questions
- Is this a real BPMN diagram?
- The picture above uses flowchart shapes for readability. The generator can produce a BPMN-style diagram with pools, lanes, gateways and events; ask for 'BPMN with lanes' in the prompt.
- What are the main steps in loan approval?
- Application and documents, identity checks, credit report, underwriting, decision, conditions and funding.
- Can I add an automated decision engine?
- Yes. Add an 'automated scoring' step before underwriting and a gateway that routes only borderline cases to a human.