Automated financial register reconciliation in a combined user interface

• US 7,240,028 B1
• Filed: 03/15/2002
• Issued: 07/03/2007
• Est. Priority Date: 03/15/2002
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Rugge, Robert D.
• Primary Examiner(s): RUDY, ANDREW J
• Application Number:
  US10/097,602
• Time in Patent Office: 1,936 Days
• Field of Search: 705/30, 707/10, 717/100
• US Class Current: 705/30
• 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

Unreconciled information regarding financial account transactions is received from multiple sources. Transactions identified in the information received from one of the sources are classified according to the probability of matching a transaction identified in information received from another source. Transactions identified in both sources are displayed in a common user interface, together with account balances adjusted for those transactions. The user is able to accept the classification, and as to at least some classes of transactions, change the classification or the matching transaction. The unaccepted transactions may be rendered so as to indicate their unaccepted state.

Claims

1. A computer-implemented method of presenting information about financial account transactions based upon data received from a first source describing a first group of transactions and data received from a second source describing a second group of transactions, the method comprising:

receiving in the computer the data from the first source;

displaying information about the first-group transactions in a graphical user interface, wherein the graphical user interface is presented on a display device connected to the computer and is a tabularly formatted display of the first-group transactions;

receiving in the computer the data from the second source, wherein the second-group transactions have not been reconciled with regard to the first-group transactions, and wherein at least one first-group transaction and at least one second-group transaction are the same transaction;

displaying in the graphical user interface, without a separate user instruction to do so, information about the second-group transactions commingled with information about the first-group transactions;

classifying the second-group transactions based on probability of matching one of the first-group transactions, wherein the classifying is performed by the computer and without a separate user instruction to do so, and wherein said classifying further includes

classifying a second-group transaction as a guaranteed match transaction if the data describing that second-group transaction sufficiently correlates with the data describing a matched first-group transaction so as to ensure that the guaranteed match transaction and the matched first-group transaction are the same,

classifying a second-group transaction as a probable match transaction if the data describing that second-group transaction does not sufficiently correlate with the data describing any of the first-group transactions to qualify that second-group transaction as a guaranteed match transaction, but does sufficiently correlate with the data describing a probably-matched first-group transaction to indicate that the probable match transaction and the probably-matched first-group transaction have a designated probability of being the same, and

classifying a second-group transaction as a probable new transaction if the data describing that second-group transaction does not sufficiently correlate with the data describing any of the first-group transactions to qualify that second-group transaction as a guaranteed match transaction or a probable match transaction;

calculating an account balance based on the first-group transactions and the second-group transactions without a separate user instruction to do so, wherein

the calculating is performed by the computer, and

as to each probable match transaction, the account balance is calculated based on the amount of only one of the probable match transaction and the corresponding probably-matched first-group transaction; and

displaying the account balance in the graphical user interface.

2. The method of claim 1, further comprising:

providing the user an opportunity to acknowledge a guaranteed match transaction; and

displaying the guaranteed match transaction, if acknowledged, in the same manner as a first-group transaction.

3. The method of claim 2, further comprising:

providing an opportunity to accept a probable match transaction;

displaying, if accepted, the probable match transaction in the same manner as a first-group transaction;

providing, if the probable match transaction is not accepted, an opportunity to select an alternate first-group transaction as a matching transaction;

merging, if an alternate first-group transaction is selected as a matching transaction, the probable match transaction with the alternate transaction, recalculating the account balance based on the merger, and displaying the merged transaction in the same manner as a first-group transaction; and

reclassifying, if an alternate transaction is not selected as a matching transaction, the probable match transaction as a new transaction, recalculating the account balance based on the reclassification, and displaying the reclassified transaction in the same manner as a first-group transaction.

4. The method of claim 3, further comprising:

providing an opportunity to accept a probable new transaction;

displaying, if accepted, the probable new transaction in the same manner as a first-group transaction;

providing, if the probable new transaction is not accepted, an opportunity to select a matching transaction; and

merging, if a matching transaction is selected, the selected matching transition with the probable new transaction, recalculating the account balance based on the merger, and displaying the merged transaction in the same manner as a first-group transaction.

5. The method of claim 4, further comprising:

receiving additional data from the second source describing additional second-group transactions before each second-group transaction described by previously-received second source data has been accepted, merged or reclassified;

classifying the additional second-group transactions;

recalculating the account balance based on the additional second-group transactions and displaying the recalculated account balance; and

displaying in the graphical user interface, without a separate user instruction to do so and commingled with information about the first-group transactions, information about the additional second-group transactions.

6. The method of claim 5, wherein second source data is periodically downloaded over a data communication network on a background program thread.

7. The method of claim 4, further comprising,

categorizing the first-group and the second-group transactions, wherein the categorizing is performed by the computer;

