AUTOMATED CASH RECONCILIATION AND REPORTING SYSTEM AND METHOD

• US 20120323747A1
• Filed: 06/17/2011
• Published: 12/20/2012
• Est. Priority Date: 06/17/2011
• Status: Abandoned Application

• Current Assignee: The Bank of New York Mellon (Bank of New York Mellon Corporation)
• Original Assignee: The Bank of New York Mellon (Bank of New York Mellon Corporation)
• Inventors: KANTIKOVIT, Tohm Lim, AHMED, Zeeshan Iftikhar, MOORE, Neil Gavin, DABBIRU, Rajendra
• Application Number:
  US13/163,039
• Publication Number:
  US 20120323747A1
• Time in Patent Office: Days
• US Class Current: 705/30
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

A system for reconciling financial data is configured to retrieve first and second financial data from respective data sources. The first and second financial data each contains one or more respective records, each containing a respective name, date, and monetary amount. The system attempts to match one of the first records with one of the second records, initially based on general equivalence of the names, dates, and the first and second monetary amounts. If any of the records remain unmatched, the system is configured to attempt to match two or more of the second records with one of the first records, utilizing the sum of the second monetary amounts, and attempt to match two or more of the first records with one of the second records based on the sum of the first monetary amounts.

Claims

1. A system for reconciling financial transactions, the system comprising:

one or more processors configured to;

retrieve first financial data from a first data source, the first financial data containing one or more first records, each containing at least a first name, a first date, and a first monetary amount;

retrieve second financial data from a second data source, the second financial data containing one or more second records, each containing at least a second name, a second date, and a second monetary amount;

attempt to match one of the first records with one of the second records based on (i) equivalence of the first name, or a possible alias of the first name, and the second name, (ii) equivalence within tolerance of the first date and the second date, and (iii) equivalence within tolerance of the first monetary amount and the second monetary amount;

responsive to any of the first records and the second records remaining unmatched, attempt to match two or more of the second records with one of the first records based on (i) equivalence of the first name, and/or possible aliases of the first name, and the second names, (ii) equivalence within tolerance of the first date and the second dates, and (iii) equivalence within tolerance the first monetary amount and a sum of the second monetary amounts; and

responsive to any of the first records and the second records remaining unmatched, attempt to match two or more of the first records with one of the second records based on (i) equivalence of the first names and the second name, (ii) equivalence within tolerance of the first dates and the second date, and (iii) equivalence within tolerance of the sum of the first monetary amounts and the second monetary amount.

2. The system of claim 1, wherein the tolerance of the equivalence within tolerance of the first date(s) and the second date(s) is definable by a user input.

3. The system of claim 1, wherein the tolerance of the equivalence within tolerance of the first monetary amount(s) and the second monetary amount(s) is definable by a user input.

4. The system of claim 1, wherein the one or more processors are further configured to execute an exception process responsive to any of the first and second records remaining unmatched after attempting to match two or more of the first records with one of the second records, wherein the exception process comprises:

displaying unmatched ones of the first and second records; and

receiving user-input designating matches between one or more of the first records and one or more of the second records.

5. The system of claim 4, wherein the possible aliases of the first name are selected from aliases of the second name.

6. The system of claim 5, wherein the exception process further comprises associating the first name as an alias of the second name for the user-input designated match between the one or more of the first records and the one or more of the second records.

7. The system of claim 1, wherein the first financial data and the second financial data are selected from a user-defined date range of financial transactions associated with the first data source and the second data source.

8. The system of claim 1, wherein the first financial data comprises data associated with completed financial transactions, and the second financial data comprises data associated with expected financial transactions.

9. The system of claim 1, wherein the one or more processors are further configured to generate a report based on matched ones of the one or more first records and the one or more second records.

10. The system of claim 1, further comprising a user interface operatively coupled to the one or more processors via a network connection.

11. The system of claim 10, wherein the user interface comprises an Internet web portal.

12. A computer-implemented method for reconciling financial transactions, the method comprising:

retrieving, via one or more processors, first financial data from a first data source, the first financial data containing one or more first records, each containing at least a first name, a first date, and a first monetary amount;

retrieving, via the one or more processors, second financial data from a second data source, the second financial data containing one or more second records, each containing at least a second name, a second date, and a second monetary amount;

attempting to match one of the first records with one of the second records based on (i) equivalence of the first name, or an alias of the first name, and the second name, (ii) equivalence within tolerance of the first date and the second date, and (iii) equivalence within tolerance of the first monetary amount and the second monetary amount;

responsive to any of the first records and the second records remaining unmatched, attempting to match two or more of the second records with one of the first records based on (i) equivalence of the first name, and/or aliases of the first name, and the second names, (ii) equivalence within tolerance of the first date and the second dates, and (iii) equivalence within tolerance the first monetary amount and a sum of the second monetary amounts; and

responsive to any of the first records and the second records remaining unmatched, attempting to match two or more of the first records with one of the second records based on (i) equivalence of the first names and the second name, (ii) equivalence within tolerance of the first dates and the second date, and (iii) equivalence within tolerance of the sum of the first monetary amounts and the second monetary amount.

13. The method of claim 12, further comprising receiving, via a user input, the tolerance of the equivalence within tolerance of the first date(s) and the second date(s).

14. The method of claim 12, further comprising receiving, via a user input, the tolerance of the equivalence within tolerance of the first monetary amount(s) and the second monetary amount(s).

15. The method of claim 12, further comprising executing an exception process responsive to any of the first and second records remaining unmatched after attempting to match two or more of the first records with one of the second records, wherein the exception process comprises:

displaying unmatched ones of the first and second records; and

receiving user-input designating matches between one or more of the first records and one or more of the second records.

16. The method of claim 15, wherein the possible aliases of the first name are selected from aliases of the second name.

17. The method of claim 16, wherein the exception process further comprises associating the first name as an alias of the second name for the received user-input designated match between the one or more of the first records and the one or more of the second records.

18. The method of claim 12, wherein the first financial data and the second financial data are selected from a user-defined date range of financial transactions associated with the first data source and the second data source.

19. The method of claim 12, wherein the first financial data comprises data associated with completed financial transactions, and the second financial data comprises data associated with expected financial transactions.

20. The method of claim 12, further comprising generating a report based on matched ones of the one or more first records and the one or more second records.