US20150178855A1 - Ocr enabled management of accounts payable and/or accounts receivable auditing data - Google Patents

Ocr enabled management of accounts payable and/or accounts receivable auditing data Download PDF

Info

Publication number
US20150178855A1
US20150178855A1 US14/634,431 US201514634431A US2015178855A1 US 20150178855 A1 US20150178855 A1 US 20150178855A1 US 201514634431 A US201514634431 A US 201514634431A US 2015178855 A1 US2015178855 A1 US 2015178855A1
Authority
US
United States
Prior art keywords
document
method
plurality
supplier
data
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.)
Abandoned
Application number
US14/634,431
Inventor
Joseph Flynn
Kerry Edward Koitzsch
Wassim G. Jraige
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lavante Inc
Original Assignee
Lavante Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority to US35054302P priority Critical
Priority to US10/349,727 priority patent/US7908188B2/en
Priority to US13/045,388 priority patent/US8996416B2/en
Application filed by Lavante Inc filed Critical Lavante Inc
Priority to US14/634,431 priority patent/US20150178855A1/en
Publication of US20150178855A1 publication Critical patent/US20150178855A1/en
Assigned to LAVANTE, INC. reassignment LAVANTE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FLYNN, JOSEPH, JRAIGE, WASSIM G., KOITZSCH, KERRY EDWARD
Assigned to SUN TRUST BANK reassignment SUN TRUST BANK SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LAVANTE, INC.
Assigned to BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT reassignment BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Assignors: LAVANTE, INC.
Assigned to LAVANTE, INC. reassignment LAVANTE, INC. TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Assignors: SUNTRUST BANK, AS ADMINISTRATIVE AGENT
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12Accounting
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/93Document management systems
    • G06F17/30011
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06KRECOGNITION OF DATA; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K9/00Methods or arrangements for reading or recognising printed or written characters or for recognising patterns, e.g. fingerprints
    • G06K9/00154Reading or verifying signatures; Writer recognition
    • G06K9/00161Reading or verifying signatures; Writer recognition based only on signature image, e.g. static signature recognition
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06KRECOGNITION OF DATA; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K9/00Methods or arrangements for reading or recognising printed or written characters or for recognising patterns, e.g. fingerprints
    • G06K9/00402Recognising digital ink, i.e. recognising temporal sequences of handwritten position coordinates
    • G06K9/00422Matching; classification
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06KRECOGNITION OF DATA; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K9/00Methods or arrangements for reading or recognising printed or written characters or for recognising patterns, e.g. fingerprints
    • G06K9/00442Document analysis and understanding; Document recognition
    • G06K9/00469Document understanding by extracting the logical structure, e.g. chapters, sections, columns, titles, paragraphs, captions, page number, and identifying its elements, e.g. author, keywords, ZIP code, money amount
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/04Billing or invoicing, e.g. tax processing in connection with a sale
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation, credit approval, mortgages, home banking or on-line banking

Abstract

