Santosh Math created FINERACT-272:
-------------------------------------

             Summary: Undo Loan transaction is not affecting the accrual 
accounting even if the loan is under " Non Performing Assets" (NPA) state
                 Key: FINERACT-272
                 URL: https://issues.apache.org/jira/browse/FINERACT-272
             Project: Apache Fineract
          Issue Type: Bug
          Components: Loan
            Reporter: Santosh Math
            Assignee: Markus Geiss
            Priority: Minor


As posted by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1153

Original Description:
1. Create a loan product with periodic accrual accounting and NPA as 10 days.
2. Create a client and attach the above mentioned loan product to that client.
3. Submit a new loan application on 01 April 2014 approve and disburse on the 
same date.
4. Click on system -> Scheduler job -> Run the job "Update Non Performing 
Assets".
(In database m_loan table in "is_npa" column the status displayed as "1")
4. Again Run the job " Add Accrual Transactions".
5. Click on the Transaction button in the above created loan account in which 
accrual accounting entries are not created because of loan under NPA state.
6. Make repayments on 08 April 2014 and 15 April 2014.
7. Click on system -> Scheduler job -> Run the job "Update Non Performing 
Assets".
(In database m_loan table in "is_npa" column the status displayed as "0")
8. Again Run the job " Add Accrual Transactions".
9. Click on the Transaction button in the above created loan account in which 
accrual accrual accounting entries are created.
10. In the same transaction page delete the transaction on 15 April 2014.
11. Again Run the job " Add Accrual Transactions" and "Update Non Performing 
Assets".
Expected Result:
Accrual entries created after NPA should get deleted in transaction page of 
loan account.
Actual Result:
Accrual entries created after NPA staus is not getting deleted.
(even In database m_loan table in "is_npa" column the status displayed as "1")



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to