Incorrect Match Event Created For Refund Transactions (Doc ID 2897203.1)

Last updated on SEPTEMBER 26, 2022

Applies to:

Symptoms

On RMB v2.9.0.1.0, Incorrect Match Event created for Refund Transactions

Payment event has multiple payments having multiple payee accounts.

Payment Event - Payor Account - 123
  * Payment - Payee Account 678 - Excess Credit Contract
  * Payment - Payee Account 910 – Bill Weighted

ACTUAL BEHAVIOR
----------------------------
When Refund is initiated at Account 123, the system is creating a Match Event for account 123 and closing the Account 678 financial transaction.
As a result, the match event does not balance and keeps the balance open for the Payment financial transaction 678.

EXPECTED BEHAVIOR
--------------------------------
The system should use the match event for the 678 account to close FTs belonging to 678.
Both payment will get refunded and match events will be balanced.

STEPS
-----------------------
Payment event has multiple payments having multiple payee accounts as mentioned above.
Try creating a refund on Payor Account - 123 for both payments.
1. Create two accounts.
2. Create payment event and add payment on account for A1(excess contract created for excess payment).
3. Add second account in payment event and match type id Apply to account.(Excess payment)
4. Create refund request and search payment with payment date.
5. Add both the payment in refund request and submit the refund request.
6. Go to payment and go to FT then click on match event ID pin and check whether match event status is balanced for both the payment.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.