A number of different tags are input in a fax cover sheet that tell an OCR system not only the identity of the supplier, but also to which client the document should be routed. The OCR system identifies a number of these tags and compares them to stored supplier data to validate to which supplier the document belongs. If the system cannot validate the document, it is routed to a GUI for manual sorting. If there is no coversheet, the system relies upon the OCR system to locate keywords on the document and caller ID information to suggest a correct supplier. The OCR system also clips a separate, horizontal slice of the document (‘snippet’) that corresponds to the display of any line item and places it in a data base for future reference and reporting. The application collects and associates all corresponding snippets to their originating line items.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of U.S. patent application Ser. No. 13/045,388, filed Mar. 10, 2011, which is a continuation-in-part of U.S. patent application Ser. No. 10/349,727, filed Jan. 22, 2003, now U.S. Pat. No. 7,908,188, issued on Mar. 15, 2011, which application claims priority to U.S. Provisional Patent Application Ser. No. 60/350,543, filed Jan. 22, 2002, which applications are herein incorporated by reference in their entireties.
  • BACKGROUND OF THE INVENTION
  • 1. Technical Field
  • The invention relates to managing accounts payable and/or accounts receivable auditing data. More particularly, the invention relates to OCR enabled management of accounts payable and/or accounts receivable auditing data.
  • 2. Description of the Background Art
  • The practice of performing recovery audits originated in the early 1970's, during a time of increased commerce for the retail industry. A growing network of national chain stores led to a rise in competition for retail shelf space from different suppliers. Large companies had a difficult time keeping track of the many different vendor price points, rebates, and other various discounts.
  • Keeping track of such details was not an integral part of purchasing departments. Such oversights led to a substantial amount of lost revenue going unnoticed in the form of duplicate payments, overpayments, missed shipments, unused credits, and other transactional errors between a company and its suppliers.
  • Accounts Payable Audit
  • Today, in a typical accounts payable (A/P) audit, auditors work with the A/P records of a company in an attempt to find potentially profitable discrepancies in a vendor transaction file for the company or individual business units of the company. Although much of an A/P audit can be performed at a third party location, the A/P audit generally requires the cooperation and time of individuals within the client-organization to work in conjunction with the auditors. The A/P audit is a useful tool but can be time consuming for the client. However, typical A/P auditing firms are unable to do a thorough job of reviewing vendor data.
  • Statement Audit
  • Another type of audit emerging within the auditing industry is a statement audit (SA). An SA is initiated from the vendors' records and, thus, requires little, if any, intrusion within the client-company. Once vendor files are secured, the auditing company begins the process of searching for gaps, differences, and discrepancies that result in the client-company losing revenue.
  • An SA deals directly with suppliers and vendors. However, if performed properly, an SA yields findings that an A/P audit could miss. Because of the unique nature of an SA, the SA can either stand alone or function alongside typical A/P recovery efforts.
  • An SA is very labor intensive because the SA audit requires the requesting, receiving, organizing, and following up with vendors on auditing data from many sources. In some statement audits, the number of sources ranges in the tens of thousands of sources. Due to the labor intensive demands of an SA, very few A/P auditing firms in the A/P auditing industry, if any, have the capability of doing a thorough and complete job for their clients.
  • Prior art statement audits fail to manage credits based on line item data or on a line item basis. Instead, prior art statement audits attempt to manage credits based only on statement level data, which is not as detailed as line item data. Prior art statement audits typically only deal with open line items. Prior art statement audits put each open line item in a file and then record a note for each open line item indicating that the open line item should be checked at some point in the future. In addition, prior art statement audits only keep track of claims. Prior art statement audits fail to keep track of every line item of a client, e.g. both Debits and Credits.
  • Transactional Errors
  • There is no accepted way to predict the success of an audit. However, a general rule of thumb is that transactional errors occur with a frequency of about 1/10 of 1%. That translates to a million dollars of annual recovery for every billion dollars of a company's annual revenue.
  • The A/P auditing industry is growing in size and stature as third party A/P auditing firms attempt to recover lost profits for their clients. However, since A/P auditing firms are unable to do a thorough job of reviewing vendor data, clients have employed internal auditors in order to recover lost profits via a statement audit. However, clients typically are unable to perform statement audits because they do not have the amount of staff necessary to perform a statement audit. Therefore, a method and system of managing accounts payable auditing data is needed.
  • Managing Accounts Payable Auditing Data
  • U.S. patent application Ser. No. 10/349,727, filed Jan. 22, 2003, and incorporated herein in its entirety by this reference thereto, discloses a method and system of managing accounts payable auditing data, where the auditing data includes at least one line item and is ordered by a propensity to yield claims. The method and system, in an exemplary embodiment, includes (1) displaying at least one aged line item, (2) identifying credit data among the at least one displayed aged line item, and (3) recording the identified credit data. In an exemplary embodiment, the aged line item is a line item that has aged for N months, where N is positive integer. In an exemplary embodiment, N is 4.
  • The displaying includes (a) prompting if there are any line items that are aged line items that have to be validated and deducted, (b) displaying the number of vendors, by rank, that have and have not responded and a status assigned to those vendors, and (c) allowing for the noting and aging for follow up of when the vendor promises a fax, a callback, a mailing of an item, or a check request and when a client puts a claim on hold.
  • The recording includes (a) allowing for the entry of contact data for at least one vendor, (b) allowing for entry of information about a vendor statement associated with the vendor, (c) allowing for selection of information about credits/claims, credits, or claims of the vendor, (d) allowing for the interaction with the information about the credits/claims, the credits, or the clams of the vendor, and (e) allowing for the entry of comments about the recording.
  • The statement recovery auditing disclosed in U.S. patent application Ser. No. 10/349,727 is based on a process of collecting a high volume of data that is located on hard copy documentation. This documentation resides in the accounting records of various audit system suppliers or audit system clients' customers. For purposes of simplification of explanation, but not of limitation, the discussion herein focuses on how the process works for any one client and any one supplier.
  • Collecting this documentation poses a number of challenges. For example, it is preferred to get fresh documentation from each supplier at least four times a year. If the client has 15,000 suppliers, then it is necessary to request, receive, and review as many as 60,000 documents. In addition to the large amount of documentation involved, also challenging is the fact that each supplier may have different formats in which they deliver the information. Lastly, the suppliers typically do not have any electronic medium for providing the documentation and they therefore prefer to mail or fax the documentation in hard copy.
  • To address these issues, it would be advantageous to provide an application that not only manages tens of thousands of outreaches to suppliers, but that also can receive and perform an initial review of the responses.
  • SUMMARY OF THE INVENTION
  • An embodiment of the invention provides an application that not only manages tens of thousands of outreaches to suppliers, but that also can receive and perform an initial review of the responses. In one embodiment, an OCR system is used to receive a document and route it through the system. In most cases, a faxing agency is provided with a cover sheet to use when sending information to the system. A number of different tags are input in the cover sheet that tell the system not only the identity of the supplier, but also to which client the document should be routed. Some of the tags used are provided by the customer, such as a “Supplier Number” and “Supplier Name,” while others are system generated, i.e. a “Universal ID.” There are also tags that are collected that are actual document meta data elements including, but not limited to, number of pages, received date, and Caller ID of the fax sender. In any case, the OCR system is used to identify a number of these tags and compare them to stored supplier data within the system to validate to which supplier the document belongs. If the system cannot be 100% sure where the document goes, the document is turned over to a GUI for manually sorting. If there is no coversheet, the system relies upon the OCR system to locate keywords on the document and caller ID information to suggest a correct supplier.
  • Additionally, the OCR system also clips a separate small horizontal slice of the document that corresponds to the display of any line item, including both Credits and Debits, and places it in a data base for future reference and reporting. This clip is referred to as a snippet. Because each targeted line item identified receives a unique identifier it is possible for the application to collect and associate all corresponding snippets to their originating line items.
  • Line items are then sent to the GUI supported by link to the originating document and links to the corresponding snippet. Also of these line items can be graphically flagged or highlighted.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a flow diagram showing the use of an OCR system to receive a document and route it through the system according to the invention;
  • FIG. 2 is a flow diagram showing the use of cover sheets that have areas to input data by hand according to the invention;
  • FIG. 3 is a flow diagram showing the use of OCR functionality where documents are examined and relevant data is placed into various databases according to the invention;
  • FIG. 4 is a flow diagram showing an embodiment in which verification documents are processed by the OCR system;
  • FIG. 5 is a flow diagram showing delivery of data from the database with the corresponding snippets and links to one or more reporting interfaces according to the invention;
  • FIG. 6 is a screen display showing an example of a report according to the invention; and
  • FIG. 7 is a block schematic diagram of a machine in the exemplary form of a computer system within which a set of instructions for causing the machine to perform any one of the foregoing embodiment of the invention may be executed.
  • DETAILED DESCRIPTION OF THE INVENTION
  • An embodiment of the invention provides an application that not only manages tens of thousands of outreaches to suppliers, but that also can receive and perform an initial review of the responses. In a presently preferred embodiment, this solution makes use of an Optical Character Recognition (OCR) system. The following discussion provides a brief summary of the basic functions and functionality that an exemplary OCR system performs. Each process is described in connection with a corresponding flow chart of FIG. 1-5. Also, it is important to understand that different OCR techniques are used at different times throughout the process. Many of the OCR tasks are performed simultaneously, and some are performed independently. It should be appreciated that some of these processes can be performed sequentially, and some are performed on-demand.
  • A presently preferred embodiment of the invention is employed in conjunction with a computer-implemented method and system that comprises the steps of managing, for example, accounts payable data of a client and/or AR data of a Supplier. In the case of accounts payable data, such data can include at least one line item; displaying an aged line item from among the at least one line item, wherein the at least one line item relates to a request from a vendor for payment on an account for the client; identifying credit data among the at least one displayed aged line item, wherein the credit data relates to a deduction that the client can take against the requested payment; and recording the identified credit data, wherein one or more of the managing, displaying, identifying and recording steps are implemented by the computer, as disclosed in U.S. patent application Ser. No. 10/349,727, filed Jan. 22, 2003, and incorporated herein in its entirety by this reference thereto. Those skilled in the art will appreciate that the invention finds application with other methods and systems and that the invention is not limited to this exemplary method and system. For example, but not limitation, the invention may be applied to managing and reconciling debits on the statements as well. Thus, the invention is concerned both with collecting and reporting credits that are due to Clients and collecting and reporting on Debits as well. Accordingly, both Accounts Payable data of the clients and Accounts Receivable data of the Supplier are subject matter for the invention.
  • Further, a key aspect of the invention is to identify and report on discrepancies between the AP records of the Clients and the AR data of the Suppliers. In theory the Clients AP and the Suppliers AR records should match but, in practice, they do not. Thus, the invention is applicable to both sets of data.
  • FIG. 1 is a flow diagram showing the use of an OCR system (100) to receive a document and route it through the system. In most cases, a faxing agency is provided with a cover sheet to use when sending information to the system. A number of different tags are input in the cover sheet that tell the system not only the identity of the supplier, but also to which client the document should be routed (102). Some of the tags used are provided by the customer, such as a “Supplier Number” and “Supplier Name,” while others are system generated, i.e. a “Universal ID.” In any case, the OCR system is used to identify a number of these tags and compare them to stored supplier data within the system (104) to validate to which supplier the document belongs (106). If the system cannot be 100% sure where the document goes, the document is turned over to a GUI for manually sorting. If there is no coversheet, the system relies upon the OCR system to locate keywords on the document and caller ID information to suggest a correct supplier.
  • There are typically two types of coversheets in use: those that are specifically created and provided to the suppliers for use, i.e. proprietary coversheets, and everything else. If the suppliers use the provided coversheet, then the system can readily find the necessary tags, etc. Also, there are many times that the supplier's unique coversheet is received and then they send the provided coversheet as well. In this case, all pages of a fax are scanned looking for the tags that indicate a provided coversheet is scanned. Even if the provided coversheet comes as the last page of a 50 page fax, the system still knows there is a coversheet.
  • If the supplier does not send the provided coversheet in the fax, the system still scans the supplier's coversheet to identify logos or company names, and also to match the caller ID of the sender to the supplier, etc.
  • FIG. 2 is a flow diagram showing the use of cover sheets that have areas to input data by hand. This embodiment of the invention uses OCR handwriting recognition to identify this data and store it into a database.
  • Example Supplier Contact data
  • When a fax is received, a first consideration in an embodiment of the invention is the preparation of, and modifications to, such received documents to bring them into the application. This preparation includes, for example, cleaning the document by de-speckling the images, as well as removing any vertical lines that show up in faxes. Additionally, the system cleans up the text. Further, the system adjusts the alignment and rotation of the pages. In a presently preferred embodiment, these actions are performed for all pages all of the time.
  • After the fax is received (and prepared as discussed above) (100) the supplier's identity is established. The OCR system finds the area where the Supplier has entered their contact information: name, phone, fax or email, for example (102). The OCR system recognizes the handwriting (204) and then compares what it sees to what is currently in the database for that supplier. (206) If there is currently no data in the database (208), the OCR enters what it sees and serves it to a user in a GUI to verify the OCR accuracy (212). If there currently is data in the database, the OCR system compares what it is identified from the document and decides if the data is the same (208). If it is determined that the contact information is the same (210), then the OCR system notes the metadata accordingly, e.g. date, time, etc. If the data is deemed different (208), then the OCR results and the preexisting system data are sent to a GUI for human verification (214).
  • Any of a number of methods can be used to recognize handwriting. Each method cleans the string, then compares the string and, ultimately, rates the string. In one embodiment, the system starts by using the Hidden Markov Model (HMM) to determine a Maximum Likelihood Estimation. When this model finishes, it determines that is not likely enough, then the system moves onto the next method, such as the Mean Squared Error MSE model.
  • FIG. 3 is a flow diagram showing the use of OCR functionality where documents are examined (100) and relevant data is placed into various databases (302). In this embodiment, data is tagged back to the document and snippets are created. In this example, a document is received and the OCR system determines if the there is any data that needs to be collected into the database for review (304). In many cases, the data collected takes the form of lines of financial data provided in the form of hard copy print outs from financial systems. The OCR system identifies any financial tables on the page and automatically reads the column headers and compares them to the headers in a table master. Then, the OCR system scans through the entirety of the document, places all the targeted line items into the database, and marks them on the document within the GUI. The OCR system then tags the location of each targeted line back to its original location in the document for fast future connectivity and recall (306).
  • Additionally, the OCR system also clips a separate small horizontal slice of the document that corresponds to the display of any line item and places it in a data base for future reference and reporting (308). This clip is referred to as a snippet. Because each targeted line item identified receives a unique identifier it is possible for the application to collect and associate all corresponding snippets to their originating line items.
  • Snippets can be created for all lines of data at any time. Thus, it is possible to allow any user, e.g. client, supplier, etc., to create different types of snippets on-demand within the GUI. The snippets described herein are specific and are generated by JAVA based programming. Snippets are regional, sub images of the original document. Borders are determined by line heights and by location of the black pixels. This is why the pre-treating and cleaning of faxes is important. The system is able to recognize white space and then continue to constrict its focus until it identifies a black pixel. Once a black pixel is identified, the system follows the rules of the JAVA program to determine what is snippet-ed. It should be appreciated that a snippet can be vertical in nature as well, and not always horizontal.
  • Line items are then sent to the GUI (310) supported by link to the originating document and links to the corresponding snippet. Also of these line items can be graphically flagged or highlighted.
  • FIG. 4 is a flow diagram showing an embodiment in which verification documents are processed by the OCR system. Many line items require additional supporting documentation from the supplier and thus require a follow up contact and request for information. This request is automatically generated by the system (400) and can ask a number of follow up questions, including a request for a signature. The document that is sent out for this purpose is not only a form, but it is also intended to be used as a cover sheet. It can contain many of the same tags, as well as additional tags as discussed in FIG. 1. The document may contain a series of questions for the entity that correspond to each line item. The supplier verifies and returns the document (402). When the document is received, the OCR system reviews the document (404) and performs a number of tasks (406).
  • As described above, the OCR system tags where the respective follow-up information is located for each line item within the document (408). Additionally, the system creates a horizontal or vertical snippet for the information and associates it to the line item within the database (410). As mentioned above, the system also collects a signature at the bottom of the page. A separate snippet is created for the signature and offered as part of the backup for any line item
  • With the creation of the follow-up snippet, signature snippet, and the snippet from the original document it is possible to deliver line item information within a GUI, complete with images from any and all related documents (412). The system also provides links back to the area and page on the originating document.
  • FIG. 5 is a flow diagram showing delivery of data from the database (500) with the corresponding snippets and links to one or more reporting interfaces (502/504).
  • FIG. 6 is a screen display showing an example of a report. In this case, in addition to the report data itself 60, some details are displayed from the originating document 62, combined with follow-up data 64 and a signature 66, as snippet images from the respective original documents.
  • Computer Implementation
  • FIG. 7 is a block schematic diagram of a machine in the exemplary form of a computer system 1600 within which a set of instructions for causing the machine to perform any one of the foregoing embodiment of the invention may be executed. In alternative embodiments, the machine may comprise or include a network router, a network switch, a network bridge, personal digital assistant (PDA), a cellular telephone, a Web appliance or any machine capable of executing or transmitting a sequence of instructions that specify actions to be taken.
  • The computer system 1600 includes a processor 1602, a main memory 1604 and a static memory 1606, which communicate with each other via a bus 1608. The computer system 1600 may further include a display unit 1610, for example, a liquid crystal display (LCD) or a cathode ray tube (CRT). The computer system 1600 also includes an alphanumeric input device 1612, for example, a keyboard; a cursor control device 1614, for example, a mouse; a disk drive unit 1616, a signal generation device 1618, for example, a speaker, and a network interface device 1628.
  • The disk drive unit 1616 includes a machine-readable medium 1624 on which is stored a set of executable instructions, i.e., software, 1626 embodying any one, or all, of the methodologies described herein below. The software 1626 is also shown to reside, completely or at least partially, within the main memory 1604 and/or within the processor 1602. The software 1626 may further be transmitted or received over a network 1630 by means of a network interface device 1628.
  • In contrast to the system 1600 discussed above, a different embodiment uses logic circuitry instead of computer-executed instructions to implement processing entities. Depending upon the particular requirements of the application in the areas of speed, expense, tooling costs, and the like, this logic may be implemented by constructing an application-specific integrated circuit (ASIC) having thousands of tiny integrated transistors. Such an ASIC may be implemented with complementary metal oxide semiconductor (CMOS), transistor-transistor logic (TTL), very large systems integration (VLSI), or another suitable construction. Other alternatives include a digital signal processing chip (DSP), discrete circuitry (such as resistors, capacitors, diodes, inductors, and transistors), field programmable gate array (FPGA), programmable logic array (PLA), programmable logic device (PLD), and the like.
  • It is to be understood that embodiments may be used as or to support software programs or software modules executed upon some form of processing core (such as the CPU of a computer) or otherwise implemented or realized upon or within a machine or computer readable medium. A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine, e.g., a computer. For example, a machine readable medium includes read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals, for example, carrier waves, infrared signals, digital signals, etc.; or any other type of media suitable for storing or transmitting information.
  • Although the invention is described herein with reference to the preferred embodiment, one skilled in the art will readily appreciate that other applications may be substituted for those set forth herein without departing from the spirit and scope of the present invention. For example, while fax technology is discussed in connection with the preferred embodiment of the invention, those skilled in the art will appreciate that the invention is applicable to a document provided in any input medium including, but not limited to, paper documents, email messages, database records, voice, video, and image data, and information-bearing signals, as well as, without limitation, documents uploaded by a user (client, supplier, etc.). A further embodiment supports Clients AP departments want to take AR ledgers that are received from suppliers in fax format and have them delivered to the clients in, for example, an Excel format. In this embodiment, a provider receives AR ledger information from suppliers, converts them into database formats, and submits the converted data back to the clients. Accordingly, the invention should only be limited by the Claims included below.

