Global government sanctions systems and methods

• US 20080183618A1
• Filed: 01/26/2007
• Published: 07/31/2008
• Est. Priority Date: 01/26/2007
• Status: Abandoned Application

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Giacco, Michael R., Freyta, Lynn Eloisa, Schirmer, Karen W.
• Application Number:
  US11/627,915
• Publication Number:
  US 20080183618A1
• Time in Patent Office: Days
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

A suspect transaction dataset may be generated from screening a transaction dataset against a master suspect list. Often, this screening process results in a large percentage of false positives hits distributed among the data in the suspect transaction dataset. Among other things, embodiments of the invention provide systems and methods for removing the false positives from a suspect transaction dataset. Some embodiments of the invention use detailed decision matrices to generate, analyze, and cull the dataset. Other embodiments use multi-tiered screening with iterative feedback loops to perform those and other dataset functions.

Claims

1. A method for screening transaction data against a master suspect list and removing false positives, the method comprising:

generating, with a computer, a suspect transaction dataset comprising a suspect record, the suspect record comprising;

a set of data, at least one of the set of data being a common datum which is substantially identical to a master suspect list datum, both the common datum and the master suspect list datum being of a datum type,

a stop designator representing the common datum, and

a master datum type code designating the datum type of the master suspect list datum;

providing the suspect transaction dataset to a reviewer;

providing, to the reviewer, a set of decision codes comprising a quick decision code;

prompting the reviewer to select a selected decision code from the set of decision codes to associate with the suspect record, the selection being based at least in part on the stop designator and the master datum type code;

associating the selected decision code with the suspect record; and

prompting the reviewer for further information relating to the removal of false positives and associating the further information with the suspect record.

2. The method of claim 1, wherein prompting the reviewer for further information occurs only when the selected decision code is not the quick decision code

3. The method of claim 1, further comprising removing the suspect record from the suspect transaction dataset when the selected decision code is the quick decision code.

4. The method of claim 1, further comprising:

communicating the suspect record to a quality controller to check whether the reviewer selected an appropriate decision code to associate with the suspect record; and

receiving a quality determination from the quality controller.

5. The method of claim 4, wherein the reviewer is a first reviewer;

and

further comprising providing the suspect record to a second reviewer when the quality determination reflects that the reviewer selected an inappropriate decision code to associate with the suspect record.

6. The method of claim 4, further comprising marking the suspect record to reflect the quality determination.

7. The method of claim 5, wherein the second reviewer is the first reviewer.

8. The method of claim 4, wherein the suspect transaction dataset is stored in a queue configured to prioritize data based at least on the quality determination.

9. The method of claim 1, further comprising:

communicating the suspect record to a next higher authority;

providing the next higher authority with a first research tool; and

receiving, from the next higher authority, a disposition based at least in part on data from the first research tool and reflecting either a block condition, a clear condition, or a hold condition.

10. The method of claim 9, wherein the next higher authority is a first next higher authority and the disposition is a first disposition, and further comprising:

communicating the suspect record to a second next higher authority when the first disposition reflects a hold condition;

providing the next higher authority with a second research tool; and

receiving, from the second next higher authority, a second disposition based at least in part on data from the second research tool and reflecting either a block condition, a clear condition, or a hold condition.

11. The method of claim 9, further comprising prompting the next higher authority for more information relating to the disposition.

12. The method of claim 9, further comprising marking the suspect record to reflect the disposition.

13. The method of claim 1, wherein the quick decision code is the selected decision code whenever the datum type designated by the master datum type code is different from datum type of the common datum.

14. The method of claim 1, further comprising providing the reviewer with a set of quick decision data;

and

wherein the quick decision code is the selected decision code whenever the datum type designated by the master datum type code is substantially equivalent to the datum type of the common datum, and the common datum is substantially equivalent to one of the set of quick decision data.

15. The method of claim 1, wherein each of the datum types is an element of a data type set comprising geographic location, individual name, and business name.

16. A system for screening transaction data against a master suspect list and removing false positives, comprising:

a data store configured to store a suspect transaction dataset comprising a suspect record, the suspect record comprising;

