CBSNexora/cbsnexora-backend
4
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

FINERACT-2081: Adding TestrailIds, removing Skip tags

Browse Source
This commit is contained in:
Peter Kovacs
2025-02-24 14:27:35 +01:00
committed by Adam Saghy
parent 44ee19ec30
commit 2456f7fa71
16 changed files with 2460 additions and 2495 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fineract-e2e-tests-runner/src/test/resources/features/0_COB.feature
+1 -1
View File
@@ -1,7 +1,7 @@
@COBFeature @COBFeature
Feature: COBFeature Feature: COBFeature
@Skip @TestRailId:C2501 @TestRailId:C2501
Scenario: As an admin I would like to see that last closed business date got updated after COB catch up job finished Scenario: As an admin I would like to see that last closed business date got updated after COB catch up job finished
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
When Admin creates a client with random data When Admin creates a client with random data
fineract-e2e-tests-runner/src/test/resources/features/Datatables.feature
+6
View File
@@ -1,23 +1,27 @@
Feature: Datatables Feature: Datatables
@TestRailId:C3005
Scenario: Datatable's primary key is unique and indexed Scenario: Datatable's primary key is unique and indexed
When A datatable for "Loan" is created When A datatable for "Loan" is created
Then The following column definitions match: Then The following column definitions match:
| Name | Primary key | Unique | Indexed | | Name | Primary key | Unique | Indexed |
| loan_id | true | true | true | | loan_id | true | true | true |
@TestRailId:C3006
Scenario: Multirow datatable's primary key is unique and indexed Scenario: Multirow datatable's primary key is unique and indexed
When A multirow datatable for "Loan" is created When A multirow datatable for "Loan" is created
Then The following column definitions match: Then The following column definitions match:
| Name | Primary key | Unique | Indexed | | Name | Primary key | Unique | Indexed |
| id | true | true | true | | id | true | true | true |
@TestRailId:C3007
Scenario: Multirow datatable has the foreign key indexed Scenario: Multirow datatable has the foreign key indexed
When A multirow datatable for "Loan" is created When A multirow datatable for "Loan" is created
Then The following column definitions match: Then The following column definitions match:
| Name | Primary key | Unique | Indexed | | Name | Primary key | Unique | Indexed |
| loan_id | false | false | true | | loan_id | false | false | true |
@TestRailId:C3008
Scenario: Datatable with unique constrained column is indexed Scenario: Datatable with unique constrained column is indexed
When A datatable for "Loan" is created with the following extra columns: When A datatable for "Loan" is created with the following extra columns:
| Name | Type | Length | Unique | Indexed | | Name | Type | Length | Unique | Indexed |
@@ -27,6 +31,7 @@ Feature: Datatables
| Name | Primary key | Unique | Indexed | | Name | Primary key | Unique | Indexed |
| col1 | false | true | true | | col1 | false | true | true |
@TestRailId:C3009
Scenario: Datatable with indexed column Scenario: Datatable with indexed column
When A datatable for "Loan" is created with the following extra columns: When A datatable for "Loan" is created with the following extra columns:
| Name | Type | Length | Unique | Indexed | | Name | Type | Length | Unique | Indexed |
@@ -36,6 +41,7 @@ Feature: Datatables
| Name | Primary key | Unique | Indexed | | Name | Primary key | Unique | Indexed |
| col1 | false | false | true | | col1 | false | false | true |
@TestRailId:C3010 @TestRailId:C3011 @TestRailId:C3012
Scenario Outline: Query data from datatable with invalid filter Scenario Outline: Query data from datatable with invalid filter
When A datatable for "Loan" is created When A datatable for "Loan" is created
And The client calls the query endpoint for the created datatable with "<column_filter>" column filter, and "<value_filter>" value filter And The client calls the query endpoint for the created datatable with "<column_filter>" column filter, and "<value_filter>" value filter
fineract-e2e-tests-runner/src/test/resources/features/EMICalculation.feature
+79 -81
View File
@@ -131,7 +131,7 @@ Feature: EMI calculation and repayment schedule checks for interest bearing loan
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 75.0 | 2.33 | 0.0 | 0.0 | 77.33 | 0.0 | 0.0 | 0.0 | 77.33 | | 75.0 | 2.33 | 0.0 | 0.0 | 77.33 | 0.0 | 0.0 | 0.0 | 77.33 |
@TestRailId:C3156 @Skip @TestRailId:C3156
Scenario: EMI calculation with 360/30 setup - decimal - reschedule Scenario: EMI calculation with 360/30 setup - decimal - reschedule
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -155,19 +155,19 @@ Feature: EMI calculation and repayment schedule checks for interest bearing loan
When Admin sets the business date to "18 February 2024" When Admin sets the business date to "18 February 2024"
When Admin creates and approves Loan reschedule with the following data: When Admin creates and approves Loan reschedule with the following data:
| rescheduleFromDate | submittedOnDate | adjustedDueDate | graceOnPrincipal | graceOnInterest | extraTerms | newInterestRate | | rescheduleFromDate | submittedOnDate | adjustedDueDate | graceOnPrincipal | graceOnInterest | extraTerms | newInterestRate |
| 01 February 2024 | 18 February 2024 | 18 February 2024 | | | | 9.4822 | | 01 February 2024 | 18 February 2024 | 18 February 2024 | | | | |
Then Loan Repayment schedule has 6 periods, with the following data for periods: Then Loan Repayment schedule has 6 periods, with the following data for periods:
| Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 48 | 18 February 2024 | | 84.02 | 15.98 | 1.22 | 0.0 | 0.0 | 17.20 | 0.0 | 0.0 | 0.0 | 17.20 | | 1 | 48 | 18 February 2024 | | 84.12 | 15.88 | 1.25 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
| 2 | 29 | 18 March 2024 | | 67.48 | 16.54 | 0.66 | 0.0 | 0.0 | 17.20 | 0.0 | 0.0 | 0.0 | 17.20 | | 2 | 29 | 18 March 2024 | | 67.65 | 16.47 | 0.66 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
| 3 | 31 | 18 April 2024 | | 50.81 | 16.67 | 0.53 | 0.0 | 0.0 | 17.20 | 0.0 | 0.0 | 0.0 | 17.20 | | 3 | 31 | 18 April 2024 | | 51.05 | 16.6 | 0.53 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
| 4 | 30 | 18 May 2024 | | 34.01 | 16.8 | 0.4 | 0.0 | 0.0 | 17.20 | 0.0 | 0.0 | 0.0 | 17.20 | | 4 | 30 | 18 May 2024 | | 34.32 | 16.73 | 0.4 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
| 5 | 31 | 18 June 2024 | | 17.08 | 16.93 | 0.27 | 0.0 | 0.0 | 17.20 | 0.0 | 0.0 | 0.0 | 17.20 | | 5 | 31 | 18 June 2024 | | 17.46 | 16.86 | 0.27 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
| 6 | 30 | 18 July 2024 | | 0.0 | 17.08 | 0.13 | 0.0 | 0.0 | 17.21 | 0.0 | 0.0 | 0.0 | 17.21 | | 6 | 30 | 18 July 2024 | | 0.0 | 17.46 | 0.14 | 0.0 | 0.0 | 17.6 | 0.0 | 0.0 | 0.0 | 17.6 |
Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 100.0 | 3.21 | 0.0 | 0.0 | 103.21 | 0.0 | 0.0 | 0.0 | 103.21 | | 100.0 | 3.25 | 0.0 | 0.0 | 103.25 | 0.0 | 0.0 | 0.0 | 103.25 |
@TestRailId:C3157 @TestRailId:C3157
Scenario: EMI calculation with 360/30 setup - integer - repayment every 2 months Scenario: EMI calculation with 360/30 setup - integer - repayment every 2 months
@@ -358,8 +358,7 @@ Feature: EMI calculation and repayment schedule checks for interest bearing loan
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 300.0 | 7.98 | 0.0 | 0.0 | 307.98 | 0.0 | 0.0 | 0.0 | 307.98 | | 300.0 | 7.98 | 0.0 | 0.0 | 307.98 | 0.0 | 0.0 | 0.0 | 307.98 |
# TODO unskip and check when early repayment for EMI is implemented (PS-2076, PS-1958) @TestRailId:C3195
@Skip @TestRailId:C3195
Scenario: EMI calculation with 365/30 multidisburse setup - UC2: 1st installment fully repaid early, then 2nd disbursement in 1std installment period, allocation rule: NEXT INSTALLMENT Scenario: EMI calculation with 365/30 multidisburse setup - UC2: 1st installment fully repaid early, then 2nd disbursement in 1std installment period, allocation rule: NEXT INSTALLMENT
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -387,46 +386,45 @@ Feature: EMI calculation and repayment schedule checks for interest bearing loan
# --- Early full repayment of 1st installment --- # --- Early full repayment of 1st installment ---
When Admin sets the business date to "05 January 2024" When Admin sets the business date to "05 January 2024"
And Customer makes "AUTOPAY" repayment on "05 January 2024" with 17.13 EUR transaction amount And Customer makes "AUTOPAY" repayment on "05 January 2024" with 17.13 EUR transaction amount
# Then Loan Repayment schedule has 6 periods, with the following data for periods: Then Loan Repayment schedule has 6 periods, with the following data for periods:
# | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | |
# | 1 | 31 | 01 February 2024 | 01 February 2024 | 83.66 | 16.34 | 0.79 | 0.0 | 0.0 | 17.13 | 17.13 | 0.0 | 0.0 | 0.0 | | 1 | 31 | 01 February 2024 | 05 January 2024 | 83.66 | 16.34 | 0.79 | 0.0 | 0.0 | 17.13 | 17.13 | 17.13 | 0.0 | 0.0 |
# | 2 | 29 | 01 March 2024 | | 67.19 | 16.47 | 0.66 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 2 | 29 | 01 March 2024 | | 67.19 | 16.47 | 0.66 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 3 | 31 | 01 April 2024 | | 50.59 | 16.6 | 0.53 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 3 | 31 | 01 April 2024 | | 50.59 | 16.6 | 0.53 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 4 | 30 | 01 May 2024 | | 33.86 | 16.73 | 0.4 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 4 | 30 | 01 May 2024 | | 33.86 | 16.73 | 0.4 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 5 | 31 | 01 June 2024 | | 17.0 | 16.86 | 0.27 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 5 | 31 | 01 June 2024 | | 17.0 | 16.86 | 0.27 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 6 | 30 | 01 July 2024 | | 0.0 | 17.0 | 0.13 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 6 | 30 | 01 July 2024 | | 0.0 | 17.0 | 0.13 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
# | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | 100.0 | 2.78 | 0.0 | 0.0 | 102.78 | 17.13 | 0.0 | 0.0 | 85.65 | | 100.0 | 2.78 | 0.0 | 0.0 | 102.78 | 17.13 | 17.13 | 0.0 | 85.65 |
# Then Loan Transactions tab has the following data: Then Loan Transactions tab has the following data:
# | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance |
# | 01 January 2024 | Disbursement | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 100.0 | | 01 January 2024 | Disbursement | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 100.0 |
# | 01 February 2024 | Repayment | 17.13 | 16.34 | 0.79 | 0.0 | 0.0 | 83.66 | | 05 January 2024 | Repayment | 17.13 | 16.34 | 0.79 | 0.0 | 0.0 | 83.66 |
# --- 2nd disbursement in first period --- # --- 2nd disbursement in first period ---
When Admin sets the business date to "08 January 2024" When Admin sets the business date to "08 January 2024"
When Admin successfully disburse the loan on "08 January 2024" with "200" EUR transaction amount When Admin successfully disburse the loan on "08 January 2024" with "200" EUR transaction amount
# Then Loan Repayment schedule has 6 periods, with the following data for periods: Then Loan Repayment schedule has 6 periods, with the following data for periods:
# | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | |
# | 1 | 31 | 01 February 2024 | 01 February 2024 | 83.66 | 16.34 | 0.79 | 0.0 | 0.0 | 17.13 | 17.13 | 0.0 | 0.0 | 0.0 | | | | 08 January 2024 | | 200.0 | | | 0.0 | | 0.0 | 0.0 | | | |
# | | | 08 February 2024 | | 200.0 | | | 0.0 | | 0.0 | 0.0 | | | | | 1 | 31 | 01 February 2024 | | 250.68 | 49.32 | 2.01 | 0.0 | 0.0 | 51.33 | 17.13 | 17.13 | 0.0 | 34.2 |
# | 2 | 29 | 01 March 2024 | | 227.52 | 56.14 | 1.86 | 0.0 | 0.0 | 58.0 | 0.0 | 0.0 | 0.0 | 58.0 | | 2 | 29 | 01 March 2024 | | 201.33 | 49.35 | 1.98 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 3 | 31 | 01 April 2024 | | 171.32 | 56.2 | 1.8 | 0.0 | 0.0 | 58.0 | 0.0 | 0.0 | 0.0 | 58.0 | | 3 | 31 | 01 April 2024 | | 151.59 | 49.74 | 1.59 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 4 | 30 | 01 May 2024 | | 114.67 | 56.65 | 1.35 | 0.0 | 0.0 | 58.0 | 0.0 | 0.0 | 0.0 | 58.0 | | 4 | 30 | 01 May 2024 | | 101.46 | 50.13 | 1.2 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 5 | 31 | 01 June 2024 | | 57.58 | 57.09 | 0.91 | 0.0 | 0.0 | 58.0 | 0.0 | 0.0 | 0.0 | 58.0 | | 5 | 31 | 01 June 2024 | | 50.93 | 50.53 | 0.8 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 6 | 30 | 01 July 2024 | | 0.0 | 57.58 | 0.45 | 0.0 | 0.0 | 58.03 | 0.0 | 0.0 | 0.0 | 58.03 | | 6 | 30 | 01 July 2024 | | 0.0 | 50.93 | 0.4 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
# | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | 300.0 | 7.16 | 0.0 | 0.0 | 307.16 | 17.13 | 0.0 | 0.0 | 290.03 | | 300.0 | 7.98 | 0.0 | 0.0 | 307.98 | 17.13 | 17.13 | 0.0 | 290.85 |
# Then Loan Transactions tab has the following data: Then Loan Transactions tab has the following data:
# | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance |
# | 01 January 2024 | Disbursement | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 100.0 | | 01 January 2024 | Disbursement | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 100.0 |
# | 01 February 2024 | Repayment | 17.13 | 16.34 | 0.79 | 0.0 | 0.0 | 83.66 | | 05 January 2024 | Repayment | 17.13 | 16.34 | 0.79 | 0.0 | 0.0 | 83.66 |
# | 08 February 2024 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 283.66 | | 08 January 2024 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 283.66 |
# TODO unskip and check when early repayment for EMI is implemented (PS-2076, PS-1958) @TestRailId:C3196
@Skip @TestRailId:C3196
Scenario: EMI calculation with 365/30 multidisburse setup - UC3: 1st installment fully repaid early, then 2nd disbursement in 1std installment period, allocation rule: LAST INSTALLMENT Scenario: EMI calculation with 365/30 multidisburse setup - UC3: 1st installment fully repaid early, then 2nd disbursement in 1std installment period, allocation rule: LAST INSTALLMENT
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -454,43 +452,43 @@ Feature: EMI calculation and repayment schedule checks for interest bearing loan
# --- Early full repayment of 1st installment --- # --- Early full repayment of 1st installment ---
When Admin sets the business date to "05 January 2024" When Admin sets the business date to "05 January 2024"
And Customer makes "AUTOPAY" repayment on "05 January 2024" with 17.13 EUR transaction amount And Customer makes "AUTOPAY" repayment on "05 January 2024" with 17.13 EUR transaction amount
# Then Loan Repayment schedule has 6 periods, with the following data for periods: Then Loan Repayment schedule has 6 periods, with the following data for periods:
# | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | |
# | 1 | 31 | 01 February 2024 | 01 February 2024 | 83.66 | 16.34 | 0.79 | 0.0 | 0.0 | 17.13 | 17.13 | 0.0 | 0.0 | 0.0 | | 1 | 31 | 01 February 2024 | | 83.66 | 16.34 | 0.79 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 2 | 29 | 01 March 2024 | | 67.19 | 16.47 | 0.66 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 2 | 29 | 01 March 2024 | | 67.19 | 16.47 | 0.66 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 3 | 31 | 01 April 2024 | | 50.59 | 16.6 | 0.53 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 3 | 31 | 01 April 2024 | | 50.59 | 16.6 | 0.53 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 4 | 30 | 01 May 2024 | | 33.86 | 16.73 | 0.4 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 4 | 30 | 01 May 2024 | | 33.86 | 16.73 | 0.4 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 5 | 31 | 01 June 2024 | | 17.0 | 16.86 | 0.27 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 5 | 31 | 01 June 2024 | | 17.0 | 16.86 | 0.27 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 |
# | 6 | 30 | 01 July 2024 | | 0.0 | 17.0 | 0.13 | 0.0 | 0.0 | 17.13 | 0.0 | 0.0 | 0.0 | 17.13 | | 6 | 30 | 01 July 2024 | 05 January 2024 | 0.0 | 17.0 | 0.13 | 0.0 | 0.0 | 17.13 | 17.13 | 17.13 | 0.0 | 0.0 |
# Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
# | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | 100.0 | 2.78 | 0.0 | 0.0 | 102.78 | 17.13 | 0.0 | 0.0 | 85.65 | | 100.0 | 2.78 | 0.0 | 0.0 | 102.78 | 17.13 | 17.13 | 0.0 | 85.65 |
# Then Loan Transactions tab has the following data: Then Loan Transactions tab has the following data:
# | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance |
# | 01 January 2024 | Disbursement | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 100.0 | | 01 January 2024 | Disbursement | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 100.0 |
# | 01 February 2024 | Repayment | 17.13 | 16.34 | 0.79 | 0.0 | 0.0 | 83.66 | | 05 January 2024 | Repayment | 17.13 | 17.0 | 0.13 | 0.0 | 0.0 | 83.0 |
# --- 2nd disbursement in first period --- # --- 2nd disbursement in first period ---
When Admin sets the business date to "08 January 2024" When Admin sets the business date to "08 January 2024"
When Admin successfully disburse the loan on "08 January 2024" with "200" EUR transaction amount When Admin successfully disburse the loan on "08 January 2024" with "200" EUR transaction amount
# Then Loan Repayment schedule has 6 periods, with the following data for periods: Then Loan Repayment schedule has 6 periods, with the following data for periods:
# | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2024 | | 100.0 | | | 0.0 | | 0.0 | 0.0 | | | |
# | 1 | 31 | 01 February 2024 | 01 February 2024 | 83.66 | 16.34 | 0.79 | 0.0 | 0.0 | 17.13 | 17.13 | 0.0 | 0.0 | 0.0 | | | | 08 January 2024 | | 200.0 | | | 0.0 | | 0.0 | 0.0 | | | |
# | | | 08 February 2024 | | 200.0 | | | 0.0 | | 0.0 | 0.0 | | | | | 1 | 31 | 01 February 2024 | | 250.68 | 49.32 | 2.01 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 2 | 29 | 01 March 2024 | | 227.52 | 56.14 | 1.86 | 0.0 | 0.0 | 58.0 | 0.0 | 0.0 | 0.0 | 58.0 | | 2 | 29 | 01 March 2024 | | 201.33 | 49.35 | 1.98 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 3 | 31 | 01 April 2024 | | 171.32 | 56.2 | 1.8 | 0.0 | 0.0 | 58.0 | 0.0 | 0.0 | 0.0 | 58.0 | | 3 | 31 | 01 April 2024 | | 151.59 | 49.74 | 1.59 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 4 | 30 | 01 May 2024 | | 114.67 | 56.65 | 1.35 | 0.0 | 0.0 | 58.0 | 0.0 | 0.0 | 0.0 | 58.0 | | 4 | 30 | 01 May 2024 | | 101.46 | 50.13 | 1.2 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 5 | 31 | 01 June 2024 | | 57.58 | 57.09 | 0.91 | 0.0 | 0.0 | 58.0 | 0.0 | 0.0 | 0.0 | 58.0 | | 5 | 31 | 01 June 2024 | | 50.93 | 50.53 | 0.8 | 0.0 | 0.0 | 51.33 | 0.0 | 0.0 | 0.0 | 51.33 |
# | 6 | 30 | 01 July 2024 | | 0.0 | 57.58 | 0.45 | 0.0 | 0.0 | 58.03 | 0.0 | 0.0 | 0.0 | 58.03 | | 6 | 30 | 01 July 2024 | | 0.0 | 50.93 | 0.4 | 0.0 | 0.0 | 51.33 | 17.13 | 17.13 | 0.0 | 34.2 |
# Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
# | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | 300.0 | 7.16 | 0.0 | 0.0 | 307.16 | 17.13 | 0.0 | 0.0 | 290.03 | | 300.0 | 7.98 | 0.0 | 0.0 | 307.98 | 17.13 | 17.13 | 0.0 | 290.85 |
# Then Loan Transactions tab has the following data: Then Loan Transactions tab has the following data:
# | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance |
# | 01 January 2024 | Disbursement | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 100.0 | | 01 January 2024 | Disbursement | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 100.0 |
# | 01 February 2024 | Repayment | 17.13 | 16.34 | 0.79 | 0.0 | 0.0 | 83.66 | | 05 January 2024 | Repayment | 17.13 | 17.0 | 0.13 | 0.0 | 0.0 | 83.0 |
# | 08 February 2024 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 283.66 | | 08 January 2024 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 283.0 |
When Admin set "LP2_ADV_PYMNT_INTEREST_DAILY_EMI_360_30_MULTIDISBURSE" loan product "DEFAULT" transaction type to "NEXT_INSTALLMENT" future installment allocation rule When Admin set "LP2_ADV_PYMNT_INTEREST_DAILY_EMI_360_30_MULTIDISBURSE" loan product "DEFAULT" transaction type to "NEXT_INSTALLMENT" future installment allocation rule
@TestRailId:C3197 @TestRailId:C3197
fineract-e2e-tests-runner/src/test/resources/features/Loan.feature
+7
View File
@@ -6078,6 +6078,7 @@ Feature: Loan
| 15 February 2024 | Accrual | 0.82 | 0.0 | 0.82 | 0.0 | 0.0 | 0.0 | false | | 15 February 2024 | Accrual | 0.82 | 0.0 | 0.82 | 0.0 | 0.0 | 0.0 | false |
Then Loan's all installments have obligations met Then Loan's all installments have obligations met
@TestRailId:C3483
Scenario: Early pay-off loan with interest, TILL_REST_FREQUENCY_DATE product Scenario: Early pay-off loan with interest, TILL_REST_FREQUENCY_DATE product
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -6140,6 +6141,7 @@ Feature: Loan
Then Loan's all installments have obligations met Then Loan's all installments have obligations met
When Admin set "LP2_ADV_PYMNT_INTEREST_DAILY_EMI_360_30_INTEREST_RECALCULATION_DAILY_TILL_REST_FREQUENCY_DATE" loan product "DEFAULT" transaction type to "LAST_INSTALLMENT" future installment allocation rule When Admin set "LP2_ADV_PYMNT_INTEREST_DAILY_EMI_360_30_INTEREST_RECALCULATION_DAILY_TILL_REST_FREQUENCY_DATE" loan product "DEFAULT" transaction type to "LAST_INSTALLMENT" future installment allocation rule
@TestRailId:C3484
Scenario: Interest recalculation - S1 daily for overdue loan Scenario: Interest recalculation - S1 daily for overdue loan
Given Global configuration "enable-business-date" is enabled Given Global configuration "enable-business-date" is enabled
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
@@ -6161,6 +6163,7 @@ Feature: Loan
| 5 | 31 | 01 June 2024 | | 17.85 | 16.43 | 0.58 | 0.0 | 0.0 | 17.01 | 0.0 | 0.0 | 0.0 | 17.01 | | 5 | 31 | 01 June 2024 | | 17.85 | 16.43 | 0.58 | 0.0 | 0.0 | 17.01 | 0.0 | 0.0 | 0.0 | 17.01 |
| 6 | 30 | 01 July 2024 | | 0.0 | 17.85 | 0.58 | 0.0 | 0.0 | 18.43 | 0.0 | 0.0 | 0.0 | 18.43 | | 6 | 30 | 01 July 2024 | | 0.0 | 17.85 | 0.58 | 0.0 | 0.0 | 18.43 | 0.0 | 0.0 | 0.0 | 18.43 |
@TestRailId:C3485
Scenario: Interest recalculation - S2 2 overdue Scenario: Interest recalculation - S2 2 overdue
Given Global configuration "enable-business-date" is enabled Given Global configuration "enable-business-date" is enabled
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
@@ -6182,6 +6185,7 @@ Feature: Loan
| 5 | 31 | 01 June 2024 | | 17.06 | 16.81 | 0.2 | 0.0 | 0.0 | 17.01 | 0.0 | 0.0 | 0.0 | 17.01 | | 5 | 31 | 01 June 2024 | | 17.06 | 16.81 | 0.2 | 0.0 | 0.0 | 17.01 | 0.0 | 0.0 | 0.0 | 17.01 |
| 6 | 30 | 01 July 2024 | | 0.0 | 17.06 | 0.1 | 0.0 | 0.0 | 17.16 | 0.0 | 0.0 | 0.0 | 17.16 | | 6 | 30 | 01 July 2024 | | 0.0 | 17.06 | 0.1 | 0.0 | 0.0 | 17.16 | 0.0 | 0.0 | 0.0 | 17.16 |
@TestRailId:C3486
Scenario: Interest recalculation - S3 1 paid, 1 overdue Scenario: Interest recalculation - S3 1 paid, 1 overdue
Given Global configuration "enable-business-date" is enabled Given Global configuration "enable-business-date" is enabled
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
@@ -6205,6 +6209,7 @@ Feature: Loan
| 5 | 31 | 01 June 2024 | | 16.93 | 16.81 | 0.2 | 0.0 | 0.0 | 17.01 | 0.0 | 0.0 | 0.0 | 17.01 | | 5 | 31 | 01 June 2024 | | 16.93 | 16.81 | 0.2 | 0.0 | 0.0 | 17.01 | 0.0 | 0.0 | 0.0 | 17.01 |
| 6 | 30 | 01 July 2024 | | 0.0 | 16.93 | 0.1 | 0.0 | 0.0 | 17.03 | 0.0 | 0.0 | 0.0 | 17.03 | | 6 | 30 | 01 July 2024 | | 0.0 | 16.93 | 0.1 | 0.0 | 0.0 | 17.03 | 0.0 | 0.0 | 0.0 | 17.03 |
@TestRailId:C3487
Scenario: Loan Details Emi Amount Variations - AssociationsAll Scenario: Loan Details Emi Amount Variations - AssociationsAll
Given Global configuration "is-interest-to-be-recovered-first-when-greater-than-emi" is enabled Given Global configuration "is-interest-to-be-recovered-first-when-greater-than-emi" is enabled
Given Global configuration "enable-business-date" is enabled Given Global configuration "enable-business-date" is enabled
@@ -6219,6 +6224,7 @@ Feature: Loan
| Term Type Id | Term Type Code | Term Type Value | Applicable From | Decimal Value | Date Value | Is Specific To Installment | Is Processed | | Term Type Id | Term Type Code | Term Type Value | Applicable From | Decimal Value | Date Value | Is Specific To Installment | Is Processed |
| 1 | loanTermType.emiAmount | emiAmount | 01 January 2023 | 50.0 | | false | | | 1 | loanTermType.emiAmount | emiAmount | 01 January 2023 | 50.0 | | false | |
@TestRailId:C3488
Scenario: Loan Details Loan Term Variations Scenario: Loan Details Loan Term Variations
Given Global configuration "is-interest-to-be-recovered-first-when-greater-than-emi" is enabled Given Global configuration "is-interest-to-be-recovered-first-when-greater-than-emi" is enabled
Given Global configuration "enable-business-date" is enabled Given Global configuration "enable-business-date" is enabled
@@ -6234,6 +6240,7 @@ Feature: Loan
| 1 | loanTermType.emiAmount | emiAmount | 01 January 2023 | 50.0 | | false | | | 1 | loanTermType.emiAmount | emiAmount | 01 January 2023 | 50.0 | | false | |
| 4 | loanTermType.dueDate | dueDate | 01 February 2023 | 50.0 | 15 January 2023 | false | | | 4 | loanTermType.dueDate | dueDate | 01 February 2023 | 50.0 | 15 January 2023 | false | |
@TestRailId:C3489
Scenario: EMI calculation with 360/30 Early repayment - Last installment strategy - UC1: Multiple early repayment Scenario: EMI calculation with 360/30 Early repayment - Last installment strategy - UC1: Multiple early repayment
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
fineract-e2e-tests-runner/src/test/resources/features/LoanAccrualActivity.feature
+3 -4
View File
@@ -2213,7 +2213,7 @@ Feature: LoanAccrualActivity
| 26 January 2024 | Accrual | 0.7 | 0.0 | 0.7 | 0.0 | 0.0 | 0.0 | false | false | | 26 January 2024 | Accrual | 0.7 | 0.0 | 0.7 | 0.0 | 0.0 | 0.0 | false | false |
| 27 January 2024 | Accrual | 0.7 | 0.0 | 0.7 | 0.0 | 0.0 | 0.0 | false | false | | 27 January 2024 | Accrual | 0.7 | 0.0 | 0.7 | 0.0 | 0.0 | 0.0 | false | false |
# PS-2245 @TestRailId:C3494
Scenario: Verify non negative amount for Accrual Activity on backdated repayment Scenario: Verify non negative amount for Accrual Activity on backdated repayment
When Admin sets the business date to "09 December 2024" When Admin sets the business date to "09 December 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -2386,7 +2386,7 @@ Feature: LoanAccrualActivity
| 10 January 2025 | Repayment | 676.22 | 675.62 | 0.6 | 0.0 | 0.0 | 0.0 | false | false | | 10 January 2025 | Repayment | 676.22 | 675.62 | 0.6 | 0.0 | 0.0 | 0.0 | false | false |
| 10 January 2025 | Accrual Activity | 0.6 | 0.0 | 0.6 | 0.0 | 0.0 | 0.0 | false | false | | 10 January 2025 | Accrual Activity | 0.6 | 0.0 | 0.6 | 0.0 | 0.0 | 0.0 | false | false |
# PS-2245 @TestRailId:C3495
Scenario: Verify non negative amount for Accrual Activity on backdated repayment and accrual adjustment Scenario: Verify non negative amount for Accrual Activity on backdated repayment and accrual adjustment
When Admin sets the business date to "09 December 2024" When Admin sets the business date to "09 December 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -2469,7 +2469,7 @@ Feature: LoanAccrualActivity
| 10 January 2025 | Accrual | 0.6 | 0.0 | 0.6 | 0.0 | 0.0 | 0.0 | false | false | | 10 January 2025 | Accrual | 0.6 | 0.0 | 0.6 | 0.0 | 0.0 | 0.0 | false | false |
| 11 January 2025 | Accrual Adjustment | 0.6 | 0.0 | 0.6 | 0.0 | 0.0 | 0.0 | false | false | | 11 January 2025 | Accrual Adjustment | 0.6 | 0.0 | 0.6 | 0.0 | 0.0 | 0.0 | false | false |
# PS-2245 @TestRailId:C3496
Scenario: Verify non negative amount for Accrual Activity on backdated repayment, accrual adjustment and revert activity Scenario: Verify non negative amount for Accrual Activity on backdated repayment, accrual adjustment and revert activity
When Admin sets the business date to "09 December 2024" When Admin sets the business date to "09 December 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -4396,7 +4396,6 @@ Feature: LoanAccrualActivity
| 20 March 2025 | Accrual | 0.18 | 0.0 | 0.18 | 0.0 | 0.0 | 0.0 | false | false | | 20 March 2025 | Accrual | 0.18 | 0.0 | 0.18 | 0.0 | 0.0 | 0.0 | false | false |
| 21 March 2025 | Accrual | 0.16 | 0.0 | 0.16 | 0.0 | 0.0 | 0.0 | false | false | | 21 March 2025 | Accrual | 0.16 | 0.0 | 0.16 | 0.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3400 @TestRailId:C3400
Scenario: Verify Interest Payment Waiver isn't reversed and replayed after one accrual is created Scenario: Verify Interest Payment Waiver isn't reversed and replayed after one accrual is created
When Admin sets the business date to "12 January 2025" When Admin sets the business date to "12 January 2025"
fineract-e2e-tests-runner/src/test/resources/features/LoanAccrualTransaction.feature
+1 -1
View File
@@ -843,7 +843,7 @@ Feature: LoanAccrualTransaction
| 1000 | 0 | 10 | 10 | 1020 | 0 | 0 | 0 | 1020 | | 1000 | 0 | 10 | 10 | 1020 | 0 | 0 | 0 | 1020 |
When Global config "charge-accrual-date" value set to "due-date" When Global config "charge-accrual-date" value set to "due-date"
@Skip @TestRailId:C3128 @TestRailId:C3128
Scenario: Verify that the final accrual calculation is correct when multiple Charges are added and waived Scenario: Verify that the final accrual calculation is correct when multiple Charges are added and waived
When Admin sets the business date to "17 April 2024" When Admin sets the business date to "17 April 2024"
When Admin creates a client with random data When Admin creates a client with random data
fineract-e2e-tests-runner/src/test/resources/features/LoanCharge.feature
-30
View File
@@ -1278,36 +1278,6 @@ Feature: LoanCharge
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 3000 | 90 | 0.0 | 46.35 | 3136.35 | 0 | 0 | 0 | 3136.35 | | 3000 | 90 | 0.0 | 46.35 | 3136.35 | 0 | 0 | 0 | 3136.35 |
# TODO Create loan product suitable for LOAN_TRANCHE_DISBURSEMENT_PERCENTAGE_FEE, replace, fix expected results
@Skip @TestRailId:C2677
Scenario: FEE06 - Verify the loan creation with charge: tranche disbursement percentage fee, multi disbursement
When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data
When Admin creates a fully customized loan with the following data:
| LoanProduct | submitted on date | with Principal | ANNUAL interest rate % | interest type | interest calculation period | amortization type | loanTermFrequency | loanTermFrequencyType | repaymentEvery | repaymentFrequencyType | numberOfRepayments | graceOnPrincipalPayment | graceOnInterestPayment | interest free period | Payment strategy |
| LP1_INTEREST_DECLINING_BALANCE_SAR_RECALCULATION_SAME_AS_REPAYMENT_COMPOUNDING_NONE_MULTI_DISBURSEMENT | 1 January 2023 | 3000 | 12 | FLAT | SAME_AS_REPAYMENT_PERIOD | EQUAL_INSTALLMENTS | 3 | MONTHS | 1 | MONTHS | 3 | 0 | 0 | 0 | PENALTIES_FEES_INTEREST_PRINCIPAL_ORDER |
And Admin successfully approves the loan on "01 January 2023" with "3000" amount and expected disbursement date on "01 January 2023"
When Admin successfully disburse the loan on "01 January 2023" with "1000" EUR transaction amount
When Admin adds "LOAN_TRANCHE_DISBURSEMENT_PERCENTAGE_FEE" charge with 1.5 % of transaction amount
When Admin sets the business date to "01 February 2023"
When Admin successfully disburse the loan on "01 February 2023" with "1000" EUR transaction amount
When Admin sets the business date to "01 March 2023"
When Admin successfully disburse the loan on "01 March 2023" with "1000" EUR transaction amount
Then Loan Transactions tab has the following data:
| Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance |
| 01 January 2023 | Repayment (at time of disbursement) | 15.0 | 0.0 | 0.0 | 15.0 | 0.0 | 0.0 |
| 01 January 2023 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1000.0 |
Then Loan Charges tab has the following data:
| Name | isPenalty | Payment due at | Due as of | Calculation type | Due | Paid | Waived | Outstanding |
| Disbursement percentage fee | false | Disbursement | | % Amount | 15.0 | 15.0 | 0.0 | 0.0 |
Then Loan Repayment schedule has 1 periods, with the following data for periods:
| Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| | | 01 January 2023 | | 1000.0 | | | 15.0 | | 15.0 | 15.0 | | | |
| 1 | 30 | 31 January 2023 | | 0.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 |
Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1000 | 0 | 15 | 0 | 1015 | 15 | 0 | 0 | 1000 |
@TestRailId:C2790 @TestRailId:C2790
Scenario: Verify that partially waived installment fee applied correctly in reverse-replay logic Scenario: Verify that partially waived installment fee applied correctly in reverse-replay logic
When Admin sets the business date to "01 January 2023" When Admin sets the business date to "01 January 2023"
fineract-e2e-tests-runner/src/test/resources/features/LoanChargeOff.feature
+37 -32
View File
@@ -153,7 +153,7 @@ Feature: Charge-off
| EXPENSE | 744007 | Credit Loss/Bad Debt | 1000.0 | | | EXPENSE | 744007 | Credit Loss/Bad Debt | 1000.0 | |
| INCOME | 404008 | Fee Charge Off | 110.0 | | | INCOME | 404008 | Fee Charge Off | 110.0 | |
@Skip @TestRailId:C2571 @chargeoffOnLoanWithInterest @TestRailId:C2571 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do Charge-off for non-fraud loan when FEE and PENALTY added (interest portion) Scenario: As a user I want to do Charge-off for non-fraud loan when FEE and PENALTY added (interest portion)
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -180,7 +180,7 @@ Feature: Charge-off
| INCOME | 404001 | Interest Income Charge Off | 30.0 | | | INCOME | 404001 | Interest Income Charge Off | 30.0 | |
| INCOME | 404008 | Fee Charge Off | 113.0 | | | INCOME | 404008 | Fee Charge Off | 113.0 | |
@Skip @TestRailId:C2572 @chargeoffOnLoanWithInterest @TestRailId:C2572 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do a Merchant Refund after charge-off for non fraud loan (interest portion) Scenario: As a user I want to do a Merchant Refund after charge-off for non fraud loan (interest portion)
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -214,8 +214,7 @@ Feature: Charge-off
| INCOME | 404008 | Fee Charge Off | | 113.0 | | INCOME | 404008 | Fee Charge Off | | 113.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 500.0 | | | LIABILITY | 145023 | Suspense/Clearing account | 500.0 | |
@TestRailId:C2573 @chargeoffOnLoanWithInterest
@Skip @TestRailId:C2573 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do a Payout refund after charge-off for non fraud loan (interest portion) Scenario: As a user I want to do a Payout refund after charge-off for non fraud loan (interest portion)
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -249,7 +248,7 @@ Feature: Charge-off
| INCOME | 404008 | Fee Charge Off | | 113.0 | | INCOME | 404008 | Fee Charge Off | | 113.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 500.0 | | | LIABILITY | 145023 | Suspense/Clearing account | 500.0 | |
@Skip @TestRailId:C2574 @chargeoffOnLoanWithInterest @TestRailId:C2574 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do a Repayment after Charge-off for fraud loan when FEE and PENALTY added (product with interest) Scenario: As a user I want to do a Repayment after Charge-off for fraud loan when FEE and PENALTY added (product with interest)
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -383,7 +382,7 @@ Feature: Charge-off
| EXPENSE | 744037 | Credit Loss/Bad Debt-Fraud | 1000.0 | | | EXPENSE | 744037 | Credit Loss/Bad Debt-Fraud | 1000.0 | |
| INCOME | 404008 | Fee Charge Off | 110.0 | | | INCOME | 404008 | Fee Charge Off | 110.0 | |
@Skip @TestRailId:C2579 @chargeoffOnLoanWithInterest @TestRailId:C2579 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do a Charge-off for fraud loan when FEE and PENALTY added (interest portion) Scenario: As a user I want to do a Charge-off for fraud loan when FEE and PENALTY added (interest portion)
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -411,7 +410,7 @@ Feature: Charge-off
| INCOME | 404001 | Interest Income Charge Off | 30.0 | | | INCOME | 404001 | Interest Income Charge Off | 30.0 | |
| INCOME | 404008 | Fee Charge Off | 113.0 | | | INCOME | 404008 | Fee Charge Off | 113.0 | |
@Skip @TestRailId:C2580 @chargeoffOnLoanWithInterest @TestRailId:C2580 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do a Merchant issue refund for fraud loan when FEE and PENALTY added (interest portion) Scenario: As a user I want to do a Merchant issue refund for fraud loan when FEE and PENALTY added (interest portion)
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -446,7 +445,7 @@ Feature: Charge-off
| INCOME | 404008 | Fee Charge Off | | 113.0 | | INCOME | 404008 | Fee Charge Off | | 113.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 500.0 | | | LIABILITY | 145023 | Suspense/Clearing account | 500.0 | |
@Skip @TestRailId:C2581 @chargeoffOnLoanWithInterest @TestRailId:C2581 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do Payout refund for fraud loan when FEE and PENALTY added (interest portion) Scenario: As a user I want to do Payout refund for fraud loan when FEE and PENALTY added (interest portion)
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -482,7 +481,7 @@ Feature: Charge-off
| LIABILITY | 145023 | Suspense/Clearing account | 500.0 | | | LIABILITY | 145023 | Suspense/Clearing account | 500.0 | |
@Skip @TestRailId:C2582 @chargeoffOnLoanWithInterest @TestRailId:C2582 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do a Repayment after Charge-off for fraud loan when FEE and PENALTY added Scenario: As a user I want to do a Repayment after Charge-off for fraud loan when FEE and PENALTY added
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -515,8 +514,7 @@ Feature: Charge-off
| INCOME | 744008 | Recoveries | | 500.0 | | INCOME | 744008 | Recoveries | | 500.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 500.0 | | | LIABILITY | 145023 | Suspense/Clearing account | 500.0 | |
@TestRailId:C2591 @chargeoffOnLoanWithInterest
@Skip @TestRailId:C2591 @chargeoffOnLoanWithInterest
Scenario: As a user I want to repay a loan which was charged-off Scenario: As a user I want to repay a loan which was charged-off
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -541,12 +539,12 @@ Feature: Charge-off
Then Loan Repayment schedule has 3 periods, with the following data for periods: Then Loan Repayment schedule has 3 periods, with the following data for periods:
| Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| | | 01 January 2023 | | 1000.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2023 | | 1000.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 31 | 01 February 2023 | 22 February 2023 | 666.67 | 333.33 | 10.0 | 0.0 | 10.0 | 353.33 | 353.33 | 0.0 | 343.33 | 0.0 | | 1 | 31 | 01 February 2023 | 22 February 2023 | 667.0 | 333.0 | 10.0 | 0.0 | 10.0 | 353.0 | 353.0 | 0.0 | 353.0 | 0.0 |
| 2 | 28 | 01 March 2023 | 23 February 2023 | 333.34 | 333.33 | 10.0 | 103.0 | 0.0 | 446.33 | 446.33 | 446.33 | 0.0 | 0.0 | | 2 | 28 | 01 March 2023 | 23 February 2023 | 334.0 | 333.0 | 10.0 | 103.0 | 0.0 | 446.0 | 446.0 | 446.0 | 0.0 | 0.0 |
| 3 | 31 | 01 April 2023 | 23 February 2023 | 0.0 | 333.34 | 10.0 | 0.0 | 0.0 | 343.34 | 343.34 | 343.34 | 0.0 | 0.0 | | 3 | 31 | 01 April 2023 | 23 February 2023 | 0.0 | 334.0 | 10.0 | 0.0 | 0.0 | 344.0 | 344.0 | 344.0 | 0.0 | 0.0 |
Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1000 | 30 | 103 | 10 | 1143 | 1143 | 789.67 | 343.33 | 0 | | 1000.0 | 30.0 | 103.0 | 10.0 | 1143.0 | 1143.0 | 790.0 | 353.0 | 0.0 |
Then Loan Transactions tab has a "DISBURSEMENT" transaction with date "01 January 2023" which has the following Journal entries: Then Loan Transactions tab has a "DISBURSEMENT" transaction with date "01 January 2023" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit | | Type | Account code | Account name | Debit | Credit |
| ASSET | 112601 | Loans Receivable | 1000.0 | | | ASSET | 112601 | Loans Receivable | 1000.0 | |
@@ -562,20 +560,12 @@ Feature: Charge-off
| Type | Account code | Account name | Debit | Credit | | Type | Account code | Account name | Debit | Credit |
| INCOME | 744008 | Recoveries | | 500.0 | | INCOME | 744008 | Recoveries | | 500.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 500.0 | | | LIABILITY | 145023 | Suspense/Clearing account | 500.0 | |
Then Loan Transactions tab has a "ACCRUAL" transaction with date "23 February 2023" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit |
| ASSET | 112603 | Interest/Fee Receivable | 30.0 | |
| INCOME | 404000 | Interest Income | | 30.0 |
| ASSET | 112603 | Interest/Fee Receivable | 103.0 | |
| INCOME | 404007 | Fee Income | | 103.0 |
| ASSET | 112603 | Interest/Fee Receivable | 10.0 | |
| INCOME | 404007 | Fee Income | | 10.0 |
Then Loan Transactions tab has a "REPAYMENT" transaction with date "23 February 2023" which has the following Journal entries: Then Loan Transactions tab has a "REPAYMENT" transaction with date "23 February 2023" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit | | Type | Account code | Account name | Debit | Credit |
| INCOME | 744008 | Recoveries | | 643.0 | | INCOME | 744008 | Recoveries | | 643.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 643.0 | | | LIABILITY | 145023 | Suspense/Clearing account | 643.0 | |
@Skip @TestRailId:C2592 @chargeoffOnLoanWithInterest @TestRailId:C2592 @chargeoffOnLoanWithInterest
Scenario: As a user I want to do a charge-off undo before any other transactions on the loan Scenario: As a user I want to do a charge-off undo before any other transactions on the loan
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -593,9 +583,9 @@ Feature: Charge-off
Then Loan Repayment schedule has 3 periods, with the following data for periods: Then Loan Repayment schedule has 3 periods, with the following data for periods:
| Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| | | 01 January 2023 | | 1000.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2023 | | 1000.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 31 | 01 February 2023 | | 666.67 | 333.33 | 10.0 | 0.0 | 10.0 | 353.33 | 0.0 | 0.0 | 0.0 | 353.33 | | 1 | 31 | 01 February 2023 | | 667.0 | 333.0 | 10.0 | 0.0 | 10.0 | 353.0 | 0.0 | 0.0 | 0.0 | 353.0 |
| 2 | 28 | 01 March 2023 | | 333.34 | 333.33 | 10.0 | 103.0 | 0.0 | 446.33 | 0.0 | 0.0 | 0.0 | 446.33 | | 2 | 28 | 01 March 2023 | | 334.0 | 333.0 | 10.0 | 103.0 | 0.0 | 446.0 | 0.0 | 0.0 | 0.0 | 446.0 |
| 3 | 31 | 01 April 2023 | | 0.0 | 333.34 | 10.0 | 0.0 | 0.0 | 343.34 | 0.0 | 0.0 | 0.0 | 343.34 | | 3 | 31 | 01 April 2023 | | 0.0 | 334.0 | 10.0 | 0.0 | 0.0 | 344.0 | 0.0 | 0.0 | 0.0 | 344.0 |
Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1000 | 30 | 103 | 10 | 1143 | 0 | 0 | 0 | 1143 | | 1000 | 30 | 103 | 10 | 1143 | 0 | 0 | 0 | 1143 |
@@ -3647,7 +3637,7 @@ Feature: Charge-off
| 29 February 2024 | Charge-off | 83.89 | 82.99 | 0.9 | 0.0 | 0.0 | 0.0 | false | false | | 29 February 2024 | Charge-off | 83.89 | 82.99 | 0.9 | 0.0 | 0.0 | 0.0 | false | false |
@Skip @TestRailId:C3361 @AdvancedPaymentAllocation @Skip @TestRailId:C3361 @AdvancedPaymentAllocation
Scenario: SKIPPED - Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when charge-off occurs with allocation to last installment with interest allocation change Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when charge-off occurs with allocation to last installment with interest allocation change
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
When Admin creates a fully customized loan with the following data: When Admin creates a fully customized loan with the following data:
@@ -5064,6 +5054,7 @@ Feature: Charge-off
| EXPENSE | 744007 | Credit Loss/Bad Debt | 83.57 | | | EXPENSE | 744007 | Credit Loss/Bad Debt | 83.57 | |
| INCOME | 404001 | Interest Income Charge Off | 0.47 | | | INCOME | 404001 | Interest Income Charge Off | 0.47 | |
@TestRailId:C3460
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when couple fee charges due dates is before charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when couple fee charges due dates is before charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5123,6 +5114,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false | | 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false |
| 01 March 2024 | Charge-off | 92.06 | 83.57 | 0.49 | 8.0 | 0.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 92.06 | 83.57 | 0.49 | 8.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3461
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when fee and penalty charges due dates is before charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when fee and penalty charges due dates is before charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5183,6 +5175,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false | | 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false |
| 01 March 2024 | Charge-off | 99.06 | 83.57 | 0.49 | 5.0 | 10.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 99.06 | 83.57 | 0.49 | 5.0 | 10.0 | 0.0 | false | false |
@TestRailId:C3462
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when fee and penalty charges due dates is before charge-off date, and one charge is waived after charge-off Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when fee and penalty charges due dates is before charge-off date, and one charge is waived after charge-off
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5258,6 +5251,7 @@ Feature: Charge-off
| 15 February 2024 | Waive loan charges | 5.0 | 0.0 | 0.0 | 0.0 | 0.0 | 83.57 | false | false | | 15 February 2024 | Waive loan charges | 5.0 | 0.0 | 0.0 | 0.0 | 0.0 | 83.57 | false | false |
| 01 March 2024 | Charge-off | 94.06 | 83.57 | 0.49 | 0.0 | 10.0 | 0.0 | false | true | | 01 March 2024 | Charge-off | 94.06 | 83.57 | 0.49 | 0.0 | 10.0 | 0.0 | false | true |
@TestRailId:C3463
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when one fee charge is added after the charge off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when one fee charge is added after the charge off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5317,6 +5311,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false | | 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false |
| 01 March 2024 | Charge-off | 89.06 | 83.57 | 0.49 | 5.0 | 0.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 89.06 | 83.57 | 0.49 | 5.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3464
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when couple fee charges due dates is after charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when couple fee charges due dates is after charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5377,6 +5372,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false | | 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false |
| 01 March 2024 | Charge-off | 91.06 | 83.57 | 0.49 | 7.0 | 0.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 91.06 | 83.57 | 0.49 | 7.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3465
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when fee and penalty charges due dates is after charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when fee and penalty charges due dates is after charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5437,6 +5433,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false | | 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false |
| 15 February 2024 | Charge-off | 98.81 | 83.57 | 0.24 | 5.0 | 10.0 | 0.0 | false | false | | 15 February 2024 | Charge-off | 98.81 | 83.57 | 0.24 | 5.0 | 10.0 | 0.0 | false | false |
@TestRailId:C3466
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when fee and penalty charges due dates is after charge-off date, and one charge is waived after charge-off Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when fee and penalty charges due dates is after charge-off date, and one charge is waived after charge-off
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5513,7 +5510,7 @@ Feature: Charge-off
| 15 February 2024 | Waive loan charges | 10.0 | 0.0 | 0.0 | 0.0 | 0.0 | 83.57 | false | false | | 15 February 2024 | Waive loan charges | 10.0 | 0.0 | 0.0 | 0.0 | 0.0 | 83.57 | false | false |
| 15 February 2024 | Charge-off | 88.81 | 83.57 | 0.24 | 5.0 | 0.0 | 0.0 | false | true | | 15 February 2024 | Charge-off | 88.81 | 83.57 | 0.24 | 5.0 | 0.0 | 0.0 | false | true |
@TestRailId:C3360 @AdvancedPaymentAllocation @TestRailId:C3497 @AdvancedPaymentAllocation
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when charge-off occurs with adjustment to last installment Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when charge-off occurs with adjustment to last installment
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5571,7 +5568,7 @@ Feature: Charge-off
| 15 January 2024 | Repayment | 17.01 | 17.01 | 0.0 | 0.0 | 0.0 | 82.99 | false | false | | 15 January 2024 | Repayment | 17.01 | 17.01 | 0.0 | 0.0 | 0.0 | 82.99 | false | false |
| 29 February 2024 | Charge-off | 83.99 | 82.99 | 1.0 | 0.0 | 0.0 | 0.0 | false | false | | 29 February 2024 | Charge-off | 83.99 | 82.99 | 1.0 | 0.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3361 @AdvancedPaymentAllocation @TestRailId:C3498 @AdvancedPaymentAllocation
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when charge-off occurs with allocation to last installment with interest allocation change Scenario: Verify accelerate maturity to charge-off date when interest recalculation is enabled - case when charge-off occurs with allocation to last installment with interest allocation change
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5649,7 +5646,7 @@ Feature: Charge-off
| 15 February 2024 | Repayment | 17.01 | 16.77 | 0.24 | 0.0 | 0.0 | 66.8 | false | true | | 15 February 2024 | Repayment | 17.01 | 16.77 | 0.24 | 0.0 | 0.0 | 66.8 | false | true |
| 29 February 2024 | Charge-off | 66.98 | 66.8 | 0.18 | 0.0 | 0.0 | 0.0 | false | false | | 29 February 2024 | Charge-off | 66.98 | 66.8 | 0.18 | 0.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3360 @AdvancedPaymentAllocation @TestRailId:C3499 @AdvancedPaymentAllocation
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when charge-off occurs with adjustment to last installment Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when charge-off occurs with adjustment to last installment
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5705,7 +5702,7 @@ Feature: Charge-off
| 15 January 2024 | Repayment | 17.04 | 16.6 | 0.44 | 0.0 | 0.0 | 83.4 | false | true | | 15 January 2024 | Repayment | 17.04 | 16.6 | 0.44 | 0.0 | 0.0 | 83.4 | false | true |
| 29 February 2024 | Charge-off | 83.99 | 83.4 | 0.59 | 0.0 | 0.0 | 0.0 | false | false | | 29 February 2024 | Charge-off | 83.99 | 83.4 | 0.59 | 0.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3361 @AdvancedPaymentAllocation @TestRailId:C3500 @AdvancedPaymentAllocation
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when charge-off occurs with allocation to last installment with interest allocation change Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when charge-off occurs with allocation to last installment with interest allocation change
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5782,6 +5779,7 @@ Feature: Charge-off
| 15 February 2024 | Repayment | 17.04 | 16.6 | 0.44 | 0.0 | 0.0 | 66.99 | false | true | | 15 February 2024 | Repayment | 17.04 | 16.6 | 0.44 | 0.0 | 0.0 | 66.99 | false | true |
| 29 February 2024 | Charge-off | 66.99 | 66.99 | 0.0 | 0.0 | 0.0 | 0.0 | false | false | | 29 February 2024 | Charge-off | 66.99 | 66.99 | 0.0 | 0.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3467
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when one fee charge due date is before charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when one fee charge due date is before charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5838,6 +5836,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false | | 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false |
| 01 March 2024 | Charge-off | 89.05 | 83.59 | 0.46 | 5.0 | 0.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 89.05 | 83.59 | 0.46 | 5.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3468
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when couple fee charges due dates is before charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when couple fee charges due dates is before charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5895,6 +5894,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false | | 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false |
| 01 March 2024 | Charge-off | 92.05 | 83.59 | 0.46 | 8.0 | 0.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 92.05 | 83.59 | 0.46 | 8.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3469
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when fee and penalty charges due dates is before charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when fee and penalty charges due dates is before charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -5953,6 +5953,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false | | 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false |
| 01 March 2024 | Charge-off | 99.05 | 83.59 | 0.46 | 5.0 | 10.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 99.05 | 83.59 | 0.46 | 5.0 | 10.0 | 0.0 | false | false |
@TestRailId:C3470
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when fee and penalty charges due dates is before charge-off date, and one charge is waived after charge-off Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when fee and penalty charges due dates is before charge-off date, and one charge is waived after charge-off
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -6026,6 +6027,7 @@ Feature: Charge-off
| 15 February 2024 | Waive loan charges | 5.0 | 0.0 | 0.0 | 0.0 | 0.0 | 83.59 | false | false | | 15 February 2024 | Waive loan charges | 5.0 | 0.0 | 0.0 | 0.0 | 0.0 | 83.59 | false | false |
| 01 March 2024 | Charge-off | 94.05 | 83.59 | 0.46 | 0.0 | 10.0 | 0.0 | false | true | | 01 March 2024 | Charge-off | 94.05 | 83.59 | 0.46 | 0.0 | 10.0 | 0.0 | false | true |
@TestRailId:C3471
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when one fee charge is added after the charge off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when one fee charge is added after the charge off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -6083,6 +6085,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false | | 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false |
| 01 March 2024 | Charge-off | 89.05 | 83.59 | 0.46 | 5.0 | 0.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 89.05 | 83.59 | 0.46 | 5.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3472
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when couple fee charges due dates is after charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when couple fee charges due dates is after charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -6141,6 +6144,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false | | 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false |
| 01 March 2024 | Charge-off | 91.05 | 83.59 | 0.46 | 7.0 | 0.0 | 0.0 | false | false | | 01 March 2024 | Charge-off | 91.05 | 83.59 | 0.46 | 7.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3473
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when fee and penalty charges due dates is after charge-off date Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when fee and penalty charges due dates is after charge-off date
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
@@ -6199,6 +6203,7 @@ Feature: Charge-off
| 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false | | 01 February 2024 | Repayment | 17.0 | 16.41 | 0.59 | 0.0 | 0.0 | 83.59 | false | false |
| 15 February 2024 | Charge-off | 98.81 | 83.59 | 0.22 | 5.0 | 10.0 | 0.0 | false | false | | 15 February 2024 | Charge-off | 98.81 | 83.59 | 0.22 | 5.0 | 10.0 | 0.0 | false | false |
@TestRailId:C3474
Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when fee and penalty charges due dates is after charge-off date, and one charge is waived after charge-off Scenario: Verify accelerate maturity to charge-off date when interest recalculation is disabled - case when fee and penalty charges due dates is after charge-off date, and one charge is waived after charge-off
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data When Admin creates a client with random data
fineract-e2e-tests-runner/src/test/resources/features/LoanChargeback.feature
+4
View File
@@ -4236,6 +4236,7 @@ Feature: LoanChargeback
| 15 July 2024 | Chargeback | 17.01 | 16.81 | 0.2 | 0.0 | 0.0 | 16.81 | false | false | | 15 July 2024 | Chargeback | 17.01 | 16.81 | 0.2 | 0.0 | 0.0 | 16.81 | false | false |
| 30 July 2024 | Chargeback | 17.0 | 16.9 | 0.1 | 0.0 | 0.0 | 33.71 | false | false | | 30 July 2024 | Chargeback | 17.0 | 16.9 | 0.1 | 0.0 | 0.0 | 33.71 | false | false |
@TestRailId:C3490
Scenario: Full chargeback with no interest recalculation, interest allocation first, before maturity date Scenario: Full chargeback with no interest recalculation, interest allocation first, before maturity date
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
@@ -4296,6 +4297,7 @@ Feature: LoanChargeback
| 01 March 2024 | Repayment | 17.01 | 16.52 | 0.49 | 0.0 | 0.0 | 67.05 | false | false | | 01 March 2024 | Repayment | 17.01 | 16.52 | 0.49 | 0.0 | 0.0 | 67.05 | false | false |
| 01 March 2024 | Chargeback | 17.01 | 16.52 | 0.49 | 0.0 | 0.0 | 83.57 | false | false | | 01 March 2024 | Chargeback | 17.01 | 16.52 | 0.49 | 0.0 | 0.0 | 83.57 | false | false |
@TestRailId:C3491
Scenario: Partial chargeback with no interest recalculation, interest allocation first, before maturity date Scenario: Partial chargeback with no interest recalculation, interest allocation first, before maturity date
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
@@ -4356,6 +4358,7 @@ Feature: LoanChargeback
| 01 March 2024 | Repayment | 17.01 | 16.52 | 0.49 | 0.0 | 0.0 | 67.05 | false | false | | 01 March 2024 | Repayment | 17.01 | 16.52 | 0.49 | 0.0 | 0.0 | 67.05 | false | false |
| 01 March 2024 | Chargeback | 15.0 | 14.51 | 0.49 | 0.0 | 0.0 | 81.56 | false | false | | 01 March 2024 | Chargeback | 15.0 | 14.51 | 0.49 | 0.0 | 0.0 | 81.56 | false | false |
@TestRailId:C3492
Scenario: Partial chargeback with disabled interest recalculation, allocation principal first, before maturity date Scenario: Partial chargeback with disabled interest recalculation, allocation principal first, before maturity date
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
@@ -4416,6 +4419,7 @@ Feature: LoanChargeback
| 01 March 2024 | Repayment | 17.01 | 16.52 | 0.49 | 0.0 | 0.0 | 67.05 | false | false | | 01 March 2024 | Repayment | 17.01 | 16.52 | 0.49 | 0.0 | 0.0 | 67.05 | false | false |
| 01 March 2024 | Chargeback | 15.0 | 15.0 | 0.0 | 0.0 | 0.0 | 82.05 | false | false | | 01 March 2024 | Chargeback | 15.0 | 15.0 | 0.0 | 0.0 | 0.0 | 82.05 | false | false |
@TestRailId:C3493
Scenario: Two chargebacks with disabled interest recalculation, allocation principal first Scenario: Two chargebacks with disabled interest recalculation, allocation principal first
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
fineract-e2e-tests-runner/src/test/resources/features/LoanDelinquency.feature
+1 -26
View File
@@ -237,7 +237,7 @@ Feature: LoanDelinquency
When Admin sets the business date to "20 October 2023" When Admin sets the business date to "20 October 2023"
Then Initiating a DELINQUENCY RESUME with an endDate results an error - startDate: "20 October 2023", endDate: "30 October 2023" Then Initiating a DELINQUENCY RESUME with an endDate results an error - startDate: "20 October 2023", endDate: "30 October 2023"
@Skip @TestRailId:C2992 @TestRailId:C2992
Scenario: Verify Loan level loan delinquency - loan goes into delinquency pause then will be resumed Scenario: Verify Loan level loan delinquency - loan goes into delinquency pause then will be resumed
When Admin sets the business date to "01 October 2023" When Admin sets the business date to "01 October 2023"
When Admin creates a client with random data When Admin creates a client with random data
@@ -1254,31 +1254,6 @@ Feature: LoanDelinquency
And Admin successfully approves the loan on "01 March 2024" with "1000" amount and expected disbursement date on "01 March 2024" And Admin successfully approves the loan on "01 March 2024" with "1000" amount and expected disbursement date on "01 March 2024"
Then Admin checks that delinquency range is: "NO_DELINQUENCY" and has delinquentDate "" Then Admin checks that delinquency range is: "NO_DELINQUENCY" and has delinquentDate ""
# TODO unskip and check when PS-1827 is done
@Skip @TestRailId:C3093
Scenario: Verify that LoanDelinquencyRangeChangeBusinessEvent has the correct Delinquency range, date and amount on both loan- and installment-level
When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data
When Admin creates a fully customized loan with the following data:
| LoanProduct | submitted on date | with Principal | ANNUAL interest rate % | interest type | interest calculation period | amortization type | loanTermFrequency | loanTermFrequencyType | repaymentEvery | repaymentFrequencyType | numberOfRepayments | graceOnPrincipalPayment | graceOnInterestPayment | interest free period | Payment strategy |
| LP2_DOWNPAYMENT_ADV_PMT_ALLOC_PROGRESSIVE_LOAN_SCHEDULE_HORIZONTAL_INSTALLMENT_LEVEL_DELINQUENCY | 01 January 2024 | 1000 | 0 | FLAT | SAME_AS_REPAYMENT_PERIOD | EQUAL_INSTALLMENTS | 90 | DAYS | 30 | DAYS | 3 | 0 | 0 | 0 | ADVANCED_PAYMENT_ALLOCATION |
And Admin successfully approves the loan on "01 January 2024" with "1000" amount and expected disbursement date on "01 January 2024"
When Admin successfully disburse the loan on "01 January 2024" with "1000" EUR transaction amount
When Admin runs inline COB job for Loan
When Admin sets the business date to "01 February 2024"
When Admin runs inline COB job for Loan
When Admin sets the business date to "05 March 2024"
When Admin runs inline COB job for Loan
Then Loan has the following LOAN level delinquency data:
| classification | delinquentAmount | delinquentDate | delinquentDays | pastDueDays |
| RANGE_60 | 750.0 | 04 January 2024 | 61 | 64 |
Then Loan has the following INSTALLMENT level delinquency data:
| rangeId | Range | Amount |
| 2 | RANGE_3 | 250.00 |
| 3 | RANGE_30 | 250.00 |
| 4 | RANGE_60 | 250.00 |
Then LoanDelinquencyRangeChangeBusinessEvent has the same Delinquency range, date and amount as in LoanDetails on both loan- and installment-level
@TestRailId:C3135 @TestRailId:C3135
Scenario: Verify that the delinquency is not applied on Loan with Rejected status Scenario: Verify that the delinquency is not applied on Loan with Rejected status
When Admin sets the business date to "01 February 2024" When Admin sets the business date to "01 February 2024"
fineract-e2e-tests-runner/src/test/resources/features/LoanDownPayment.feature
+3 -10
View File
@@ -317,7 +317,6 @@ Feature: Loan DownPayment
| 01 January 2022 | Repayment | 250.0 | 250.0 | 0.0 | 0.0 | 0.0 | 750.0 | | 01 January 2022 | Repayment | 250.0 | 250.0 | 0.0 | 0.0 | 0.0 | 750.0 |
| 10 January 2022 | Disbursement | 400.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1150.0 | | 10 January 2022 | Disbursement | 400.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1150.0 |
@TestRailId:C2818 @TestRailId:C2818
Scenario: Double disbursement on installment day - auto enabled Scenario: Double disbursement on installment day - auto enabled
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
@@ -359,7 +358,6 @@ Feature: Loan DownPayment
| 01 February 2022 | Disbursement | 400.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1150.0 | | 01 February 2022 | Disbursement | 400.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1150.0 |
| 01 February 2022 | Down Payment | 100.0 | 100.0 | 0.0 | 0.0 | 0.0 | 1050.0 | | 01 February 2022 | Down Payment | 100.0 | 100.0 | 0.0 | 0.0 | 0.0 | 1050.0 |
@TestRailId:C2819 @TestRailId:C2819
Scenario: Double disbursement on installment day - auto disabled Scenario: Double disbursement on installment day - auto disabled
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
@@ -1529,14 +1527,14 @@ Feature: Loan DownPayment
| 01 February 2022 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1750.0 | | 01 February 2022 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1750.0 |
| 01 February 2022 | Repayment | 250.0 | 250.0 | 0.0 | 0.0 | 0.0 | 1500.0 | | 01 February 2022 | Repayment | 250.0 | 250.0 | 0.0 | 0.0 | 0.0 | 1500.0 |
# To recheck after verifying that loan product details are correct # TODO unskip and check when PS-2345 is done
@Skip @TestRailId:C2852 @Skip @TestRailId:C2852
Scenario: Single disbursement with interest - auto disabled Scenario: Single disbursement with interest - auto disabled
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
When Admin creates a client with random data When Admin creates a client with random data
When Admin creates a fully customized loan with the following data: When Admin creates a fully customized loan with the following data:
| LoanProduct | submitted on date | with Principal | ANNUAL interest rate % | interest type | interest calculation period | amortization type | loanTermFrequency | loanTermFrequencyType | repaymentEvery | repaymentFrequencyType | numberOfRepayments | graceOnPrincipalPayment | graceOnInterestPayment | interest free period | Payment strategy | | LoanProduct | submitted on date | with Principal | ANNUAL interest rate % | interest type | interest calculation period | amortization type | loanTermFrequency | loanTermFrequencyType | repaymentEvery | repaymentFrequencyType | numberOfRepayments | graceOnPrincipalPayment | graceOnInterestPayment | interest free period | Payment strategy |
| LP2_DOWNPAYMENT_INTEREST | 01 January 2022 | 1000 | 12 | FLAT | SAME_AS_REPAYMENT_PERIOD | EQUAL_INSTALLMENTS | 3 | MONTHS | 1 | MONTHS | 3 | 0 | 0 | 0 | DUE_PENALTY_INTEREST_PRINCIPAL_FEE_IN_ADVANCE_PENALTY_INTEREST_PRINCIPAL_FEE | | LP2_DOWNPAYMENT_INTEREST | 01 January 2022 | 1000 | 0 | FLAT | SAME_AS_REPAYMENT_PERIOD | EQUAL_INSTALLMENTS | 3 | MONTHS | 1 | MONTHS | 3 | 0 | 0 | 0 | DUE_PENALTY_INTEREST_PRINCIPAL_FEE_IN_ADVANCE_PENALTY_INTEREST_PRINCIPAL_FEE |
And Admin successfully approves the loan on "01 January 2022" with "1000" amount and expected disbursement date on "01 January 2023" And Admin successfully approves the loan on "01 January 2022" with "1000" amount and expected disbursement date on "01 January 2023"
When Admin successfully disburse the loan on "01 January 2022" with "1000" EUR transaction amount When Admin successfully disburse the loan on "01 January 2022" with "1000" EUR transaction amount
Then Loan Repayment schedule has 4 periods, with the following data for periods: Then Loan Repayment schedule has 4 periods, with the following data for periods:
@@ -1550,7 +1548,7 @@ Feature: Loan DownPayment
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1000.0 | 30 | 0 | 0 | 1030.0 | 0.0 | 0 | 0 | 1030 | | 1000.0 | 30 | 0 | 0 | 1030.0 | 0.0 | 0 | 0 | 1030 |
# To recheck after verifying that loan product details are correct # TODO unskip and check when PS-2345 is done
@Skip @TestRailId:C2853 @Skip @TestRailId:C2853
Scenario: Single disbursement delinquency - auto disabled Scenario: Single disbursement delinquency - auto disabled
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
@@ -1752,7 +1750,6 @@ Feature: Loan DownPayment
When Admin successfully undo disbursal When Admin successfully undo disbursal
Then Loan status has changed to "Approved" Then Loan status has changed to "Approved"
@TestRailId:C2858 @TestRailId:C2858
Scenario: Multi disbursement with undo last disbursement when auto downpayment is enabled without manual transaction after last downpayment Scenario: Multi disbursement with undo last disbursement when auto downpayment is enabled without manual transaction after last downpayment
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
@@ -1802,7 +1799,6 @@ Feature: Loan DownPayment
| 01 January 2022 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1000.0 | | 01 January 2022 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1000.0 |
| 01 January 2022 | Down Payment | 250.0 | 250.0 | 0.0 | 0.0 | 0.0 | 750.0 | | 01 January 2022 | Down Payment | 250.0 | 250.0 | 0.0 | 0.0 | 0.0 | 750.0 |
@TestRailId:C2859 @TestRailId:C2859
Scenario: Multi disbursement with undo last disbursement when auto downpayment is disabled without manual transaction after last downpayment Scenario: Multi disbursement with undo last disbursement when auto downpayment is disabled without manual transaction after last downpayment
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
@@ -1864,7 +1860,6 @@ Feature: Loan DownPayment
| 01 January 2022 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1000.0 | | 01 January 2022 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1000.0 |
| 01 January 2022 | Repayment | 250.0 | 250.0 | 0.0 | 0.0 | 0.0 | 750.0 | | 01 January 2022 | Repayment | 250.0 | 250.0 | 0.0 | 0.0 | 0.0 | 750.0 |
@TestRailId:C2866 @TestRailId:C2866
Scenario: Verify backdated disbursement - after down payment, before first installment due date, installment start date calculated by loan disbursement date Scenario: Verify backdated disbursement - after down payment, before first installment due date, installment start date calculated by loan disbursement date
When Admin sets the business date to "01 January 2023" When Admin sets the business date to "01 January 2023"
@@ -2272,7 +2267,6 @@ Feature: Loan DownPayment
| 01 February 2022 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1100.0 | | 01 February 2022 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1100.0 |
| 01 February 2022 | Down Payment | 50.0 | 50.0 | 0.0 | 0.0 | 0.0 | 1050.0 | | 01 February 2022 | Down Payment | 50.0 | 50.0 | 0.0 | 0.0 | 0.0 | 1050.0 |
@TestRailId:C2939 @TestRailId:C2939
Scenario: Multiple disbursements on same day - auto disabled Scenario: Multiple disbursements on same day - auto disabled
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
@@ -2666,7 +2660,6 @@ Feature: Loan DownPayment
| Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | Reverted | | Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | Reverted |
| 01 January 2022 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1000.0 | false | | 01 January 2022 | Disbursement | 1000.0 | 0.0 | 0.0 | 0.0 | 0.0 | 1000.0 | false |
@TestRailId:C3163 @TestRailId:C3163
Scenario: Verify that downpayment cannot be enabled during loan creation if the product has downpayment disabled Scenario: Verify that downpayment cannot be enabled during loan creation if the product has downpayment disabled
When Admin sets the business date to "01 January 2022" When Admin sets the business date to "01 January 2022"
fineract-e2e-tests-runner/src/test/resources/features/LoanInterestPause.feature
+6
View File
@@ -1,6 +1,7 @@
@InterestPauseFeature @InterestPauseFeature
Feature: Loan interest pause on repayment schedule Feature: Loan interest pause on repayment schedule
@TestRailId:C3475
Scenario: S1 - pause calculation within same period, interestRecalculation = true Scenario: S1 - pause calculation within same period, interestRecalculation = true
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
@@ -37,6 +38,7 @@ Feature: Loan interest pause on repayment schedule
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 100 | 1.95 | 0 | 0 | 101.95 | 17.01 | 0 | 0 | 84.94 | | 100 | 1.95 | 0 | 0 | 101.95 | 17.01 | 0 | 0 | 84.94 |
@TestRailId:C3476
Scenario: S2 - pause calculation between two periods, interestRecalculation = true Scenario: S2 - pause calculation between two periods, interestRecalculation = true
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
@@ -73,6 +75,7 @@ Feature: Loan interest pause on repayment schedule
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 100 | 1.57 | 0 | 0 | 101.57 | 17.01 | 0 | 0 | 84.56 | | 100 | 1.57 | 0 | 0 | 101.57 | 17.01 | 0 | 0 | 84.56 |
@TestRailId:C3477
Scenario: Backdated pause after the repayment Scenario: Backdated pause after the repayment
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
@@ -132,6 +135,7 @@ Feature: Loan interest pause on repayment schedule
| 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false | | 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false |
| 01 March 2024 | Repayment | 17.01 | 16.62 | 0.39 | 0.0 | 0.0 | 66.95 | false | true | | 01 March 2024 | Repayment | 17.01 | 16.62 | 0.39 | 0.0 | 0.0 | 66.95 | false | true |
@TestRailId:C3478
Scenario: Multiple pause Scenario: Multiple pause
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
@@ -209,6 +213,7 @@ Feature: Loan interest pause on repayment schedule
| 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false | | 01 February 2024 | Repayment | 17.01 | 16.43 | 0.58 | 0.0 | 0.0 | 83.57 | false | false |
| 01 March 2024 | Repayment | 17.01 | 16.62 | 0.39 | 0.0 | 0.0 | 66.95 | false | true | | 01 March 2024 | Repayment | 17.01 | 16.62 | 0.39 | 0.0 | 0.0 | 66.95 | false | true |
@TestRailId:C3479
Scenario: Interest accrual pause between two periods - UC2 Scenario: Interest accrual pause between two periods - UC2
When Admin sets the business date to "2 January 2024" When Admin sets the business date to "2 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
@@ -318,6 +323,7 @@ Feature: Loan interest pause on repayment schedule
| 03 April 2024 | Accrual | 0.02 | 0.0 | 0.02 | 0.0 | 0.0 | 0.0 | false | false | | 03 April 2024 | Accrual | 0.02 | 0.0 | 0.02 | 0.0 | 0.0 | 0.0 | false | false |
| 04 April 2024 | Accrual | 0.02 | 0.0 | 0.02 | 0.0 | 0.0 | 0.0 | false | false | | 04 April 2024 | Accrual | 0.02 | 0.0 | 0.02 | 0.0 | 0.0 | 0.0 | false | false |
@TestRailId:C3480
Scenario: Early repayment and interest pause Scenario: Early repayment and interest pause
When Admin sets the business date to "1 January 2024" When Admin sets the business date to "1 January 2024"
And Admin creates a client with random data And Admin creates a client with random data
fineract-e2e-tests-runner/src/test/resources/features/LoanProduct.feature
+2
View File
@@ -182,6 +182,7 @@ Feature: LoanProduct
When Refund undo happens on "1 July 2022" When Refund undo happens on "1 July 2022"
Then Loan has 1000 outstanding amount Then Loan has 1000 outstanding amount
@TestRailId:C3481
Scenario: As a user I would like to verify Charge-Off reasons options in loan product template response Scenario: As a user I would like to verify Charge-Off reasons options in loan product template response
When Admin sets the business date to "12 December 2021" When Admin sets the business date to "12 December 2021"
When Admin creates a client with random data When Admin creates a client with random data
@@ -194,6 +195,7 @@ Feature: LoanProduct
| Delinquent | | 3 | true | false | | Delinquent | | 3 | true | false |
| Other | | 4 | true | false | | Other | | 4 | true | false |
@TestRailId:C3482
Scenario: As a user I would like to verify Charge-Off reasons options in specific loan product response Scenario: As a user I would like to verify Charge-Off reasons options in specific loan product response
When Admin sets the business date to "12 December 2021" When Admin sets the business date to "12 December 2021"
When Admin creates a client with random data When Admin creates a client with random data
fineract-e2e-tests-runner/src/test/resources/features/LoanReAging.feature
-1
View File
@@ -136,7 +136,6 @@ Feature: LoanReAging
| 20 February 2024 | Re-age | 750.0 | 750.0 | 0.0 | 0.0 | 0.0 | 0.0 | true | | 20 February 2024 | Re-age | 750.0 | 750.0 | 0.0 | 0.0 | 0.0 | 0.0 | true |
Then Admin checks that delinquency range is: "RANGE_30" and has delinquentDate "2024-01-19" Then Admin checks that delinquency range is: "RANGE_30" and has delinquentDate "2024-01-19"
@TestRailId:C3053 @AdvancedPaymentAllocation @TestRailId:C3053 @AdvancedPaymentAllocation
Scenario: Verify that Loan re-aging transaction works properly when chargeback happens after re-aging Scenario: Verify that Loan re-aging transaction works properly when chargeback happens after re-aging
When Admin sets the business date to "01 January 2024" When Admin sets the business date to "01 January 2024"
fineract-e2e-tests-runner/src/test/resources/features/LoanRepayment.feature
+11 -11
View File
@@ -857,7 +857,7 @@ Feature: LoanRepayment
| INCOME | 404001 | Interest Income Charge Off | 10.0 | | | INCOME | 404001 | Interest Income Charge Off | 10.0 | |
| INCOME | 404008 | Fee Charge Off | 13.0 | | | INCOME | 404008 | Fee Charge Off | 13.0 | |
@Skip @TestRailId:C2626 @chargeoffOnLoanWithInterest @TestRailId:C2626 @chargeoffOnLoanWithInterest
Scenario: Verify that the accounting treatment is correct for Goodwill Credit transaction after Charge-off Scenario: Verify that the accounting treatment is correct for Goodwill Credit transaction after Charge-off
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -948,7 +948,7 @@ Feature: LoanRepayment
| INCOME | 404001 | Interest Income Charge Off | | 10.0 | | INCOME | 404001 | Interest Income Charge Off | | 10.0 |
| INCOME | 404008 | Fee Charge Off | | 13.0 | | INCOME | 404008 | Fee Charge Off | | 13.0 |
@Skip @TestRailId:C2628 @chargeoffOnLoanWithInterest @TestRailId:C2628 @chargeoffOnLoanWithInterest
Scenario: Verify that the accounting treatment is correct for Goodwill Credit transaction when the loan was Charged-off and undo happened for Goodwill Scenario: Verify that the accounting treatment is correct for Goodwill Credit transaction when the loan was Charged-off and undo happened for Goodwill
When Admin sets the business date to "1 January 2023" When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data And Admin creates a client with random data
@@ -968,9 +968,9 @@ Feature: LoanRepayment
Then Loan Repayment schedule has 3 periods, with the following data for periods: Then Loan Repayment schedule has 3 periods, with the following data for periods:
| Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| | | 01 January 2023 | | 1000.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2023 | | 1000.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 31 | 01 February 2023 | | 666.67 | 333.33 | 10.0 | 103.0 | 10.0 | 456.33 | 100.0 | 100.0 | 0.0 | 356.33 | | 1 | 31 | 01 February 2023 | | 667.0 | 333.0 | 10.0 | 103.0 | 10.0 | 456.0 | 100.0 | 100.0 | 0.0 | 356.0 |
| 2 | 28 | 01 March 2023 | | 333.34 | 333.33 | 10.0 | 0.0 | 0.0 | 343.33 | 0.0 | 0.0 | 0.0 | 343.33 | | 2 | 28 | 01 March 2023 | | 334.0 | 333.0 | 10.0 | 0.0 | 0.0 | 343.0 | 0.0 | 0.0 | 0.0 | 343.0 |
| 3 | 31 | 01 April 2023 | | 0.0 | 333.34 | 10.0 | 0.0 | 0.0 | 343.34 | 0.0 | 0.0 | 0.0 | 343.34 | | 3 | 31 | 01 April 2023 | | 0.0 | 334.0 | 10.0 | 0.0 | 0.0 | 344.0 | 0.0 | 0.0 | 0.0 | 344.0 |
Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1000 | 30 | 103 | 10 | 1143 | 100 | 100 | 0 | 1043 | | 1000 | 30 | 103 | 10 | 1143 | 100 | 100 | 0 | 1043 |
@@ -1261,7 +1261,7 @@ Feature: LoanRepayment
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1000 | 0 | 0 | 60 | 1060 | 700 | 700 | 0 | 360 | | 1000 | 0 | 0 | 60 | 1060 | 700 | 700 | 0 | 360 |
@Skip @TestRailId:C2639 @PaymentStrategyDueInAdvance @TestRailId:C2639 @PaymentStrategyDueInAdvance
Scenario: Verify the due-penalty-fee-interest-principal-in-advance-principal-penalty-fee-interest-strategy payment strategy - adding charge due in the future, then repayment before due date with full amount Scenario: Verify the due-penalty-fee-interest-principal-in-advance-principal-penalty-fee-interest-strategy payment strategy - adding charge due in the future, then repayment before due date with full amount
When Admin sets the business date to "01 January 2023" When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data When Admin creates a client with random data
@@ -1288,10 +1288,10 @@ Feature: LoanRepayment
Then Loan Repayment schedule has 1 periods, with the following data for periods: Then Loan Repayment schedule has 1 periods, with the following data for periods:
| Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| | | 01 January 2023 | | 1000.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 January 2023 | | 1000.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 31 | 01 February 2023 | 17 January 2023 | 0.0 | 1000.0 | 0.0 | 0.0 | 50.0 | 1050.0 | 1050.0 | 1000.0 | 0.0 | 0.0 | | 1 | 31 | 01 February 2023 | 17 January 2023 | 0.0 | 1000.0 | 0.0 | 0.0 | 50.0 | 1050.0 | 1050.0 | 1050.0 | 0.0 | 0.0 |
Then Loan Repayment schedule has the following data in Total row: Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1000 | 0 | 0 | 50 | 1050 | 1050 | 1000 | 0 | 0 | | 1000 | 0 | 0 | 50 | 1050 | 1050 | 1050 | 0 | 0 |
@TestRailId:C2655 @PaymentStrategyDueInAdvance @TestRailId:C2655 @PaymentStrategyDueInAdvance
Scenario: Verify the due-penalty-fee-interest-principal-in-advance-principal-penalty-fee-interest-strategy payment strategy - due principal Scenario: Verify the due-penalty-fee-interest-principal-in-advance-principal-penalty-fee-interest-strategy payment strategy - due principal
@@ -1870,7 +1870,7 @@ Feature: LoanRepayment
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1500 | 0 | 10 | 25 | 1535 | 1000 | 1000 | 0 | 535 | | 1500 | 0 | 10 | 25 | 1535 | 1000 | 1000 | 0 | 535 |
@Skip @TestRailId:C2799 @PaymentStrategyDueInAdvance @TestRailId:C2799 @PaymentStrategyDueInAdvance
Scenario: Verify the due-penalty-fee-interest-principal-in-advance-principal-penalty-fee-interest-strategy payment strategy: Same day transaction Scenario: Verify the due-penalty-fee-interest-principal-in-advance-principal-penalty-fee-interest-strategy payment strategy: Same day transaction
When Admin sets the business date to "01 January 2023" When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data When Admin creates a client with random data
@@ -2813,8 +2813,8 @@ Feature: LoanRepayment
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 1000 | 10 | 20 | 20 | 1050 | 1050 | 0 | 0 | 0 | | 1000 | 10 | 20 | 20 | 1050 | 1050 | 0 | 0 | 0 |
@Skip @TestRailId:C2800 @PaymentStrategyDueInAdvancePenaltyInterestPrincipalFee @TestRailId:C2800 @PaymentStrategyDueInAdvancePenaltyInterestPrincipalFee
Scenario: Verify the due-penalty-interest-principal-fee-in-advance-penalty-interest-principal-fee-strategy payment strategy: Same day transaction Scenario: Verify the due-penalty-interest-principal-fee-in-advance-penalty-interest-principal-fee-strategy payment strategy: Same day transaction - UC2
When Admin sets the business date to "01 January 2023" When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data When Admin creates a client with random data
When Admin creates a fully customized loan with the following data: When Admin creates a fully customized loan with the following data:
fineract-e2e-tests-runner/src/test/resources/features/LoanReschedule.feature
+24 -23
View File
@@ -222,38 +222,39 @@ Feature: LoanReschedule
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 3000 | 0 | 0 | 0 | 3000 | 0 | 0 | 0 | 3000 | | 3000 | 0 | 0 | 0 | 3000 | 0 | 0 | 0 | 3000 |
# TODO unskip and check when PS-1543 is done (periods back to 3 or 5) @TestRailId:C2808
@Skip @TestRailId:C2808
Scenario: Verify that loan is rescheduled properly in case of: multiple installments, mid-term grace period on interest Scenario: Verify that loan is rescheduled properly in case of: multiple installments, mid-term grace period on interest
When Admin sets the business date to "01 July 2023" When Admin sets the business date to "01 July 2023"
When Admin creates a client with random data When Admin creates a client with random data
When Admin creates a fully customized loan with the following data: When Admin creates a fully customized loan with the following data:
| LoanProduct | submitted on date | with Principal | ANNUAL interest rate % | interest type | interest calculation period | amortization type | loanTermFrequency | loanTermFrequencyType | repaymentEvery | repaymentFrequencyType | numberOfRepayments | graceOnPrincipalPayment | graceOnInterestPayment | interest free period | Payment strategy | | LoanProduct | submitted on date | with Principal | ANNUAL interest rate % | interest type | interest calculation period | amortization type | loanTermFrequency | loanTermFrequencyType | repaymentEvery | repaymentFrequencyType | numberOfRepayments | graceOnPrincipalPayment | graceOnInterestPayment | interest free period | Payment strategy |
| LP1_INTEREST_FLAT | 01 July 2023 | 3000 | 12 | FLAT | SAME_AS_REPAYMENT_PERIOD | EQUAL_INSTALLMENTS | 10 | MONTHS | 1 | MONTHS | 10 | 0 | 0 | 0 | PENALTIES_FEES_INTEREST_PRINCIPAL_ORDER | | LP1_INTEREST_FLAT | 01 July 2023 | 4000 | 12 | FLAT | SAME_AS_REPAYMENT_PERIOD | EQUAL_INSTALLMENTS | 4 | MONTHS | 1 | MONTHS | 4 | 0 | 0 | 0 | PENALTIES_FEES_INTEREST_PRINCIPAL_ORDER |
And Admin successfully approves the loan on "01 July 2023" with "3000" amount and expected disbursement date on "01 July 2023" And Admin successfully approves the loan on "01 July 2023" with "4000" amount and expected disbursement date on "01 July 2023"
And Admin successfully disburse the loan on "01 July 2023" with "3000" EUR transaction amount And Admin successfully disburse the loan on "01 July 2023" with "4000" EUR transaction amount
# Then Loan Repayment schedule has 3 periods, with the following data for periods: Then Loan Repayment schedule has 4 periods, with the following data for periods:
# | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | | | 01 July 2023 | | 3000.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 July 2023 | | 4000.0 | | | 0.0 | | 0.0 | 0.0 | | | |
# | 1 | 31 | 01 August 2023 | | 2000.0 | 1000.0 | 30.0 | 0.0 | 0.0 | 1030.0 | 0.0 | 0.0 | 0.0 | 1030.0 | | 1 | 31 | 01 August 2023 | | 3000.0 | 1000.0 | 40.0 | 0.0 | 0.0 | 1040.0 | 0.0 | 0.0 | 0.0 | 1040.0 |
# | 2 | 31 | 01 September 2023 | | 1000.0 | 1000.0 | 30.0 | 0.0 | 0.0 | 1030.0 | 0.0 | 0.0 | 0.0 | 1030.0 | | 2 | 31 | 01 September 2023 | | 2000.0 | 1000.0 | 40.0 | 0.0 | 0.0 | 1040.0 | 0.0 | 0.0 | 0.0 | 1040.0 |
# | 3 | 30 | 01 October 2023 | | 0.0 | 1000.0 | 30.0 | 0.0 | 0.0 | 1030.0 | 0.0 | 0.0 | 0.0 | 1030.0 | | 3 | 30 | 01 October 2023 | | 1000.0 | 1000.0 | 40.0 | 0.0 | 0.0 | 1040.0 | 0.0 | 0.0 | 0.0 | 1040.0 |
# Then Loan Repayment schedule has the following data in Total row: | 4 | 31 | 01 November 2023 | | 0.0 | 1000.0 | 40.0 | 0.0 | 0.0 | 1040.0 | 0.0 | 0.0 | 0.0 | 1040.0 |
# | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | Then Loan Repayment schedule has the following data in Total row:
# | 3000 | 90 | 0 | 0 | 3090 | 0 | 0 | 0 | 3090 | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 4000 | 160 | 0 | 0 | 4160 | 0 | 0 | 0 | 4160 |
When Admin sets the business date to "05 July 2023" When Admin sets the business date to "05 July 2023"
When Admin creates and approves Loan reschedule with the following data: When Admin creates and approves Loan reschedule with the following data:
| rescheduleFromDate | submittedOnDate | adjustedDueDate | graceOnPrincipal | graceOnInterest | extraTerms | newInterestRate | | rescheduleFromDate | submittedOnDate | adjustedDueDate | graceOnPrincipal | graceOnInterest | extraTerms | newInterestRate |
| 01 September 2023 | 05 July 2023 | | | 2 | | | | 01 September 2023 | 05 July 2023 | | | 2 | | |
# Then Loan Repayment schedule has 3 periods, with the following data for periods: Then Loan Repayment schedule has 4 periods, with the following data for periods:
# | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | | Nr | Days | Date | Paid date | Balance of loan | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
# | | | 01 July 2023 | | 3000.0 | | | 0.0 | | 0.0 | 0.0 | | | | | | | 01 July 2023 | | 4000.0 | | | 0.0 | | 0.0 | 0.0 | | | |
# | 1 | 31 | 01 August 2023 | | 2000.0 | 1000.0 | 30.0 | 0.0 | 0.0 | 1030.0 | 0.0 | 0.0 | 0.0 | 1030.0 | | 1 | 31 | 01 August 2023 | | 3000.0 | 1000.0 | 40.0 | 0.0 | 0.0 | 1040.0 | 0.0 | 0.0 | 0.0 | 1040.0 |
# | 2 | 31 | 01 September 2023 | | 1000.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 | | 2 | 31 | 01 September 2023 | | 2000.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 |
# | 3 | 30 | 01 October 2023 | | 0.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 | | 3 | 30 | 01 October 2023 | | 1000.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 | 0.0 | 0.0 | 0.0 | 1000.0 |
# Then Loan Repayment schedule has the following data in Total row: | 4 | 31 | 01 November 2023 | | 0.0 | 1000.0 | 120.0 | 0.0 | 0.0 | 1120.0 | 0.0 | 0.0 | 0.0 | 1120.0 |
# | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding | Then Loan Repayment schedule has the following data in Total row:
# | 3000 | 30 | 0 | 0 | 3030 | 0 | 0 | 0 | 3030 | | Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 4000 | 160 | 0 | 0 | 4160 | 0 | 0 | 0 | 4160 |
@TestRailId:C2809 @TestRailId:C2809
Scenario: Verify that loan is rescheduled properly in case of: multiple installments, new interest rate Scenario: Verify that loan is rescheduled properly in case of: multiple installments, new interest rate