Abstract:
Disclosed is a generalized method for automated account reconciliation capable of matching transactions in one accounting dataset to transactions in another accounting dataset with little initial data preparation. The method is highly flexible in that it does not require source data in a particular format, can accept both structured and unstructured (e.g. Descriptive text) data as input, is not domain- or language-dependent, and requires little to no training or user-provided heuristics. The method is also adjustable depending on a user&#39;s tolerance of error. Based on probability and information theory, computational linguistics, and statistics, the method can complete accounting reconciliation problems in significantly less time than is possible manually, and with just as high accuracy. Especially for large reconciliation problems, the method can save an overwhelming portion of the cost associated with this kind of task in the past.

Description:
BACKGROUND OF THE INVENTION 
       [0001]    1. Field of the Invention 
         [0002]    The present invention relates to a generalized method for automated account reconciliation which can be used to match transactions in one accounting dataset to transactions in another accounting dataset. It is based on advanced machine learning (or artificial intelligence) and statistical algorithms and can be applied to data in any format. 
         [0003]    2. Description of the Prior Art 
         [0004]    U.S. Pat. No. 7,895,094 describes a global account reconciliation tool which provides standard templates for entering transaction and account data, allowing for more ready discovery of open (i.e., unreconciled) accounting items. Once data is brought into these templates, the tool provides for either (1) auto-matching functionality relying on user-defined business rules, or (2) manual reconciliation. 
         [0005]    This tool is limited to working with data which has been fitted into the templates it embodies, and any automation of the reconciliation process is not inherent to the tool, but relies on heuristics provided by the user. For the user, the process of installing and learning how to use the tool, and defining business rules could be time-consuming enough to outweigh the efficiencies of automated reconciliation. Furthermore, the accuracy of reconciliation results depends heavily on the suitability of the heuristics embodied in the user-provided business rules. This in turn makes the tool dependent on the expertise of the user in formulating heuristics. 
         [0006]    U.S. Pat. No. 7,970,668 discloses a system and method for automated comprehensive reconciliation processing. This invention includes the maintenance of an automated checklist of the various reconciliation steps, enabling maintenance of an audit trail and generation of metrics. 
         [0007]    This method does not automate the actual matching of items in one dataset to items in another, but instead is essentially a tracking system allowing an analyst to ensure that data is complete and that all necessary reconciliation steps are duly completed. The most time-consuming part of account reconciliation, for datasets of any reasonable size (upwards of thousands of records), is the process of actually matching data from one dataset to another. Therefore, for such datasets, this method is unlikely to achieve significant efficiency and time-saving in the area where it matters most. 
         [0008]    U.S. Pat. No. 8,019,739 discloses a method and system for an on line-like account processing and management. This method processes otherwise batch files using a pseudo-on line transaction processing (OPT) technique and is geared towards increasing the availability of data. 
         [0009]    Again, this method does not automate the actual matching of items from disparate datasets, which for reconciliation problems of any significant size is the most time-consuming and labor-intensive part of the process, even if data is available real-time. Therefore, for such datasets, this method is unlikely to achieve significant efficiency and time-saving in the area where it matters most. 
       SUMMARY OF THE INVENTION 
       [0010]    The present invention is a computer-implemented generalized method for automated account reconciliation capable of matching transactions in one accounting dataset to transactions in another accounting dataset. It does not rely on data being provided in any specific template or format, and can be used with structured data (for example, categorical or continuous data provided in the fields of a database or spreadsheet) or unstructured data (for example, text data such as ‘free-form’ transaction descriptions, in any human language, which might also be provided in the fields of a database or spreadsheet). Using principles from information theory, probability theory, natural language processing, machine learning (or artificial intelligence), data mining, record linkage, candidate matches between items (transactions) in one dataset and those in another dataset are identified. Using principles from statistics and probability theory, candidates are then either ruled in, if the similarity between items in a pair is too high to have occurred by chance, or ruled out in other cases. The present invention can be used to automate matching that is would otherwise be done manually, saving most of the labor for large reconciliation projects. The quality of manually-performed reconciliation essentially cannot be known without reviewing the manual output and measuring against some benchmark, and additionally it is highly unlikely that human-performed reconciliation would ever be error-free. Since the present invention for automated reconciliation is based on principles from statistics, on the other hand, it is possible to judge in advance the likely error rate, since these are specified in the confidence threshold which is one of the settings in the present invention. A system based on this invention can therefore be calibrated to achieve 95%, 99%, or any other desired accuracy level. 
         [0011]    It is therefore a primary object of the present invention to provide a generalized method for automated account reconciliation which will significantly streamline the process of reconciling financial accounts at a significant savings. 
         [0012]    It is another object of the present invention to provide a generalized method for automated account reconciliation which can easily be adapted to use with transactional data in different formats, to eliminate the necessity for a user of the invention to manipulate data into a required format before it can be reconciled, saving the user of the invention time in its use. 
         [0013]    It is a further object of the present invention to provide a generalized method for automated account reconciliation where the user of the invention is not required to develop heuristics or business rules in order for automated account reconciliation to be made possible, again saving the user of the invention time in its use, and eliminating requirements for user expertise. 
         [0014]    It is still a further object of the present invention to provide a generalized method for automated account reconciliation which can deal with unstructured data, in cases where key information on each transaction may be included within a transaction description rather than in structured data fields; the invention does not make any presumptions about which human language or character set (e.g. English, French, Russian) is used to encode the unstructured data. 
         [0015]    It is still a further object of the present invention to provide a generalized method for automated account reconciliation which can be known in advance to produce measurably reliable results. 
         [0016]    It is still a further object of the present invention to provide a generalized method for automated account reconciliation which can, after reconciling datasets, produce reports showing ‘open’ (unreconciled) items as well as matched items, including the groupings of matched items. 
         [0017]    These and other objects of the present invention will become apparent to those skilled in this art upon reading the accompanying description, drawings, and claims set forth herein. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0018]    Non-limiting and non-exhaustive embodiments of the invention are described with reference to the following figures. 
           [0019]      FIG. 1  shows an overview of the process used for generalized automated account reconciliation. 
           [0020]      FIG. 2  shows example transactions that might be used as input for the present invention. 
           [0021]      FIG. 3  shows how characteristics or features of transactions, here the words in a transaction description, may be weighted using the point wise mutual information measure from the field of computational linguistics. 
           [0022]      FIG. 4  shows the output of computations of pair wise similarity for all pairs of transactions using the cosine measure, where each transaction is treated as a vector of point wise mutual information measures. 
           [0023]      FIG. 5  shows the output of ruling out certain pairs of transactions in cases where the similarity between their respective distributions does not meet a required statistical threshold, meaning that the similarity could simply have occurred by chance. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0024]      FIG. 1  shows an overview of the best mode contemplated by the inventor of the process for generalized automated account reconciliation according to the concepts of the present invention. As can be amply seen from  FIG. 1 , the process begins with extracting features of each transaction description and is highly general in what can be allowed as input. The ‘features’ can include items self-contained within a single field of a database table, spreadsheet, or delimited file, such as a transaction date, fund number, account number, or other potentially distinguishing characteristic. They may also include items included in a larger grouping all within a single field; an example would be individual words within a transaction description, all of which is contained in a single free-form text field. Often, it is essential to extract features of the latter type, as in some cases the only place where key identifying information for a transaction can be found may be within a transaction description, as is amply seen in the example shown in  FIG. 2  of the drawings. As long as each transaction has at least one feature, there is no theoretical lower or upper limit on how many features may be extracted. 
         [0025]    For extraction of words from a transaction description (or other unstructured text), a text tokenizer is required. An example of a preferred method for text tokenization would be the regular expressions Regex.Split method used in conjunction with “\w” (the non-word character delimiter), which can be applied to virtually any human language encoded in any Unicode script. If the source transactional data is in a Microsoft SQL Server 2005 or 2008 database (available from Microsoft Corporation, Redmond, Wash.), then a highly efficient way of tokenizing text fields is to implement the regular expressions method above within a Common Language Runtime database function which can then be referenced within an SQL (Structured Query Language) database query. Within other database management systems, there are likely to be equivalent methods for text tokenization. The text tokenizer converts text within transaction descriptions from the format shown in  FIG. 2  to a format where each word within the text is a separate feature; the latter format is highly amenable to further data manipulation. The conversion process (inter alia) is shown in  FIG. 3  of the drawings. 
         [0026]    While  FIG. 3  focuses on the extraction of words from text, rows can be added to the table of features for each transaction to include not just words, but any characteristic of the transaction, such as account, date, fund number, or any other field which may allow transactions to be reconciled. As long as each transaction has at least one feature, there is no theoretical lower or upper limit on how many features may be included. 
         [0027]    The generalized method for automated account reconciliation incorporates the use of a weighting scheme based on information theory to measure the distinctiveness of particular features (to include words from text or other features) in particular transactions. An example of a preferred weighting scheme would be Point wise Mutual Information, which can be defined as the probability of feature i in (or conditional upon) transaction j, divided by the probability of feature i occurring in the entire population. In effect, this weighting scheme calculates how much more likely a feature is to occur in conjunction with a particular transaction than may be expected on the basis of chance. A formula for Point wise Mutual Information is shown in  FIG. 3 , along with sample results of applying this weighting to features from tokenized text. The most distinctive features (including words) for the transaction are assigned higher weightings, while features which are non-distinctive are assigned lower weightings. Use of a weighting scheme in this fashion is resilient to typographical and other encoding errors in the source data, and will automatically recognize which features are most distinguishing within a particular population, without any a priori knowledge of the characteristics of the population. This is a key reason that the present invention is highly generalizable to different datasets. 
         [0028]    Once the transaction features are extracted and weighting is assigned, the generalized method for automated account reconciliation conceives of the transactions as being associated with n-dimensional vectors in a Euclidean space, where n is the number of distinct features in the entire population. For a particular transaction, the n-dimensional vector is the list of features, each associated with the Point wise Mutual Information value for that feature. This conception allows similarities between pairs of transactions to be calculated using a geometric measure. An example of such a geometric measure is the cosine metric used in the field of Information Retrieval, which can range between −1 and +1. A cosine of +1 indicates that the vectors for the pair of transactions are perfectly aligned with one another, a cosine of 0 indicates that the vectors are completely orthogonal to one another, and a cosine of −1 indicates that the vectors are perfectly negatively aligned. Thus, a higher cosine between a pair of transactions indicates that the pair is more similar to one another.  FIG. 4  illustrates the results of measuring cosines between all pairs of transactions in a population. The cosine between a vector and itself is always 1, as is amply seen in the diagonal row of  FIG. 4 . The values are not shown in the lower-left half of  FIG. 4 , as these would be the mirror image of those in the top-right half. Note that use of the cosine metric allows matches to be made between pairs even if the matches are not based on ‘hard’ criteria; in other words, this part of the process assigns each pair a measure of greater or lesser similarity, rather than saying that a pair ‘is similar’ or ‘is not similar’. Furthermore, the cosine metric can be applied equally regardless of the underlying extracted features. 
         [0029]    In  FIG. 4 , the size of the table of all candidate pairs is determined by the Cartesian product of the two datasets being compared. In cases where the number of transactions is large, a ‘blocking’ strategy (as in the field of Record Linkage) can be used to subdivide the datasets, thereby reducing the overall number of computations that have to be made. An example of an appropriate blocking strategy would be to rule out pairs where the monetary amounts are not equal and opposite. 
         [0030]    To complete the process of automated account reconciliation, a mechanism is needed for deciding which candidate pairs of transactions should be ruled in (reconciled) or ruled out. An example of a preferred method for achieving this is to treat each transaction now as a statistical distribution; this allows a determination of whether pairs of distributions are too similar for the similarity to have occurred by chance. In  FIG. 3 , the list of features and values (as shown in the output) would be an example of such a distribution. In order to rule a particular pair in or out, any of a number of statistical correlation functions (including but not limited to chi-squared, Pearson&#39;s rho, Spearman&#39;s rho) may be applied. In the present invention, the measure of correlation is compared to a table of critical values appropriate for the correlation measure. The number of degrees of freedom is the number of independent features used to compute the correlation. If the measure of correlation exceeds the critical value at a pre-defined confidence threshold (which can be set and/or varied by the user), then the candidate pair is ruled in (that is, the pair of transactions is reconciled), otherwise it is ruled out. If, for a particular transaction, there are multiple candidates for which the correlation exceeds the critical value, then the pair for which the vectors has the highest cosine can be ruled in and the remaining pairs ruled out. 
         [0031]    Once decisions have been made on which items to reconcile, the method allows for a means of reporting matched pairs and unmatched items. One means of accomplishing this is to store all data in database tables which include additional fields to encode which items are reconciled to which other items. If this field is blank, the item is unreconciled. For those skilled in the art, it is then clear that reports of reconciled and unreconciled items can easily be generated and rendered to a display by designing queries as needed, for example using Structured Query Language. 
         [0032]    The processes explained above may constitute computer-executable instructions embodied or stored within a machine-readable storage medium, that when executed by a machine will cause the machine (e.g. computer, processor, etc.) to perform the operations described. Additionally, the processes may be embodied within hardware, such as an application specific integrated circuit (“ASIC”) or the like. 
         [0033]    A machine-readable storage medium includes any mechanism that provides (i.e., stores) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.). For example, a machine-readable storage medium includes recordable/non-recordable media (e.g. read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, etc.). 
         [0034]    The above description of illustrated embodiments of the invention, including what is described in the Abstract, is not intended to be exhaustive or to limit the invention to the precise forms disclosed. While specific embodiments of, and examples for, the invention are described herein for illustrative purposes, various modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. 
         [0035]    The problems addressed by the generalized method for automated account reconciliation are many as can be easily seen by those skilled in the art. The generalized method for automated account reconciliation is not restricted to working with data in a particular format or even text in a particular human language. It is not limited in terms of the number or type of features that transactions may have. It is not limited by size of dataset, and in fact is anticipated to provide increasingly greater efficiencies and savings with larger datasets. It avoids the need for heuristics specific to particular datasets. Through the connection with statistics, it can be reliably estimated in advance, by setting particular confidence thresholds, how accurate the results are likely to be. The present invention can dramatically reduce the amount of labor, and therefore the costs, associated with account reconciliation, particularly on a large scale. Since account reconciliation is a function performed by virtually every accounting department of every organization, the present invention has widespread uses. 
         [0036]    Thus it will be appreciated by those skilled in the art that the present invention is not restricted to the particular preferred embodiments described with reference to the drawings, and that variations may be made therein without departing from the scope of the present invention as defined in the appended claims and equivalents thereof