Cocoa-Puffs commented on code in PR #4884:
URL: https://github.com/apache/fineract/pull/4884#discussion_r2239643527


##########
fineract-e2e-tests-runner/src/test/resources/features/Loan.feature:
##########
@@ -5284,8 +5284,8 @@ Feature: Loan
       | 2  | 15   | 16 January 2024  | 16 January 2024 | 250.0           | 
125.0         | 0.0      | 0.0  | 0.0       | 125.0 | 125.0 | 0.0        | 0.0  
| 0.0         |
       |    |      | 16 January 2024  |                 | 500.0           |     
          |          | 0.0  |           | 0.0   | 0.0   |            |      |   
          |
       | 3  | 0    | 16 January 2024  | 16 January 2024 | 625.0           | 
125.0         | 0.0      | 0.0  | 0.0       | 125.0 | 125.0 | 0.0        | 0.0  
| 0.0         |
-      | 4  | 15   | 31 January 2024  |                 | 313.0           | 
312.0         | 0.0      | 0.0  | 0.0       | 312.0 | 125.0 | 125.0      | 0.0  
| 187.0       |
-      | 5  | 15   | 15 February 2024 |                 | 0.0             | 
313.0         | 0.0      | 0.0  | 0.0       | 313.0 | 125.0 | 125.0      | 0.0  
| 188.0       |
+      | 4  | 15   | 31 January 2024  |                 | 312.5           | 
312.5         | 0.0      | 0.0  | 0.0       | 312.5 | 125.0 | 125.0      | 0.0  
| 187.5       |

Review Comment:
   Because this is a non-interest bearing loan, previously disbursements were 
handled without using the EMI model. In the 
`recalculateRepaymentInstallmentsWithoutEMICalculation` method we have some 
rounding logic based on `installmentAmountInMultiplesOf` of the loan. So 
previously the periods got rounded to whole numbers (in case of 
installmentAmountInMultiplesOf = 1). Now with the EMI calculator we can just 
calculate the exact emi for the periods.



-- 
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