EDSONZ-WASSWA opened a new pull request, #5791:
URL: https://github.com/apache/fineract/pull/5791

   ## Description
   
   Background
   When a borrower misses several payments, Fineract calculates penalty charges 
on each overdue installment. Up until this change, attempting to reschedule 
such a loan would fail immediately with a not.allowed.due.to.overdue.charges 
validation error, making it impossible to help borrowers who genuinely needed 
their repayment schedule restructured. 
   This was a real gap  the most common reason a lender reschedules a loan is 
precisely because the borrower has fallen behind.
   
   What this PR does
   The system used to stop loan rescheduling completely whenever overdue 
penalty charges existed. Now it doesn't have to.
   There's a new optional flag " waiveOverdueCharges" that a lender can pass 
when approving a reschedule. Set it to true and the system clears all 
outstanding overdue penalties right before building the new repayment schedule.
   This practically makes sense:
    when restructuring a loan, the lender usually wants to clear those 
penalties as part of the deal, so this just handles it in one step instead of 
two.
   Leave the flag out or set it to false and nothing changes the original block 
stays in place. No decision made, no charges touched.
   For the actual waiving, it hooks straight into the existing charge waiver 
logic, so you get the same audit trail and transaction records as a manual 
waiver through the User interface (UI).
   
   ## Checklist
   
   Please make sure these boxes are checked before submitting your pull request 
- thanks!
   
   - [ ] Write the commit message as per [our 
guidelines](https://github.com/apache/fineract/blob/develop/CONTRIBUTING.md#pull-requests)
   - [ ] Acknowledge that we will not review PRs that are not passing the build 
_("green")_ - it is your responsibility to get a proposed PR to pass the build, 
not primarily the project's maintainers.
   - [ ] Create/update [unit or integration 
tests](https://fineract.apache.org/docs/current/#_testing) for verifying the 
changes made.
   - [ ] Follow our [coding 
conventions](https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions).
   - [ ] Add required Swagger annotation and update API documentation at 
fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with 
details of any API changes
   - [ ] [This PR must not be a "code 
dump"](https://cwiki.apache.org/confluence/display/FINERACT/Pull+Request+Size+Limit).
 Large changes can be made in a branch, with assistance. Ask for help on the 
[developer mailing list](https://fineract.apache.org/#contribute).
   
   Your assigned reviewer(s) will follow our [guidelines for code 
reviews](https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide).
   this is the link to the jira ticket 
[https://mifosforge.jira.com/issues?filter=-1&selectedIssue=WEB-479](https://mifosforge.jira.com/issues?filter=-1&selectedIssue=WEB-479)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to