ANALYSIS OF E-RECEIPTS TO DETERMINE POSSIBLE EXCEPTIONS

• US 20160019657A1
• Filed: 07/17/2014
• Published: 01/21/2016
• Est. Priority Date: 07/17/2014
• Status: Abandoned Application

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Mande, Christian Michael
• Application Number:
  US14/333,646
• Publication Number:
  US 20160019657A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

Disclosed is an aggregation computing system and associated method for determining exceptions in purchase level data and online banking data. The system typically includes an online banking database that has online banking data associated with a first customer account, the online banking data including first transaction information associated with a first transaction. The aggregation computing system also typically includes an aggregation module that is configured for: receiving second transaction information associated with a second transaction by a customer using the first customer account, the second transaction information comprising purchase level data; comparing the second transaction information with the online banking data associated with the first customer account; based on comparing the second transaction information with the online banking data, identifying an exception; and graphically presenting within an online banking interface an indication of the exception.

Claims

1. An aggregation computing system for determining exceptions in purchase level data and online banking data, comprising:

a computer apparatus including a processor and a memory;

an online banking database stored in the memory, the online banking database comprising online banking data associated with a first customer account, the online banking data comprising first transaction information associated with a first transaction; and

an aggregation module stored in the memory, executable by the processor and configured for;

receiving second transaction information associated with a second transaction by a customer using the first customer account, the second transaction information comprising purchase level data;

comparing the second transaction information with the online banking data associated with the first customer account;

based on comparing the second transaction information with the online banking data, identifying an exception; and

graphically presenting within an online banking interface an indication of the exception.

2. The aggregation computing system according to claim 1, wherein:

the aggregation module is configured for, based on comparing the second transaction information with the online banking data, determining that the second transaction and the first transaction are the same transaction and associating the second transaction with the first customer account; and

identifying the exception comprises determining that a discrepancy exists between the first transaction information and the second transaction information.

3. The aggregation computing system according to claim 2, wherein determining that the discrepancy exists between the first transaction information and the second transaction information comprises determining that a first transaction total included in the first transaction information differs from a second transaction total included in the second transaction information.

4. The aggregation computing system according to claim 1, wherein identifying the exception comprises determining that the online banking database does not possess purchase level data associated with the first transaction.

5. The aggregation computing system according to claim 1, wherein:

the second transaction information comprises information regarding a merchant associated with the second transaction; and

identifying the exception comprises determining that the merchant is not associated with a previous transaction associated with the first customer account.

6. The aggregation computing system according to claim 1, wherein:

the second transaction information comprises information regarding a merchant location associated with the second transaction; and

identifying the exception comprises determining that the merchant location is not associated with a previous transaction associated with the first customer account.

7. A computer program product for determining exceptions in purchase level data and online banking data, comprising a non-transitory computer-readable storage medium having computer-executable instructions for:

receiving second transaction information associated with a second transaction by a customer using the first customer account, the second transaction information comprising purchase level data;

comparing the second transaction information with online banking data associated with the first customer account, the online banking data being included in an online banking database, the online banking data comprising first transaction information associated with a first transaction;

based on comparing the second transaction information with the online banking data, identifying an exception; and

graphically presenting within an online banking interface an indication of the exception.

8. The computer program product according to claim 7, wherein:

the non-transitory computer-readable storage medium has computer-executable instructions for, based on comparing the second transaction information with the online banking data, determining that the second transaction and the first transaction are the same transaction and associating the second transaction with the first customer account; and

identifying the exception comprises determining that a discrepancy exists between the first transaction information and the second transaction information.

9. The computer program product according to claim 8, wherein determining that the discrepancy exists between the first transaction information and the second transaction information comprises determining that a first transaction total included in the first transaction information differs from a second transaction total included in the second transaction information.

10. The computer program product according to claim 7, wherein identifying the exception comprises determining that the online banking database does not possess purchase level data associated with the first transaction.

11. The computer program product according to claim 7, wherein:

the second transaction information comprises information regarding a merchant associated with the second transaction; and

identifying the exception comprises determining that the merchant is not associated with a previous transaction associated with the first customer account.

12. The computer program product according to claim 7, wherein:

the second transaction information comprises information regarding a merchant location associated with the second transaction; and

identifying the exception comprises determining that the merchant location is not associated with a previous transaction associated with the first customer account.

13. A method for determining exceptions in purchase level data and online banking data, comprising:

receiving, via a computer processor, second transaction information associated with a second transaction by a customer using the first customer account, the second transaction information comprising purchase level data;

comparing, via a computer processor, the second transaction information with online banking data associated with the first customer account, the online banking data being included in an online banking database, the online banking data comprising first transaction information associated with a first transaction;

based on comparing the second transaction information with the online banking data, identifying, via a computer processor, an exception; and

graphically presenting, via a computer processor, within an online banking interface an indication of the exception.

14. The method according to claim 13, comprising, based on comparing the second transaction information with the online banking data, determining that the second transaction and the first transaction are the same transaction and associating the second transaction with the first customer account;

wherein identifying the exception comprises determining that a discrepancy exists between the first transaction information and the second transaction information.

15. The method according to claim 14, wherein determining that the discrepancy exists between the first transaction information and the second transaction information comprises determining that a first transaction total included in the first transaction information differs from a second transaction total included in the second transaction information.

16. The method according to claim 13, wherein identifying the exception comprises determining that the online banking database does not possess purchase level data associated with the first transaction.

17. The method according to claim 13, wherein:

the second transaction information comprises information regarding a merchant associated with the second transaction; and

identifying the exception comprises determining that the merchant is not associated with a previous transaction associated with the first customer account.

18. The method according to claim 13, wherein:

the second transaction information comprises information regarding a merchant location associated with the second transaction; and

identifying the exception comprises determining that the merchant location is not associated with a previous transaction associated with the first customer account.