Home/Products/Loan Origination System
Lending · Loan origination

Loan Origination System

Originate, underwrite and disburse loans in one role-gated pipeline — thirteen stages from application intake to final disbursement, with amount-based approval routing, SLA tracking and a full audit trail. Deployed in the cloud or on-premise.

Cloud or on-premiseAzure AD + LDAPAudit trail on every actionMulti-office
los.creodata · Pending decisionsWestlands · BCC
Pipeline today
Applications awaiting a credit decision
Office 04
In pipeline
142
across 6 offices
Avg turnaround
11d
−1.4d MoM
SLA breaches
3
escalated
Pending BCC decisionsOpen queue →
JS
João da Silva
Equipment finance · 6d at stage
KES 65.0MCRITICAL
FA
Fatima Al-Mansouri
Working capital · 4d at stage
KES 48.0MURGENT
ML
Mara Logistics Ltd
Trade finance · 2d at stage
KES 12.0MHIGH
AN
Amani Njoroge
Asset finance · 1d at stage
KES 2.4MNORMAL
13
Workflow stages
From CSO intake to final disbursement — each role-gated and recorded
5
Approval tiers
BCC, Head, MCC, Committee and Risk, routed by loan amount
6
Backend services
Workflow, products, auth, audit, notifications and SLA on .NET 9
2
Deployment modes
Azure cloud or on-prem Kubernetes — Azure AD or Windows/LDAP
The journey, at a glance

From application to disbursement, one accountable path.

Behind the scenes there are thirteen role-gated stages. For everyone else, the loan moves through six clear phases — each with a named owner and a clock running against it.

Stage 1
Apply
CSO

Capture the borrower, accounts and loan request; attach the required documents.

Stage 2
Assign
Branch Manager

Route the application to a relationship manager within the office.

Stages 3–4
Assess
RM · Credit Admin

Prepare the credit proposal; verify documents for completeness.

Stages 5–9
Decide
Credit committees

BCC, Head, MCC or Committee decide — escalated by amount.

Stages 11–12·R
Clear
Legal · Finance · Risk

Legal clearance, finance approval and a risk gate on large facilities.

Stages 10·13
Disburse
Disbursement

Release funds against the approval trail and close the application.

The workspace

Every officer works the same queue-to-decision surface.

No swivel-chairing between systems. Officers pick up what's assigned to them, see the full application in one aggregate view, and act — while the SLA clock and audit log run underneath. Click through the surfaces.

los.creodata/stage5/pending
Workflow/Pending decisions
Westlands
Pending BCC decisions
24 applications awaiting a credit decision · sorted by priority then age
My officeOverdueAll
ApplicantProductAmountAt stageSLAPriorityAction
JS
João da Silva
Business · Mara Holdings
Equipment financeKES 65.0M6dBreachedCRITICALMake decision
FA
Fatima Al-Mansouri
Business · Al-Mansouri Co
Working capitalKES 48.0M4dOverdueURGENTMake decision
ML
Mara Logistics Ltd
Business
Trade financeKES 12.0M2d1d leftHIGHMake decision
CX
Chen Xiaoming
Individual
Term loanKES 9.5M1d2d leftNORMALMake decision
AN
Amani Njoroge
Individual
Asset financeKES 2.4M1d2d leftNORMALMake decision
ZT
Zawadi Traders
Business
OverdraftKES 6.0M0d3d leftNORMALMake decision
The full pipeline

Thirteen stages, each gated to a role.

The workflow engine enforces who can act at every step and where the application goes next. Higher-value loans pick up extra committee and risk gates; smaller ones take the short path. No stage can be skipped, and nothing moves without a recorded handoff.