establishing a budgetary limit for at least one transaction category;

calculating an effect upon the budgetary limit caused by second-group transactions that are within the at least one category, wherein the calculating an effect is performed by the computer and without a separate user instruction to do so; and

recalculating the effect upon the budgetary limit upon a user selecting an alternate transaction as a matching transaction, upon a user selecting a matching transaction for a probable new transaction, or upon a probable match transaction being classified as a probable new transaction, wherein the step of recalculating the effect is performed by the computer.

8. A computer-readable medium having computer-executable instructions for performing steps of a computer-implemented method of presenting information about financial account transactions based upon data received from a first source describing a first group of transactions and data received from a second source describing a second group of transactions, the steps comprising:

receiving in the computer the data from the first source;

displaying information about the first-group transactions in a graphical user interface, wherein the graphical user interface is presented on a display device connected to the computer and is a tabularly formatted display of the first-group transactions;

receiving in the computer the data from the second source, wherein the second-group transactions have not been reconciled with regard to the first-group transactions, and wherein at least one first-group transaction and at least one second-group transaction are the same transaction;

displaying in the graphical user interface, without a separate user instruction to do so, information about the second-group transactions commingled with information about the first-group transactions;

classifying the second-group transactions based on probability of matching one of the first-group transactions, wherein the classifying is performed by the computer and without a separate user instruction to do so, and wherein said classifying further includes

classifying a second-group transaction as a guaranteed match transaction if the data describing that second-group transaction sufficiently correlates with the data describing a matched first-group transaction so as to ensure that the guaranteed match transaction and the matched first-group transaction are the same,

classifying a second-group transaction as a probable match transaction if the data describing that second-group transaction does not sufficiently correlate with the data describing any of the first-group transactions to qualify that second-group transaction as a guaranteed match transaction, but does sufficiently correlate with the data describing a probably-matched first-group transaction to indicate that the probable match transaction and the probably-matched first-group transaction have a designated probability of being the same, and

classifying a second-group transaction as a probable new transaction if the data describing that second-group transaction does not sufficiently correlate with the data describing any of the first-group transactions to qualify that second-group transaction as a guaranteed match transaction or a probable match transaction;

calculating an account balance based on the first-group transactions and the second-group transactions without a separate user instruction to do so, wherein

the calculating is performed by the computer, and

as to each probable match transaction, the account balance is calculated based on the amount of only one of the probable match transaction and the corresponding probably-matched first-group transaction; and

displaying the account balance is the graphical user interface.

9. The computer-readable medium of claim 8 having further computer-executable instructions for performing the further steps of:

providing the user an opportunity to acknowledge a guaranteed match transaction; and

displaying the guaranteed match transaction, if acknowledged, in the same manner as a first-group transaction.

10. The computer-readable medium of claim 9 having further computer-executable instructions for performing the further steps of:

providing an opportunity to accept a probable match transaction;

displaying, if accepted, the probable match transaction in the same manner as a first-group transaction;

providing, if the probable match transaction is not accepted, an opportunity to select an alternate first-group transaction as a matching transaction;

merging, if an alternate first-group transaction is selected as a matching transaction, the probable match transaction with the alternate transaction, recalculating the account balance based on the merger, and displaying the merged transaction in the same manner as a first-group transaction; and

reclassifying, if an alternate transaction is not selected as a matching transaction, the probable match transaction as a new transaction, recalculating the account balance based on the reclassification, and displaying the reclassified transaction in the same manner as a first-group transaction.

11. The computer-readable medium of claim 10 having further computer-executable instructions for performing the further steps of:

providing an opportunity to accept a probable new transaction;

displaying, if accepted, the probable new transaction in the same manner as a first-group transaction;

providing, if the probable new transaction is not accepted, an opportunity to select a matching transaction; and

merging, if a matching transaction is selected, the selected matching transaction with the probable new transaction, recalculating the account balance based on the merger, and displaying the merged transaction in the same manner as a first-group transaction.

12. The computer-readable medium of claim 11 having further computer-executable instructions for performing the further steps of:

receiving additional data from the second source describing additional second-group transactions before each second-group transaction described by previously-received second source data has been accepted, merged or reclassified;

classifying the additional second-group transactions;

recalculating the account balance based on the additional second-group transactions and displaying the recalculated account balance; and

displaying in the graphical user interface, without a separate user instruction to do so and commingled with information about the first-group transactions, information about the additional second-group transactions.

13. The computer-readable medium of claim 12 wherein second source data is periodically downloaded over a data communication network on a background program thread.

14. The computer-readable medium of claim 11 having further computer-executable instructions for performing the further steps of:

categorizing the first-group and the second-group transactions, wherein the categorizing is performed by the computer;

establishing a budgetary limit for at least one transaction category;

