Use of Status field during and after case resolution

Consider the below scenario and please respond to query
mentioned at the end.
- Screening call is made for “WT MARINE PTE LTD”
- A match is found on WC1 side
- Admin goes in and resolve that case with status
selected as “Positive – Declined”
- Now a rescreening call is made for same case
- Below response is received for rescreening call
“[{"resultId":"0a3687cf-673a-1553-99e1-3690005e01ef","referenceId":"e_tr_wco_4540054","matchStrength":"EXACT","matchedTerm":"WT
Marine Pte Ltd","submittedTerm":"WT Marine Pte.
Ltd","matchedNameType":"AKA","secondaryFieldResults":[],"sources":["b_trwc_DPRK-WC","b_trwc_393","b_trwc_386"],"categories":["Other
Bodies","Sanctions","Sanctions"],"creationDate":"2018-12-06T18:49:15.333Z","modificationDate":"2018-12-11T18:36:52.294Z","resolution":{"statusId":"0a3687cf-65b4-1aaa-99b1-9b030000282e","riskId":"0a3687cf-65b4-1aaa-99b1-9b030000282d","reasonId":"0a3687cf-65b4-1aaa-99b1-9b0300002825","resolutionRemark":null,"resolutionDate":"2018-12-11T18:36:52.294Z"},"resultReview":{"reviewRequired":false,"reviewRequiredDate":"2018-11-08T00:00:00.000Z","reviewRemark":null,"reviewDate":null}}]”
How do we interpret this response? Since user is declining
it on WC1 site, should this rescreening call be resulting in flag or not?
Also it will be helpful if you can provide the meaning for
statuses like “Positive”, “False”, possible”, “Unspecified” and how should we
interpret the response for the calls made for cases resolved with these
statuses.
Best Answer
-
After the compliance team has resolved the case as Positive-Declined in the WC1 UI, in the back end, the "resolutionStatus" attribute of the result set gets changed to:
"resolution":{"statusId":"0a3687cf-65b4-1aaa-99b1-9b030000282e","riskId":"0a3687cf-65b4-1aaa-99b1-9b030000282d","reasonId":"0a3687cf-65b4-1aaa-99b1-9b0300002825"
Kindly note if the case has not been resolved, the value that the resolutionStatus will bear is "null".
So in order to identify if the compliance team has declined/approved a client, you need to find out if the "resolutionStatus" has a value different than "null". You can use the API call "
SEQ-case-investigate-results: Get screening results" to fetch the result set and to find out the value of the resolutionStatus attribute. The key here is to find out the value of statusId, riskId and reasonId and what each stands for to make sense of whether the case was marked as positive, false, etc.
You can use the API call "SEQ-1f: Get the resolution toolkit for a group" to find out which statusId value found in the resolutionStatus attributes corresponds to which status. It is important to use the correct group Id to fetch this JSON of this API call as the resolution toolkit and its values changes for each group.
Regarding the question, "Since user is declining it on WC1 site, should this rescreening call be resulting in flag or not?"
This will not result in any flag. As this has been marked as Positive, only the resolutionStatus attribute would change. But kindly the event that changes the resolutionStatus is the action of resolving cases and not rescreening. Rescreening the already screened case, would make our system to search for new hits if any or updates on the existing matches. In both cases, the re screening would not update the resolutionStatus of any match. If you re screen the case and the WC1 system finds that there is an update on the match that was previously marked as positive/false or resolved in general, only then it would raise a flag. The flag would be in the form of marking a change in the attribute "reviewRequired".
As you can see currently, the "reviewRequired" has the below values:
"resultReview":{"reviewRequired":false,"reviewRequiredDate":"2018-11-08T00:00:00.000Z","reviewRemark":null,"reviewDate":null}
If there was a new update on this already resolved case due to re screening today, the above JSON would change to
"resultReview":{"reviewRequired":true,"reviewRequiredDate":"2018-12-12T00:00:00.000Z","reviewRemark":null,"reviewDate":null}
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 Datastream
- 1.5K DSS
- 632 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 563 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 749 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 123 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