Claims (20)

1. A method comprising:
receiving a document comprising a plurality of tags;
identifying at least some of the plurality of tags;
comparing the identified tags to supplier data stored in a database to validate the document;
clipping a portion of the document that corresponds to a line item;
storing the clipped portion and the originating line item in the database;
associating the clipped portion with the originating line item;
tagging a location of the originating line item to its original location in the document; and
causing the originating line item to be presented on a graphical user interface, the originating line item comprising a first link to the document and a second link to the corresponding clipped portion.
2. The method of claim 1, further comprising:
determining whether any tables are in the document; and
responsive to determining a table is present, identifying any column headers in the table and comparing the column headers to headers in a table master.
3. The method of claim 2, further comprising:
scanning through an entirety of the document;
marking the originating line item on a digital representation of the document, the digital representation adapted to be displayed on a graphical user interface.
4. The method of claim 1, wherein the plurality of tags are presented in a cover sheet.
5. The method of claim 4, further comprising:
determining whether the cover sheet is present; and
responsive to determining the cover sheet is not present, identifying one or more keywords or phone numbers within the document that are associated with a particular supplier.
6. The method of claim 1, further comprising:
determining whether the document can be validated; and
responsive to determining the document cannot be validated, routing the document to a graphical user interface for manual sorting.
7. The method of claim 1, further comprising:
identifying an area of the document where a supplier has provided handwritten contact information;
processing and recognizing the handwritten contact information;
comparing the handwritten contact information to contact information for the supplier stored in the database;
responsive to determining contact information does not exist in the database for the supplier, storing the recognized handwritten contact information in the database and presenting the recognized handwritten contact information through a graphical user interface for human verification;
responsive to determining contact information exists in the database for the supplier, comparing the recognized handwritten contact information to the existing contact information to determine whether there is a match;
responsive to finding a match, processing metadata accordingly; and
responsive to not finding a match, transmitting the recognized handwritten contact information and the existing contact information to a graphical user interface for human verification.
8. A method for managing accounts payable data, accounts receivable data, or both, the method comprising:
receiving a document comprising a first portion having a plurality of tags and a second portion having a plurality of line items;
processing the first portion of the document and identifying at least one of the plurality of tags;
comparing the at least one identified tag to account data stored in a database to validate the document;
processing the second portion of the document and identifying each of the plurality of line items;
marking each identified line item on a digital representation of the document, the digital representation adapted to be displayed on a graphical user interface;
identifying a location within the document corresponding to each identified line item; and
causing the identified line items to be presented on a graphical user interface.
9. The method of claim 8, further comprising:
clipping a portion of the document that corresponds to each of the plurality of line items;
storing the clipped portions in the database; and
associating each clipped portion with the originating line item.
10. The method of claim 9, wherein the identified line items presented on the graphical user interface comprise one or both of a first link to the document and a second link to the corresponding clipped portion.
11. The method of claim 8, further comprising:
automatically generating a verification request.
12. The method of claim 8, further comprising:
presenting an aged line item from among the identified line items;
identifying credit data for the aged line item; and
recording the identified credit data in the database.
13. The method of claim 12, wherein the aged line item relates to a request for payment from a vendor or an account for a client.
14. The method of claim 12, wherein the credit data relates to a deduction a client can take against a requested payment.
15. A method comprising:
receiving a document comprising a first portion having a plurality of tags and a second portion having a plurality of line items;
identifying at least one of the plurality of tags;
comparing the identified tag to supplier data to match the document with a particular supplier, the supplier data stored in a database;
identifying each of the plurality of line items;
storing the first plurality of identified line items in the database; and
comparing each of the first plurality of identified line items to client data to identify discrepancies, the client data stored in the database.
16. The method of claim 15, wherein the client data comprises accounts payable data provided by a particular client, a second plurality of line items identified within one or more documents provided by the particular client, or a combination thereof.
17. The method of claim 15, wherein validating the document comprises:
determining whether the identified tag matches the supplier data;
responsive to finding a match, associating the document with the particular supplier; and
responsive to not finding a match, transmitting the document to a graphical user interface for human verification.
18. The method of claim 15, further comprising:
matching, based on the comparison of the first plurality of identified line items to the client data, the document to a transaction between a particular client and the particular supplier; and
identifying, within the database, one or more documents associated with the transaction, the documents comprising a second plurality of identified line items.
19. The method of claim 18, further comprising:
responsive to identifying a discrepancy between the first plurality of identified line items and the second plurality of identified line items, causing any contradictory line items to be presented on a graphical user interface, wherein the contradictory line items are those identified line items causing the discrepancy.
20. The method of claim 19, further comprising:
presenting an aged line item from among the contradictory line items, wherein the aged line item is an identified line item that has aged for N months, wherein N is a positive integer.
US14/634,431 2002-01-22 2015-02-27 Ocr enabled management of accounts payable and/or accounts receivable auditing data Abandoned US20150178855A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US35054302P true 2002-01-22 2002-01-22
US10/349,727 US7908188B2 (en) 2002-01-22 2003-01-22 Method and system of managing accounts payable auditing data
US13/045,388 US8996416B2 (en) 2002-01-22 2011-03-10 OCR enabled management of accounts payable and/or accounts receivable auditing data
US14/634,431 US20150178855A1 (en) 2002-01-22 2015-02-27 Ocr enabled management of accounts payable and/or accounts receivable auditing data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/634,431 US20150178855A1 (en) 2002-01-22 2015-02-27 Ocr enabled management of accounts payable and/or accounts receivable auditing data

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13/045,388 Continuation US8996416B2 (en) 2002-01-22 2011-03-10 OCR enabled management of accounts payable and/or accounts receivable auditing data

