Acces On 4 Eyes In OFSAA CS And TF
(Doc ID 3029151.1)
Last updated on JUNE 19, 2024
Applies to:
Oracle Financial Services Transaction Filtering - Version 8.0.5 and laterInformation in this document applies to any platform.
Goal
User need information on 4 eye for below scenario.
We have a doubt if its posible to implement 4 eyes in OFSAA CS and TF.
1- OFSAA CS Batch has a 4-eyes validation for all true match cases. A first analyst proposes the positive and a second analyst must sanction it. The problem is that right now the same person can be the first and the second level, and this did not please the CSSF. The tool should be modified so that in cases of true match, the analyst who sanctions must be different from the one who sanctions.
2- For the cases related to sanctions in OFSAA CS Batch, we need that those that are closed as false positive also require validation 4 eyes, as in the case of true match.
3- For OFSAA TF all alerts are managed at a single level. For those containing name hits related to sanction lists we would need the system to force the decision to be sanctioned at the first level before releasing the transfer. As in the previous cases, the sanctioner should not be the one proposing at the first level
4- Its posible to create a audit user for tf? this user shouldn't manage alerts.
Solution
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
Goal |
Solution |
References |