Thanks Bharath, I have created a ticket for the same (2nd approach), do I need to assign it to myself? I'm actually not able to assign it.
https://issues.apache.org/jira/browse/FINERACT-2342 On Thu, Aug 7, 2025 at 1:33 PM Bharath Gowda <bgo...@mifos.org> wrote: > Hi Sidhant, > > > Thanks for sharing the details > > In my view, I would go with Approach 2 if time is not a constraint - to > have a new type of charge at the time of FORECLOSURE. > - It is more straightforward > - It is a common request and many others would be benefited from this as > well > > But Approach 1 is still not a bad workaround if you are looking for a > faster solution. > > > Regards, > Bharath > Lead Implementation Analyst | Mifos Initiative > PMC Member | Apache Fineract > Mobile: +91.7019635592 > http://mifos.org <http://facebook.com/mifos> > <http://www.twitter.com/mifos> > > > On Tue, Aug 5, 2025 at 5:19 PM sidhant goel <sidhant@freo.money.invalid> > wrote: > >> *Hello Fineract Community,* >> >> We are currently in the process of migrating to Apache Fineract as our >> Loan Management System (LMS) and have been exploring options for >> implementing a foreclosure charge for loan preclosures. >> >> During our research, we identified two possible approaches: >> >> 1. >> >> Adding the charge manually as a *Specified Due Date Charge* at the >> time of foreclosure. >> 2. >> >> Introducing a new ChargeTimeType.FORECLOSURE enumeration and >> implementing the corresponding logic during the foreclosure process. >> >> We've successfully completed a proof of concept for the second approach, >> but we’re keen to hear the community's thoughts on the best way to achieve >> this within the Fineract framework. We're also excited about the >> opportunity to contribute to the project and collaborate with others in the >> community. 🙂 >> >> Looking forward to your insights! >> >
