DYNAMIC DATA NORMALIZATION AND DUPLICATE ANALYSIS

• US 20170178246A1
• Filed: 12/04/2016
• Published: 06/22/2017
• Est. Priority Date: 12/17/2015
• Status: Abandoned Application

• Current Assignee: SpringAhead, Inc.
• Original Assignee: SpringAhead, Inc.
• Inventors: Austen, Tyler, Van Heusen, Kevin, Milligan, Claire, Farrell, Christopher, Milbourne, Mark
• Application Number:
  US15/368,616
• Publication Number:
  US 20170178246A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

Methods and apparatuses for dynamic data normalization and duplicate analysis include normalizing data (e.g., merchant identifier data) received from a source entity (e.g., transaction card provider), as well as identifying and resolving potential duplicate transaction data objects based on one or more transaction characteristics. For example, data normalization includes partitioning an identifier into one or more merchant identifier portions, sending a merchant identifier request to a merchant database, and receiving a set of merchant representation candidates in response to sending the merchant identifier request. Further, for instance, duplicate analysis includes determining whether a transaction data object from the first set of transaction data objects that falls within the overlapping portion is not present in the second set of transaction data objects, and identifying the transaction data object within the second set of transaction data objects and the one or more non-overlapping portions.

Claims

1. A method of resolving one or more expense records at a network entity, comprising:

receiving, at the network entity, a set of transaction data objects including a first transaction data object from one or more first transaction sources, wherein each transaction data object of the set of transaction data objects includes one or more transaction characteristics;

determining, at the network entity, whether one or more transaction characteristics of the first transaction data object matches one or more transaction characteristics of a second transaction data object stored in a database of the network entity and received from one or more second transaction sources;

in accordance with a determination that one or more transaction characteristics of the first transaction data object matches one or more transaction characteristics of the second transaction data object, adjusting one or more properties of a first expense record associated with the second transaction data object according to the one or more transaction characteristics of the first transaction data object; and

in accordance with a determination that one or more transaction characteristics of the first transaction data object does not match one or more transaction characteristics of the second transaction data object, generating a second expense record associated with the first transaction data obj ect.

2. The method of claim 1, wherein the one or more transaction characteristics of the first transaction data object corresponds to one or both of a first date or a first time value of a transaction occurrence associated with the first transaction data object and the one or more transaction characteristics of the second transaction data object corresponds to one or both of a second date or a second time value of a transaction occurrence associated with the second transaction data object.

3. The method of claim 2, wherein one or both of the first date or the first time value of the first transaction data object is distinct from one or both of the second date or the second time value of the second transaction data object.

4. The method of claim 2, wherein adjusting one or more properties of the first record associated with the second transaction data object according to the one or more transaction characteristics of the first transaction data object includes adjusting one or both of a date characteristic or a time characteristic of the transaction record according to a date characteristic or a time characteristic of the first transaction data object.

5. The method of claim 1, wherein the one or more properties of the first expense record includes a transaction data object association corresponding to a link between the first expense record and a transaction data object, and wherein adjusting the one or more properties of the first expense record associated with the second transaction data object according to the one or more transaction characteristics of the first transaction data object includes adjusting a transaction data object association of the first expense record from the second transaction data object to the first transaction data object.

6. The method of claim 1, wherein the one or more transaction characteristics of the first transaction data object corresponds to a first aggregation entity and the one or more transaction characteristics of the second transaction data object corresponds to a second aggregation entity.

7. The method of claim 1, wherein determining whether one or more transaction characteristics of the first transaction data object matches one or more transaction characteristics of the second transaction data object includes:

determining that the second transaction data object is not detected within a portion of the set of transaction data objects; and

identifying the first transaction data object as similar to the second transaction data object based on the one or more transaction characteristics.

8. The method of claim 1, wherein the one or more transaction characteristics of the first transaction data object corresponds to a first merchant characteristic representing a posted transaction and the one or more transaction characteristics of the second transaction data object corresponds to a second merchant characteristic different from the first merchant characteristic and representing a pending transaction.