a set of data, at least one of the set of data being a common datum which is substantially identical to a master suspect list datum, both the common datum and the master suspect list datum being of a datum type,

a stop designator representing the common datum, and

a common datum type code designating the datum type of the common datum; and

a control processor interfaced with the data store and associated with a computer readable medium, computer readable medium comprising instructions executable by the control processor to;

provide, to a reviewer, a set of decision codes comprising a quick decision code,

prompt the reviewer to select a selected decision code from the set of decision codes to associate with the suspect record, the selection being based at least in part on the stop designator and the common datum type code,

associate the selected decision code with the suspect record, and

prompt the reviewer for further information relating to the removal of false positives and associating the further information with the suspect record.

17. The system of claim 16, wherein the instruction to prompt the reviewer for further information occurs only when the selected decision code is not the quick decision code.

18. A method for screening a transaction dataset against a master suspect list and removing false positives, the method comprising:

screening the transaction dataset against the suspect list using a first computer comprising a first screener and a first set of screening criteria, and generating a suspect transaction dataset, the suspect transaction dataset comprising a set of suspect data, at least a portion of the set of suspect data being false positives;

screening each suspect datum in at least a portion of the suspect transaction dataset using a second screener and a second set of screening criteria, and generating a set of second screen results, each of the set of second screen results representing either a clean or a suspect condition of a respective screened suspect datum;

screening at least a portion of the set of second screen results to remove at least a portion of the set of false positives using a third screener and a third set of screening criteria, and generating a third screen result; and

updating, using a second computer, the first set of screening criteria based at least in part on the third screen result.

19. The method of claim 18, wherein screening at least a portion of the second screen result further comprises:

evaluating for quality at least a portion of the set of second screen results for which the second screen result represents a clean condition;

generating an evaluation result from the evaluating step, the evaluation result reflecting either an accurate second screen result or an inaccurate second screen result; and

sending at least a portion of the set of second screen results to a fourth screener when the evaluation result reflects an inaccurate second screen result.

20. The method of claim 19, wherein the third screener is one of a group of reviewers and the fourth screener is the same one of the group of reviewers.

21. The method of claim 18, wherein screening at least a portion of the second screen result further comprises:

providing the third screener with a research tool;

evaluating, using the research tool, each of the set of second screen results for which the second screen result represents a suspect condition;

generating an evaluation result from the evaluating step, the evaluation result reflecting either a determination condition or a no determination condition; and

sending at least a portion of the set of second screen results to a fourth screener when the evaluation result reflects a no determination condition.

22. The method of claim 21, wherein the third screener is one of a hierarchy of reviewers and the fourth screener is another of the hierarchy of reviewers.

23. The method of claim 18, further comprising updating at least one of the suspect transaction dataset or the suspect list based at least in part on the third screen result.

24. The method of claim 18, further comprising sending, to a report generator, screen result data reflecting at least the third screen result.

25. The method of claim 24, further comprising generating a report based at least in part on the screen result data.

26. The method of claim 18, wherein the second computer is the first computer.

27. A system for screening a transaction dataset against a master suspect list and removing false positives, the system comprising:

a first screening system comprising a first screener, a first set of screening criteria, and a first data store, and configured to;

generate a suspect transaction dataset by screening the transaction dataset against the master suspect list using the first screener and the first set of screening criteria, and

store the suspect transaction dataset to the first data store;

a second screening system, communicatively coupled with the first screening system, comprising a second screener, a second set of screening criteria, and a second data store, and configured to;

screen at least a portion of the suspect transaction dataset using the second screener and the second set of screening criteria,

generate a second screen result, and

store the second screen result to the second data store;

a third screening system, communicatively coupled with the second screening system, comprising a third screener and a third set of screening criteria, and configured to;

screen at least a portion of the second screen result using the third screener and the third set of screening criteria,

generate a third screen result, and

update the first set of screening criteria based at least in part on the third screen result.

28. The system of claim 27, further comprising a report generator configured to generate a report based at least in part on screen result data, the screen result data reflecting at least the third screen result.

29. The system of claim 27, wherein at least one of the first screening system, the second screening system, or the third screening system comprises a person.