Publications (1)

Publication Number Publication Date
US20150178855A1 true US20150178855A1 (en) 2015-06-25

Family

ID=46798809

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/045,388 Active 2023-06-22 US8996416B2 (en) 2002-01-22 2011-03-10 OCR enabled management of accounts payable and/or accounts receivable auditing data
US14/634,431 Abandoned US20150178855A1 (en) 2002-01-22 2015-02-27 Ocr enabled management of accounts payable and/or accounts receivable auditing data

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US13/045,388 Active 2023-06-22 US8996416B2 (en) 2002-01-22 2011-03-10 OCR enabled management of accounts payable and/or accounts receivable auditing data

Country Status (2)

Country Link
US (2) US8996416B2 (en)
WO (1) WO2012122402A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150294297A1 (en) * 2014-04-15 2015-10-15 Capital One Financial Corporation System and method for inter-bank and intra-bank mobile banking communications and transfers

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9105073B2 (en) * 2012-04-24 2015-08-11 Amadeus S.A.S. Method and system of producing an interactive version of a plan or the like
US20150120517A1 (en) * 2013-10-29 2015-04-30 Bank Of America Corporation Data lifting for duplicate elimination
US9412135B2 (en) 2013-10-29 2016-08-09 Bank Of America Corporation Check data lift for online accounts
WO2016007334A1 (en) * 2014-06-30 2016-01-14 Shaaban Ahmed System and method for automed collections of debts for business

