Skip to content

Commit 53d9790

Browse files
magyari-adamadamsaghy
authored andcommitted
FINERACT-2338: Allow backdated interest change on progressive loans - documentation
1 parent 56c71f7 commit 53d9790

File tree

2 files changed

+109
-0
lines changed

2 files changed

+109
-0
lines changed
Lines changed: 108 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,108 @@
1+
= Backdated interest modification
2+
3+
In the previous implementation we were only allowing the interest rate modification from current date and from now on we will allow Interest modification backdated on progressive loans as well.
4+
5+
[IMPORTANT]
6+
====
7+
Only available on progressive loans.
8+
====
9+
10+
== Functionality
11+
Validations updated to allow backdated interest change, even on charged-off or otherwise closed loan. Making progressive loans more flexible.
12+
13+
1. Interest rate can be modified from backdate any date from first disbursement date
14+
15+
2. Interest will be affected from the applied date itself.
16+
17+
3. Backdate can be done on already paid Installments as well
18+
19+
4. Repayment schedule will be recalculated with New EMI and Interest from the Interest applied schedule date
20+
21+
- Backdated PAID Installments and Unpaid/Partial Paid Installment EMI would be changed as per the new calculated EMI
22+
23+
5. Installments paid Interest amount will be reverse replayed as per the new Interest rate from the applied date
24+
25+
- Transactions will be reversed replayed if there is any change is allocations
26+
27+
- Accrual adjustments will be done during reverse replay (during the COB process)
28+
29+
6. No of Installments will remain the same, only EMI and Interest would get affected
30+
31+
7. Backdated Interest modification allowed on the loan that is charged off
32+
- If the repayment that was made before the charge-off is reversed and replayed due to backdated Interest modification,then the accounting entry of the reversed transaction and replayed transaction should follow standard accounting rules and not charge-off accounting rules
33+
34+
8. Backdated interest modification allowed on the loan that is overpaid, and CBR is complete.
35+
- Any action that triggers the recalculation (ex: reversal of backdated transaction) on the CBR loan will result in treating CBR as a credit transaction during reverse-replay. Same logic to be applied if the backdated interest modification is allowed on CBR loan accounts.
36+
37+
9. Asset transfer (externalization)
38+
- If the repayment that was made before the asset owner change got reversed and replayed due to backdated Interest modification,
39+
then, the accounting entry for the reversed transaction and replayed transaction include the tag of the current asset owner
40+
41+
10. Since backdated Interest modification is allowed on CBR/overpaid loans, we can keep the modification open on closed loans as well
42+
43+
- system will do the chronological reverse-replay when the backdated Interest is changed on closed loans, schedule and transaction will be allocated accordingly
44+
45+
46+
== API endpoints
47+
=== Create reschedule loans request (create reschedule)
48+
49+
* *Endpoint*: `/rescheduleloans`
50+
* *Method*: `POST`
51+
52+
.Example interest rate change request
53+
[source,json]
54+
----
55+
{
56+
"loanId": 1, // Mandatory
57+
"newInterestRate": 1, // Mandatory for interest rate change type reschedule
58+
"rescheduleFromDate": "2024-01-01", // Mandatory
59+
"rescheduleReasonId": 54, // Mandatory
60+
"submittedOnDate": "2024-01-01", // Mandatory
61+
"dateFormat": "yyyy-MM-dd", // Mandatory
62+
"locale": "en" // Mandatory
63+
}
64+
----
65+
66+
.Example interest rate change response
67+
[source,json]
68+
----
69+
{
70+
"resourceId": 1,
71+
"loanId": 1,
72+
"clientId": 1,
73+
"officeId": 1
74+
}
75+
----
76+
77+
=== Update reschedule loans request (approve reschedule)
78+
79+
* *Endpoint*: `/rescheduleloans/<reschedule_Id>`
80+
* *Method*: `POST`
81+
82+
.Example reschedule approve request
83+
[source,json]
84+
----
85+
{
86+
"approvedOnDate": "2024-01-01", // Mandatory for approval
87+
"submittedOnDate": "2024-01-01", // Mandatory
88+
"dateFormat": "yyyy-MM-dd", // Mandatory
89+
"locale": "en" // Mandatory
90+
}
91+
----
92+
93+
.Example reschedule approve response
94+
[source,json]
95+
----
96+
{
97+
"changes": {
98+
"approvedByUserId": 1,
99+
"approvedOnDate": "2024-01-01",
100+
"dateFormat": "yyyy-MM-dd",
101+
"locale": "en"
102+
},
103+
"clientId": 186,
104+
"loanId": 188,
105+
"officeId": 1,
106+
"resourceId": 35
107+
}
108+
----

fineract-doc/src/docs/en/chapters/features/index.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,3 +5,4 @@ This section covers specific features and functionality available in Apache Fine
55
include::capitalized-income.adoc[leveloffset=+1]
66
include::buydown-fee.adoc[leveloffset=+1]
77
include::approved-amount-modification.adoc[leveloffset=+1]
8+
include::backdated_interest_modification.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)