CA2027948C - Computer aided reconciliation method and apparatus - Google Patents
Computer aided reconciliation method and apparatus Download PDFInfo
- Publication number
- CA2027948C CA2027948C CA002027948A CA2027948A CA2027948C CA 2027948 C CA2027948 C CA 2027948C CA 002027948 A CA002027948 A CA 002027948A CA 2027948 A CA2027948 A CA 2027948A CA 2027948 C CA2027948 C CA 2027948C
- Authority
- CA
- Canada
- Prior art keywords
- records
- list
- record
- reconciling
- date
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/128—Check-book balancing, updating or printing arrangements
Abstract
The present invention is a method of reconciling a first list formed of a first number of first records and a second list formed of a second number of second records. The first list is typically a bank statement including as records the cheques and other transactions affecting the account balance that have occurred during the accounting period for the bank statement.
The second list is typically the customer's own list of records including the cheques and other transactions affecting the customer's account balance.
The second list is typically the customer's own list of records including the cheques and other transactions affecting the customer's account balance.
Description
TITLE:
COMPUTER AIDED RECONCILIATION METHOD AND APPARATUS
INVENTORS:
Eric Campbell Williams Dunn Thomas Andrew Proulx BACKGROUND OF THE INVENTION:
Field of the Invention The present invention relates to the field of automated systems for comparing and reconciling accounting records and more particularly to reconciling customer account information kept by a customer of a bank and corresponding account information kept by a bank.
_Reconciliation Process Generally Reconciliation is a process for comparing a bank statement prepared by a bank with corresponding customer information kept by a customer and for explaining the reasons for any differences resulting from the comparison. Typically, the final balance according to the bank statement is compared with the final balance according to the customer's information for a particular accounting period. Each individual transaction affecting the balance is compared. , Prior Art Generally Many bank accounts are reconciled manually by bank customers. A bank customer visually compares a printed bank statement and corresponding customer accounting information. The visual process tends to be time-consuming, tedious, and error-prone.
To reconcile an account, the customer or other reconciler typically sorts the records into numerical order and arranges the cancelled checks and other bank statement records together with the customer's own accounting information so that they are all in view.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 c- c.
~o~~~~~
For each transaction record on the bank statement, the customer visually scans the customer's own accounting information to identify a matching transaction record.
Typically transactions are visually matched based on amount, serial number if any, and date range. If a bank transaction is paired with an identical customer transaction, the customer marks the paired records and continues to the next record until all records have been examined. If a close but not perfect match is found, the customer must determine the reason for the discrepancy. Then either the bank or the customer must correct any erroneous or missing information. After all records are matched and discrepancy noted, the reconciler totals (1) the amounts of checks listed in the customer records that have not yet cleared the bank, (2) the customer deposits not entered by the bank, and (3) bank transactions that the customer has not entered. The customer then calculates the correct ending balance as follows: True ending balance equals bank ending balance plus outstanding deposits or credits minus outstanding checks or debits. If the calculated ending balance equals the ending balance in the customer's accounting information, reconciliation is complete. If the balances do not equal, the reconciler must search for discrepancies or errors and correct them until the account is reconciled.
Many banks offer a comparison service to help reconcile customers' accounts. For such services, each participating customer provides a copy of the customer's accounting information to the bank, usually in electronic form such as on disk, on tape or by computer transmission in a format specified by the bank. The bank enters the customer accounting information into the bank's computer. The bank's computer also contains the bank statement information for the customer. The bank's computer compares the bank and customer account-Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/I9-16:17 ing information to prepare a report for the customer identifying discrepancies. Typically, the bank makes no effort to reconcile any discrepancies.
Some banks provide customers with a bank statement in electronic form. Typically, a customer electronical-ly enters the data from the electronic bank statement into the customer's computer and the customer's computer compares the bank data with the customer's data, but this method offers no assistance in resolving discrepan-cies.
For bank customers, the number of records processed per month or other accounting period can vary greatly depending on the nature of the customer. For personal accounts, the number of checks, withdrawals, and other records on a monthly statement may range from a few to several hundred. For customer accounts of businesses, the number of records per month may be in the thousands.
Usually, a high percentage of the records for each transaction period are easily matched and therefore '" reconcilable with little difficulty. However, differe-nces between records from a bank statement list of records and a customer's corresponding list of records for the same accounting period can be 2% or higher of the total number of records.
For a customer's account which has an average of four thousand records per month and a 2% difference rate, eighty non-identical records must be reconciled because of some discrepancy between the bank listing and the customer listing. At the time of reconcilia-tion, a customer will normally have entered records into the customers accounting information for transactions in the next accounting period so that the customer's list of records is usually larger than the bank's list of records and this difference makes the reconciliation process more difficult.
In general, for checking accounts, the elements Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 20~.79~8 _ ,_ for each record which are compared include the date of the check, the number of the check, and the amount of the check. These elements are selected for comparison because the bank conventionally supplies the informa-tion to a customer with the customer's list of records with the monthly bank statement. However, many transactions in addition to checks occur in a checking account and require attention in order to reconcile the bank list with the customer list of records.
For example, bank service charges of many different types are entered by the bank into the bank statement and often this information is not added to the customer's list of records. Other transactions which appear on records on a bank list include credits, reversal of charges, and insufficient funds transactions.
These bank records often lead to discrepancies between a bank listing of records and a corresponding customer listing of records.
Other sources of discrepancies between the bank listing and the customer listing are errors in records that are introduced either by the bank or by the customer. For example, one common error is the transposition of digits in either the date element or in the amount element. Another common type of error is the omission of a check number. Also, certain records in a bank listing have no record number. For example, bank service charges or withdrawals from automatic tellers (ATMs) have no "check" number.
The difficulty of reconciling records having discrepancies due to errors can become complex and is a function of the number of records having discrepancies, the number of recorcs in one listing having no cor-responding records in the other listing, and in the nature of errors causing discrepancies. For example, if a business tends ~o write a large number of checks for similar dollar amoun~s on similar dates, it is Attorney Docket No.:I~ITU7340DEL
Y7P1/DEL/INTU/7340.001 89/10/19-16:17 -difficult to correlate visually a record in a bank list with a similar record (particularly when a difference due to an error or otherwise exists) in the customer list. Such a correlation is further com-pounded if transactions of like or similar dollar amounts omit a check number for reasons of error or otherwise.
The amount of time required to visually correlate and match erroneous information can be excessive. Even when computers are employed to do a comparison of records which are easily matched because the elements in the records are identical, the reconciliation of the unmatched (and sometimes erroneous) records can be highly time consuming.
The problem of reconciliation extends to other types of accounts, also. For example, reconciliation of a list of records from a credit card statement provided by a credit card issuer with a customer's own list of credit card records is often more difficult than checking account reconciliation. The increased difficulty occurs because credit card statements usually only identify the amount and date of the transaction without the equivalent of a transaction number (such as the check number usually present on checks in a checking account). Because there are~fewer elements to use in the comparison of information, credit card account reconciliation proves quite difficult when attempted visually.
While the above and other methods compare lists of accounting records to identify discrepancies, none of those methods adequately assist in reconciliating discrepancies.
In accordance with the above background of the invention, there is a need for improved methods and computer software for use with computers in reconciling periodic listings of accounting records.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 _6_ SUMMARY
The present invention is a method of reconciling a first list formed of a first number of first records and a second list formed of a second number of second records. The first list is typically a bank statement including as records the checks and other transactions affecting the account balance that have occurred during the accounting period for the bank statement. The second list is typically the customer's own list of records including the checks and other transactions affecting the customer's account balance.
For each unmatched record in the first list, a corresponding record from the second list is selected based upon a match value. Whenever the match value exceeds a threshold value, the corresponding records from the first and second lists are paired and thereafter, are removed from further reconciliation processing. The match value is determined as a result of comparing record elements and other attributes of records from the first and second lists. The highest match value for an unmatched record in the second list relative to a selected record in the first list is proposed as a match. The probable match, as determined by the highest match value, is selected or rejected either by human intervention or by automatic process ing. For each probable match accepted, the accepted match pair, including a record from the first list and a record from the second list, is then removed from further processing. The probable matching steps are repeated until all acceptable probable matches have been determined. Thereafter, if unmatched records exist in the first list, further processing continues.
For example, if no probable match exists, it may be determined that the lack of a likely match results from Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 ~0~.'~9~~
m_ -7-the omission of a record in the second list and the match can be made by insertion of a corresponding record in the second list so that a matched pair in the first and second list results. For example, such a record insertion often is necessary in a customer listing to correspond with a service charge in the first listing from a bank statement.
Typically, a second list such as a customer list will have many unmatched records after all of the records from the bank statements first list have been matched. These unmatched records represent transac-tions that are likely to appear on the bank statements for the next accounting period.
The method of determining the match value relies upon assigning probability values to differences between elements being compared where the elements for a checking account are typically the record number for a check, the record date, and the record amount.
Furthermore, different characteristics of each of the elements are analyzed and any discrepancies in such characteristics are also assigned probability values.
The match value is determined by summing all of -_ the individually assigned probability characteristics for each of the elements compared and for each of the characteristics of each of the elements compared. In one embodiment, the match value is quantized into 38 different levels.
In a simple three level example of a match value, the record element is 1/3, the record amount is 1/3, and the record date is 1/3. If a comparison of a record from the first list with a record from a second list finds identity in the date element, the record number element and the record amount element, then the match value is 1. If the record number and the record date are identical, but the record amounts are different, then the match value is 2/3_ Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C
~6z~~
_. _8_ If, in comparing one record element from the first list with unmatched record elements in the second list, one particular record element in the second list has a match value of 2/3 because the record number and date are the same, and all other records in the second list have a match value of 1/3 (for example, the date is the same but the record number and the record amount are different), or none of the elements are the same, then the most probable match of the first record with a record in the second list is the one with the match value of 2/3.
While this example of a 3 level match value demonstrates the principle, it has been found to be unsatisfactory for general use. For example, if a business writes checks for the same amount on the same date to numerous payees and an error occurs in the amount of one check, many different consequences may result during the reconciliation process. For example, for all those checks for the same amount on the same date with different check numbers will have a match value of 1/3. There will be no distinction between the correct check with an erroneous field and all of the other incorrect checks without corresponding fields.
While many different levels for match values can be established, several match characteristics of elements have been found important for efficient probable match correlation. One important factor is the date window. In considering probable matches of a record from the first list with a record from a second list, a higher contribution to the match value is important for those record dates which are within a predetermined range relative to the record date in the first list.
Another important characteristic in establishing a probability value for the match value is that the record amount in the second list be within a small Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C C
_ 20~.7~~$
g_ percentage difference from the record amount in the first list. For example, a record difference of not greater than 10% has been found useful.
Another characteristic of the matching process which is important is that the absence of any par-ticular element in a record does not preclude that element from being considered as a probable match. For example, the omission of a check number does not disqualify a record from being a probable match for a record in the first list, particularly when the record amount and the record date are identical. While the absence of an element or a particular characteristic of an element may reduce the match value, it does not disqualify the record from a probable match, par-ticularly if the match value for that record is high relative to the match values of other unmatched records.
To accomplish this task, it brings together and employs, in appropriate compatible format, computer information from both the account holder and the bank.
The present invention reduces the amount of human time and effort required to accomplish the task of bank account reconciliation.
The present invention provides a means to use existing accounting information with little or no modification needed.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 depicts a flow diagram of the bank account processing which occurs to create an electronic bank statement for sending to a bank customer together with the customer processing which occurs to establish the bank list from the bank and the customer list from the customer_ FIG_ 2 depicts the reconciliation process which occurs with the electronic bank list and the electronic customer list in a computer.
Attorney Docket No.:INTU7~40DEL
WP1/DEL/INTU/7340.001 89/10/19-15:17 ~~- ~A.27~~~
., -10-FIG. 3 depicts a block diagram of the reconcilia-tion method arid apparatus of the present invention.
DETAILED DESCRIPTION
The reconciliation process includes two distinct but related and coordinated procedures which take place at different locations and at different times;
namely at a bank and at a bank account customer~'s home or business.
Bank Procedures Banks routinely keep computerized information of all transactions that affect the checking accounts of bank account customers. Such transactions may be originated by the customer, the bank, or a third party.
The transactions~may or may not originate with paper documents, but the bank converts the transactions to electronic information and stores them in computer files. At accounting intervals known as statement cycles, the bank provides each customer with a summary list of all transactions affecting the customer's account. Such summaries called bank statements, are delivered to customers on paper or in various electron-ic forms.
When banks periodically send their customers electronic versions of their bank statements, most often, banks send the~customer a floppy disk in the mail, but some banks will convey the data over a modem line to the customer's computer from the bank's computer.
FIG. 1 shows a typical bank computer procedure used to produce disks for its customers. The bank first establishes a computerized way to identify Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 ~o~-~~~s customers that are to receive electronic bank state-ments. Then the bank extracts the necessary bank statement data for each customer at regular intervals.
The bank computer program reads the appropriate data files, extracts the needed data for the selected customers, formats the data (typically to ASCII
specifications), and makes the data available for downloading to floppy disks. The extracting and downloading are accomplished by means of conventional programs specific to the banks own computer methods of storing data. Typically, the data is downloaded to a microcomputer or other computer tailored to produce floppy disks for customers.
Once the downloading is accomplished, the bank's data is typically converted to a compressed format, sorted by customer account, associated with descriptors (such as "Check" or "Deposit") for each customer transaction, and associated with a name/address and disk size for each customer. The finished disk for each customer is mailed to the customer.
Customer Procedures Individuals and businesses often use computers and various software to keep accounting information of the transactions made on their checking or other bank accounts. As indicated in FIG. 1, the customer accounting information is electronically stored within a customer computer or on computer media such as disks or tapes. The customer information may be retrieved and examined to accomplish account reconciliation or other purposes.
Processes for reconciling accounts vary depending on the individual customer. The prerequisites for account reconciliation are (1) a bank account state-ment, and (2) customer accounting information.
The present invention accomplishes the reconcilia-Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C
20~.~9 ~$
.-- -12 -tion process using a computer. The customer account holder keeps computerized accounting information and typically receives a computerized bank account state-ment from the bank. The customer accounting informa-tion typically incorporates a number of "drivers", which are programs that read accounting information from publicly available software packages. Drivers may directly read accounting data from a particular software package, or they may indirectly read informa-tion that the reconciler has created via a function of the software used to create the information. In either case, the customer typically uses the customer's existing information created over the accounting period, rather than requiring a re-keying of each transaction, or the customer uses data extracted from existing accounting information by means of basic export functions rather than requiring new programming to make the data usable. Once both the customer's and the bank's information, are loaded into the computer, the reconciliation process commences. If discrepancies are found, the process displays a bank statement record on a screen along with the closest match found. The user chooses among several potential courses of action to resolve the discrepancy. When all transactions from the bank statement have been paired or- corrected, the customer may choose to print reconciliation reports.
The customer can change the customer account informa-tion, or contact the bank to change theirs, depending on which party made errors, if any. Reconciliation is then complete. This process is repeated whenever a bank statement is produced, often monthly.
Automating the bank reconciliation process requires bringing the customer's data and the bank's data together on a computer. Once the data is avail-able, it must be matched up accurately and rapidly. To fully automate the matching process, the software must Attorney Docket No.:INTU7340DEL
WPi/DEL/INTU/7340.001 89/10/19-16:17 ;, _ -13-provide an efficient method for dealing with discrepan-cies between the customer's information and the bank's statement. Frequently, coping with the discrepancies is the most time-consuming part of reconciling a bank statement. The present invention provides a deter-ministic, error-free approach to reconciling which quickly deals with exactly-matching records and then handles the non-exactly-matching records in an effi-cient manner.
FIG. 3 depicts a computer apparatus for performing the reconciliation method of the present invention.
The apparatus of FIG. 3 can be a general purpose computer, such as an IBM personal computer, or can be a special purpose computer for performing the method of the present invention. In FIG. 3, the store 1 is a mainstore or other store for storing the list L1 records associated with a bank statement. The store 2 is a mainstore or other memory for storing the customer records for the customer list L2. Under control of the controller il, each of the records R1(ri) is fetched from the store 1 into the register 3 for comparison with each of the records R2(r2) from the L2 list of store 2. For each R1(rl) record in register 3, unpaired ones of the N records in the L2 list are fetched into the register 4. For each record R2(r2) in register 4, a comparison is made with the record R1(rl) in register 3 in order to calculate a Match Score, MS(rl,r2) in the Match Score calculator 5. The results of the Match Score from the calculator 5 are sensed in the threshold detector 8. If the Match Score, MS(rl,r2), from calculator 5 exceeds the pairing threshold, the threshold detector 8 causes the pairing of Rl(rl) and R2(r2) to be marked in the paired memory 7. If not exceeding the pairing threshold, then the Match Score for the record R1(rl) and R2(r2) is stored into the temporary memory 6. After processing all of Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.OOi 89/10/19-16:17 _.
-~4- 2b,2~~~~
the N records from the L1 store 1 and determining all of the paired records in the pairing memory 7, the unpaired records corresponding to the Match Scores for the R1(rl) records appear in the temporary memory 6.
For each unpaired record R1(rl), the highest Match Score values for a group of records R2 are presented on a user display 9 for view by a user at a user terminal 10. The user terminal 10 has an opportunity to select a record in the group of records on display 9. If a selection is made, the selected pair of records are entered into the pair memory 7. This process is repeated for all unmatched records from the L1 store 1 appearing in the temporary store 6.
Reconciliation Process 1. The computer stores two separate lists of transactions, for example, the Bank Statement List from the bank and the Check Register List from the bank customer. The Bank Statement List is a list of bank transactions which have cleared the bank in the most recent processing cycle for an accounting period. The Check Register List is a list of records for bank transactions as maintained by the customer and which have not been reconciled to a prior bank statement. In general the Check Register List will be longer than the Bank Statement List because it will contain transac-tions dated after the ending date of the accounting period for the Bank Statement List.
Each list includes a number of records such as checks, deposits, fees or other transactions affecting the account balance. Each record typically includes a number of elements. Typical elements for a checking account are a date, a check number, an amount, a payee, a payor, and an account number. Some records do not have all elements. For example, bank fees do not have any check or other transaction number.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C
_. _15_ By way of definition, the Bank Statement List is the first list, L1, and it has N first records designated R1(1), R1(2), ..., R1(rl), ..., R1(N) where each one of the records R1(rl) is formed of up to P
elements E1(1),E1(2), E1(3), ..., E1(e), ..., E1(P).
Similarly by way of definition, the Check Register List is the second list L2 and it has M second records designated R2(1), R2(2), ..., R2(r2), ..., R2(M) where each one of the records R2(r2) is formed of P elements E2(1),E2(2), E2(3), ..., E2(e), ..., E2(P). Typically, M is greater than N because the customer list includes checks which have not yet been processed by the bank.
COMPUTER AIDED RECONCILIATION METHOD AND APPARATUS
INVENTORS:
Eric Campbell Williams Dunn Thomas Andrew Proulx BACKGROUND OF THE INVENTION:
Field of the Invention The present invention relates to the field of automated systems for comparing and reconciling accounting records and more particularly to reconciling customer account information kept by a customer of a bank and corresponding account information kept by a bank.
_Reconciliation Process Generally Reconciliation is a process for comparing a bank statement prepared by a bank with corresponding customer information kept by a customer and for explaining the reasons for any differences resulting from the comparison. Typically, the final balance according to the bank statement is compared with the final balance according to the customer's information for a particular accounting period. Each individual transaction affecting the balance is compared. , Prior Art Generally Many bank accounts are reconciled manually by bank customers. A bank customer visually compares a printed bank statement and corresponding customer accounting information. The visual process tends to be time-consuming, tedious, and error-prone.
To reconcile an account, the customer or other reconciler typically sorts the records into numerical order and arranges the cancelled checks and other bank statement records together with the customer's own accounting information so that they are all in view.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 c- c.
~o~~~~~
For each transaction record on the bank statement, the customer visually scans the customer's own accounting information to identify a matching transaction record.
Typically transactions are visually matched based on amount, serial number if any, and date range. If a bank transaction is paired with an identical customer transaction, the customer marks the paired records and continues to the next record until all records have been examined. If a close but not perfect match is found, the customer must determine the reason for the discrepancy. Then either the bank or the customer must correct any erroneous or missing information. After all records are matched and discrepancy noted, the reconciler totals (1) the amounts of checks listed in the customer records that have not yet cleared the bank, (2) the customer deposits not entered by the bank, and (3) bank transactions that the customer has not entered. The customer then calculates the correct ending balance as follows: True ending balance equals bank ending balance plus outstanding deposits or credits minus outstanding checks or debits. If the calculated ending balance equals the ending balance in the customer's accounting information, reconciliation is complete. If the balances do not equal, the reconciler must search for discrepancies or errors and correct them until the account is reconciled.
Many banks offer a comparison service to help reconcile customers' accounts. For such services, each participating customer provides a copy of the customer's accounting information to the bank, usually in electronic form such as on disk, on tape or by computer transmission in a format specified by the bank. The bank enters the customer accounting information into the bank's computer. The bank's computer also contains the bank statement information for the customer. The bank's computer compares the bank and customer account-Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/I9-16:17 ing information to prepare a report for the customer identifying discrepancies. Typically, the bank makes no effort to reconcile any discrepancies.
Some banks provide customers with a bank statement in electronic form. Typically, a customer electronical-ly enters the data from the electronic bank statement into the customer's computer and the customer's computer compares the bank data with the customer's data, but this method offers no assistance in resolving discrepan-cies.
For bank customers, the number of records processed per month or other accounting period can vary greatly depending on the nature of the customer. For personal accounts, the number of checks, withdrawals, and other records on a monthly statement may range from a few to several hundred. For customer accounts of businesses, the number of records per month may be in the thousands.
Usually, a high percentage of the records for each transaction period are easily matched and therefore '" reconcilable with little difficulty. However, differe-nces between records from a bank statement list of records and a customer's corresponding list of records for the same accounting period can be 2% or higher of the total number of records.
For a customer's account which has an average of four thousand records per month and a 2% difference rate, eighty non-identical records must be reconciled because of some discrepancy between the bank listing and the customer listing. At the time of reconcilia-tion, a customer will normally have entered records into the customers accounting information for transactions in the next accounting period so that the customer's list of records is usually larger than the bank's list of records and this difference makes the reconciliation process more difficult.
In general, for checking accounts, the elements Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 20~.79~8 _ ,_ for each record which are compared include the date of the check, the number of the check, and the amount of the check. These elements are selected for comparison because the bank conventionally supplies the informa-tion to a customer with the customer's list of records with the monthly bank statement. However, many transactions in addition to checks occur in a checking account and require attention in order to reconcile the bank list with the customer list of records.
For example, bank service charges of many different types are entered by the bank into the bank statement and often this information is not added to the customer's list of records. Other transactions which appear on records on a bank list include credits, reversal of charges, and insufficient funds transactions.
These bank records often lead to discrepancies between a bank listing of records and a corresponding customer listing of records.
Other sources of discrepancies between the bank listing and the customer listing are errors in records that are introduced either by the bank or by the customer. For example, one common error is the transposition of digits in either the date element or in the amount element. Another common type of error is the omission of a check number. Also, certain records in a bank listing have no record number. For example, bank service charges or withdrawals from automatic tellers (ATMs) have no "check" number.
The difficulty of reconciling records having discrepancies due to errors can become complex and is a function of the number of records having discrepancies, the number of recorcs in one listing having no cor-responding records in the other listing, and in the nature of errors causing discrepancies. For example, if a business tends ~o write a large number of checks for similar dollar amoun~s on similar dates, it is Attorney Docket No.:I~ITU7340DEL
Y7P1/DEL/INTU/7340.001 89/10/19-16:17 -difficult to correlate visually a record in a bank list with a similar record (particularly when a difference due to an error or otherwise exists) in the customer list. Such a correlation is further com-pounded if transactions of like or similar dollar amounts omit a check number for reasons of error or otherwise.
The amount of time required to visually correlate and match erroneous information can be excessive. Even when computers are employed to do a comparison of records which are easily matched because the elements in the records are identical, the reconciliation of the unmatched (and sometimes erroneous) records can be highly time consuming.
The problem of reconciliation extends to other types of accounts, also. For example, reconciliation of a list of records from a credit card statement provided by a credit card issuer with a customer's own list of credit card records is often more difficult than checking account reconciliation. The increased difficulty occurs because credit card statements usually only identify the amount and date of the transaction without the equivalent of a transaction number (such as the check number usually present on checks in a checking account). Because there are~fewer elements to use in the comparison of information, credit card account reconciliation proves quite difficult when attempted visually.
While the above and other methods compare lists of accounting records to identify discrepancies, none of those methods adequately assist in reconciliating discrepancies.
In accordance with the above background of the invention, there is a need for improved methods and computer software for use with computers in reconciling periodic listings of accounting records.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 _6_ SUMMARY
The present invention is a method of reconciling a first list formed of a first number of first records and a second list formed of a second number of second records. The first list is typically a bank statement including as records the checks and other transactions affecting the account balance that have occurred during the accounting period for the bank statement. The second list is typically the customer's own list of records including the checks and other transactions affecting the customer's account balance.
For each unmatched record in the first list, a corresponding record from the second list is selected based upon a match value. Whenever the match value exceeds a threshold value, the corresponding records from the first and second lists are paired and thereafter, are removed from further reconciliation processing. The match value is determined as a result of comparing record elements and other attributes of records from the first and second lists. The highest match value for an unmatched record in the second list relative to a selected record in the first list is proposed as a match. The probable match, as determined by the highest match value, is selected or rejected either by human intervention or by automatic process ing. For each probable match accepted, the accepted match pair, including a record from the first list and a record from the second list, is then removed from further processing. The probable matching steps are repeated until all acceptable probable matches have been determined. Thereafter, if unmatched records exist in the first list, further processing continues.
For example, if no probable match exists, it may be determined that the lack of a likely match results from Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 ~0~.'~9~~
m_ -7-the omission of a record in the second list and the match can be made by insertion of a corresponding record in the second list so that a matched pair in the first and second list results. For example, such a record insertion often is necessary in a customer listing to correspond with a service charge in the first listing from a bank statement.
Typically, a second list such as a customer list will have many unmatched records after all of the records from the bank statements first list have been matched. These unmatched records represent transac-tions that are likely to appear on the bank statements for the next accounting period.
The method of determining the match value relies upon assigning probability values to differences between elements being compared where the elements for a checking account are typically the record number for a check, the record date, and the record amount.
Furthermore, different characteristics of each of the elements are analyzed and any discrepancies in such characteristics are also assigned probability values.
The match value is determined by summing all of -_ the individually assigned probability characteristics for each of the elements compared and for each of the characteristics of each of the elements compared. In one embodiment, the match value is quantized into 38 different levels.
In a simple three level example of a match value, the record element is 1/3, the record amount is 1/3, and the record date is 1/3. If a comparison of a record from the first list with a record from a second list finds identity in the date element, the record number element and the record amount element, then the match value is 1. If the record number and the record date are identical, but the record amounts are different, then the match value is 2/3_ Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C
~6z~~
_. _8_ If, in comparing one record element from the first list with unmatched record elements in the second list, one particular record element in the second list has a match value of 2/3 because the record number and date are the same, and all other records in the second list have a match value of 1/3 (for example, the date is the same but the record number and the record amount are different), or none of the elements are the same, then the most probable match of the first record with a record in the second list is the one with the match value of 2/3.
While this example of a 3 level match value demonstrates the principle, it has been found to be unsatisfactory for general use. For example, if a business writes checks for the same amount on the same date to numerous payees and an error occurs in the amount of one check, many different consequences may result during the reconciliation process. For example, for all those checks for the same amount on the same date with different check numbers will have a match value of 1/3. There will be no distinction between the correct check with an erroneous field and all of the other incorrect checks without corresponding fields.
While many different levels for match values can be established, several match characteristics of elements have been found important for efficient probable match correlation. One important factor is the date window. In considering probable matches of a record from the first list with a record from a second list, a higher contribution to the match value is important for those record dates which are within a predetermined range relative to the record date in the first list.
Another important characteristic in establishing a probability value for the match value is that the record amount in the second list be within a small Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C C
_ 20~.7~~$
g_ percentage difference from the record amount in the first list. For example, a record difference of not greater than 10% has been found useful.
Another characteristic of the matching process which is important is that the absence of any par-ticular element in a record does not preclude that element from being considered as a probable match. For example, the omission of a check number does not disqualify a record from being a probable match for a record in the first list, particularly when the record amount and the record date are identical. While the absence of an element or a particular characteristic of an element may reduce the match value, it does not disqualify the record from a probable match, par-ticularly if the match value for that record is high relative to the match values of other unmatched records.
To accomplish this task, it brings together and employs, in appropriate compatible format, computer information from both the account holder and the bank.
The present invention reduces the amount of human time and effort required to accomplish the task of bank account reconciliation.
The present invention provides a means to use existing accounting information with little or no modification needed.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 depicts a flow diagram of the bank account processing which occurs to create an electronic bank statement for sending to a bank customer together with the customer processing which occurs to establish the bank list from the bank and the customer list from the customer_ FIG_ 2 depicts the reconciliation process which occurs with the electronic bank list and the electronic customer list in a computer.
Attorney Docket No.:INTU7~40DEL
WP1/DEL/INTU/7340.001 89/10/19-15:17 ~~- ~A.27~~~
., -10-FIG. 3 depicts a block diagram of the reconcilia-tion method arid apparatus of the present invention.
DETAILED DESCRIPTION
The reconciliation process includes two distinct but related and coordinated procedures which take place at different locations and at different times;
namely at a bank and at a bank account customer~'s home or business.
Bank Procedures Banks routinely keep computerized information of all transactions that affect the checking accounts of bank account customers. Such transactions may be originated by the customer, the bank, or a third party.
The transactions~may or may not originate with paper documents, but the bank converts the transactions to electronic information and stores them in computer files. At accounting intervals known as statement cycles, the bank provides each customer with a summary list of all transactions affecting the customer's account. Such summaries called bank statements, are delivered to customers on paper or in various electron-ic forms.
When banks periodically send their customers electronic versions of their bank statements, most often, banks send the~customer a floppy disk in the mail, but some banks will convey the data over a modem line to the customer's computer from the bank's computer.
FIG. 1 shows a typical bank computer procedure used to produce disks for its customers. The bank first establishes a computerized way to identify Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 ~o~-~~~s customers that are to receive electronic bank state-ments. Then the bank extracts the necessary bank statement data for each customer at regular intervals.
The bank computer program reads the appropriate data files, extracts the needed data for the selected customers, formats the data (typically to ASCII
specifications), and makes the data available for downloading to floppy disks. The extracting and downloading are accomplished by means of conventional programs specific to the banks own computer methods of storing data. Typically, the data is downloaded to a microcomputer or other computer tailored to produce floppy disks for customers.
Once the downloading is accomplished, the bank's data is typically converted to a compressed format, sorted by customer account, associated with descriptors (such as "Check" or "Deposit") for each customer transaction, and associated with a name/address and disk size for each customer. The finished disk for each customer is mailed to the customer.
Customer Procedures Individuals and businesses often use computers and various software to keep accounting information of the transactions made on their checking or other bank accounts. As indicated in FIG. 1, the customer accounting information is electronically stored within a customer computer or on computer media such as disks or tapes. The customer information may be retrieved and examined to accomplish account reconciliation or other purposes.
Processes for reconciling accounts vary depending on the individual customer. The prerequisites for account reconciliation are (1) a bank account state-ment, and (2) customer accounting information.
The present invention accomplishes the reconcilia-Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C
20~.~9 ~$
.-- -12 -tion process using a computer. The customer account holder keeps computerized accounting information and typically receives a computerized bank account state-ment from the bank. The customer accounting informa-tion typically incorporates a number of "drivers", which are programs that read accounting information from publicly available software packages. Drivers may directly read accounting data from a particular software package, or they may indirectly read informa-tion that the reconciler has created via a function of the software used to create the information. In either case, the customer typically uses the customer's existing information created over the accounting period, rather than requiring a re-keying of each transaction, or the customer uses data extracted from existing accounting information by means of basic export functions rather than requiring new programming to make the data usable. Once both the customer's and the bank's information, are loaded into the computer, the reconciliation process commences. If discrepancies are found, the process displays a bank statement record on a screen along with the closest match found. The user chooses among several potential courses of action to resolve the discrepancy. When all transactions from the bank statement have been paired or- corrected, the customer may choose to print reconciliation reports.
The customer can change the customer account informa-tion, or contact the bank to change theirs, depending on which party made errors, if any. Reconciliation is then complete. This process is repeated whenever a bank statement is produced, often monthly.
Automating the bank reconciliation process requires bringing the customer's data and the bank's data together on a computer. Once the data is avail-able, it must be matched up accurately and rapidly. To fully automate the matching process, the software must Attorney Docket No.:INTU7340DEL
WPi/DEL/INTU/7340.001 89/10/19-16:17 ;, _ -13-provide an efficient method for dealing with discrepan-cies between the customer's information and the bank's statement. Frequently, coping with the discrepancies is the most time-consuming part of reconciling a bank statement. The present invention provides a deter-ministic, error-free approach to reconciling which quickly deals with exactly-matching records and then handles the non-exactly-matching records in an effi-cient manner.
FIG. 3 depicts a computer apparatus for performing the reconciliation method of the present invention.
The apparatus of FIG. 3 can be a general purpose computer, such as an IBM personal computer, or can be a special purpose computer for performing the method of the present invention. In FIG. 3, the store 1 is a mainstore or other store for storing the list L1 records associated with a bank statement. The store 2 is a mainstore or other memory for storing the customer records for the customer list L2. Under control of the controller il, each of the records R1(ri) is fetched from the store 1 into the register 3 for comparison with each of the records R2(r2) from the L2 list of store 2. For each R1(rl) record in register 3, unpaired ones of the N records in the L2 list are fetched into the register 4. For each record R2(r2) in register 4, a comparison is made with the record R1(rl) in register 3 in order to calculate a Match Score, MS(rl,r2) in the Match Score calculator 5. The results of the Match Score from the calculator 5 are sensed in the threshold detector 8. If the Match Score, MS(rl,r2), from calculator 5 exceeds the pairing threshold, the threshold detector 8 causes the pairing of Rl(rl) and R2(r2) to be marked in the paired memory 7. If not exceeding the pairing threshold, then the Match Score for the record R1(rl) and R2(r2) is stored into the temporary memory 6. After processing all of Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.OOi 89/10/19-16:17 _.
-~4- 2b,2~~~~
the N records from the L1 store 1 and determining all of the paired records in the pairing memory 7, the unpaired records corresponding to the Match Scores for the R1(rl) records appear in the temporary memory 6.
For each unpaired record R1(rl), the highest Match Score values for a group of records R2 are presented on a user display 9 for view by a user at a user terminal 10. The user terminal 10 has an opportunity to select a record in the group of records on display 9. If a selection is made, the selected pair of records are entered into the pair memory 7. This process is repeated for all unmatched records from the L1 store 1 appearing in the temporary store 6.
Reconciliation Process 1. The computer stores two separate lists of transactions, for example, the Bank Statement List from the bank and the Check Register List from the bank customer. The Bank Statement List is a list of bank transactions which have cleared the bank in the most recent processing cycle for an accounting period. The Check Register List is a list of records for bank transactions as maintained by the customer and which have not been reconciled to a prior bank statement. In general the Check Register List will be longer than the Bank Statement List because it will contain transac-tions dated after the ending date of the accounting period for the Bank Statement List.
Each list includes a number of records such as checks, deposits, fees or other transactions affecting the account balance. Each record typically includes a number of elements. Typical elements for a checking account are a date, a check number, an amount, a payee, a payor, and an account number. Some records do not have all elements. For example, bank fees do not have any check or other transaction number.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C
_. _15_ By way of definition, the Bank Statement List is the first list, L1, and it has N first records designated R1(1), R1(2), ..., R1(rl), ..., R1(N) where each one of the records R1(rl) is formed of up to P
elements E1(1),E1(2), E1(3), ..., E1(e), ..., E1(P).
Similarly by way of definition, the Check Register List is the second list L2 and it has M second records designated R2(1), R2(2), ..., R2(r2), ..., R2(M) where each one of the records R2(r2) is formed of P elements E2(1),E2(2), E2(3), ..., E2(e), ..., E2(P). Typically, M is greater than N because the customer list includes checks which have not yet been processed by the bank.
2. Starting with the first record, R1(1), in the Bank Statement List, L1, the computer generates a match score for one or more of the as-yet-unmatched records in the Check Register List, according to a scoring method described below. The match scores calculated have a score range, for example, from 0 to 100. Specifically, record R1(1) is compared with R2(1) to obtain a match score MS(1,1) having a value between 0 and 100. Next, R1(1) is compared with R2(2) to obtain a match score MS(1,2) between 0 and 100.
3. The computer compares each match score produced to a fixed number pairing threshold, Pmatch If the match score exceeds Pmatch~ the corresponding Check Register List record, R2(e), is considered an exact match and is paired with the selected Bank Statement List record. This pairing constitutes reconciliation for the paired records and completes processing for those paired records, R1(1) and R2(e).
Thereafter, Rl(1) is compared with R2(3), R2(4) and so on to obtain match scores MS(1,3), MS(1,4) and so on.
If the match score does not exceed Pmatch for R1(1), the Bank Statement List record Rl(1) is temporarily set aside and processing proceeds with the next Bank Statement List record, for example, R1(2).
Attorney Docket No.:ZNTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 _~6- 2b~.~9~8 4. Processing of Bank Statement List records continues in this fashion for all of the records R1(1), R1(2), ..., R1(N) to find those that can be exactly matched and paired with R2(1), R2(2), ..., R2(M) records.
Thereafter, Rl(1) is compared with R2(3), R2(4) and so on to obtain match scores MS(1,3), MS(1,4) and so on.
If the match score does not exceed Pmatch for R1(1), the Bank Statement List record Rl(1) is temporarily set aside and processing proceeds with the next Bank Statement List record, for example, R1(2).
Attorney Docket No.:ZNTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 _~6- 2b~.~9~8 4. Processing of Bank Statement List records continues in this fashion for all of the records R1(1), R1(2), ..., R1(N) to find those that can be exactly matched and paired with R2(1), R2(2), ..., R2(M) records.
5. Once all of the records which can be exactly matched have been paired, the matching process is restarted at the first Bank Statement List record R1(rl) which has not yet been paired to some Check Register List record, R2(r2).
Match scores for each of the Check Register List records which have not yet been paired to a Bank Statement List record are ordered from high to low. A
group of Check Register List records is matched to a first one of the unpaired Check Register List records.
For example, the selected group includes the ten highest match scores, provided each of the match scores exceeds a fixed number no-match threshold, pnomatch~ is successively highlighted, in order of descending match score, for presentation to the user for user acceptance or user rejection. If the user verifies that the highlighted Check Register List record matches the current Bank Statement List record, the records are paired and processing for the current Bank Statement List record is complete. If the user rejects the suggested pairing, the Check Register List record with the next-highest match score is highlighted for the user.
If the user rejects all of the ten highest-scoring records, or all of those records having a match score which exceeds Pnomatch~ the user is given an opportunity to add a record to the Check Register List and have the added record paired with the current bank Statement List record. If the user confirms that a record should be added, processing is terminated for this step; otherwise the entire cycle is repeated from Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 _ _17_ the selection of the 10 highest match scores remaining.
Match scores for each of the Check Register List records which have not yet been paired to a Bank Statement List record are ordered from high to low. A
group of Check Register List records is matched to a first one of the unpaired Check Register List records.
For example, the selected group includes the ten highest match scores, provided each of the match scores exceeds a fixed number no-match threshold, pnomatch~ is successively highlighted, in order of descending match score, for presentation to the user for user acceptance or user rejection. If the user verifies that the highlighted Check Register List record matches the current Bank Statement List record, the records are paired and processing for the current Bank Statement List record is complete. If the user rejects the suggested pairing, the Check Register List record with the next-highest match score is highlighted for the user.
If the user rejects all of the ten highest-scoring records, or all of those records having a match score which exceeds Pnomatch~ the user is given an opportunity to add a record to the Check Register List and have the added record paired with the current bank Statement List record. If the user confirms that a record should be added, processing is terminated for this step; otherwise the entire cycle is repeated from Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 _ _17_ the selection of the 10 highest match scores remaining.
6. Processing of the non-exact matches continues in the fashion described above under 5, until all of the Bank Statement List records have been matched either to pre-existing check Register List records or to new Check Register List records created during the process.
1 1 ion of the Match Scores For Two Tvnical _RPCOrds Ri(rl) and R2(r2) The method for calculating match scores, MS, must be precise enough so that the majority of pairingss are completely automatic, but discriminating enough so that spurious matches are not made. In order to make the semi-automatic pairing process (for non-exact matches) efficient, the matches need to be for plausible pairings and need to be presented in a logical order.
To achieve these objectives, is one embodiment, a set of matching rules that produce 38 different match scores have been found to work well in a typical accounting environment. For example, in the "amount"
element comparison, a relatively high match score results if the compared amounts are the same except for a digit transposition. In the "date" element com-parison, experience-based rules for determining how long various records take to clear the bank affect the match score.
Match scores, MS(rl,r2), between a first list, L1, record R1(rl) and a second list, L2, record R2(r2) are calculated as follows:
If Pdate(dl,d2,c1) - 0, MS(rl,r2) - 0.
If Pdate(dl,d2) ~= 0, MS(rl,r2) - (Pdate(dl.d2,c1) Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 pamount(al,a2) + Pnumber(cl,c2))/3 where, Pdate(dl,d2,c1) the Date Score probability value -set as a function of comparing the [Adates in the date elements dl and d2 of R1(rl) and R2(r2), respec-tively, as a function of the number element, cl.
pamount{al,a2) the Amount Score probability value -set as a function of comparing the amounts in the amount elements al and a2 of R1(rl) and R2(r2), respectively.
pnumber(cl,c2) the Number Score probability value -set as a function of comparing the numbers in the number elements cl and c2 of the records R1(rl) and R2(r2), respectively.
MS(rl,r2) - Match Score probability value set as a function of comparing R1(rl) and R2(r2) records.
dl - Date of record R1(rl) from Bank Statement List d2 Date Register = of record R2(r2) from Check List al Amount from record R1{rl) of Bank Statement =
List a2 = Amountfrom R2(r2) of Check Register List cl - Check Number frin recird R1(rl) {or 0 if none) of Bank Statement List c2 = Check Number from record R2(r2) (or 0 if none) of Check Register List Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 _,9~.0~.~9~$
calculation of the Date Score The Date Score, Pdate(dl,d2,c1), is determined as one of the date score probability values, sdi, in TABLE
1 as follows:
Pdate(dl,d2,c1) - sdi where i has one of the values 1, 2, ..., 6.
dd = (dl - d2) sdi = one of the date score probability values determined by TABLE 1.
i = 1, 2, ..., 6 Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C ~.
-... -20-0<dd<90 _ _ sdl c1~0 -31<dd<190 ~ sd2 i dd<0 ; sd3 or i dd>90 dd<-31 or dd>190 0<dd<5 _ _ sd4 ~ -S<dd<31 sd5 i i cl=0 ;
dd<0 or dd>S
sd6 dd<-5 or dd>31.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 zl2~2~~~~
~.lculation of the Amount Score The Amount Score, Pamount(al,a2), is determined as one of the amount score probability values sai as follows:
Pamount(ai.a2) - sdi where i has on of the values 1, 2, ... 26.
sdi - one of the amount probability values determined by TABLE 2.
i = 1, 2, ..., 26 gl = sign of al g2 = sign of a2 11 = number of digits in al 12 = number of digits in a2 D - number of digits differing in al, a2 (stopping the comparison at the end of the shorter of the two if their lengths differ) T - sum of the arithmetic digit-wise difference between al and a2 (using only as many digits as are present in the shorter number) Attorney Docket No.:INTU7340DEL
WPi/DEL/INTU/7340.001 89/10/19-16:17 c 8 ~g2 gl 1 g2 D = 0 sal sat ;11-12;=1 ! D = 1 sa3 sa4 , , , D>1 ~ say sa6 , 1112 ' , T = 0 sa7 sag ;11-12;>1 ;
T ~ 0 ~ sag sal0 , , , D = 0 call salt , , ;al/a2 -1;<.0 s al3 sal4 D = 1 ' , ;11=12 ; ; T = 0 sal5 sal6 , , , ;al/a2-1;>.06 ; T ~ 0 i i sal7 sal8 , ;al/a2-1;<.06 sal9 sa20 D = 2 i ' T = 0 , , sa21 sa22 , , i ' T # 0 ~~al/a2-1;> .06 ; sa23 sa24 , , D > 2 sa25 sa26 Attorney Docket No.:TNTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 ~" lCi1 ~ at ~ Ori Ot Lne lVUmne1 m:v~~
The Number Score, Pnumber(cl.c2), is determined as one of the number score probability values sni in TABLE 3 as follows:
Pnumber(cl,c2) - sni where i has one of the values 1, 2, ..., 6.
sni - one of the number probability values determined by TABLE 3.
i = 1, 2, ..., 6.
c2 = 0 cl ~ 0 snl i ~ cl = c2 ~ sn2 c2 ~ 0 ;
;, , ~ ; ;cl-C2;=1 i sn3 i ;cl-c2;>1 ~ sn4 c2 = 0 sn5 cl - 0 ;
c2 ~ 0 sn6 Typical probability values for sdi of TABLE 1, sai of TABLE 2, and of sni of TABLE 3 are c,~iven in the following TABLE 4. With the values of TABLE 4, the value of the pairing threshold, Pmatch~ is typically 96 and the value of the exclusion threshold, Pnomatch~ is typically 50.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 sdl=100 sd2=50 sd3=10 sd4=90 sd5=40 sd6=20 sal=60 sat=30 sa3=50 sa4=25 say=40 sa6=20 sa7=50 sag=25 sag=25 sal0=12 sail=100 salt=50 sal3=80 sal4=40 sal5=80 sal6=40 sal7=30 sal8=15 sal9=70 sa20=35 sa21=50 sa22=25 sa23=20 sa24=10 sa25=20 sa26=10 snl=20 sn2=100 sn3=80 sn4=40 sn5=60 sn6=20 An example of the operation of the present invention is given for a bank statement list, L1, in TABLE 5 having the records R1(1), R1(2), R1(3), ..., R1(M). In TABLE 5, only the three L1 records R1(1), R1{2), and R1(3) are explicitly shown. The example of the operation of the present invention also uses a customer list, L2, in TABLE 6 having the records R2(1), R2(2), R2(3), ..., R2(n). In TABLE 6, only the eleven L2 records R2(1), R2(2), ..., R2(11) are explicitly shown.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 __ -25-L1 -Bank List R1 Tvne Date um r Am n 1 Deposit 7/6/88 1,988.00 2 Check 7/7/88 3386 1000.50 3 Deposit 7/6/88 572.59 4 Fee 7/30/88 2.50 M Check L2- Customer List R2 Type D a Number Am un 1 Deposit 7/5/88 9,188.00 2 Deposit 7/6/88 19,906.96 3 Deposit 7/4/88 9,733.49 4 Deposit 7/7/88 3,829.68 Check 7/5/88 3391 214.50 6 Check 7/5/88 3392 394.17 7 Check 7/5/88 3393 214.34 8 Check 7/5/88 3389 3,513.74 9 Check 7/5/88 3390 4,687.53 Check 7/5/88 3386 1000.50 11 Deposit 7/5/88 572.59 N Check Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 The comparison process begins by comparing, in comparing steps C(1,1), C(1,2), ..., C(1,11) one of the L1 records, R1(1), with the L2 records R2(1), R2(2), ..., R2(11) in an example where N equals eleven to form the corresponding match scores, MS(1,1), MS(1,2), ..., MS(1,11). The results of the comparison and the match scores calculated are listed in TABLE 7.
In TABLE 7, note that none of the match scores exceeds the pairing threshold, Pmatch~ value of 96 and there-fore none of the records of L1 and L2 are paired at this time.
R1(1)- L2 Compare C R1 R2 Match Score Paired 1 1 1 <96 NO
2 1 2 <96 NO
3 1 3 <96 NO
4 1 4 <96 NO
1 5 <96 NO
6 1 6 <96 NO
7 1 7 <96 NO
8 1 8 <96 NO
9 1 9 <96 NO .
1 10 <96 NO
11 1 11 <96 NO
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 -.. _27_ The comparison process continues by comparing, in comparing steps C(2,1), C(2,2), ..., C(2,11) one of the L1 records, R1(2), with the L2 records R2(1), R2(2), ..., R2(11) in an example where N equals eleven to form the corresponding match scores, MS(2,1), MS(2,2), ..., MS(2,11). The results of the comparison and the match scores calculated are listed in TABLE 8.
In TABLE 8, note that the match score, MS(2,10) for the comparison, C(2,10), is 100 indicating an exact match which exceeds the pairing threshold, Pmatch value of 96 and therefore the bank record R1(2) is paired with the customer record R2(10).
R1(2)-L2 Compare R1 R2 Match Score Paired 1 2 1 <96 NO
2 2 2 <96 NO
3 2 3 <96 NO
4 2 4 <96 NO
2 5 <96 NO
6 2 6 <96 NO
7 2 7 <96 NO
g 2 g <96 NO
g 2 g <96 NO
11 2 11 <g6 NO
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 The comparison process continues by comparing, in comparing steps C(3,1), C(3,2), ..., C(3,11) one of the L1 records, R1(3), with the L2 records R2(1), R2(2), ..., R2(11), excluding, however if desired the paired record R2(10) to form the corresponding match scores, MS(2,1), MS(2,2), ..., MS(2,11), possible excluding MS(2,10) as already being paired. The results of the comparison and the match scores calculated are listed in TABLE 9. In TABLE 9, note that the match score, MS(3,11) for the comparison, C(3,11), is 97 indicating a non-exact match (because the dates are one day different) which exceeds the pairing threshold, Pmatch~ value of 96 and therefore the bank record R1(3) is automatically paired with the customer record 82(11).
81(31-L2 Compare C R1 R2 Match Score Paired 1 3 1 <96 NO
2 3 2 <96 NO
3 3 3 <96 NO
4 3 4 <96 NO
3 5 <96 NO
6 3 6 <96 NO
7 3 7 <96 NO
8 3 8 <96 NO
9 3 9 <96 NO
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 c '- -29-The comparison process continues by comparing, in comparing steps C(4,1), C(4,2), ..., C(4,11) one of the L1 records, R1(4), with the L2 records R2(1), R2(2), ..., R2(11), excluding, however if desired the paired records. The results of the comparison and the match scores calculated will all be below the exclusion threshold since the bank fee of record R1(4) has no corresponding record in L2.
The comparison process continues by comparing, in comparing steps C(1,1), C(1,2), ..., C(1,11) the unpaired one of the L1 records, R1(1), with the remaining unpaired ones of the L2 records R2(1), R2(2), ..., R2(il), excluding the paired records 82(10) and R2(il). Typically, the match score results of the initial comparison are saved so that the comparison is not required to be repeated. The results of the comparison and the match scores calculated are listed in TABLE 10. In TABLE 10, note that the match scores ;;q MS(1,1), MS(1,2) and MS(1,3) of 77, 67, and 57 for the L2 records R2(1), R2(2) and R2(3) all exceed the no-match exclusion threshold, pnomatch- Therefore, the records R2(1), R2(2) and R2(3) are all part of the group presented to a user on a computer screen so that the user can select whether or not to pair one of the L2 customer records R2 ( 1 ) , R2 ( 2 ) and R2 ( 3 ) with the L 1 bank record R1(1).
The likely pairing that would be selected is R1(1) and R2(1) since it appears that a digit-reversing error has appeared in the amount element (9188.00 or 1988.00) of either the bank or the customer record. Once a paring is selected, the user is enabled to correct the customer listing and to form a report that shows the reconciliation.
The process continues with the computer by permitting the user to enter any records into the customer list L2 corresponding to any unpaired records Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 in the bank list. At this time the user would likely add a record corresponding to R1(4), the bank fee. The program displays records to the user in the order that is most probable for pairing records and account reconciliation.
L2 Customer List R2 Tvpe D a Number Amount MatchScore Gr a 1 Deposit 7/5/88 9,188.00 77 YES
2 Deposit 7/6/88 19,906.96 67 YES
3 Deposit 7/4/88 9,733.49 57 YES
4 Deposit 7/7/88 3,829.68 40 NO
Check 7/5/88 3391 214.50 43 NO
6 Check 7/5/88 3392 394.17 43 NO
7 Check 7/5/88 3393 214.34 43 NO
g Check 7/5/88 3389 3,513.74 40 NO
9 Check 7/5/88 3390 4,687.53 40 NO
.
Further details of the method of the present .. invention are embodied in "Computer Program - Appendix A" attached to this specification.
Attorney Docket No.:ZNTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17
1 1 ion of the Match Scores For Two Tvnical _RPCOrds Ri(rl) and R2(r2) The method for calculating match scores, MS, must be precise enough so that the majority of pairingss are completely automatic, but discriminating enough so that spurious matches are not made. In order to make the semi-automatic pairing process (for non-exact matches) efficient, the matches need to be for plausible pairings and need to be presented in a logical order.
To achieve these objectives, is one embodiment, a set of matching rules that produce 38 different match scores have been found to work well in a typical accounting environment. For example, in the "amount"
element comparison, a relatively high match score results if the compared amounts are the same except for a digit transposition. In the "date" element com-parison, experience-based rules for determining how long various records take to clear the bank affect the match score.
Match scores, MS(rl,r2), between a first list, L1, record R1(rl) and a second list, L2, record R2(r2) are calculated as follows:
If Pdate(dl,d2,c1) - 0, MS(rl,r2) - 0.
If Pdate(dl,d2) ~= 0, MS(rl,r2) - (Pdate(dl.d2,c1) Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 pamount(al,a2) + Pnumber(cl,c2))/3 where, Pdate(dl,d2,c1) the Date Score probability value -set as a function of comparing the [Adates in the date elements dl and d2 of R1(rl) and R2(r2), respec-tively, as a function of the number element, cl.
pamount{al,a2) the Amount Score probability value -set as a function of comparing the amounts in the amount elements al and a2 of R1(rl) and R2(r2), respectively.
pnumber(cl,c2) the Number Score probability value -set as a function of comparing the numbers in the number elements cl and c2 of the records R1(rl) and R2(r2), respectively.
MS(rl,r2) - Match Score probability value set as a function of comparing R1(rl) and R2(r2) records.
dl - Date of record R1(rl) from Bank Statement List d2 Date Register = of record R2(r2) from Check List al Amount from record R1{rl) of Bank Statement =
List a2 = Amountfrom R2(r2) of Check Register List cl - Check Number frin recird R1(rl) {or 0 if none) of Bank Statement List c2 = Check Number from record R2(r2) (or 0 if none) of Check Register List Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 _,9~.0~.~9~$
calculation of the Date Score The Date Score, Pdate(dl,d2,c1), is determined as one of the date score probability values, sdi, in TABLE
1 as follows:
Pdate(dl,d2,c1) - sdi where i has one of the values 1, 2, ..., 6.
dd = (dl - d2) sdi = one of the date score probability values determined by TABLE 1.
i = 1, 2, ..., 6 Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 C ~.
-... -20-0<dd<90 _ _ sdl c1~0 -31<dd<190 ~ sd2 i dd<0 ; sd3 or i dd>90 dd<-31 or dd>190 0<dd<5 _ _ sd4 ~ -S<dd<31 sd5 i i cl=0 ;
dd<0 or dd>S
sd6 dd<-5 or dd>31.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 zl2~2~~~~
~.lculation of the Amount Score The Amount Score, Pamount(al,a2), is determined as one of the amount score probability values sai as follows:
Pamount(ai.a2) - sdi where i has on of the values 1, 2, ... 26.
sdi - one of the amount probability values determined by TABLE 2.
i = 1, 2, ..., 26 gl = sign of al g2 = sign of a2 11 = number of digits in al 12 = number of digits in a2 D - number of digits differing in al, a2 (stopping the comparison at the end of the shorter of the two if their lengths differ) T - sum of the arithmetic digit-wise difference between al and a2 (using only as many digits as are present in the shorter number) Attorney Docket No.:INTU7340DEL
WPi/DEL/INTU/7340.001 89/10/19-16:17 c 8 ~g2 gl 1 g2 D = 0 sal sat ;11-12;=1 ! D = 1 sa3 sa4 , , , D>1 ~ say sa6 , 1112 ' , T = 0 sa7 sag ;11-12;>1 ;
T ~ 0 ~ sag sal0 , , , D = 0 call salt , , ;al/a2 -1;<.0 s al3 sal4 D = 1 ' , ;11=12 ; ; T = 0 sal5 sal6 , , , ;al/a2-1;>.06 ; T ~ 0 i i sal7 sal8 , ;al/a2-1;<.06 sal9 sa20 D = 2 i ' T = 0 , , sa21 sa22 , , i ' T # 0 ~~al/a2-1;> .06 ; sa23 sa24 , , D > 2 sa25 sa26 Attorney Docket No.:TNTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 ~" lCi1 ~ at ~ Ori Ot Lne lVUmne1 m:v~~
The Number Score, Pnumber(cl.c2), is determined as one of the number score probability values sni in TABLE 3 as follows:
Pnumber(cl,c2) - sni where i has one of the values 1, 2, ..., 6.
sni - one of the number probability values determined by TABLE 3.
i = 1, 2, ..., 6.
c2 = 0 cl ~ 0 snl i ~ cl = c2 ~ sn2 c2 ~ 0 ;
;, , ~ ; ;cl-C2;=1 i sn3 i ;cl-c2;>1 ~ sn4 c2 = 0 sn5 cl - 0 ;
c2 ~ 0 sn6 Typical probability values for sdi of TABLE 1, sai of TABLE 2, and of sni of TABLE 3 are c,~iven in the following TABLE 4. With the values of TABLE 4, the value of the pairing threshold, Pmatch~ is typically 96 and the value of the exclusion threshold, Pnomatch~ is typically 50.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 sdl=100 sd2=50 sd3=10 sd4=90 sd5=40 sd6=20 sal=60 sat=30 sa3=50 sa4=25 say=40 sa6=20 sa7=50 sag=25 sag=25 sal0=12 sail=100 salt=50 sal3=80 sal4=40 sal5=80 sal6=40 sal7=30 sal8=15 sal9=70 sa20=35 sa21=50 sa22=25 sa23=20 sa24=10 sa25=20 sa26=10 snl=20 sn2=100 sn3=80 sn4=40 sn5=60 sn6=20 An example of the operation of the present invention is given for a bank statement list, L1, in TABLE 5 having the records R1(1), R1(2), R1(3), ..., R1(M). In TABLE 5, only the three L1 records R1(1), R1{2), and R1(3) are explicitly shown. The example of the operation of the present invention also uses a customer list, L2, in TABLE 6 having the records R2(1), R2(2), R2(3), ..., R2(n). In TABLE 6, only the eleven L2 records R2(1), R2(2), ..., R2(11) are explicitly shown.
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 __ -25-L1 -Bank List R1 Tvne Date um r Am n 1 Deposit 7/6/88 1,988.00 2 Check 7/7/88 3386 1000.50 3 Deposit 7/6/88 572.59 4 Fee 7/30/88 2.50 M Check L2- Customer List R2 Type D a Number Am un 1 Deposit 7/5/88 9,188.00 2 Deposit 7/6/88 19,906.96 3 Deposit 7/4/88 9,733.49 4 Deposit 7/7/88 3,829.68 Check 7/5/88 3391 214.50 6 Check 7/5/88 3392 394.17 7 Check 7/5/88 3393 214.34 8 Check 7/5/88 3389 3,513.74 9 Check 7/5/88 3390 4,687.53 Check 7/5/88 3386 1000.50 11 Deposit 7/5/88 572.59 N Check Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 The comparison process begins by comparing, in comparing steps C(1,1), C(1,2), ..., C(1,11) one of the L1 records, R1(1), with the L2 records R2(1), R2(2), ..., R2(11) in an example where N equals eleven to form the corresponding match scores, MS(1,1), MS(1,2), ..., MS(1,11). The results of the comparison and the match scores calculated are listed in TABLE 7.
In TABLE 7, note that none of the match scores exceeds the pairing threshold, Pmatch~ value of 96 and there-fore none of the records of L1 and L2 are paired at this time.
R1(1)- L2 Compare C R1 R2 Match Score Paired 1 1 1 <96 NO
2 1 2 <96 NO
3 1 3 <96 NO
4 1 4 <96 NO
1 5 <96 NO
6 1 6 <96 NO
7 1 7 <96 NO
8 1 8 <96 NO
9 1 9 <96 NO .
1 10 <96 NO
11 1 11 <96 NO
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 -.. _27_ The comparison process continues by comparing, in comparing steps C(2,1), C(2,2), ..., C(2,11) one of the L1 records, R1(2), with the L2 records R2(1), R2(2), ..., R2(11) in an example where N equals eleven to form the corresponding match scores, MS(2,1), MS(2,2), ..., MS(2,11). The results of the comparison and the match scores calculated are listed in TABLE 8.
In TABLE 8, note that the match score, MS(2,10) for the comparison, C(2,10), is 100 indicating an exact match which exceeds the pairing threshold, Pmatch value of 96 and therefore the bank record R1(2) is paired with the customer record R2(10).
R1(2)-L2 Compare R1 R2 Match Score Paired 1 2 1 <96 NO
2 2 2 <96 NO
3 2 3 <96 NO
4 2 4 <96 NO
2 5 <96 NO
6 2 6 <96 NO
7 2 7 <96 NO
g 2 g <96 NO
g 2 g <96 NO
11 2 11 <g6 NO
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 The comparison process continues by comparing, in comparing steps C(3,1), C(3,2), ..., C(3,11) one of the L1 records, R1(3), with the L2 records R2(1), R2(2), ..., R2(11), excluding, however if desired the paired record R2(10) to form the corresponding match scores, MS(2,1), MS(2,2), ..., MS(2,11), possible excluding MS(2,10) as already being paired. The results of the comparison and the match scores calculated are listed in TABLE 9. In TABLE 9, note that the match score, MS(3,11) for the comparison, C(3,11), is 97 indicating a non-exact match (because the dates are one day different) which exceeds the pairing threshold, Pmatch~ value of 96 and therefore the bank record R1(3) is automatically paired with the customer record 82(11).
81(31-L2 Compare C R1 R2 Match Score Paired 1 3 1 <96 NO
2 3 2 <96 NO
3 3 3 <96 NO
4 3 4 <96 NO
3 5 <96 NO
6 3 6 <96 NO
7 3 7 <96 NO
8 3 8 <96 NO
9 3 9 <96 NO
Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 c '- -29-The comparison process continues by comparing, in comparing steps C(4,1), C(4,2), ..., C(4,11) one of the L1 records, R1(4), with the L2 records R2(1), R2(2), ..., R2(11), excluding, however if desired the paired records. The results of the comparison and the match scores calculated will all be below the exclusion threshold since the bank fee of record R1(4) has no corresponding record in L2.
The comparison process continues by comparing, in comparing steps C(1,1), C(1,2), ..., C(1,11) the unpaired one of the L1 records, R1(1), with the remaining unpaired ones of the L2 records R2(1), R2(2), ..., R2(il), excluding the paired records 82(10) and R2(il). Typically, the match score results of the initial comparison are saved so that the comparison is not required to be repeated. The results of the comparison and the match scores calculated are listed in TABLE 10. In TABLE 10, note that the match scores ;;q MS(1,1), MS(1,2) and MS(1,3) of 77, 67, and 57 for the L2 records R2(1), R2(2) and R2(3) all exceed the no-match exclusion threshold, pnomatch- Therefore, the records R2(1), R2(2) and R2(3) are all part of the group presented to a user on a computer screen so that the user can select whether or not to pair one of the L2 customer records R2 ( 1 ) , R2 ( 2 ) and R2 ( 3 ) with the L 1 bank record R1(1).
The likely pairing that would be selected is R1(1) and R2(1) since it appears that a digit-reversing error has appeared in the amount element (9188.00 or 1988.00) of either the bank or the customer record. Once a paring is selected, the user is enabled to correct the customer listing and to form a report that shows the reconciliation.
The process continues with the computer by permitting the user to enter any records into the customer list L2 corresponding to any unpaired records Attorney Docket No.:INTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17 in the bank list. At this time the user would likely add a record corresponding to R1(4), the bank fee. The program displays records to the user in the order that is most probable for pairing records and account reconciliation.
L2 Customer List R2 Tvpe D a Number Amount MatchScore Gr a 1 Deposit 7/5/88 9,188.00 77 YES
2 Deposit 7/6/88 19,906.96 67 YES
3 Deposit 7/4/88 9,733.49 57 YES
4 Deposit 7/7/88 3,829.68 40 NO
Check 7/5/88 3391 214.50 43 NO
6 Check 7/5/88 3392 394.17 43 NO
7 Check 7/5/88 3393 214.34 43 NO
g Check 7/5/88 3389 3,513.74 40 NO
9 Check 7/5/88 3390 4,687.53 40 NO
.
Further details of the method of the present .. invention are embodied in "Computer Program - Appendix A" attached to this specification.
Attorney Docket No.:ZNTU7340DEL
WP1/DEL/INTU/7340.001 89/10/19-16:17
Claims (26)
1. A method of reconciling in a computer a first list formed of a first number of first records in the computer with a second list formed of a second number of second records in the computer where, except for errors or omissions, each of said first records is identical to a corresponding one of said second records, the method comprising:
for each one of said first records, comparing said one of said first records with one or more of said second records to determine match scores, one match score for each compared one of said second records, each match score designating the probability said one of said first records corresponds to the compared one of said second records, for each one of said first records having a match score exceeding a predetermined pairing threshold, pairing said one of said first records with the compared one of said second records whereby said one of said first records and the compared one of said second records are reconciled, for each one of said first records not having a match score exceeding said predetermined pairing threshold, matching said one of said first records with a group of second records where said group of second records is determined based upon the magnitudes of corresponding match scores for said second records, accepting or rejecting the pairing of said one of said first records with one of said second records in said group whereby, upon accepting, said one of said first records and the compared one said second records are reconciled.
for each one of said first records, comparing said one of said first records with one or more of said second records to determine match scores, one match score for each compared one of said second records, each match score designating the probability said one of said first records corresponds to the compared one of said second records, for each one of said first records having a match score exceeding a predetermined pairing threshold, pairing said one of said first records with the compared one of said second records whereby said one of said first records and the compared one of said second records are reconciled, for each one of said first records not having a match score exceeding said predetermined pairing threshold, matching said one of said first records with a group of second records where said group of second records is determined based upon the magnitudes of corresponding match scores for said second records, accepting or rejecting the pairing of said one of said first records with one of said second records in said group whereby, upon accepting, said one of said first records and the compared one said second records are reconciled.
2. The method of reconciling the first list and the second list of claim 1 wherein said accepting step is performed under user control.
3. The method of reconciling the first list and the second list of claim 1 further including, for one or more of said first records not paired with a second record, adding under user control a new second record to said second list corresponding to one of said first records whereby said one of said first records and the compared one of said second records are reconciled.
4. The method of reconciling the first list and the second list of claim 1 wherein said matching step is performed by determining said group to include only ones of said second records having match scores between said pairing threshold and an exclusion threshold.
5. The method of reconciling the first list and the second list of claim 1 wherein said matching step is performed by determining said group to include only a limited number of ones of said second records and to include ones of said second records having match scores closest to said pairing threshold.
6. The method of reconciling the first list and the second list of claim 1 wherein, said first list L1 has N first records designated R1(1), R1(2), ..., R1(r1), ..., R1(N); where each one of said records R1(r1) is formed of P elements E1(1), E1(2), E1(3), ..., E1(e), ...,E1 (P), said second list L2 has M second records designated R2(1), R2(2) ,..., R2 (r2), ..., R2 (M); where each one of said records R2(r2) is formed of P elements E2(1), E2(2), E2(3), ..., E2(e), ..., E2(P), said comparing step is performed for each first record R1(r1) by Q element comparing steps C(q), for q from 1,2, ..., Q, whereby for each first record R1(r1) each of the first elements E1(e), for e from 1, 2, ...
,~U, is compared with each of the second elements E2(e), for e from 1, 2, ..., U, respectively, for the compared one of said second records R2(r2).
,~U, is compared with each of the second elements E2(e), for e from 1, 2, ..., U, respectively, for the compared one of said second records R2(r2).
7. The method of reconciling the first list and the second list of claim 6 wherein the results of each element comparing step C(q) is a probability value P(1), for q from 1, 2, ..., Q, and where said match score is the SUM P(q) for q from 1, 2, ..., Q.
8. The method of reconciling the first list and the second list of claim 6 wherein said first list is a bank statement for a checking account, said second list is a customer's account information, and said elementsinclude a date element, a check element and an amount element.
9. The method of reconciling the first list and the second list of claim 8 wherein said element comparing includes comparing to determine if the amount in the amount element of a first record R1(r1) is within an amount range of an amount in a corresponding amount element of a second record R2(r2).
10. The method of reconciling the first list and the second list of claim 9 wherein said element comparing for each first record R1(r1) with a second record R2(r2) includes, setting a probability value P date as a function of whether the date in the date element of said first record is within a date range of a date in a corresponding date element of said second record, setting a probability value P amount as a function of whether the amount in the amount element of said first record is within a amount rage of a amount in a corresponding amount element of said second record, setting a probability value P number as a function of whether the number in the number element of said first record is the same as the number in a corresponding number element of said second record, forming the match score MS equal to the sum of P date, P amount, and P number.
11. The method of reconciling the first list and the second list of Claim 9 wherein said element comparing for each first record R1(r1) with a second record R2(r2) includes, setting a Date Score, P date(d1,d2,C1), probability value as a function of comparing the dates in the date elements d1 and d2 of R1(r1) and R2(r2), respectively, as a function of the number element, c1, of record R1(r1), setting an Amount Score, P amount(a1,a2), probability value as a function of comparing the amounts in the amount elements a1 and a2 of records R1(r1) and R2(r2), respectively, setting a Number Score, P number(c1,c2), probability value as a function of comparing the numbers in the number elements c1 and c2 of the records R1(r1) and R2(r2), respectively, forming the match score MS(r1,r2) as follows:
if P date(d1,d2,c1)=0, MS(r1,r2)=0, if P date (d1, d2) =0, MS (r1, r2) = (P date (d1, d2, C1)+P amount (a1, a2)+P number(C1, C2))/3.
if P date(d1,d2,c1)=0, MS(r1,r2)=0, if P date (d1, d2) =0, MS (r1, r2) = (P date (d1, d2, C1)+P amount (a1, a2)+P number(C1, C2))/3.
12. The method of reconciling the first list and the second list of claim 11 wherein the Date Score, P date(d1,d2,C1), is determined as one of the date score probability values sd i where i has one of the values 1, 2, ..., 6 and where dd equals (d1-d2) as follows:
13. The method of reconciling the first list and the second list of claim 11 wherein the Amount Score, P amount (a1, a2), is determined as one of the amount score probability values sa i where i has one of the values 1, 2, ..., 26, where g1 equals the sign of a1, where g2 equals the sign of a2, where l1 equals the number of digits in a1, where 12 equals the number of digits in a2, where D equals the number of digits differing in a1 and a2, and where T equals the sum of the arithmetic digit-wise difference between a1 and a2 as follows:
14. The method of reconciling the first list and the second list of claim 11 wherein the Number Score, P number (c1, c2), is determined as one of the number score probability values sn i, where i has one of the values 1, 2, ..., 6, as follows:
15. A method of reconciling in a computer a first list formed of a first number of first records in the computer with a second list formed of a second number of second records in the computer where, said first list L1 has N first records designated R1(1), R1(2), ..., R1(r1), ..., R1(N); where each one of said records R1(r1) is formed of P elements E1(1), E1(2), E1(3), ..., E1(e), ..., E1(P), said second list L2 has M second records designated R2(1), R2(2), ..., R2(r2), ..., R2 (M); where each one of said records R2(r2) is formed of P elements E2(1), E2(2), E2(3), ..., E2(e) , ..., E2 (P), for each one of said first records, comparing said one of said first records with one or more of said second records to determine match scores, one match score for each compared one of said second records, each match score designating the probability said one of said first records corresponds to the compared one of said second records, and wherein said first list is a statement for a first listing of an account, said second list is a second listing of said account, and said elements include a date element and an amount element, said comparing step is performed for each first record R1(r1) by Q element comparing steps C(q), for q from 1, 2, ... Q, whereby for each first record R1(r1) each of the first elements E1(e), for a from 1, 2, ...
, U, is compared with each of the second elements E2(e), for e from 1, 2, ..., U, respectively, for the compared one of said second records R2(r2), for each one of said first records having a match score exceeding a predetermined pairing threshold, pairing said one of said first records with the compared one of said second records whereby said one of said first records and the compared one of said second records are reconciled, for each one of said first records not having a match score exceeding said predetermined pairing threshold, matching said one of said first records with a group of second records where said group of second records is determined based upon the magnitudes of corresponding match scores for said second records, accepting or rejecting the pairing of said one of said first records with one of said second records in said group whereby, upon accepting, said one of said first records and the compared one said second records are reconciled.
, U, is compared with each of the second elements E2(e), for e from 1, 2, ..., U, respectively, for the compared one of said second records R2(r2), for each one of said first records having a match score exceeding a predetermined pairing threshold, pairing said one of said first records with the compared one of said second records whereby said one of said first records and the compared one of said second records are reconciled, for each one of said first records not having a match score exceeding said predetermined pairing threshold, matching said one of said first records with a group of second records where said group of second records is determined based upon the magnitudes of corresponding match scores for said second records, accepting or rejecting the pairing of said one of said first records with one of said second records in said group whereby, upon accepting, said one of said first records and the compared one said second records are reconciled.
16. The method of reconciling the first list and the second list of claim 15 wherein said element comparing includes string match comparing to determine if an element of a first record R1(r1) is the same or as similar to a corresponding element of a second record R2(r2).
17. The method of reconciling the first list and the second list of claim 16 wherein said string match comparing includes comparing to detect added characters.
18. The method of reconciling the first list and the second list of claim 16 wherein said string match comparing includes comparing to detect missing characters.
19. The method of reconciling the first list and the second list of claim 16 wherein said string match comparing includes comparing to detect transposition of characters.
20. The method of reconciling the first list and the second list of claim 15 wherein said element comparing includes comparing to determine if the date in the date element of a first record R1(r1) is within a date range of date in a corresponding date element of a second record R2(r2).
21. A method of reconciling in a computer a first list formed of a first number of first records in the computer with a second list formed of a second number of second records in the computer where, except for errors or omissions, each of said first records is identical to a corresponding one of said second records, the method comprising, for each one of said first records, comparing said one of said first records with one or more of said second records to determine match scores, one match score for each compared one of said second records, each match score designating the probability said one of said first records corresponds to the compared one of said second records, for each one of said first records having a match score exceeding a predetermined pairing threshold, pairing said one of said first records with the compared one of said second records whereby said one of said first records and the compared one of said second records are reconciled, for each one of said first records having a match score between said predetermined pairing threshold and an exclusion threshold, matching said one of said first records with a group of second records where said group of second records is determined based upon the magnitudes of corresponding match scores for said second records, displaying to a user on a computer terminal said group of second records in an order based upon the magnitudes of corresponding match scores for said second records whereby the user is presented with records for pairing in the order of most likely correspondence of records, accepting or rejecting the pairing of said one of said first records with one of said second records in said group under user control whereby, upon accepting, said one of said first records and the compared one said second records are reconciled.
22. The method of reconciling the first list and the second list of claim 21 further including, for one or more of said first records not paired with a second record, adding under user control a new second record to said second list corresponding to one of said first records whereby said one of said first records and the compared one of said second records are reconciled.
23. The method of reconciling the first list and the second list of claim 21 further including generating a report summarizing the reconciliation results including a listing of unpaired records and balances of the first list and the second list.
24. The method of reconciling the first list and the second list of claim 21 further including the step of updating the second list to correct errors discovered as a result of reconciliation.
25. The method of reconciling the first list and the second list of claim 21 further including the step of updating the second list to add records as a result of reconciliation.
26. The method of reconciling the first list and the second list of claim 21 further including the step of updating the second list to indicate records in the second list paired with records in the first list as a result of reconciliation.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US424,006 | 1989-10-19 | ||
| US07/424,006 US5134564A (en) | 1989-10-19 | 1989-10-19 | Computer aided reconfiliation method and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2027948A1 CA2027948A1 (en) | 1991-04-20 |
| CA2027948C true CA2027948C (en) | 2000-01-25 |
Family
ID=23681076
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002027948A Expired - Fee Related CA2027948C (en) | 1989-10-19 | 1990-10-18 | Computer aided reconciliation method and apparatus |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US5134564A (en) |
| CA (1) | CA2027948C (en) |
Families Citing this family (94)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5519606A (en) * | 1992-01-21 | 1996-05-21 | Starfish Software, Inc. | System and methods for appointment reconciliation |
| US7299240B1 (en) | 1992-04-10 | 2007-11-20 | Intellisync Corporation | Method for translating computer data from one record structure to another |
| US5586313A (en) * | 1993-02-12 | 1996-12-17 | L.I.D.P. Consulting Services, Inc. | Method for updating a file |
| US5337263A (en) * | 1993-06-15 | 1994-08-09 | Patermaster John J | Simplified checkbook balancing computer system |
| US5684990A (en) * | 1995-01-11 | 1997-11-04 | Puma Technology, Inc. | Synchronization of disparate databases |
| US5842174A (en) * | 1995-04-10 | 1998-11-24 | Yanor; David Patrick | Telephone billing analyzer |
| US6405218B1 (en) | 1996-11-13 | 2002-06-11 | Pumatech, Inc. | Synchronizing databases |
| US6212529B1 (en) * | 1996-11-13 | 2001-04-03 | Puma Technology, Inc. | Synchronization of databases using filters |
| US5943676A (en) | 1996-11-13 | 1999-08-24 | Puma Technology, Inc. | Synchronization of recurring records in incompatible databases |
| US7302446B1 (en) | 1996-11-13 | 2007-11-27 | Intellisync Corporation | Synchronizing databases |
| US7013315B1 (en) | 1996-11-13 | 2006-03-14 | Intellisync Corporation | Synchronization of databases with record sanitizing and intelligent comparison |
| US7490112B1 (en) | 1997-04-15 | 2009-02-10 | Intellisync Corporation | System and methods for synchronizing information among disparate datasets |
| US7403916B1 (en) * | 1997-06-02 | 2008-07-22 | Microsoft Corporation | Method and system for correcting payee names and adjusting an account balance for a financial statement |
| US5903881A (en) * | 1997-06-05 | 1999-05-11 | Intuit, Inc. | Personal online banking with integrated online statement and checkbook user interface |
| US7263527B1 (en) * | 1997-08-11 | 2007-08-28 | International Business Machines Corporation | Grouping selected transactions in account ledger |
| US6925477B1 (en) | 1998-03-31 | 2005-08-02 | Intellisync Corporation | Transferring records between two databases |
| US6825940B1 (en) * | 1998-07-01 | 2004-11-30 | Ncr Corporation | Method of processing documents in an image-based document processing system and an apparatus therefor |
| US7007003B1 (en) | 1998-12-04 | 2006-02-28 | Intellisync Corporation | Notification protocol for establishing synchronization mode for use in synchronizing databases |
| US7734541B2 (en) * | 1998-12-08 | 2010-06-08 | Yodlee.Com, Inc. | Interactive funds transfer interface |
| US7451103B1 (en) | 1999-03-29 | 2008-11-11 | Citibank, N.A. | System and method for centralized automated reconciliation of custody accounts |
| US6401104B1 (en) * | 1999-07-03 | 2002-06-04 | Starfish Software, Inc. | System and methods for synchronizing datasets using cooperation among multiple synchronization engines |
| US6446048B1 (en) | 1999-09-03 | 2002-09-03 | Intuit, Inc. | Web-based entry of financial transaction information and subsequent download of such information |
| US7904317B1 (en) | 1999-10-14 | 2011-03-08 | The TriZetto Group | Method and apparatus for repricing a reimbursement claim against a contract |
| US6879959B1 (en) * | 2000-01-21 | 2005-04-12 | Quality Care Solutions, Inc. | Method of adjudicating medical claims based on scores that determine medical procedure monetary values |
| US7403917B1 (en) * | 2000-03-24 | 2008-07-22 | Intuit Inc. | Reconciling combinations of transactions |
| AU2005202263A1 (en) * | 2000-08-25 | 2005-06-09 | American Express Travel Related Services Company, Inc. | System and method for account reconciliation |
| MXPA03001652A (en) * | 2000-08-25 | 2004-04-02 | American Express Travel Relate | System and method for account reconciliation. |
| AU2002225659A1 (en) | 2000-11-21 | 2002-06-03 | Myhealthbank, Inc. | Health plan management method and apparatus |
| US7359920B1 (en) | 2001-04-18 | 2008-04-15 | Intellisync Corporation | Communication protocol for synchronization of personal information management databases |
| US7240028B1 (en) * | 2002-03-15 | 2007-07-03 | Microsoft Corporation | Automated financial register reconciliation in a combined user interface |
| US7539634B2 (en) * | 2002-06-27 | 2009-05-26 | Oracle International Corporation | Account reconciliation system and method |
| US20040064404A1 (en) * | 2002-10-01 | 2004-04-01 | Menachem Cohen | Computer-based method for automatic remote coding of debtor credit databases with bankruptcy filing information |
| AU2003294556A1 (en) * | 2002-12-09 | 2004-06-30 | Accubalance Corporation | Personal digital account register |
| US20040187108A1 (en) * | 2003-02-21 | 2004-09-23 | Knowles W. Jeffrey | Method of scheduling and event processing in computer operating system |
| US20040167863A1 (en) * | 2003-02-21 | 2004-08-26 | Knowles W. Jeffrey | System and method of transferring data through transaction process |
| US7729990B2 (en) * | 2003-05-28 | 2010-06-01 | Stephen Michael Marceau | Check image access system |
| US20050027648A1 (en) * | 2003-07-29 | 2005-02-03 | Knowles W. Jeffrey | System and method of account reconciliation for electronic transactions |
| US8121913B2 (en) * | 2003-08-19 | 2012-02-21 | Swiss Reinsurance Company Ltd. | Architecture for account reconciliation |
| US7289974B2 (en) * | 2003-09-05 | 2007-10-30 | Sap Ag | System and method for data reconciliation |
| US20050097046A1 (en) | 2003-10-30 | 2005-05-05 | Singfield Joy S. | Wireless electronic check deposit scanning and cashing machine with web-based online account cash management computer application system |
| US7797216B2 (en) * | 2004-01-12 | 2010-09-14 | Intuit Inc. | Method and system for backfilling transactions in an account |
| US8768729B2 (en) | 2004-10-14 | 2014-07-01 | Trizetto Corporation | System and method for using a first electronic representation of contract terms for generating a second electronic representation of the contract terms |
| US20060085327A1 (en) * | 2004-10-15 | 2006-04-20 | Green Gary F | Systems and methods for using credit card in government purchasing transactions |
| US20060229958A1 (en) * | 2005-04-06 | 2006-10-12 | Anthony Sergio | System, method, and computer program product for reconciling financial data from multiple sources |
| US7921043B2 (en) * | 2005-07-28 | 2011-04-05 | Intuit Inc. | Intelligent reconciliation of database transfer errors |
| US7526486B2 (en) | 2006-05-22 | 2009-04-28 | Initiate Systems, Inc. | Method and system for indexing information about entities with respect to hierarchies |
| US20080033750A1 (en) * | 2006-06-02 | 2008-02-07 | The Trizetto Group, Inc. | Enhanced systems and methods for processing of healthcare information |
| EP2030134A4 (en) * | 2006-06-02 | 2010-06-23 | Initiate Systems Inc | A system and method for automatic weight generation for probabilistic matching |
| US7698268B1 (en) * | 2006-09-15 | 2010-04-13 | Initiate Systems, Inc. | Method and system for filtering false positives |
| US8356009B2 (en) * | 2006-09-15 | 2013-01-15 | International Business Machines Corporation | Implementation defined segments for relational database systems |
| US7685093B1 (en) * | 2006-09-15 | 2010-03-23 | Initiate Systems, Inc. | Method and system for comparing attributes such as business names |
| US8708227B1 (en) | 2006-10-31 | 2014-04-29 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of checks |
| US7873200B1 (en) | 2006-10-31 | 2011-01-18 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of checks |
| US8359339B2 (en) * | 2007-02-05 | 2013-01-22 | International Business Machines Corporation | Graphical user interface for configuration of an algorithm for the matching of data records |
| US10380559B1 (en) | 2007-03-15 | 2019-08-13 | United Services Automobile Association (Usaa) | Systems and methods for check representment prevention |
| US8515926B2 (en) | 2007-03-22 | 2013-08-20 | International Business Machines Corporation | Processing related data from information sources |
| WO2008121170A1 (en) * | 2007-03-29 | 2008-10-09 | Initiate Systems, Inc. | Method and system for parsing languages |
| US8423514B2 (en) * | 2007-03-29 | 2013-04-16 | International Business Machines Corporation | Service provisioning |
| WO2008121700A1 (en) * | 2007-03-29 | 2008-10-09 | Initiate Systems, Inc. | Method and system for managing entities |
| US8429220B2 (en) * | 2007-03-29 | 2013-04-23 | International Business Machines Corporation | Data exchange among data sources |
| US7856385B2 (en) * | 2007-09-07 | 2010-12-21 | National Default Exchange Lp | System and method for management and processing of bankruptcy claims and payments |
| BRPI0817530B1 (en) * | 2007-09-28 | 2020-02-04 | Initiate Systems Inc | method and system for processing data records in multiple languages and computer-readable storage media |
| US9058512B1 (en) | 2007-09-28 | 2015-06-16 | United Services Automobile Association (Usaa) | Systems and methods for digital signature detection |
| JP5306360B2 (en) | 2007-09-28 | 2013-10-02 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Method and system for analysis of systems for matching data records |
| US8713434B2 (en) * | 2007-09-28 | 2014-04-29 | International Business Machines Corporation | Indexing, relating and managing information about entities |
| US8738500B1 (en) * | 2007-10-12 | 2014-05-27 | United Services Automobile Associates (USAA) | Systems and methods for replacing critical paper communications with electronic media in financial service industry |
| US9159101B1 (en) | 2007-10-23 | 2015-10-13 | United Services Automobile Association (Usaa) | Image processing |
| US9892454B1 (en) | 2007-10-23 | 2018-02-13 | United Services Automobile Association (Usaa) | Systems and methods for obtaining an image of a check to be deposited |
| US10380562B1 (en) | 2008-02-07 | 2019-08-13 | United Services Automobile Association (Usaa) | Systems and methods for mobile deposit of negotiable instruments |
| US8374963B1 (en) | 2008-02-14 | 2013-02-12 | United Services Automobile Association (Usaa) | Method and system for electronic checking |
| US20090240611A1 (en) * | 2008-03-21 | 2009-09-24 | Augustine Nancy L | Systems and methods for displaying a data modification timeline |
| US10504185B1 (en) | 2008-09-08 | 2019-12-10 | United Services Automobile Association (Usaa) | Systems and methods for live video financial deposit |
| US8103561B2 (en) * | 2008-11-14 | 2012-01-24 | Oracle International Corporation | Reconciling financial transactions |
| US8108273B2 (en) * | 2009-02-05 | 2012-01-31 | Oracle International Corporation | Replicating data in financial systems |
| US20100211485A1 (en) * | 2009-02-17 | 2010-08-19 | Augustine Nancy L | Systems and methods of time period comparisons |
| US8452689B1 (en) | 2009-02-18 | 2013-05-28 | United Services Automobile Association (Usaa) | Systems and methods of check detection |
| US10956728B1 (en) | 2009-03-04 | 2021-03-23 | United Services Automobile Association (Usaa) | Systems and methods of check processing with background removal |
| US9779392B1 (en) | 2009-08-19 | 2017-10-03 | United Services Automobile Association (Usaa) | Apparatuses, methods and systems for a publishing and subscribing platform of depositing negotiable instruments |
| US8977571B1 (en) | 2009-08-21 | 2015-03-10 | United Services Automobile Association (Usaa) | Systems and methods for image monitoring of check during mobile deposit |
| US8699779B1 (en) | 2009-08-28 | 2014-04-15 | United Services Automobile Association (Usaa) | Systems and methods for alignment of check during mobile deposit |
| US20110184775A1 (en) * | 2010-01-26 | 2011-07-28 | Bank Of America Corporation | Automated Routing Process |
| US9129340B1 (en) | 2010-06-08 | 2015-09-08 | United Services Automobile Association (Usaa) | Apparatuses, methods and systems for remote deposit capture with enhanced image detection |
| US8756075B1 (en) | 2011-05-18 | 2014-06-17 | Trizetto Corporation | System and method for processing payment bundles |
| US10296976B1 (en) | 2011-09-23 | 2019-05-21 | Cognizant Trizetto Software Group, Inc. | System and method for calculating estimated payment based on partial coding data |
| US10380565B1 (en) | 2012-01-05 | 2019-08-13 | United Services Automobile Association (Usaa) | System and method for storefront bank deposits |
| US10318923B1 (en) | 2012-08-01 | 2019-06-11 | Cognizant Trizetto Software Group, Inc. | Payment assurance and claim pre-validation |
| US10552810B1 (en) | 2012-12-19 | 2020-02-04 | United Services Automobile Association (Usaa) | System and method for remote deposit of financial instruments |
| US11138578B1 (en) | 2013-09-09 | 2021-10-05 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of currency |
| US9286514B1 (en) | 2013-10-17 | 2016-03-15 | United Services Automobile Association (Usaa) | Character count determination for a digital image |
| US9727664B2 (en) | 2014-05-06 | 2017-08-08 | International Business Machines Corporation | Grouping records in buckets distributed across nodes of a distributed database system to perform comparison of the grouped records |
| US10402790B1 (en) | 2015-05-28 | 2019-09-03 | United Services Automobile Association (Usaa) | Composing a focused document image from multiple image captures or portions of multiple image captures |
| JP6923336B2 (en) * | 2016-03-29 | 2021-08-18 | 株式会社オービック | Bulk deposit processing device, batch deposit processing method, and batch deposit processing program |
| US11030752B1 (en) | 2018-04-27 | 2021-06-08 | United Services Automobile Association (Usaa) | System, computing device, and method for document detection |
| US11900755B1 (en) | 2020-11-30 | 2024-02-13 | United Services Automobile Association (Usaa) | System, computing device, and method for document detection and deposit processing |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4047154A (en) * | 1976-09-10 | 1977-09-06 | Rockwell International Corporation | Operator interactive pattern processing system |
| US4417136A (en) * | 1981-08-05 | 1983-11-22 | Ncr Canada Ltd - Ncr Canada Ltee | Method and apparatus for improving bank operation productivity |
| US4523330A (en) * | 1982-12-23 | 1985-06-11 | Ncr Canada Ltd - Ncr Canada Ltee | Banking system and method |
| US4737911A (en) * | 1985-06-07 | 1988-04-12 | Nelson H. Shapiro | Process for electronically maintaining financial records, especially for checkbook balancing and rectification |
| US4813077A (en) * | 1986-07-30 | 1989-03-14 | Scan-Optics, Inc. | Sales transaction record processing system and method |
| US4866611A (en) * | 1987-01-29 | 1989-09-12 | International Business Machines Corporation | Method for automatically reconciling entries on two copies of independently maintained electronic calendars |
-
1989
- 1989-10-19 US US07/424,006 patent/US5134564A/en not_active Expired - Lifetime
-
1990
- 1990-10-18 CA CA002027948A patent/CA2027948C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| US5134564A (en) | 1992-07-28 |
| CA2027948A1 (en) | 1991-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2027948C (en) | Computer aided reconciliation method and apparatus | |
| US5727249A (en) | Automated payment system and method | |
| US7117171B1 (en) | System and method for making a payment from a financial account | |
| US8628116B2 (en) | Transparent deposit carrier having a plurality of pockets | |
| US7107244B2 (en) | Bill payment system and method with merchant information | |
| US7461775B2 (en) | Apparatus and methods for processing misread or miskeyed magnetic indicia | |
| US8510224B2 (en) | Database for check risk decisions populated with check activity data from banks of first deposit | |
| US20140114821A1 (en) | Apparatus for consolidating financial transaction information | |
| US6059185A (en) | Automated system and method for improved check processing | |
| US7020639B1 (en) | Check verification system and method | |
| US7801779B2 (en) | Cash under and cash over adjustments to receipt totals for bank deposits | |
| CN112035406A (en) | Conversion processing method of paper capital data file | |
| US20230298111A9 (en) | Systems and Methods for Improved Transaction Reconciliation | |
| US20220058593A1 (en) | Auto reconciliation of business payments with bank data and third-party commission invoices | |
| US20080021830A1 (en) | System and method of processing accounts receivable and banking integration | |
| JP2965944B2 (en) | Funding processing system, funding processing method, and recording medium recording funding processing execution program | |
| EP1096437A2 (en) | Check verification system and method | |
| JP3357044B1 (en) | Computer-based financial accounting processing method and program | |
| JP2587749C (en) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |