My Oracle Support Banner

Alert stay open after cut-off configuration automatically releases payment in TF (Doc ID 2742380.1)

Last updated on JANUARY 12, 2021

Applies to:

Oracle Financial Services Transaction Filtering - Version 8.0.6 and later
Information in this document applies to any platform.

Symptoms

SWIFT MT message type include real payments. Some of them just include data that may be sent from one financial institution to another related to compliance or fraud related issues.

For this reason, banks consider these specific payment types as 'Non-Blocking' message types, which means that they should never be blocked.

'Non-Blocking' should behave like this:
- They should be screened by EDQ as any other payment type. This should generate a score in EDQ.
- If the resulting score is below the IPE threshold, no TF Alert will be created. A JMS message with status CLEAN should be returned.
- If the score is above the IPE threshold, a TF Alert will be created. However, since these messages should never be blocked, the output JMS message should still have a status CLEAN.

Currently configured Cut-Off functionality to Release two of the Non-Blocking payment types after 5 seconds.

However, after that time expires, the corresponding TF Alert gets closed in the dashboard.

Some clients want some payment types to be released under a specific SLA, but they still want those payments to be investigated to understand if they actually should have been released or not.

This information help them to improve their processes and get valuable information about if their current automated release rules can be improved.

We think it could be interesting to add an option to Cut-Off functionality to allow keeping TF Alerts open even if it is configured to release the payment automatically.

This could be offered as an option in Cut-Off configuration screen.

Steps to reproduce :

Step 1 : Login to TF as Admin user

Step 2 : Open Cut off configuration screen and configure it for payments.

Step 3 : Check the message status once the cut off time is expired.

Expected result :

Alerts should be kept open even though cut off time is released.

Actual result :

Alerts are getting released once the cut off time is expired.

Cut off configuration : 

Changes

Cut off configuration modified.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


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