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

FINERACT-2070: E2E testcase migration - feature files - pt3

Browse Source
This commit is contained in:
Peter Kovacs
2024-11-10 14:38:04 +01:00
committed by Adam Saghy
parent 6770352da8
commit ab1a634d17
5 changed files with 2958 additions and 347 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fineract-e2e-tests-runner/src/test/resources/features/LoanCBR.feature
+167 -31
View File
@@ -1,7 +1,7 @@
@LoanCBR
Feature: Credit Balance Refund
@TestRailId:C2505
Scenario: Verify that Loan status goes from overpaid to active in case of CBR transaction (with replaying when CBR>new balance → clears overpaid, remaining increasing loan balance)
When Admin sets the business date to "01 January 2023"
When Admin creates a client with random data
@@ -48,7 +48,7 @@ Feature: Credit Balance Refund
| LIABILITY | l1 | Overpayment account | 100.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
@TestRailId:C2511
Scenario: Verify that Loan status goes from overpaid to closed in case of CBR transaction when transaction amount equals overpaid amount
When Admin sets the business date to "1 January 2023"
When Admin creates a client with random data
@@ -88,7 +88,7 @@ Feature: Credit Balance Refund
| LIABILITY | l1 | Overpayment account | 200.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
@TestRailId:C2515
Scenario: Single repayment reversal
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -122,7 +122,7 @@ Feature: Credit Balance Refund
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
@TestRailId:C2516
Scenario: Multi repayment reversal
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -161,7 +161,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 200.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
@TestRailId:C2517
Scenario: Overpaid paid portion
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -202,7 +202,7 @@ Feature: Credit Balance Refund
| LIABILITY | l1 | Overpayment account | 100.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
@TestRailId:C2518
Scenario: Repayment reversal
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -241,7 +241,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 1000.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 1000.0 |
@TestRailId:C2519
Scenario: Refund reversal
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -280,7 +280,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 1000.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 1000.0 |
@TestRailId:C2520
Scenario: Partial refund reversal
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -319,7 +319,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 500.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 500.0 |
@TestRailId:C2521
Scenario: Chargeback after CBR
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -368,7 +368,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 500.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 500.0 |
@TestRailId:C2522
Scenario: Refund after CBR scenario
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -422,7 +422,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 500.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 500.0 |
@TestRailId:C2523
Scenario: Single repayment reversal (after maturity)
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -455,7 +455,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 200.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
@TestRailId:C2524
Scenario: Multi repayment reversal (after maturity)
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -494,7 +494,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 200.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
@TestRailId:C2525
Scenario: Overpaid paid portion (after maturity)
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -535,7 +535,7 @@ Feature: Credit Balance Refund
| LIABILITY | l1 | Overpayment account | 100.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
@TestRailId:C2526
Scenario: Repayment reversal (after maturity)
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -574,7 +574,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 1000.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 1000.0 |
@TestRailId:C2527
Scenario: Refund reversal (after maturity)
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -613,7 +613,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 1000.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 1000.0 |
@TestRailId:C2528
Scenario: Partial refund reversal (after maturity)
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -652,7 +652,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 500.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 500.0 |
@TestRailId:C2529
Scenario: Chargeback after CBR (after maturity)
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -701,7 +701,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 500.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 500.0 |
@TestRailId:C2530
Scenario: Refund after CBR scenario (after maturity)
When Admin sets the business date to "1 January 2023"
And Admin creates a client with random data
@@ -755,7 +755,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 500.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 500.0 |
@TestRailId:C2841
Scenario: Verify that accruals created for charges after CBR post-maturity
When Admin sets the business date to "01 July 2023"
And Admin creates a client with random data
@@ -804,7 +804,7 @@ Feature: Credit Balance Refund
| 02 August 2023 | Credit Balance Refund | 200.0 | 10.0 | 0.0 | 0.0 | 0.0 | 10.0 |
| 03 August 2023 | Accrual | 10.0 | 0.0 | 0.0 | 10.0 | 0.0 | 0.0 |
@TestRailId:C2885
Scenario: Verify that Loan status goes from overpaid to active in case of CBR transaction (with replaying when CBR>new balance → clears overpaid, remaining increasing loan balance) - LP2_DOWNPAYMENT_AUTO_ADVANCED_PAYMENT_ALLOCATION loan product
When Admin sets the business date to "01 September 2023"
When Admin creates a client with random data
@@ -875,7 +875,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 100.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 100.0 |
@TestRailId:C2886
Scenario: Verify that Loan status goes from overpaid to closed in case of CBR transaction when transaction amount equals overpaid amount - LP2_DOWNPAYMENT_AUTO_ADVANCED_PAYMENT_ALLOCATION loan product
When Admin sets the business date to "01 September 2023"
When Admin creates a client with random data
@@ -941,7 +941,7 @@ Feature: Credit Balance Refund
| LIABILITY | l1 | Overpayment account | 100.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 100.0 |
@TestRailId:C2887
Scenario: Verify that Loan status goes from overpaid to active in case of Refund transaction was reverted - LP2_DOWNPAYMENT_AUTO_ADVANCED_PAYMENT_ALLOCATION loan product
When Admin sets the business date to "01 September 2023"
When Admin creates a client with random data
@@ -1018,7 +1018,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 100.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 100.0 |
@TestRailId:C2888
Scenario: Multi repayment reversal (after maturity) - LP2_DOWNPAYMENT_AUTO_ADVANCED_PAYMENT_ALLOCATION loan product
When Admin sets the business date to "01 September 2023"
When Admin creates a client with random data
@@ -1091,7 +1091,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 100.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 100.0 |
@TestRailId:C2889
Scenario: Verify that Loan status goes from overpaid to active in case of CBR transaction (after maturity) - LP2_DOWNPAYMENT_AUTO_ADVANCED_PAYMENT_ALLOCATION loan product
When Admin sets the business date to "01 September 2023"
When Admin creates a client with random data
@@ -1170,7 +1170,7 @@ Feature: Credit Balance Refund
| ASSET | 112601 | Loans Receivable | 100.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 100.0 |
@TestRailId:C2890
Scenario: Verify that accruals created for charges after CBR post-maturity - LP2_DOWNPAYMENT_AUTO_ADVANCED_PAYMENT_ALLOCATION loan product
When Admin sets the business date to "01 September 2023"
When Admin creates a client with random data
@@ -1240,7 +1240,7 @@ Feature: Credit Balance Refund
| 18 October 2023 | Credit Balance Refund | 100.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 19 October 2023 | Accrual | 10.0 | 0.0 | 0.0 | 10.0 | 0.0 | 0.0 |
@TestRailId:C2989
Scenario: Verify that CBR transaction date cannot be in the future
When Admin sets the business date to "01 September 2023"
When Admin creates a client with random data
@@ -1258,7 +1258,7 @@ Feature: Credit Balance Refund
When Admin sets the business date to "15 September 2023"
Then Credit Balance Refund transaction on future date "20 September 2023" with 250 EUR transaction amount will result an error
@TestRailId:C3020
Scenario: Verify that Charge-off and CBR transaction GL entries are correct in case of repayment reversal after CBR and Fraud flagged loan
When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data
@@ -1305,7 +1305,7 @@ Feature: Credit Balance Refund
| EXPENSE | 744037 | Credit Loss/Bad Debt-Fraud | 250.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 250.0 |
@TestRailId:C3021
Scenario: Verify that Charge-off and CBR transaction GL entries are correct in case of repayment reversal after CBR and Non-Fraud loan
When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data
@@ -1351,7 +1351,7 @@ Feature: Credit Balance Refund
| EXPENSE | 744007 | Credit Loss/Bad Debt | 250.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 250.0 |
@TestRailId:C3040
Scenario: Verify that Charge-off and CBR transaction GL entries are correct before and after a repayment reversal taken place after CBR - UC1
When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data
@@ -1425,7 +1425,7 @@ Feature: Credit Balance Refund
| LIABILITY | l1 | Overpayment account | 250.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 350.0 |
@TestRailId:C3041
Scenario: Verify that Charge-off and CBR transaction GL entries are correct before and after a repayment reversal taken place after CBR - UC2
When Admin sets the business date to "01 January 2024"
When Admin creates a client with random data
@@ -1494,7 +1494,7 @@ Feature: Credit Balance Refund
| EXPENSE | 744007 | Credit Loss/Bad Debt | 250.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 250.0 |
@TestRailId:C3092
Scenario: Verify that overpayment portion calculated properly in case of CBR reverse-replay
When Admin sets the business date to "25 January 2024"
When Admin creates a client with random data
@@ -1538,3 +1538,139 @@ Feature: Credit Balance Refund
| 01 March 2024 | Credit Balance Refund | 124.83 | 36.99 | 0.0 | 0.0 | 0.0 | 36.99 | false |
| 02 March 2024 | Merchant Issued Refund | 19.99 | 19.99 | 0.0 | 0.0 | 0.0 | 17.0 | false |
| 02 March 2024 | Merchant Issued Refund | 19.99 | 17.0 | 0.0 | 0.0 | 0.0 | 0.0 | false |
@TestRailId:C3140
Scenario: Verify that the journal entries are correct in case of merchant issued refund (chargeoff, backdated transaction, undo repayment, downpayment)
When Admin sets the business date to "24 May 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_AUTO_ADVANCED_PAYMENT_ALLOCATION | 24 May 2024 | 200 | 0 | FLAT | SAME_AS_REPAYMENT_PERIOD | EQUAL_INSTALLMENTS | 30 | DAYS | 30 | DAYS | 1 | 0 | 0 | 0 | ADVANCED_PAYMENT_ALLOCATION |
And Admin successfully approves the loan on "24 May 2024" with "200" amount and expected disbursement date on "24 May 2024"
When Admin successfully disburse the loan on "24 May 2024" with "200" EUR transaction amount
When Admin runs inline COB job for Loan
When Admin sets the business date to "25 May 2024"
When Customer undo "1"th "Down Payment" transaction made on "24 May 2024"
Then Loan Repayment schedule has 2 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 |
| | | 24 May 2024 | | 200.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 0 | 24 May 2024 | | 150.0 | 50.0 | 0.0 | 0.0 | 0.0 | 50.0 | 0.0 | 0.0 | 0.0 | 50.0 |
| 2 | 30 | 23 June 2024 | | 0.0 | 150.0 | 0.0 | 0.0 | 0.0 | 150.0 | 0.0 | 0.0 | 0.0 | 150.0 |
Then Loan Transactions tab has the following data:
| Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | Reverted | Replayed |
| 24 May 2024 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 200.0 | false | false |
| 24 May 2024 | Down Payment | 50.0 | 50.0 | 0.0 | 0.0 | 0.0 | 150.0 | true | false |
Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 200.0 | 0.0 | 0.0 | 0.0 | 200.0 | 0.0 | 0.0 | 0.0 | 200.0 |
When Admin runs inline COB job for Loan
When Admin sets the business date to "26 May 2024"
And Admin does charge-off the loan on "26 May 2024"
And Customer makes "AUTOPAY" repayment on "25 May 2024" with 10 EUR transaction amount
When Customer makes "MERCHANT_ISSUED_REFUND" transaction with "AUTOPAY" payment type on "26 May 2024" with 200 EUR transaction amount and system-generated Idempotency key
Then Loan Repayment schedule has 2 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 |
| | | 24 May 2024 | | 200.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 0 | 24 May 2024 | 26 May 2024 | 150.0 | 50.0 | 0.0 | 0.0 | 0.0 | 50.0 | 50.0 | 0.0 | 50.0 | 0.0 |
| 2 | 30 | 23 June 2024 | 26 May 2024 | 0.0 | 150.0 | 0.0 | 0.0 | 0.0 | 150.0 | 150.0 | 150.0 | 0.0 | 0.0 |
Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 200.0 | 0.0 | 0.0 | 0.0 | 200.0 | 200.0 | 150.0 | 50.0 | 0.0 |
Then Loan Transactions tab has the following data:
| Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | Reverted | Replayed |
| 24 May 2024 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 200.0 | false | false |
| 24 May 2024 | Down Payment | 50.0 | 50.0 | 0.0 | 0.0 | 0.0 | 150.0 | true | false |
| 25 May 2024 | Repayment | 10.0 | 10.0 | 0.0 | 0.0 | 0.0 | 190.0 | false | false |
| 26 May 2024 | Charge-off | 190.0 | 190.0 | 0.0 | 0.0 | 0.0 | 0.0 | false | true |
| 26 May 2024 | Merchant Issued Refund | 200.0 | 190.0 | 0.0 | 0.0 | 0.0 | 0.0 | false | false |
When Admin runs inline COB job for Loan
Then Loan status will be "OVERPAID"
Then Loan has 0 outstanding amount
Then Loan has 10 overpaid amount
When Admin sets the business date to "27 May 2024"
When Admin makes Credit Balance Refund transaction on "27 May 2024" with 10 EUR transaction amount
Then Loan Repayment schedule has 2 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 |
| | | 24 May 2024 | | 200.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 0 | 24 May 2024 | 26 May 2024 | 150.0 | 50.0 | 0.0 | 0.0 | 0.0 | 50.0 | 50.0 | 0.0 | 50.0 | 0.0 |
| 2 | 30 | 23 June 2024 | 26 May 2024 | 0.0 | 150.0 | 0.0 | 0.0 | 0.0 | 150.0 | 150.0 | 150.0 | 0.0 | 0.0 |
Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 200.0 | 0.0 | 0.0 | 0.0 | 200.0 | 200.0 | 150.0 | 50.0 | 0.0 |
Then Loan Transactions tab has the following data:
| Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | Reverted | Replayed |
| 24 May 2024 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 200.0 | false | false |
| 24 May 2024 | Down Payment | 50.0 | 50.0 | 0.0 | 0.0 | 0.0 | 150.0 | true | false |
| 25 May 2024 | Repayment | 10.0 | 10.0 | 0.0 | 0.0 | 0.0 | 190.0 | false | false |
| 26 May 2024 | Charge-off | 190.0 | 190.0 | 0.0 | 0.0 | 0.0 | 0.0 | false | true |
| 26 May 2024 | Merchant Issued Refund | 200.0 | 190.0 | 0.0 | 0.0 | 0.0 | 0.0 | false | false |
| 27 May 2024 | Credit Balance Refund | 10.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | false | false |
When Customer undo "1"th "Repayment" transaction made on "25 May 2024"
Then Loan Repayment schedule has 2 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 |
| | | 24 May 2024 | | 200.0 | | | 0.0 | | 0.0 | 0.0 | | | |
| 1 | 0 | 24 May 2024 | 26 May 2024 | 150.0 | 50.0 | 0.0 | 0.0 | 0.0 | 50.0 | 50.0 | 0.0 | 50.0 | 0.0 |
| 2 | 30 | 23 June 2024 | | 0.0 | 160.0 | 0.0 | 0.0 | 0.0 | 160.0 | 150.0 | 150.0 | 0.0 | 10.0 |
Then Loan Repayment schedule has the following data in Total row:
| Principal due | Interest | Fees | Penalties | Due | Paid | In advance | Late | Outstanding |
| 210.0 | 0.0 | 0.0 | 0.0 | 210.0 | 200.0 | 150.0 | 50.0 | 10.0 |
Then Loan Transactions tab has the following data:
| Transaction date | Transaction Type | Amount | Principal | Interest | Fees | Penalties | Loan Balance | Reverted | Replayed |
| 24 May 2024 | Disbursement | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | 200.0 | false | false |
| 24 May 2024 | Down Payment | 50.0 | 50.0 | 0.0 | 0.0 | 0.0 | 150.0 | true | false |
| 25 May 2024 | Repayment | 10.0 | 10.0 | 0.0 | 0.0 | 0.0 | 190.0 | true | false |
| 26 May 2024 | Charge-off | 200.0 | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | false | true |
| 26 May 2024 | Merchant Issued Refund | 200.0 | 200.0 | 0.0 | 0.0 | 0.0 | 0.0 | false | true |
| 27 May 2024 | Credit Balance Refund | 10.0 | 10.0 | 0.0 | 0.0 | 0.0 | 10.0 | false | true |
Then Loan Transactions tab has a "DISBURSEMENT" transaction with date "24 May 2024" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit |
| ASSET | 112601 | Loans Receivable | 200.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 200.0 |
Then Loan Transactions tab has a "DOWN_PAYMENT" transaction with date "24 May 2024" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit |
| ASSET | 112601 | Loans Receivable | | 50.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 50.0 | |
| ASSET | 112601 | Loans Receivable | 50.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 50.0 |
Then Loan Transactions tab has a "REPAYMENT" transaction with date "25 May 2024" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit |
| ASSET | 112601 | Loans Receivable | | 10.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 10.0 | |
| ASSET | 112601 | Loans Receivable | 10.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 10.0 |
Then Loan Transactions tab has a "CHARGE_OFF" transaction with date "26 May 2024" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit |
| ASSET | 112601 | Loans Receivable | | 200.0 |
| EXPENSE | 744007 | Credit Loss/Bad Debt | 200.0 | |
Then Loan Transactions tab has a "MERCHANT_ISSUED_REFUND" transaction with date "26 May 2024" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit |
| EXPENSE | 744007 | Credit Loss/Bad Debt | | 200.0 |
| LIABILITY | 145023 | Suspense/Clearing account | 200.0 | |
Then Loan Transactions tab has a "CREDIT_BALANCE_REFUND" transaction with date "27 May 2024" which has the following Journal entries:
| Type | Account code | Account name | Debit | Credit |
| EXPENSE | 744007 | Credit Loss/Bad Debt | 10.0 | |
| LIABILITY | 145023 | Suspense/Clearing account | | 10.0 |
@TestRailId:C3203
Scenario: Verify that loan status is correct when CBR is reversed on an overpaid loan
When Admin sets the business date to "01 July 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_AUTO_ADVANCED_PAYMENT_ALLOCATION | 01 July 2024 | 1000 | 0 | FLAT | SAME_AS_REPAYMENT_PERIOD | EQUAL_INSTALLMENTS | 30 | DAYS | 30 | DAYS | 1 | 0 | 0 | 0 | ADVANCED_PAYMENT_ALLOCATION |
And Admin successfully approves the loan on "01 July 2024" with "1000" amount and expected disbursement date on "01 July 2024"
When Admin successfully disburse the loan on "01 July 2024" with "1000" EUR transaction amount
When Admin sets the business date to "10 July 2024"
And Customer makes "AUTOPAY" repayment on "10 July 2024" with 1000 EUR transaction amount
Then Loan status will be "OVERPAID"
Then Loan has 0 outstanding amount
Then Loan has 250 overpaid amount
When Admin sets the business date to "11 July 2024"
When Admin makes Credit Balance Refund transaction on "11 July 2024" with 250 EUR transaction amount
Then Loan status will be "CLOSED_OBLIGATIONS_MET"
Then Loan has 0 outstanding amount
When Admin sets the business date to "12 July 2024"
When Customer undo "1"th transaction made on "11 July 2024"
Then Loan status will be "OVERPAID"
Then Loan has 0 outstanding amount
Then Loan has 250 overpaid amount