# US 2017/0287065 A1 · System and method for identifying related credit inquiries

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0287065 A1
- Document ID: US20170287065A1
- Status: Published application
- Kind: A1
- Application number: 15/434,551
- Filed: 2017-02-16
- Published: 2017-10-05
- Earliest claimed: 2013-03-14
- Assignees: Csidentity Corporation
- Applicants: Csidentity Corporation
- Inventors: Steven E. Samler; Matthew Hall
- Web page: https://patentgrep.com/patent/US20170287065A1

## CPC

- G06Q 40/03: Credit; Loans; Processing thereof
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

In one embodiment, a method includes receiving a credit inquiry for a monitored consumer. The method further includes performing at least one credit-inquiry analysis on the credit inquiry. The performing yields at least one of a matched creditor from master creditor records and an inferred credit category based on a lexical analysis. In addition, the method includes, responsive to the performing, determining whether the credit inquiry is related to a previous credit inquiry for the monitored consumer. Further, the method includes, responsive to a determination that the credit inquiry is related to a previous credit inquiry, suppressing a credit alert to the monitored consumer.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A system comprising:
one or more databases configured to electronic files of consumers and information related to credit inquiries on the credit files of the consumers;
a server computer communicably coupled to the one or more databases, wherein the server computer is programmed to:
access an electronic file of a monitored user to identify a credit event, wherein the electronic file is stored in a data store;
extract, from the electronic file information related to the credit event, the extracted information comprising a name of an initiator of the credit event and at least one other field;
perform name matching using the name of the initiator of the credit event and stored names in master records;
perform token-based matching using the at least one other field and corresponding fields in the master records;
perform a lexical analysis of the name of the initiator of the inquiry event;
determine an agreed-upon multi-module match among the name matching, the token-based matching, and the lexical analysis;
determine, based at least in part on the agreed-upon multi-module match whether there is a related credit event of the monitored user that occurred within a predetermined window of time of the identified credit event; and
responsive to a determination that there is not a related credit event of the monitored user that occurred within a predetermined window of time of the identified credit event, generate and send an alert of the identified credit event to the monitored user.

### Claim 22 (depends on 21)

The system of claim 21, the one or more databases is further configured to store master creditor records which comprise a master name list and a master address list.

### Claim 23 (depends on 22)

The system of claim 22, performing the name matching analysis comprises looking up the name of the initiator from the master name list and returning creditors from the master records whose name matches the name of the initiator.

### Claim 24 (depends on 22)

The system of claim 22, performing the token based matching comprises:
creating a source token set based on an address of the initiator;
creating a target token set based on an address of a creditor in a master address list;
categorizing each token in the source token set and each token in the target set into a plurality of categories;
filtering the source token set and the target token set to remove tokens deemed insignificant;
for each of the source token set and the target token set, combining sequential tokens that have been categorized a same category;
identifying each instance of an exact match between a token of the source token set and a token of the target token set;
removing the token of the source token set from the source token set and removing the token of the target token set from the target token set where the exact match occur; and
detecting a match between the source token set and the target set in response to a determination that the source token set and the target token set are empty.

### Claim 25 (depends on 22)

The system of claim 22, the server computer is further programmed to perform a thesaurus lookup on the name of the initiator to identify a match from the master records.

### Claim 26 (depends on 21)

The system of claim 21, the lexical analysis comprises an n-grams analysis on a sequence of words in the name of the initiator.

### Claim 27 (depends on 21)

The system of claim 21, the server computer is further programmed to: responsive to a determination that there is a related credit event of the monitored user that occurred within the predetermined window of time of the identified credit event, preventing the computer system from generating the alert.

### Claim 28

A method comprising, by a computer system comprising at least one processor and memory:
accessing an electronic file of a monitored user to identify a credit event, wherein the electronic file is stored in a data store;
extracting, from the electronic file information related to the credit event, the extracted information comprising a name of an initiator of the credit event and at least one other field;
performing name matching using the name of the initiator of the credit event and stored names in master records;
performing token-based matching using the at least one other field and corresponding fields in the master records;
performing a lexical analysis of the name of the initiator of the inquiry event;
determining an agreed-upon multi-module match among the name matching, the token-based matching, and the lexical analysis;
determining, based at least in part on the agreed-upon multi-module match whether there is a related credit event of the monitored user that occurred within a predetermined window of time of the identified credit event; and
responsive to a determination that there is not a related credit event of the monitored user that occurred within a predetermined window of time of the identified credit event, generating and sending an alert of the identified credit event to the monitored user.

