DYNAMIC DATA NORMALIZATION AND DUPLICATE ANALYSIS

• US 20170178247A1
• 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: Farrell, Christopher, Milbourne, Mark, Austen, Tyler, Van Heusen, Kevin, Milligan, Claire
• Application Number:
  US15/368,617
• Publication Number:
  US 20170178247A1
• 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 an expense record, comprising:

receiving, at a network entity within a network, a first set of transaction data objects associated with a first transaction window;

receiving, at the network entity, a second set of transaction data objects associated with a second transaction window that overlaps at least a portion of the first transaction window;

determining, at the network entity, 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;

in accordance with a determination that the transaction data object from the first set of transaction data objects that falls within the overlapping portion is present in the second set of transaction data objects, transmitting the first transaction data object to an entity within the network; and

adjusting one or more properties of the expense record associated with the transaction data object of the first set of transaction data objects based on one or more distinct characteristics of the transaction data object of the second set of transaction data objects.

2. The method of claim 1, further comprising:

in accordance with a determination that the 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, determining one or more non-overlapping portions of the first transaction window and the second transaction window; and

identifying, at the network entity, the transaction data object within the one or more non-overlapping portions of the second set of transaction data objects.

3. The method of claim 1, wherein adjusting the one or more properties of the expense record associated with the transaction data object of the first set of transaction data objects include adjusting one or both of a date characteristic or a time characteristic of the expense record according to a date characteristic or a time characteristic of the transaction data object of the second set of transaction data objects.

4. The method of claim 3, wherein the date characteristic and the time characteristic are each distinct from a date characteristic and a time characteristic each associated with the transaction data object of the first set of transaction data objects.

5. The method of claim 1, wherein adjusting the one or more properties of the expense record associated with the transaction data object of the first set of transaction data objects includes adjusting an association of the expense record from the transaction data object of the first set of transaction data objects to the transaction data object of the second set of transaction data objects.

6. The method of claim 1, wherein the first transaction window includes a first transaction window date and a second transaction window date later than the first transaction window date.

7. The method of claim 6, wherein the second transaction window includes a third transaction window date prior to the first transaction window date of the first transaction window and a fourth transaction window date after the first transaction window date and prior to the second transaction window date of the first transaction window.

8. The method of claim 7, wherein the overlapping portion is between the third transaction window date and the second transaction window date.

9. The method of claim 1, wherein the transaction data object is associated with a source characteristic corresponding to one or both of a transaction processor or a location of an underlying transaction of the transaction data object.

10. The method of claim 9, wherein determining whether the 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 includes determining based on one or more source characteristics associated with the transaction data object.

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

12. The method of claim 1, wherein the first set of transaction data objects and the second set of transaction data objects are associated with a single transaction card account.

13. The method of claim 1, wherein each transaction data object of the first set of the transaction data objects and the second set of transaction data objects is associated with a credit or debit card transaction.

14. The method of claim 1, wherein the second transaction window overlaps at least the portion of the first transaction window in a time domain.

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

receive, at a network entity within a network, a first set of transaction data objects associated with a first transaction window;

receive, at the network entity, a second set of transaction data objects associated with a second transaction window that overlaps at least a portion of the first transaction window;

determine, at the network entity, 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;

in accordance with a determination that the transaction data object from the first set of transaction data objects that falls within the overlapping portion is present in the second set of transaction data objects, transmit the first transaction data object to an entity within the network; and

adjust one or more properties of the expense record associated with the transaction data object of the first set of transaction data objects based on one or more distinct characteristics of the transaction data object of the second set of transaction data objects.

16. An apparatus for resolving an expense record, comprising:

a memory configured to store data; and

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

receive, at a network entity within a network, a first set of transaction data objects associated with a first transaction window;

receive, at the network entity, a second set of transaction data objects associated with a second transaction window that overlaps at least a portion of the first transaction window;

determine, at the network entity, 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;

in accordance with a determination that the transaction data object from the first set of transaction data objects that falls within the overlapping portion is present in the second set of transaction data objects, transmit the first transaction data object to an entity within the network; and

adjust one or more properties of an expense record associated with the transaction data object of the first set of transaction data objects based on one or more distinct characteristics of the transaction data object of the second set of transaction data objects.

17. The apparatus of claim 16, where the at least one processor is further configured to:

in accordance with a determination that the 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, determine one or more non-overlapping portions of the first transaction window and the second transaction window; and

identify, at the network entity, the transaction data object within the one or more non-overlapping portions of the second set of transaction data objects and the one or more non-overlapping portions.

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

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

20. The apparatus of claim 16, wherein the first transaction window includes a first transaction window date and a second transaction window date later than the first transaction window date.