You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Mihaly Dallos (Jira)" <ji...@apache.org> on 2023/01/02 13:35:00 UTC

[jira] [Updated] (FINERACT-1839) Reversal on the loan account after CBR

     [ https://issues.apache.org/jira/browse/FINERACT-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mihaly Dallos updated FINERACT-1839:
------------------------------------
    Description: 
{panel}
*As a* user
*I want to* _reverse a transaction posted before the loan account CBR_
*in order to* meet the real transaction reversal scenario
{panel}
h4. *Background and details:*

Standard practice is not to allow any reversal of old transactions once the CBR is posted on the loan account
{panel}
*Proposed solution*
 # Allowing reversal of financial transactions after the CBR on loan account

 # CBR transaction should be updated with the proper outstanding balance based on the reversal of transaction

 # Loan account should become ACTIVE state again, whenthe reverval on transaction happens

 # Repayment schedule balance and allocations should be adjusted as per the lastest transaction changes

 # Attached excel contians all the scenarios and use cases of transaction and repayment schedule of the loan account

 # No accounting changes for the CBR Transaction when it gets updated.
{panel}
{panel}
*Acceptance Criteria*
 # Tests covers the attached scenarios; where the reversal of refund is happening after a long gap.

 # Delinquency calculation doesn’t have regression
{panel}

  was:
{panel}
*As a* user
*I want to* _reverse a transaction posted before the loan account CBR_
*in order to* meet the real transaction reversal scenario
{panel}
h4. *Background and details:*

Standard practice is not to allow any reversal of old transactions once the CBR is posted on the loan account
{panel}
*Challenges (as we allow reversal of old transaction after CBR)*
 * Undo/Edit of the previous transaction should result in reverse and replay of the CBR transaction which is not standard behavior for CBR Transaction

 * If the Edit amount of the previous transaction unfolds new unusual scenarios which are difficult to handle

 ** if the modified amount is lesser than the CBR amount - then the loan has to be reopened considering CBR as a type of reverse transaction and handling all the complexities of repayment and amount allocations

 ** If the modified amount is greater than the CBR amount - then the loan should be treated as overpaid and hence enabling a new scenario of CBR

 * Handling the transaction and repayment schedule linkage complexity once we consider CBR for the opening of the loan account
{panel}
{panel}
*Proposed solution*
 # Reversal of refund can happen long after the *chargeback transaction.* In this case acount balance needs to be increased by the reversed amount.

 # If delinquency calculation is the concern then the CBR transaction has to be reversed manually to adjust and replay the previous transaction
{panel}


> Reversal on the loan account after CBR
> --------------------------------------
>
>                 Key: FINERACT-1839
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1839
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Mihaly Dallos
>            Priority: Major
>              Labels: PepperSoup
>
> {panel}
> *As a* user
> *I want to* _reverse a transaction posted before the loan account CBR_
> *in order to* meet the real transaction reversal scenario
> {panel}
> h4. *Background and details:*
> Standard practice is not to allow any reversal of old transactions once the CBR is posted on the loan account
> {panel}
> *Proposed solution*
>  # Allowing reversal of financial transactions after the CBR on loan account
>  # CBR transaction should be updated with the proper outstanding balance based on the reversal of transaction
>  # Loan account should become ACTIVE state again, whenthe reverval on transaction happens
>  # Repayment schedule balance and allocations should be adjusted as per the lastest transaction changes
>  # Attached excel contians all the scenarios and use cases of transaction and repayment schedule of the loan account
>  # No accounting changes for the CBR Transaction when it gets updated.
> {panel}
> {panel}
> *Acceptance Criteria*
>  # Tests covers the attached scenarios; where the reversal of refund is happening after a long gap.
>  # Delinquency calculation doesn’t have regression
> {panel}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)