9. The method of claim 1, wherein receiving the set of transaction data objects from the one or more transaction sources includes receiving a first portion of the set of transaction data objects from one of the one or more first transaction sources and a second portion of the set of transaction data objects from another one of the one or more transaction sources.

10. The method of claim 1, wherein the second transaction data object represents a pending transaction associated with a transaction card account and the first transaction data object represents a posted transaction associated with the transaction card account.

11. The method of claim 1, wherein the set of transaction data objects is associated with a transaction card account.

12. The method of claim 1, wherein each transaction data object from the set of the transaction data objects is associated with a credit or debit card transaction.

13. A computer-readable storage medium comprising one or more programs for execution by one or more processors of an electronic device, the one or more programs including instructions which, when executed by the one or more processors, cause the electronic device to:

receive a set of transaction data objects including a first transaction data object from one or more first transaction sources, wherein each transaction data object of the set of transaction data objects includes one or more transaction characteristics;

determine whether one or more transaction characteristics of the first transaction data object matches one or more transaction characteristics of a second transaction data object stored in a database of the network entity and received from one or more second transaction sources;

in accordance with a determination that one or more transaction characteristics of the first transaction data object matches one or more transaction characteristics of the second transaction data object, adjust one or more properties of a first expense record associated with the second transaction data object according to the one or more transaction characteristics of the first transaction data object; and

in accordance with a determination that one or more transaction characteristics of the first transaction data object does not match one or more transaction characteristics of the second transaction data object, generate a second expense record associated with the first transaction data obj ect.

14. The computer-readable storage medium of claim 13, wherein the one or more transaction characteristics of the first transaction data object corresponds to one or both of a first date or a first time value of a transaction occurrence associated with the first transaction data object and the one or more transaction characteristics of the second transaction data object corresponds to one or both of a second date or a second time value of a transaction occurrence associated with the second transaction data object.

15. An apparatus for resolving one or more expense records, comprising:

a memory configured to store data; and

at least one processor communicatively coupled to the memory, wherein the at least one processor is configured to;

receive a set of transaction data objects including a first transaction data object from one or more first transaction sources, wherein each transaction data object of the set of transaction data objects includes one or more transaction characteristics;

determine whether one or more transaction characteristics of the first transaction data object matches one or more transaction characteristics of a second transaction data object stored in a database of the network entity and received from one or more second transaction sources;

in accordance with a determination that one or more transaction characteristics of the first transaction data object matches one or more transaction characteristics of the second transaction data object, adjust one or more properties of a first expense record associated with the second transaction data object according to the one or more transaction characteristics of the first transaction data object; and

in accordance with a determination that one or more transaction characteristics of the first transaction data object does not match one or more transaction characteristics of the second transaction data object, generate a second expense record associated with the first transaction data obj ect.

16. The apparatus of claim 15, wherein the one or more transaction characteristics of the first transaction data object corresponds to one or both of a first date or a first time value of a transaction occurrence associated with the first transaction data object and the one or more transaction characteristics of the second transaction data object corresponds to one or both of a second date or a second time value of a transaction occurrence associated with the second transaction data object.

17. The apparatus of claim 16, wherein one or both of the first date or the first time value of the first transaction data object is distinct from one or both of the second date or the second time value of the second transaction data object.

18. The apparatus of claim 16, wherein to adjust one or more properties of the first expense record associated with the second transaction data object according to the one or more transaction characteristics of the first transaction data object, the at least one processor is further configured to adjust one or both of a date characteristic or a time characteristic of the transaction record according to a date characteristic or a time characteristic of the first transaction data object.

19. The apparatus of claim 15, wherein to adjust the one or more properties of the first expense record associated with the second transaction data object according to the one or more transaction characteristics of the first transaction data object, the at least one processor is further configured to adjust a transaction data object association of the first expense record from the second transaction data object to the first transaction data object.

20. The apparatus of claim 15, wherein the one or more transaction characteristics of the first transaction data object corresponds to a first aggregation entity and the one or more transaction characteristics of the second transaction data object corresponds to a second aggregation entity.