Origination
Stages 1–4
1
Application intake
Customer Service Officer
2
Assignment
Branch Manager
3
Proposal preparation
Relationship Manager
4
Document verification
Branch Credit Admin
Credit decision
Stages 5–9
5
BCC decision≤ 50K
Business Credit Committee
6
Head approval≤ 100K
Head of Corporate / Retail
7
Credit analysis
Credit Analyst
8
MCC review≤ 500K
Management Credit Committee
9
Committee review
Committee Members
Fulfilment
Stages 10–13 · R
11
Legal processing
Legal Officer
12
Finance approval
Finance Officer
R
Risk approval
Risk Officer · high-value
10
Loan disbursement
Disbursement Officer
13
Final disbursement
Final Disbursement Officer
Amount-based routing

The loan amount decides who signs off.

Approval authority is tiered. Each decision point checks the amount against the next limit and routes the application up or onward — so a small asset-finance deal clears in a few hands, while a multi-million facility gathers every committee and risk sign-off it needs.

Every decision endpoint re-checks the amount against the next limit before it routes — authority is enforced server-side, not just in the UI.
Smaller loans skip the higher committees entirely and move straight to legal and disbursement.
Facilities above the risk threshold pick up a dedicated risk-officer gate before any funds are released.
Tier 1
BCC decision
First credit decision at the branch
≤ 50K
Tier 2
Head of Corporate / Retail
High-value review above the BCC limit
> 10M
Tier 3
MCC review
Major credit decisions
≤ 500K
Tier 4
Board / Committee
Largest facilities
> 400M
Tier 5
Risk approval
Final risk gate before disbursement
> 100M
Capabilities

Built for accountable, auditable lending.

13-stage role-based workflow

The workflow engine orchestrates intake to disbursement, gating each stage to a role with explicit, recorded handoffs.

Amount-based routing

Loan value automatically routes applications through BCC, Head, MCC, Committee and Risk gates — checked at every decision point.

SLA & turnaround monitoring

Every stage is timed against a target; overdue and breached applications surface with priority and escalation.

Full audit trail

Every decision, assignment and document action is logged with actor, timestamp and a correlation ID for distributed tracing.

Multi-office & branch

Applications, queues and approval limits are scoped per office, so each branch sees and acts on only its own pipeline.

Configurable product catalog

Products, categories, fees, collateral, requirements and routing rules are configured per market — no code changes.

Notifications at every handoff

Templated, message-queue-backed email keeps officers and committees moving the moment work lands in their queue.

Azure AD + on-prem LDAP

Role-based access integrates with Entra ID in the cloud or Windows / LDAP on-premise — least privilege by default.

Architecture

A portal over six services — your cloud or ours.

A Next.js portal fronts a backend-for-frontend proxy that injects credentials server-side, so the browser never sees a service key. Behind it, six independent .NET services each own one concern. The same build runs on Azure or on your own Kubernetes.

Backend services
Workflow engine
Drives the 13-stage application lifecycle, transitions and routing.
Product catalog
Loan products, categories, attributes, fees, collateral and rules.
Authorization
RBAC roles, permissions and per-office user-role assignment.
Audit logging
Immutable audit logs and decision records across every stage.
Email notifications
Templated, message-queue-backed notifications and an outbox.
SLA monitoring
SLA configuration and turnaround tracking per stage and office.
Cloud and on-premise, at parity

Identity, storage and messaging sit behind abstractions, so every feature works the same on Azure or in your data centre — and authentication follows your estate.

Azure cloud
Azure Functions (.NET 9)
PostgreSQL
Entra ID / Azure AD
Application Insights
On-prem Kubernetes
Kubernetes (containers)
PostgreSQL + RabbitMQ
Windows / LDAP
OpenTelemetry (OTLP)
Identity & access

Role-based access, scoped per office. Authentication adapts to where you run.

Cloud — Azure AD / Entra ID
MSAL single sign-on for staff identities managed in your tenant.
On-prem — Windows / LDAP
Directory-backed authentication for air-gapped deployments.
BFF proxy keeps keys server-side
Service credentials are injected by the proxy — never exposed to the browser.

See a loan move from application to disbursement.

A live walkthrough on a realistic pipeline — your products, your offices, your approval limits.