You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Abhishek Chaudhary <ab...@gmail.com> on 2026/06/25 16:06:14 UTC

Bug FINERACT-2658 current understandings

I have been reading Sir Adam's bug issue on amortization
as per my understanding the problem occurs when the payment is reversed as
when it happen the transaction get cancelled but the mappings stay behind
and we end up making a new transaction with no matching mapping which
breaks the repot
Fix I have in mind is making counter skip whos transaction was cancelled I
plan on doing this fix for both capitalized income and buydown fee if
possible
Since im new to the project could you let me know weather my understanding
is correct and weather the fix is in the right direction?

Re: Bug FINERACT-2658 current understandings

Posted by Ádám Sághy <ad...@gmail.com>.
Thank you for your interest, but the fix is on the way. You are more than welcomed to review once it raised! ;)

Regards,
Adam

> On Jun 25, 2026, at 6:06 PM, Abhishek Chaudhary <ab...@gmail.com> wrote:
> 
> I have been reading Sir Adam's bug issue on amortization
> as per my understanding the problem occurs when the payment is reversed as when it happen the transaction get cancelled but the mappings stay behind and we end up making a new transaction with no matching mapping which breaks the repot
> Fix I have in mind is making counter skip whos transaction was cancelled I plan on doing this fix for both capitalized income and buydown fee if possible
> Since im new to the project could you let me know weather my understanding is correct and weather the fix is in the right direction?