### Claim 29 (depends on 28)

The method of claim 28, performing the name matching analysis comprises looking up the name of the initiator from the master records and returning creditors from the master records whose name matches the name of the initiator.

### Claim 30 (depends on 28)

The method of claim 28, performing the token-based matching comprises:
creating a source token set based on an address of the initiator;
creating a target token set based on an address of a creditor in a master address list;
categorizing each token in the source token set and each token in the target set into a plurality of categories;
filtering the source token set and the target token set to remove tokens deemed insignificant;
for each of the source token set and the target token set, combining sequential tokens that have been categorized a same category;
identifying each instance of an exact match between a token of the source token set and a token of the target token set;
removing the token of the source token set from the source token set and removing the token of the target token set from the target token set where the exact match occur; and
detecting a match between the source token set and the target set in response to a determination that the source token set and the target token set are empty.

### Claim 31 (depends on 28)

The method of claim 28, further comprising performing a thesaurus lookup on the name of the initiator to identify a match from the master records.

### Claim 32 (depends on 28)

The method of claim 28, the lexical analysis comprises an n-grams analysis on a sequence of words in the name of the initiator.

### Claim 33 (depends on 28)

The method of claim 28, further comprising: responsive to a determination that there is a related credit event of the monitored user that occurred within the predetermined window of time of the identified credit event, preventing the computer system from generating the alert.

### Claim 34

A non-transitory computer readable medium storing software instructions thereon, the software instructions cause a computer system to:
access an electronic file of a monitored user to identify a credit event, wherein the electronic file is stored in a data store;
extract, from the electronic file information related to the credit event, the extracted information comprising a name of an initiator of the credit event and at least one other field;
perform name matching using the name of the initiator of the credit event and stored names in master records;
perform token-based matching using the at least one other field and corresponding fields in the master records;
perform a lexical analysis of the name of the initiator of the inquiry event; determine an agreed-upon multi-module match among the name matching, the token-based matching, and the lexical analysis;
determine, based at least in part on the agreed-upon multi-module match whether there is a related credit event of the monitored user that occurred within a predetermined window of time of the identified credit event; and
responsive to a determination that there is not a related credit event of the monitored user that occurred within a predetermined window of time of the identified credit event, generate and send an alert of the identified credit event to the monitored user.

### Claim 35 (depends on 34)

The non-transitory computer readable medium of claim 34, performing the name matching analysis comprises looking up the name of the initiator from the master records and returning creditors from the master records whose name matches the name of the initiator.

### Claim 36 (depends on 35)

The non-transitory computer readable medium of claim 35, the software instructions further cause the computer system to perform a thesaurus lookup on the name of the initiator to identify a match from the master records.

### Claim 37 (depends on 35)

The non-transitory computer readable medium of claim 35, the master records comprises a master name list and a master address list.

### Claim 38 (depends on 34)

The non-transitory computer readable medium of claim 34, performing the token based matching comprises:
creating a source token set based on an address of the initiator;
creating a target token set based on an address of a creditor in a master address list;
categorizing each token in the source token set and each token in the target set into a plurality of categories;
filtering the source token set and the target token set to remove tokens deemed insignificant;
for each of the source token set and the target token set, combining sequential tokens that have been categorized a same category;
identifying each instance of an exact match between a token of the source token set and a token of the target token set;
removing the token of the source token set from the source token set and removing the token of the target token set from the target token set where the exact match occur; and
detecting a match between the source token set and the target set in response to a determination that the source token set and the target token set are empty.

### Claim 39 (depends on 34)

The non-transitory computer readable medium of claim 34, the lexical analysis comprises an n-grams analysis on a sequence of words in the name of the initiator.

### Claim 40 (depends on 34)

The non-transitory computer readable medium of claim 34, the software instructions further cause the computer system to: responsive to a determination that there is a related credit event of the monitored user that occurred within the predetermined window of time of the identified credit event, prevent the computer system from generating the alert.
