Skip to content

FINERACT-2807: Fix fixed interest scaling when in the middle of period - #6417

Open
Cocoa-Puffs wants to merge 1 commit into
apache:developfrom
openMF:FINERACT-2807-fix-reage-equal-amortiztion-issue
Open

FINERACT-2807: Fix fixed interest scaling when in the middle of period#6417
Cocoa-Puffs wants to merge 1 commit into
apache:developfrom
openMF:FINERACT-2807-fix-reage-equal-amortiztion-issue

Conversation

@Cocoa-Puffs

Copy link
Copy Markdown
Contributor

Description

Describe the changes made and why they were made. (Ignore if these details are present on the associated Apache Fineract JIRA ticket.)

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Write the commit message as per our guidelines
  • 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 for verifying the changes made.
  • Follow our 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". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.
  • If merging this PR resolves a JIRA issue, I will mark that issue as resolved and set "Fix Version/s" appropriately.

Your assigned reviewer(s) will follow our guidelines for code reviews.

@Cocoa-Puffs
Cocoa-Puffs force-pushed the FINERACT-2807-fix-reage-equal-amortiztion-issue branch from 753100f to 7d5fedd Compare September 9, 2026 08:01
ProgressiveLoanInterestScheduleModel scheduleModelCopy = scheduleModel.deepCopy(mc);
calculateRateFactorForScheduleTillDateInclusive(scheduleModelCopy, targetDate);
if (fixedInterestTillDate) {
scaleFixedInterestTillDate(scheduleModelCopy, targetDate);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

scaleFixedInterestTillDate runs before calculateLastUnpaidRepaymentPeriodEMI, so fixedInterest is already mutated when the EMI-pass uses it as a floor (see ~1290–1292: paidPrincipal + fixedInterest).

Maybe it will be better to move scaleFixedInterestTillDate after calculateLastUnpaidRepaymentPeriodEMI?

*/
private void scaleFixedInterestTillDate(ProgressiveLoanInterestScheduleModel scheduleModelCopy, LocalDate targetDate) {
scheduleModelCopy.repaymentPeriods().forEach(rp -> {
if (rp.getFixedInterest().isGreaterThanZero()) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it`s worth to gate with && rp.isReAged()? updateModelForReageEqualAmortization sets reAged=true on exactly the periods that later receive fixedInterest, so this does not weaken the fix. It does keep scaling off non-re-age uses of fixedInterest (e.g. copyWithoutPaidAmounts / accelerate-maturity aggregation).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants