WO2018067698A1 - Système et procédé de vérification de données non structurées de planification de ressources d'entreprise - Google Patents

Système et procédé de vérification de données non structurées de planification de ressources d'entreprise Download PDF

Info

Publication number
WO2018067698A1
WO2018067698A1 PCT/US2017/055135 US2017055135W WO2018067698A1 WO 2018067698 A1 WO2018067698 A1 WO 2018067698A1 US 2017055135 W US2017055135 W US 2017055135W WO 2018067698 A1 WO2018067698 A1 WO 2018067698A1
Authority
WO
WIPO (PCT)
Prior art keywords
electronic document
transaction
data
template
matching
Prior art date
Application number
PCT/US2017/055135
Other languages
English (en)
Inventor
Noam Guzman
Isaac SAFT
Original Assignee
Vatbox, Ltd.
M&B IP Analysts, LLC
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 claimed from US15/361,934 external-priority patent/US20170154385A1/en
Application filed by Vatbox, Ltd., M&B IP Analysts, LLC filed Critical Vatbox, Ltd.
Priority to CN201780071509.7A priority Critical patent/CN110023970A/zh
Priority to EP17859117.8A priority patent/EP3523771A4/fr
Publication of WO2018067698A1 publication Critical patent/WO2018067698A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/93—Document management systems
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/047—Payment circuits using payment protocols involving electronic receipts
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
    • 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
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • 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/123—Tax preparation or submission

Definitions

  • the present disclosure relates generally to verifying enterprise systems, and more specifically to verifying unstructured data in enterprise resource planning systems.
  • ERP enterprise resource planning
  • ERP systems generally collect data related to business activities of various departments in an enterprise. Such collected data may come from different data sources, and may be in different formats. ERP systems provide an integrated view of this business activity data, and further enable generation of expense reports that can later be sent to the relevant tax authority.
  • employees engage in a high number of business activities. Such business activities may further result in a large number of business expenses to be reported to tax authorities. Reporting such business expenses may result in tax breaks and refunds.
  • employees typically provide receipts based on expenses incurred and are usually required to indicate the types of such expenses. Based on the indication, an ERP system may generate a report which is provided with any received receipts to the relevant tax authority.
  • ERP systems must associate and track relations between sets of the managed data. For example, information related to tax reporting of a receipt must be maintained with an association to the receipt itself. Any errors in associations between data sets can result in incorrect reporting, which in turn may cause loss of profits due to unsuccessful redemptions and exemptions, and failure to comply with laws and regulations. Thus, accurate data management is crucial for ERP systems.
  • Tracking such data presents additional challenges when portions of the data are unstructured. For example, there are further difficulties associated with tracking expense receipts stored as image files. Some existing solutions to these challenges involve identifying contents of files containing unstructured data based on file extension names provided by users. Such solutions are subject to human error (e.g., typos, mistaking contents of files, etc.), and may not fully describe the contents therein. These disadvantages may further contribute to inaccuracies in ERP systems.
  • Certain embodiments disclosed herein include a method for verifying unstructured enterprise resource planning data.
  • the method comprises: analyzing a first electronic document to determine at least one transaction parameter of a transaction, wherein the first electronic document includes at least partially unstructured data; creating a template for the transaction, wherein the template is a structured dataset including the determined at least one transaction parameter; searching, in an enterprise resource planning system, for a matching second electronic document based on the created template; and verifying the transaction, when the matching second electronic document is found.
  • Certain embodiments disclosed herein also include a non-transitory computer readable medium having stored thereon causing a processing circuitry to execute a process, the process comprising: analyzing a first electronic document to determine at least one transaction parameter of a transaction, wherein the first electronic document includes at least partially unstructured data; creating a template for the transaction, wherein the template is a structured dataset including the determined at least one transaction parameter; searching, in an enterprise resource planning system, for a matching second electronic document based on the created template; and verifying the transaction, when the matching second electronic document is found.
  • Certain embodiments disclosed herein also include a system for verifying unstructured enterprise resource planning data.
  • the system comprises: a processing circuitry; and a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to: analyze a first electronic document to determine at least one transaction parameter of a transaction, wherein the first electronic document includes at least partially unstructured data; create a template for the transaction, wherein the template is a structured dataset including the determined at least one transaction parameter; search, in an enterprise resource planning system, for a matching second electronic document based on the created template; and verify the transaction, when the matching second electronic document is found.
  • Figure 1 is a network diagram utilized to describe the various disclosed embodiments.
  • Figure 2 is a flowchart illustrating a method for verifying enterprise resource planning data according to an embodiment.
  • Figure 3 is a flowchart illustrating a method for creating a template according to an embodiment.
  • Figure 4 is a block diagram of a verifier according to an embodiment.
  • the various disclosed embodiments include a system and method for verifying enterprise resource planning data by converting at least partially unstructured data into a structured format.
  • a template is created for a first reporting electronic document for verification.
  • the reporting electronic document includes at least partially unstructured data indicating transaction parameters for a transaction.
  • the template is created based on key fields and values identified via analysis of the reporting electronic document. Metadata for the reporting electronic document is generated based on the created template. Using the metadata, the reporting electronic document is verified by searching, in a storage of an enterprise resource planning system, for a matching second evidencing electronic document. If no matching evidencing electronic document is found (i.e., the reporting electronic document is unverified), one or more data sources may be searched to retrieve a matching evidencing electronic document verifying the reporting electronic document.
  • Fig. 1 shows an example network diagram 100 utilized to describe the various disclosed embodiments.
  • the network diagram 100 includes a verifier 120, an enterprise system 130, a database 140, and a user device 150 communicatively connected via a network 1 10.
  • the network may be, but is not limited to, a wireless, cellular or wired network, a local area network (LAN), a wide area network (WAN), a metro area network (MAN), the Internet, the worldwide web (WW), similar networks, and any combination thereof.
  • LAN local area network
  • WAN wide area network
  • MAN metro area network
  • WWW worldwide web
  • the enterprise system 130 is associated with an enterprise, and may store data related to transactions made by the enterprise or representatives of the enterprise as well as enterprise characteristic parameters indicating characteristics of the enterprise such as, but not limited to, country of formation, revenue data, structural data, and the like.
  • the enterprise may be, but is not limited to, a business whose employees may purchase goods and services on behalf of the business.
  • the enterprise system 130 may be, but is not limited to, a server, a database, an enterprise resource planning system, a customer relationship management system, or any other system storing relevant data.
  • the enterprise system 130 is an enterprise resource planning system storing reporting electronic documents, evidencing electronic documents, or both.
  • the database 140 stores at least evidencing electronic documents.
  • the database 140 may be operated by or otherwise associated with the enterprise associated with the enterprise system 130.
  • the database 140 may store evidencing electronic documents that are not stored in the enterprise system 130 such as, for example, evidencing electronic documents that are not uploaded to the enterprise system 130.
  • the database 140 may be queried to determine whether the database 140 stores the appropriate evidencing electronic document.
  • the user device 150 may be, but is not limited to, a personal computer, a laptop, a tablet computer, a smartphone, a wearable computing device, or any other device capable of capturing, storing, and sending unstructured data sets.
  • the user device 150 may be a smart phone including a camera.
  • the user device 150 may be utilized by, for example, an employee of an organization associated with the enterprise system 130.
  • the verifier 120 includes an optical recognition processor (e.g., the optical recognition processor 430, Fig. 4).
  • the optical recognition processor is configured to identify at least characters in data and, in particular, in unstructured data.
  • the verifier 120 is configured to receive a first reporting electronic document from the enterprise system 130.
  • the reporting electronic document is an at least partially unstructured electronic document including, but is not limited to, unstructured data, semi-structured data, structured data lacking a known format (e.g., a predetermined format recognized by the verifier 120), or a combination thereof.
  • the reporting electronic document received from the enterprise system 130 is typically, but is not limited to, an electronic document that may be, for example, manually filled in by an employee (by, e.g., typing or otherwise inputting information).
  • the reporting electronic document may be an image showing an expense report, or an unstructured or semi-structured text file including text of an expense report.
  • the reporting electronic document indicates information related to one or more transactions.
  • the reporting electronic document may include a line filled by an employee stating: "60 Euros in Taxi in Paris @ 10 Euros per trip" which actually refers to 6 taxi trips of 10 Euros each, i.e., 6 different transactions. In such a case, in order to verify the expense, 6 corresponding evidencing electronic documents are to be matched to the expenses report.
  • the reporting electronic document may be uploaded to the enterprise system 130 by, e.g., a user of the user device 150.
  • a user of the user device 150 may take a picture of an expense report via a camera (not shown) of the user device 150 and send the image to the enterprise system 130.
  • the verifier 120 is configured to analyze the at least partially unstructured reporting electronic document.
  • the analysis may include, but is not limited to, recognizing elements shown in the at least partially unstructured electronic document via computer vision techniques and creating templates of transaction attributes based on the recognized elements.
  • Such computer vision techniques may further include image recognition, pattern recognition, signal processing, character recognition, and the like.
  • Each created template is a structured dataset including the identified transaction parameters for a transaction.
  • the template includes one or more fields representing categories of transaction data, with each field including appropriate transaction parameters. Creation of structured dataset templates is described further herein below.
  • the verifier 120 is configured to generate metadata for each transaction (e.g., a business activity such as an expense) indicated in the at least partially unstructured reporting electronic document.
  • the metadata for a transaction may indicate one or more of the transaction parameters indicated in the reporting electronic document, and may be generated with respect to one or more fields of the respective template.
  • the fields for which the metadata is generated may be predetermined fields selected to represent information of the transaction that uniquely identifies the transaction such that an evidencing electronic document (e.g., a receipt) that matches the metadata provides evidence of the transaction.
  • the metadata may include a location in which the expense was incurred (indicated in a "location” field), characteristics (e.g., type of business, types of products sold, etc.) of the place of business in which the expense was made (e.g., as indicated in a "business info” field), a time at which the expense was incurred (e.g., as indicated in a "time” field), an amount (e.g., a monetary value or quantity indicated in a corresponding field), combinations thereof, and the like.
  • the verifier 120 is configured to verify each transaction indicated in the reporting electronic document by searching for a matching evidencing electronic document in the enterprise system 130 based on the generated metadata for the transaction. Specifically, a query may be generated based on the metadata and utilized to search the enterprise system 130 for a matching evidencing electronic document.
  • the matching evidencing electronic document may be associated with metadata matching the metadata generated for the reporting electronic document above a predetermined threshold.
  • the report is verified. If it is determined that there is a mismatch (i.e., the identified report structured data does not match the metadata of any evidencing electronic document stored in the enterprise system), a notification regarding the mismatch may be generated and sent to, e.g., the user device 150.
  • the verifier 120 may be configured to search for a matching evidencing electronic document for every unverified transaction in the database 140. If a match is found in the database, the verifier 120 may be configured to store the matching evidencing electronic document in the enterprise system 130 and to determined that the respective transaction is verified.
  • Using structured templates for verifying enterprise data allows for more efficient and accurate determination than, for example, by utilizing unstructured data directly.
  • metadata generated based on the templates may be generated with respect to particular fields such that the metadata more efficiently and more accurately demonstrates parameters that uniquely identify the transaction.
  • the metadata may be used to accurately search for matching evidencing electronic documents while reducing processing power and time related to comparing metadata.
  • the template may be stored instead of the reporting electronic document in the enterprise system 130 and, thus, may reduce memory usage as compared to storing the electronic document itself, especially when the electronic document is an image or other digital representation of visual data, as such visual representations typically require more memory usage than a structured text-based document.
  • the verifier 120 typically includes a processing circuitry (e.g., the processing circuitry 410, Fig. 4) coupled to a memory (e.g., the memory 415, Fig. 4).
  • the processing circuitry may comprise or be a component of a processor (not shown) or an array of processors coupled to the memory.
  • the memory contains instructions that can be executed by the processing circuitry. The instructions, when executed by the processing circuitry, configure the processing circuitry to perform the various functions described herein.
  • the embodiments disclosed herein are not limited to the specific architecture illustrated in Fig. 1 , and that other architectures may be equally used without departing from the scope of the disclosed embodiments.
  • the verifier 120 may reside in a cloud computing platform, a datacenter, and the like.
  • the database 140 may equally be another data source such as, for example a server having access to one or more databases. Further, multiple databases may be utilized without departing from the scope of the disclosure.
  • Fig. 2 is an example flowchart 200 illustrating a method for verifying data in an enterprise system according to an embodiment.
  • the method may be performed by a verifier (e.g., the verifier 120).
  • a first reporting electronic document is received or retrieved.
  • the reporting electronic document includes at least partially unstructured data related to one or more transactions.
  • the at least partially unstructured data includes, but is not limited to, unstructured data, semi-structured data, or structured data lacking a known format.
  • the transaction electronic document may be retrieved from, for example, an enterprise resource planning (ERP) system (e.g., the enterprise system 130, Fig. 1 ), or may be received from, for example, a user device (e.g., the user device 150, Fig. 1 ).
  • ERP enterprise resource planning
  • the transaction electronic document may be an image showing, for example, one or more expense reports related to business activities.
  • the image may be captured by a mobile device operated by an employee of an organization who takes a picture of an expense report form.
  • a template is created for each transaction indicated in the reporting electronic document.
  • the transaction electronic document may be analyzed via an optical character recognition (OCR) processor.
  • OCR optical character recognition
  • the analysis may further include using machine vision to identify elements in the at least partially unstructured data, cleaning or disambiguating the data, and generating a structured data including key fields and values identified in the at least partially unstructured data.
  • machine vision may be utilized to identify information related to a transaction noted in the receipt such as price, location, date, buyer, seller, and the like.
  • the disambiguation may include identifying multiple transactions within one set of fields and key values in the template.
  • the identification of multiple transactions may be based on one or more multi-transaction identification rules. For example, such rules may be based on a total price, e.g., if the total price is above a threshold value, it may be determined that the total price represents multiple transactions.
  • a template may be created for each of the multiple transactions. Disambiguation during template creation is described further herein below with respect to Fig. 3.
  • Metadata is generated for the respective transaction.
  • the metadata may be generated based on values in fields that uniquely identify the transaction.
  • a template including the fields "date,” “price,” “quantity,” and “item name” or “item number”
  • metadata indicating the values in those fields may be generated.
  • a corresponding evidencing electronic document is searched for in order to verify the transaction.
  • S240 may include generating a query based on the metadata, and searching for a matching evidencing electronic document through one or more data sources using the generated query.
  • the data sources include an enterprise resource planning system.
  • a second set data source may be searched for matching evidencing electronic documents. If a matching evidencing electronic document is found in the second data source, it may be retrieved and stored in the first data source.
  • a notification may be generated.
  • the notification may indicate whether the transaction was verified, i.e., whether a matching evidencing electronic document could be found for the transaction.
  • Fig. 3 is an example flowchart S220 illustrating a method for creating a template based on an electronic document including at least partially unstructured data according to an embodiment.
  • the electronic document is obtained.
  • Obtaining the electronic document may include, but is not limited to, receiving the electronic document (e.g., receiving a scanned image) or retrieving the electronic document (e.g., retrieving the electronic document from a consumer enterprise system, a merchant enterprise system, or a database).
  • the electronic document is analyzed to identify elements in the at least partially unstructured data.
  • the analysis may include, but is not limited to, using optical character recognition (OCR) to determine characters in the electronic document.
  • OCR optical character recognition
  • the elements may include, but are not limited to, characters, strings, or both, related to a transaction.
  • the elements may include printed data appearing in an expense receipt related to a business activity. Such printed data may include, but is not limited to, date, time, quantity, name of seller, type of seller business, value added tax payment, type of product purchased, payment method registration numbers, and the like.
  • key fields and values in the electronic document are identified.
  • the key field may include, but are not limited to, merchant's name and address, date, currency, good or service sold, a transaction identifier, an invoice number, and so on.
  • An electronic document may include unnecessary details that would not be considered to be key values.
  • a logo of the merchant may not be required and, thus, is not a key value.
  • a list of key fields may be predefined, and pieces of data that may match the key fields are extracted. Then, a cleaning process is performed to ensure that the information is accurately presented. For example, if the OCR would result in a data presented as "121 1212005", the cleaning process will convert this data to 12/12/2005. As another example, if a name is presented as "Mo$den", this will change to "Mosden”.
  • the cleaning process may be performed using external information resources, such as dictionaries, calendars, and the like.
  • S430 results in a complete set of the predefined key fields and their respective values.
  • S330 may further include disambiguating the unstructured data.
  • the disambiguation may be based on, but not limited to, a file name of the unstructured data set, dictionaries, algorithms, thesauruses, and the like. Disambiguation may result in more accurate identification of the transactions.
  • the disambiguation may be based on, but not limited to, the structure of the data (e.g., data in a field "Destination" may be disambiguated based on names of locations), dictionaries, algorithms, thesauruses, and the like.
  • a notification may be generated and sent to a user (e.g., a user of the user device 150), prompting the user to provide further clarification.
  • a user e.g., a user of the user device 150
  • a string "$300.00” character on the same line as the string "Total Price” may be utilized to determine that the value to be included in a "purchase price” field is $300.00.
  • the string "Drance” may be disambiguated based on a dictionary to result in metadata indicating that a location associated with the unstructured data set is France.
  • the structured data for a field may be "Taxi in Paris" and value for the field may be "60 Euros”. Based on one or more rules for maximum taxi price, it may be determined that the amount "60 Euros" is too high for a taxi expense and, therefore, that the field corresponds to multiple taxi trips.
  • a structured dataset is generated.
  • the generated dataset includes the identified key fields and values.
  • Fig. 4 is an example schematic diagram of the verifier 120 according to an embodiment.
  • the verifier 120 includes a processing circuitry 410 coupled to a memory 415, a storage 420, and a network interface 440.
  • the verifier 120 may include an optical character recognition (OCR) processor 430.
  • OCR optical character recognition
  • the components of the verifier 120 may be communicatively connected via a bus 450.
  • the processing circuitry 410 may be realized as one or more hardware logic components and circuits.
  • illustrative types of hardware logic components include field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), Application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), and the like, or any other hardware logic components that can perform calculations or other manipulations of information.
  • the memory 415 may be volatile (e.g., RAM, etc.), non-volatile (e.g., ROM, flash memory, etc.), or a combination thereof.
  • computer readable instructions to implement one or more embodiments disclosed herein may be stored in the storage 420.
  • the memory 415 is configured to store software.
  • Software shall be construed broadly to mean any type of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code).
  • the instructions when executed by the one or more processors, cause the processing circuitry 410 to perform the various processes described herein. Specifically, the instructions, when executed, cause the processing circuitry 410 to generate consolidated data based on electronic documents, as discussed herein.
  • the storage 420 may be magnetic storage, optical storage, and the like, and may be realized, for example, as flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVDs), or any other medium which can be used to store the desired information.
  • flash memory or other memory technology
  • CD-ROM Compact Discs
  • DVDs Digital Versatile Disks
  • the storage 420 may also store metadata generated based on analyses of unstructured data by the OCR processor 430. In a further embodiment, the storage 420 may further store queries generated based on the metadata.
  • the OCR processor 430 may include, but is not limited to, a feature and/or pattern recognition processor (RP) 435 configured to identify patterns, features, or both, in unstructured data sets. Specifically, in an embodiment, the OCR processor 430 is configured to identify at least characters in the unstructured data. The identified characters may be utilized to create a dataset including data required for verification of a request.
  • RP pattern recognition processor
  • the network interface 440 allows the verifier 120 to communicate with the enterprise system 130, the database 140, the user device 150, or a combination of, for the purpose of, for example, receiving electronic documents, sending notifications, searching for electronic documents, storing data, and the like.
  • reporting electronic document may be an expense report indicating multiple transactions made by an employee.
  • the various embodiments disclosed herein can be implemented as hardware, firmware, software, or any combination thereof.
  • the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium consisting of parts, or of certain devices and/or a combination of devices.
  • the application program may be uploaded to, and executed by, a machine comprising any suitable architecture.
  • the machine is implemented on a computer platform having hardware such as one or more central processing units (“CPUs"), a memory, and input/output interfaces.
  • CPUs central processing units
  • the computer platform may also include an operating system and microinstruction code.
  • a non-transitory computer readable medium is any computer readable medium except for a transitory propagating signal.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • General Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Engineering & Computer Science (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Technology Law (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un système et un procédé de vérification de données non structurées de planification de ressources d'entreprise. Le procédé consiste à analyser un premier document électronique pour déterminer au moins un paramètre de transaction d'une transaction, le premier document électronique comprenant au moins des données partiellement non structurées ; à créer un modèle pour la transaction, le modèle étant un ensemble de données structurées comprenant ledit paramètre de transaction déterminé ; à rechercher, dans un système de planification de ressources d'entreprise, un second document électronique correspondant sur la base du modèle créé ; et à vérifier la transaction une fois que le second document électronique correspondant a été trouvé.
PCT/US2017/055135 2016-10-09 2017-10-04 Système et procédé de vérification de données non structurées de planification de ressources d'entreprise WO2018067698A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201780071509.7A CN110023970A (zh) 2016-10-09 2017-10-04 用于验证非结构化的企业资源计划数据的系统和方法
EP17859117.8A EP3523771A4 (fr) 2016-10-09 2017-10-04 Système et procédé de vérification de données non structurées de planification de ressources d'entreprise

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662405921P 2016-10-09 2016-10-09
US62/405,921 2016-10-09
US15/361,934 2016-11-28
US15/361,934 US20170154385A1 (en) 2015-11-29 2016-11-28 System and method for automatic validation

Publications (1)

Publication Number Publication Date
WO2018067698A1 true WO2018067698A1 (fr) 2018-04-12

Family

ID=61832191

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/055135 WO2018067698A1 (fr) 2016-10-09 2017-10-04 Système et procédé de vérification de données non structurées de planification de ressources d'entreprise

Country Status (3)

Country Link
EP (1) EP3523771A4 (fr)
CN (1) CN110023970A (fr)
WO (1) WO2018067698A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2022305355A1 (en) * 2021-06-30 2024-01-18 Pricewaterhousecoopers Llp Ai-augmented auditing platform including techniques for automated document processing

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010049680A1 (en) * 1998-01-08 2001-12-06 Hidekazu Yanagimoto Information retrieval system, apparatus and method for selecting databases using retrieval terms
US20030212617A1 (en) * 2002-05-13 2003-11-13 Stone James S. Accounts payable process
US20100161616A1 (en) * 2008-12-16 2010-06-24 Carol Mitchell Systems and methods for coupling structured content with unstructured content

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8774516B2 (en) * 2009-02-10 2014-07-08 Kofax, Inc. Systems, methods and computer program products for determining document validity

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010049680A1 (en) * 1998-01-08 2001-12-06 Hidekazu Yanagimoto Information retrieval system, apparatus and method for selecting databases using retrieval terms
US20030212617A1 (en) * 2002-05-13 2003-11-13 Stone James S. Accounts payable process
US20100161616A1 (en) * 2008-12-16 2010-06-24 Carol Mitchell Systems and methods for coupling structured content with unstructured content

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3523771A4 *

Also Published As

Publication number Publication date
EP3523771A1 (fr) 2019-08-14
EP3523771A4 (fr) 2020-04-29
CN110023970A (zh) 2019-07-16

Similar Documents

Publication Publication Date Title
US10614527B2 (en) System and method for automatic generation of reports based on electronic documents
US11062132B2 (en) System and method for identification of missing data elements in electronic documents
US11138372B2 (en) System and method for reporting based on electronic documents
US20170323006A1 (en) System and method for providing analytics in real-time based on unstructured electronic documents
US20170193608A1 (en) System and method for automatically generating reporting data based on electronic documents
US20160321578A1 (en) System and method for verifying enterprise resource planning data
EP3494495A1 (fr) Système et procédé pour remplir des documents électroniques
EP3430540A1 (fr) Système et procédé pour la génération automatique de données de rapport basées sur des documents électroniques
US10558880B2 (en) System and method for finding evidencing electronic documents based on unstructured data
US20180096435A1 (en) System and method for verifying unstructured enterprise resource planning data
US20180046663A1 (en) System and method for completing electronic documents
US20170169518A1 (en) System and method for automatically tagging electronic documents
WO2018067698A1 (fr) Système et procédé de vérification de données non structurées de planification de ressources d'entreprise
US20170161315A1 (en) System and method for maintaining data integrity
US10387561B2 (en) System and method for obtaining reissues of electronic documents lacking required data
EP3494496A1 (fr) Système et procédé de génération de rapports sur la base de documents électroniques
EP3526758A1 (fr) Recherche de documents électroniques d'attestation sur la base de données non structurées
WO2017201012A1 (fr) Système et procédé pour fournir des analyses en temps réel sur la base de documents électroniques non structurés
WO2017142615A1 (fr) Système et procédé de gestion d'intégrité de données
EP3417383A1 (fr) Vérification automatique de demandes sur la base de documents électroniques
US20200118122A1 (en) Techniques for completing missing and obscured transaction data items
EP3494530A1 (fr) Obtention de réédition de documents électroniques manquant de données requises
WO2017142624A1 (fr) Système et procédé de marquage automatique de document électronique
EP3491554A1 (fr) Mise en correspondance de documents électroniques de transaction avec des documents électroniques de preuve
EP3430584A1 (fr) Système et procédé de vérification automatique de transactions sur la base de documents électroniques

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17859117

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2017859117

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017859117

Country of ref document: EP

Effective date: 20190509