calculating an effect upon the budgetary limit caused by second-group transactions that are within the at least one category, wherein the calculating an effect is performed by the computer and without a separate user instruction to do so; and

recalculating the effect upon the budgetary limit upon a user selecting an alternate transaction as a matching transaction, upon a user selecting a matching transaction for a probable new transaction, or upon a probable match transaction being classified as a probable new transaction, wherein the step of recalculating the effect is performed by the computer.

15. A system for presenting information about financial account transactions based upon data received from multiple sources, comprising:

a display;

a memory; and

a processor in communication with the display and memory, and configured to perform steps of a method of presenting information about financial account transactions based upon data received from a first source describing a first group of transactions and data received from a second source describing a second group of transactions, the steps including

receiving the data from the first source,

displaying information about the first-group transactions in a graphical user interface, wherein the graphical user interface is presented on the display and is a tabularly formatted display of the first-group transactions,

receiving the data from the second source, wherein the second-group transactions have not been reconciled with regard to the first-group transactions, and wherein at least one first-group transaction and at least one second-group transaction are the same transaction,

displaying in the graphical user interface, without a separate user instruction to do so, information about the second-group transactions commingled with information about the first-group transactions,

classifying the second-group transactions based on probability of matching one of the first-group transactions, wherein the classifying is performed without a separate user instruction to do so, and wherein said classifying further includes

classifying a second-group transaction as a guaranteed match transaction if the data describing that second-group transaction sufficiently correlates with the data describing a matched first-group transaction so as to ensure that the guaranteed match transaction and the matched first-group transaction are the same,

classifying a second-group transaction as a probable match transaction if the data describing that second-group transaction does not sufficiently correlate with the data describing any of the first-group transactions to qualify that second-group transaction as a guaranteed match transaction, but does sufficiently correlate with the data describing a probably-matched first-group transaction to indicate that the probable match transaction and the probably-matched first-group transaction have a designated probability of being the same, and

classifying a second-group transaction as a probable new transaction if the data describing that second-group transaction does not sufficiently correlate with the data describing any of the first-group transactions to qualify that second-group transaction as a guaranteed match transaction or a probable match transaction,

calculating an account balance based on the first-group transactions and the second-group transactions without a separate user instruction to do so wherein, as to each probable match transaction, the account balance is calculated based on the amount of only one of the probable match transaction and the corresponding probably-matched first-group transaction, and

displaying the account balance in the graphical user interface.

16. The system of claim 15 wherein the processor is further configured to:

provide the user an opportunity to acknowledge a guaranteed match transaction, and

display the guaranteed match transaction, if acknowledged, in the same manner as a first-group transaction.

17. The system of claim 16 wherein the processor is further configured to:

provide an opportunity to accept a probable match transaction,

display the probable match transaction, if accepted, in the same manner as a first-group transaction,

provide, if the probable matching transaction is not accepted, an opportunity to select an alternate first-group transaction as a matching transaction,

merge, if an alternate first-group transaction is selected as a matching transaction, the probable match transaction with the alternate transaction, recalculate the account balance based on the merger, and display the merged transaction in the same manner as a first-group transaction, and

reclassify, if an alternate transaction is not selected as a matching transaction, the probable match transaction as a new transaction, recalculate the account balance based on the reclassification, and display the reclassified transaction in the same manner as a first-group transaction.

18. The system of claim 17 wherein the processor is further configured to:

provide an opportunity to accept a probable new transaction,

display the probable new transaction, if accepted, in the same manner as a first-group transaction,

provide, if the probable new transaction is not accepted, an opportunity to select a matching transaction, and

merge, if a matching transaction is selected, the selected matching transaction with the probable new transaction, recalculate the account balance based on the merger, and display the merged transaction in the same manner as a first-group transaction.

19. The system of claim 18 wherein the processor is further configured to:

receive additional data from the second source describing additional second-group transactions before each second-group transaction described by previously-received second source data has been accepted, merged or reclassified,

classify the additional second-group transactions,

recalculate the account balance based on the additional second-group transactions and display the recalculated account balance, and

display in the graphical user interface, without a separate user instruction to do so and commingled with information about the first-group transactions, information about the additional second-group transactions.

20. The system of claim 19 wherein the processor is configured to periodically download second source data over a data communication network on a background program thread.

21. The system of claim 18 wherein the processor is further configured to:

categorize the first-group and the second-group transactions;

establish a budgetary limit for at least one transaction category;

calculate an effect upon the budgetary limit caused by second-group transactions that are within the at least one category, wherein the calculating an effect is performed without a separate user instruction to do so; and

recalculate the effect upon the budgetary limit upon a user selecting an alternate transaction as a matching transaction, upon a user selecting a matching transaction for a probable new transaction, or upon a probable match transaction being classified as a probable new transaction.