'One Installment' Payment Is Doing Merge Installment, When It Should Not Do.
(Doc ID 2593544.1)
Last updated on SEPTEMBER 10, 2020
Applies to:Oracle FLEXCUBE Universal Banking - Version 11.83.03.0.0 and later
Information in this document applies to any platform.
On : 11.83.03.0.0 version, Implementation Support
'One Installment' payment is doing merge installment, when it should not do.
The system is merging the second with the third installment after apply a payment to One Installment, within the last fifteen days of second installment, which is just covering the first installment amount, that is overdue.
The information of the case is as below:
The loan was created for a product with value date 29 April 2019.
The first installment due date is 4 June 2019 and the second installment due date is 2 July 2019.
On 19 June 2019, between the first and second installment (within the last 15 days of the second installment), the user is applying a payment with value date as 19th June 2019 and recomputation basis as "One Installment", where the payment amount is just covering the complete first installment amount plus the more component of the first installment, the payment is not being applied to any amount of second installment, however, it is merging the second installment with the next one and this is not correct, i.e. for the second installment the schedule_st_date is 4 June 2019 but the schedule_due_date is 19 June 2019 .
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document