Citations (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5237628A (en) * 1991-06-03 1993-08-17 Nynex Corporation System and method for automatic optical data entry
US5448375A (en) * 1992-03-20 1995-09-05 Xerox Corporation Method and system for labeling a document for storage, manipulation, and retrieval
US5579407A (en) * 1992-04-21 1996-11-26 Murez; James D. Optical character classification
US5669007A (en) * 1994-06-16 1997-09-16 International Business Machines Corporation Method and system for analyzing the logical structure of a document
US5764866A (en) * 1995-05-26 1998-06-09 Ricoh Company, Ltd. Scanner, network scanner system, and method for network scanner system
US5809481A (en) * 1996-08-08 1998-09-15 David Baron Advertising method and system
US5875038A (en) * 1996-05-28 1999-02-23 Gerber Scientific, Inc. Facsimile queuing and transmission system
US5948038A (en) * 1996-07-31 1999-09-07 American Traffic Systems, Inc. Traffic violation processing system
US6097834A (en) * 1997-06-13 2000-08-01 Paystation America Inc. Financial transaction processing systems and methods
US6138129A (en) * 1997-12-16 2000-10-24 World One Telecom, Ltd. Method and apparatus for providing automated searching and linking of electronic documents
US20020141660A1 (en) * 2001-03-12 2002-10-03 Multiscan Corp. Document scanner, system and method
US20020176598A1 (en) * 2001-03-05 2002-11-28 Kristian Knowles Test processing workflow tracking system
US20030002068A1 (en) * 2001-06-27 2003-01-02 Michael Constantin Method of routing and processing document images sent using a digital scanner and transceiver
US20050177507A1 (en) * 2001-02-05 2005-08-11 Notiva Corporation Method and system for processing transactions
US20050246337A1 (en) * 2004-04-29 2005-11-03 Forman George H System and method for information management using handwritten identifiers
US20070033118A1 (en) * 2005-08-02 2007-02-08 Taxscan Technologies, Llc Document Scanning and Data Derivation Architecture.
US7231594B1 (en) * 1999-02-10 2007-06-12 Collegenet, Inc. Method for paperless attachment of supplementary forms to a world wide web application
US7370014B1 (en) * 2001-11-01 2008-05-06 Metavante Corporation Electronic bill presentment and payment system that obtains user bill information from biller web sites
US20080144881A1 (en) * 2006-12-13 2008-06-19 Bottomline Technologies (De) Inc. Electronic transaction processing server with automated transaction evaluation
US20080270293A1 (en) * 2007-04-26 2008-10-30 Bottomline Technologies (De) Inc. Accounts payable automation system with automated discount and factoring management
US20090216726A1 (en) * 2008-02-22 2009-08-27 Ramachandran Muthaiah System and Method for Facilitating Business Communications
US20100161466A1 (en) * 2006-10-10 2010-06-24 Gilder Clark S Electronic lockbox using digitally originated checks
US7978901B1 (en) * 2006-12-15 2011-07-12 First Data Corporation Centralized processing of checks for distributed merchant locations
US20110258195A1 (en) * 2010-01-15 2011-10-20 Girish Welling Systems and methods for automatically reducing data search space and improving data extraction accuracy using known constraints in a layout of extracted data elements

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5210687A (en) * 1987-04-16 1993-05-11 L & C Family Partnership Business transaction and investment growth monitoring data processing system
US6018718A (en) * 1997-08-28 2000-01-25 Walker Asset Management Limited Partnership Method and system for processing customized reward offers
US6311169B2 (en) 1998-06-11 2001-10-30 Consumer Credit Associates, Inc. On-line consumer credit data reporting system
US6687677B1 (en) * 1999-11-22 2004-02-03 International Business Machines Corporation System and method for deploying a procurement and accounts payable system
US6643625B1 (en) * 1999-12-17 2003-11-04 Ge Mortgage Holdings, Llc System and method for auditing loan portfolios and loan servicing portfolios
US6847942B1 (en) * 2000-05-02 2005-01-25 General Electric Canada Equipment Finance G.P. Method and apparatus for managing credit inquiries within account receivables
US6901387B2 (en) 2001-12-07 2005-05-31 General Electric Capital Financial Electronic purchasing method and apparatus for performing the same
US20080208780A1 (en) * 2007-02-28 2008-08-28 Caterpillar Inc. System and method for evaluating documents
US20090276669A1 (en) * 2008-04-30 2009-11-05 Caterpillar Inc. Method for processing and redirecting misdirected advanced shipping notices (ASNs)
US8756229B2 (en) * 2009-06-26 2014-06-17 Quantifind, Inc. System and methods for units-based numeric information retrieval
US8332417B2 (en) * 2009-06-30 2012-12-11 International Business Machines Corporation Method and system for searching using contextual data

Patent Citations (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5237628A (en) * 1991-06-03 1993-08-17 Nynex Corporation System and method for automatic optical data entry
US5448375A (en) * 1992-03-20 1995-09-05 Xerox Corporation Method and system for labeling a document for storage, manipulation, and retrieval
US5579407A (en) * 1992-04-21 1996-11-26 Murez; James D. Optical character classification
US5669007A (en) * 1994-06-16 1997-09-16 International Business Machines Corporation Method and system for analyzing the logical structure of a document
US5764866A (en) * 1995-05-26 1998-06-09 Ricoh Company, Ltd. Scanner, network scanner system, and method for network scanner system
US5875038A (en) * 1996-05-28 1999-02-23 Gerber Scientific, Inc. Facsimile queuing and transmission system
US5948038A (en) * 1996-07-31 1999-09-07 American Traffic Systems, Inc. Traffic violation processing system
US5809481A (en) * 1996-08-08 1998-09-15 David Baron Advertising method and system
US6097834A (en) * 1997-06-13 2000-08-01 Paystation America Inc. Financial transaction processing systems and methods
US6138129A (en) * 1997-12-16 2000-10-24 World One Telecom, Ltd. Method and apparatus for providing automated searching and linking of electronic documents
US7231594B1 (en) * 1999-02-10 2007-06-12 Collegenet, Inc. Method for paperless attachment of supplementary forms to a world wide web application
US20050177507A1 (en) * 2001-02-05 2005-08-11 Notiva Corporation Method and system for processing transactions
US20020176598A1 (en) * 2001-03-05 2002-11-28 Kristian Knowles Test processing workflow tracking system
US20020141660A1 (en) * 2001-03-12 2002-10-03 Multiscan Corp. Document scanner, system and method
US20030002068A1 (en) * 2001-06-27 2003-01-02 Michael Constantin Method of routing and processing document images sent using a digital scanner and transceiver
US7370014B1 (en) * 2001-11-01 2008-05-06 Metavante Corporation Electronic bill presentment and payment system that obtains user bill information from biller web sites
US20050246337A1 (en) * 2004-04-29 2005-11-03 Forman George H System and method for information management using handwritten identifiers
US20070033118A1 (en) * 2005-08-02 2007-02-08 Taxscan Technologies, Llc Document Scanning and Data Derivation Architecture.
US20100161466A1 (en) * 2006-10-10 2010-06-24 Gilder Clark S Electronic lockbox using digitally originated checks
US20080144881A1 (en) * 2006-12-13 2008-06-19 Bottomline Technologies (De) Inc. Electronic transaction processing server with automated transaction evaluation
US7978901B1 (en) * 2006-12-15 2011-07-12 First Data Corporation Centralized processing of checks for distributed merchant locations
US20080270293A1 (en) * 2007-04-26 2008-10-30 Bottomline Technologies (De) Inc. Accounts payable automation system with automated discount and factoring management
US20090216726A1 (en) * 2008-02-22 2009-08-27 Ramachandran Muthaiah System and Method for Facilitating Business Communications
US20110258195A1 (en) * 2010-01-15 2011-10-20 Girish Welling Systems and methods for automatically reducing data search space and improving data extraction accuracy using known constraints in a layout of extracted data elements

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150294297A1 (en) * 2014-04-15 2015-10-15 Capital One Financial Corporation System and method for inter-bank and intra-bank mobile banking communications and transfers

Also Published As

Publication number Publication date
WO2012122402A3 (en) 2013-01-10
US20110213685A1 (en) 2011-09-01
WO2012122402A2 (en) 2012-09-13
US8996416B2 (en) 2015-03-31
WO2012122402A4 (en) 2013-03-14

Similar Documents

Publication Publication Date Title
US7571848B2 (en) Decentralized system and method for the remote capture, processing and transmission of check 21™ compliant checking document information
US7818215B2 (en) Processing techniques for text capture from a rendered document
US8005743B2 (en) Electronic trading confirmation system
US9008447B2 (en) Method and system for character recognition
US9275051B2 (en) Automatic modification of web pages
US9684902B2 (en) Processing techniques for text capture from a rendered document
US8620760B2 (en) Methods and systems for initiating application processes by data capture from rendered documents
AU758266B2 (en) Remote image capture with centralized processing and storage
US7137064B2 (en) System and method for facilitating document imaging requests
US8628116B2 (en) Transparent deposit carrier having a plurality of pockets
US8275715B2 (en) Apparatuses, methods and systems for a deposit process manager decisioning engine
US7447347B2 (en) Method and system for retaining MICR code format
US8121908B2 (en) Data collection method and report generation apparatus including an automatch function for generating a report illustrating a field order and associated invoice
CA2588789C (en) Method and system for verifying check images
US7536325B2 (en) Method and system for generating account reconciliation data
CA2480361C (en) Single access point for filing of converted electronic forms to multiple processing entities
US7181420B2 (en) Methods and systems for online self-service receivables management and automated online receivables dispute resolution
US8401878B2 (en) Method and system for connecting an insured to an insurer using a mobile device
US7475335B2 (en) Method for automatically and dynamically composing document management applications
US7925518B2 (en) System and method for payment of medical claims
US7729990B2 (en) Check image access system
US7068832B1 (en) Lockbox imaging system
US20060122983A1 (en) Locating electronic instances of documents based on rendered instances, document fragment digest generation, and digest based document fragment determination
US8548886B1 (en) Account opening system, method and computer program product
US6603487B1 (en) System for electronically developing and processing a document

Legal Events

Date Code Title Description
AS Assignment

Owner name: LAVANTE, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FLYNN, JOSEPH;KOITZSCH, KERRY EDWARD;JRAIGE, WASSIM G.;REEL/FRAME:042416/0468

Effective date: 20110308

AS Assignment

Owner name: SUN TRUST BANK, GEORGIA

Free format text: SECURITY INTEREST;ASSIGNOR:LAVANTE, INC.;REEL/FRAME:042741/0689

Effective date: 20170518

STCB Information on status: application discontinuation

Free format text: FINAL REJECTION MAILED

AS Assignment

Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NO

Free format text: NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS;ASSIGNOR:LAVANTE, INC.;REEL/FRAME:048605/0799

Effective date: 20190314

AS Assignment

Owner name: LAVANTE, INC., GEORGIA

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:SUNTRUST BANK, AS ADMINISTRATIVE AGENT;REEL/FRAME:048612/0725

Effective date: 20190314

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION