Skip to content

Commit 8716fcf

Browse files
udgatanikhiludgatanikhil
authored
Update LMSHandoff.md
1 parent c3c0328 commit 8716fcf

File tree

1 file changed

+100
-56
lines changed

1 file changed

+100
-56
lines changed

‎docs/MFL/LAP/Disbursement module/LMSHandoff.md‎

Lines changed: 100 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -1,65 +1,109 @@
11
<h2>LMS Handoff</h2>
22

33
<h3>First Tranche</h3>
4+
5+
<ul>
6+
<li>Ops user has to ‘approve disbursement’ for the active tranche to initiate the LMS handoff on disbursement tab</li>
7+
</ul>
8+
9+
<h4>Pre-checks/validations</h4>
10+
<p>
11+
Pre-checks/validations run on LMS handoff initiation for the first tranche. If any pre-check fails, LMS handoff is blocked:
12+
</p>
13+
14+
<ul>
15+
<li>All sanction conditions should be approved by Ops</li>
16+
<li>Ops checklist should be completed</li>
17+
<li>Disbursement date should be less than or equal to the LMS business date</li>
18+
<li>UCIC should be present for all applicant/co-applicants (fetched from PAN or mobile)</li>
19+
<li>“isNPA” flag should be false for all applicant and co-applicants</li>
20+
<li>IFSC code should be present in the Bank master</li>
21+
<li>Pincode should be present in the Pincode master</li>
22+
</ul>
23+
24+
<h4>LMS handoff APIs (First Tranche)</h4>
25+
<p>
26+
LMS handoff for first tranche initiates the below series of APIs in the following order:
27+
</p>
28+
29+
<ol>
30+
<li>Create Customer - for primary applicant and all co-applicants</li>
31+
<li>Process Receipt - For IMD details - This will be moved to journey now just after IMD is paid and not in the disbursal workflow</li>
32+
<li>Create Collateral</li>
33+
<li>Book Loan</li>
34+
<li>Process Instrumentation - For NACH details</li>
35+
<li>Create Document - Series of 4 APIs</li>
36+
</ol>
37+
38+
<h4>LMS Workflow Status</h4>
39+
<p>
40+
After LMS handoff is initiated, Ops user gets an option to “check status” of the LMS workflow. List of possible statuses:
41+
</p>
42+
43+
<ul>
44+
<li>“Payment initiated” - When LMS workflow initiated but status not fetched</li>
45+
<li>“Failed” - When any any pre-checks fails or any API out of the following fail: createCustomerAPI, createCollateral, bookLoan</li>
46+
<li>“Documents pending” - This is a substatus - When first 5 APIs are successful (till Process instrumentation) and Create Document API is in progress (this API might take some time, depends on number of documents)</li>
47+
<li>“Document failure” - This is a substatus - When Create Document API fails</li>
48+
<li>“Disbursed” - When createCustomer, createCollateral, bookLoan APIs are successful. System doesn't wait for the status of NACH API or createDocument API</li>
49+
</ul>
50+
51+
<h4>Retrigger Logic</h4>
52+
53+
<ul>
54+
<li>Ops user gets an option to retrigger LMS handoff (“retrigger disbursement” button) if the status is “failed”</li>
55+
<li>Retrigger option resumes the LMS workflow from the API which last failed</li>
56+
<li>Currently there is no option to retrigger from UI if either of NACH/Document APIs fail i.e. after the status of tranche is "Disbursed. Functionality to be added</li>
57+
<li>If Create Document API fails due to any document, rest other documents are uploaded</li>
58+
</ul>
59+
60+
<p>
61+
If LMS handoff is re-triggered in failure scenarios, following pre-checks are re-run:
62+
</p>
63+
464
<ul>
5-
<li>Ops user has to <strong>approve disbursement</strong> for the active tranche to initiate the LMS handoff on the Disbursement tab.</li>
6-
<li>Pre-checks/validations run on LMS handoff initiation for the first tranche. If any pre-check fails, LMS handoff is blocked:
7-
<ul>
8-
<li>All sanction conditions should be approved by Ops</li>
9-
<li>Ops checklist should be completed</li>
10-
<li>Disbursement date should be less than or equal to the LMS business date</li>
11-
<li>UCIC should be present for all applicant/co-applicants (fetched from PAN or mobile)</li>
12-
<li><code>isNPA</code> flag should be false for all applicant and co-applicants</li>
13-
<li>IFSC code should be present in the Bank master</li>
14-
<li>Pincode should be present in the Pincode master</li>
15-
</ul>
16-
</li>
17-
<li>LMS handoff for first tranche initiates the following series of APIs in order:
18-
<ul>
19-
<li>Create Customer – for primary applicant and all co-applicants</li>
20-
<li>Process Receipt – for IMD details (moved to journey after IMD is paid)</li>
21-
<li>Create Collateral</li>
22-
<li>Book Loan</li>
23-
<li>Process Instrumentation – for NACH details</li>
24-
<li>Create Document – series of 4 APIs</li>
25-
</ul>
26-
</li>
27-
<li>After initiation, Ops user can <strong>check status</strong> of the LMS workflow. Possible statuses:
28-
<ul>
29-
<li><strong>Payment initiated:</strong> LMS workflow started but status not fetched</li>
30-
<li><strong>Failed:</strong> Any pre-check fails or API failure (createCustomer, createCollateral, bookLoan)</li>
31-
<li><strong>Documents pending:</strong> First 5 APIs succeed, Create Document API in progress</li>
32-
<li><strong>Document failure:</strong> Create Document API fails</li>
33-
<li><strong>Disbursed:</strong> createCustomer, createCollateral, bookLoan APIs succeed; system doesn’t wait for NACH or Create Document API</li>
34-
</ul>
35-
</li>
36-
<li>Ops user can <strong>retrigger LMS handoff</strong> if status is “failed”. Retrigger resumes from the last failed API.</li>
37-
<li>If Create Document API fails, other documents are uploaded. Pre-checks re-run for retrigger:
38-
<ul>
39-
<li>Disbursement date ≤ LMS business date</li>
40-
<li>UCIC present for all applicants/co-applicants</li>
41-
<li><code>isNPA</code> flag = false</li>
42-
</ul>
43-
</li>
65+
<li>Disbursement date should be less than or equal to the LMS business date</li>
66+
<li>UCIC should be present for all applicant/co-applicants (fetched from PAN or mobile)</li>
67+
<li>“isNPA” flag should be false for all applicant and co-applicants</li>
4468
</ul>
4569

70+
<hr />
71+
4672
<h3>Second / Subsequent Tranche</h3>
73+
74+
<h4>Pre-checks/validations</h4>
75+
<p>
76+
Pre-checks/validations run on initiating LMS handoff for second/subsequent tranches:
77+
</p>
78+
79+
<ul>
80+
<li>Disbursement date should be less than or equal to the LMS business date</li>
81+
</ul>
82+
83+
<h4>LMS handoff APIs (Second / Subsequent Tranche)</h4>
84+
<ul>
85+
<li>Disbursal API</li>
86+
</ul>
87+
88+
<h4>LMS Workflow Status</h4>
89+
<p>
90+
List of the possible statuses of the LMS handoff for second/subsequent tranches:
91+
</p>
92+
93+
<ul>
94+
<li>Failed</li>
95+
<li>Disbursed</li>
96+
</ul>
97+
98+
<h4>Retrigger Logic</h4>
99+
<ul>
100+
<li>Ops user gets an option to retrigger LMS handoff for second/subsequent tranches if the status is “failed”</li>
101+
</ul>
102+
103+
<p>
104+
If LMS handoff is re-triggered in case of failure for second/subsequent tranches, following pre-checks are re-run:
105+
</p>
106+
47107
<ul>
48-
<li>Pre-checks/validations run before LMS handoff:
49-
<ul>
50-
<li>Disbursement date ≤ LMS business date</li>
51-
</ul>
52-
</li>
53-
<li>LMS handoff initiates the <strong>Disbursal API</strong>.</li>
54-
<li>Possible LMS statuses:
55-
<ul>
56-
<li>Failed</li>
57-
<li>Disbursed</li>
58-
</ul>
59-
</li>
60-
<li>Ops user can retrigger LMS handoff if status is “failed”. Pre-checks are re-run:
61-
<ul>
62-
<li>Disbursement date ≤ LMS business date</li>
63-
</ul>
64-
</li>
108+
<li>Disbursement date should be less than or equal to the LMS business date</li>
65109
</ul>

0 commit comments

Comments
 (0)