Applications · Loan origination
From enquiry to money in the account. Every gate on the record.
Sourcing, application, KYC, bureau and field verification, credit assessment with deviations, sanction, documentation and disbursement, including the tranches and utilisation control that follow the money out. Agents assemble the file; credit officers sanction it.
sourcing · application · KYC · verificationBureau pull & DMN risk gridsDeviation & multi-level sanctionTranches, memo & utilisation
Evidence → deviation → delegated decisionThe recommendation can be prepared. The sanction stays with the credit officer and manager.LN-28418 · Credit review · deviation open
KYC & screeningClearBureauClearBank statementsDeviationDocumentsComplete
10:18•••
Seasonal dip is tied to two cited GST periods; all other displayed checks are clear.
Receivables confirmation remains before sanction.
Officer + manager review
The journey can move quickly without hiding the credit judgment.
LN-28418 is a file, not a stack of hand-offs. Identity, source evidence, deviation, delegated authority, conditions and money-out controls remain traceable from enquiry onward.
One file from source to evidence
Applicant, product, KYC, bureau and bank data enter one resumable record.
LN-28418 · Ravi IndustriesMake every policy hit explainable
The cash-flow floor, observed value and source periods sit beside the other clear checks.
−6.7% to policy floor · bank evidenceRoute by actual delegation
Nisha assesses the file. Arvind owns the deviation decision permitted by the amount and policy.
Nisha Kulkarni → Arvind MenonHold money until conditions clear
Sanction, documentation and disbursement remain distinct controlled gates with retained evidence.
Receivables confirmation · manager clearanceThe lending file, judged on what it takes to move it.
Origination software is bought on journey screens and lived with at the deviation, the missing document and the condition nobody checked before release. These rows are those.
Sourcing
Fragmented LOS
→A lead list per branch, and a partner spreadsheet.
Governed lending file
Branches, field officers, referral partners and digital journeys write one applicant record, with sourcing attribution and payout tracked: so the channel cost of a file is known at sanction.
Application capture
Fragmented LOS
→A form, and documents collected twice.
Governed lending file
Captured once, on web or the field app, with the document set derived from the product and the applicant profile: a file with a gap cannot advance, and the gap is named.
KYC & verification
Fragmented LOS
→Manual checks, and a scanned folder.
Governed lending file
KYC, screening and de-duplication run on arrival; residence and business verification are geo-verified visits with photographs, so every check is timestamped against the applicant.
Credit assessment
Fragmented LOS
→A credit note assembled by hand, on the analyst's template.
Governed lending file
Bureau pull, income assessment and policy as DMN grids; the underwriting agent assembles the file and proposes a decision with the policy cited: the credit officer sanctions.
Deviations & sanction
Fragmented LOS
→An exception approved over email, remembered by nobody.
Governed lending file
Each deviation is priced against policy and routed to the level permitted to clear it; the sanction carries the conditions it was granted under.
Disbursement
Fragmented LOS
→A payment file, and a reconciliation the following week.
Governed lending file
Conditions precedent checked, tranches scheduled, memo generated, and the banking file released only on the last clearance, with utilisation tracked after the money moves.
The loan book stays in your core lending or banking system. What moves here is the journey, the evidence, the decisions and the engagement around them: the parts that are process, not ledger.
The recommendation is prepared. The credit decision stays human.
Identity, bureau, bank evidence, policy variance and conditions remain traceable while the officer and manager assess the structure.
LN-28418 stays one governed file from application through sanction and release.Recommendation heldReview recorded · unsanctioned
Four checks, one open variance
PAN · GST · screening log · Identity and business match
Commercial bureau · 08 Aug · No active delinquency
Bank feed · 12 months · 2 months below policy floor
GST · ITR · invoices · Current set verified
The variance is priced and delegated
−6.7% to policy floor · Seasonal dip aligns with two cited GST periods; existing facility history is clear.
Applicant desk
Credit officer
Arvind Menon
The recommendation never replaces the decision
Product, applicant, and business profile joined
Source records retained on LN-28418
Two monthly credits below current policy floor
No sanction action taken; officer review requested
Evidence board · file completeness
Every clear check is visible beside the one that is not.
Filter KYC, bureau, bank and document evidence without losing the source, finding, or policy implication.
The filter changes the view. LN-28418 and its retained sources do not change.Identity and business match
No active delinquency
2 months below policy floor
Current set verified
Officer → manager · clear delegation
One prepared structure. Two different human judgments.
Nisha owns the file assessment. Arvind owns the deviation decision. The record makes that boundary visible before sanction.
Prepared work supports both checkpoints without impersonating either one.Credit officer mobile · complete decision task
Review the applicant, exception, evidence, consequence, path, and authority without shrinking the file.
The mobile surface carries the whole delegated task at a readable scale.
Record → deviation → evidence → consequence → prepared structure → named action.10:22•••
MSME cash-flow · 24 months · ₹48 L
Seasonal dip is tied to two cited GST periods; all other displayed checks are clear.
Receivables confirmation remains before sanction.
Compare with ₹48 L requested; retain quarterly review and manager clearance.
Nisha Kulkarni→Arvind Menon
Officer assessment is due before manager decision.Officer review recorded. No sanction applied.Secured, unsecured and group lending, on one machine.
Microfinance JLG, retail, MSME, gold, vehicle and business loans differ in product master and policy grid, not in the discipline underneath. Every variant preserves the same discipline underneath the product-specific policy.
Product & scheme master
Products, tenures, rate cards, charges, eligibility rules and effective dates: versioned, so a file is assessed under the policy in force on its own date.
product · rate · effective dateSourcing & channel
Branch, field officer, referral partner and digital sourcing with attribution, productivity tracking and channel payout computed on disbursed value.
attribution · payoutApplication journey
Web, assisted and field capture with co-applicants, guarantors and group members; resumable, and the same file whichever channel touched it last.
resumable · co-applicant · groupKYC, AML & de-duplication
Identity and address verification, screening, and de-duplication against the existing book, with the match reasons shown, not just a flag.
kyc · screening · dedupeBureau & assessment
Bureau pull with policy hit rules, income and cash-flow assessment, scorecards and DMN risk grids that the credit team can change without a release.
bureau · scorecard · dmnField verification
Residence, business and collateral verification as geo-verified visits with photographs, readings and the verifier named on every observation.
geo · photo · verifierSanction & documentation
Delegation matrix by amount, product and deviation; sanction letter, agreement, e-sign and e-stamp generated from the record with version history.
delegation · e-sign · versionDisbursement management
Conditions precedent, tranche schedules, disbursement memo, banking file release, and utilisation and end-use evidence collected after payout.
cp · tranche · memo · utilisationApplication in → controlled money out
A file that cannot disburse until its last condition clears.
Prepared recommendations can shorten review. They cannot clear a deviation, remove a condition or release a banking file.
“which sanctioned files have not disbursed in ten days, and what condition is open”Prepared by the system · sanctioned and released through named human gates
Application inBRANCH · PARTNER · DIGITAL
↓Underwriting agentBUREAU · INCOME · GRID
↓Within policy?DEVIATION · DELEGATION
↓Credit officerSANCTIONS WITH CONDITIONS
↓DisburseCP CHECK · TRANCHE · MEMO
↓Live accountUTILISATION · TRAIL PINNED
Four agents on the file. Officers still sanction.
Agents assemble and route. Officers still sanction, and release remains a controlled action.
Pulls the bureau report, reads the documents and assembles the credit file with every gap named.
proposes; never decidesRuns KYC, screening and de-duplication, and shows the reason behind every match it raises.
exceptions go to compliancePrices each deviation against policy and routes it to the level permitted to clear it.
no deviation without an approverTracks conditions precedent and tranche dates, and holds the release until the last one clears.
release stays a human action
Bring one loan product. Watch a file reach disbursement.
A 90-minute working session: your product master, credit policy grid and delegation matrix drafted as an FRS, approved, and generated to a staging tenant with one file walked end to end.
For your technical team
Origination is meta on the platform: the same customer record collections works, durable execution behind every sanction condition, and each decision attributable to the policy version in force when it was made, inside your VPC where the regulator expects it.