EP3430540A1 - System and method for automatically generating reporting data based on electronic documents - Google Patents
System and method for automatically generating reporting data based on electronic documentsInfo
- Publication number
- EP3430540A1 EP3430540A1 EP17767105.4A EP17767105A EP3430540A1 EP 3430540 A1 EP3430540 A1 EP 3430540A1 EP 17767105 A EP17767105 A EP 17767105A EP 3430540 A1 EP3430540 A1 EP 3430540A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- electronic document
- reporting
- transaction
- template
- 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.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/123—Tax preparation or submission
-
- 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
Definitions
- the present disclosure relates generally to data analysis, and more particularly to generating reporting based on analysis of unstructured data.
- the Value-Added Tax is a broadly based consumption tax assessed on the value added to goods and services.
- a particular VAT applies to most goods and services that are bought or sold within a given community.
- Other taxes applied to purchases may similarly be refunded under particular circumstances.
- sellers may offer rebates for purchases of products sold in certain locations and under particular circumstances. Such refunds of the purchase price may be reclaimed by following procedures established by the refunding entity.
- the laws and regulations of many countries allow foreign travelers the right for reimbursement or a refund of certain taxes such as, e.g., VATs paid for goods and/or services abroad.
- One procedure to request a refund is to physically approach a customs official at an airport, fill out a form, and file the original receipts respective of the expenses incurred during the visit. This procedure should be performed prior to checking in or boarding to the next destination. Additionally, particularly with respect to goods purchased abroad, the procedure to request a refund may require that the payer show the unused goods to a custom official to verify that the goods being exported match the goods that the payer paid VATs on.
- Certain embodiments disclosed herein include a method for generating reporting data based on an electronic document.
- the method comprises: analyzing the electronic document to determine at least one transaction parameter of a transaction, wherein the 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; obtaining, based on the created template, a plurality of reporting requirements; and generating, based on the created template and the obtained plurality of reporting requirements, qualified reporting data.
- Certain embodiments disclosed herein also include a non-transitory computer readable medium having stored thereon instructions for causing a processing circuitry to perform a process, the process comprising: analyzing an electronic document to determine at least one transaction parameter of a transaction, wherein the 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; obtaining, based on the created template, a plurality of reporting requirements; and generating, based on the created template and the obtained plurality of reporting requirements, qualified reporting data.
- Certain embodiments disclosed herein also include a system for generating reporting data based on an electronic document.
- 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 an electronic document to determine at least one transaction parameter of a transaction, wherein the 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; obtain, based on the created template, a plurality of reporting requirements; and generate, based on the created template and the obtained plurality of reporting requirements, qualified reporting data.
- Figure 1 is a network diagram utilized to describe the various disclosed embodiments.
- Figure 2 is a schematic diagram of a data integrity manager according to an embodiment.
- Figure 3 is a flowchart illustrating a method for automatically generating reporting data according to an embodiment.
- Figure 4 is a flowchart illustrating a method for creating a dataset based on at least one electronic document according to an embodiment.
- the various disclosed embodiments include a method and system for automatically generating reporting data based on an electronic document.
- a dataset is created based on an electronic document.
- the at least one electronic document is at least partially unstructured.
- a template of transaction attributes is created. Reporting requirements are obtained based on the template.
- the qualified reporting data may include, e.g., a completed value-added tax (VAT) reclaim form, at least one electronic document evidencing a transaction, or both.
- the generated qualified reporting data may be sent to, e.g., a reporting authority server.
- VAT completed value-added tax
- Fig. 1 shows an example network diagram 100 utilized to describe the various disclosed embodiments.
- a report generator 120 an enterprise system 130, a database 140, and a plurality of web sources 150-1 through 150-N (hereinafter referred to individually as a web source 150 and collectively as web sources 150, merely for simplicity purposes), are communicatively connected via a network 1 10.
- the network 1 10 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 (WWW), 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 purchases made by the enterprise or representatives of the enterprise as well as data related to the enterprise itself.
- the enterprise may be, but is not limited to, a business whose employees may purchase goods and services subject to VAT taxes while abroad.
- 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 data stored by each of the enterprise system 130 may include, but is not limited to, electronic documents (e.g., an image file showing, for example, a scan of an invoice, a text file, a spreadsheet file, etc.).
- Data included in each electronic document may be structured, semi-structured, unstructured, or a combination thereof.
- the structured or semi-structured data may be in a format that is not recognized by the report generator 120 and, therefore, may be treated like unstructured data.
- the database 140 stores at least data evidencing transactions.
- data may include, but is not limited to, evidentiary electronic documents including information related to transactions.
- the evidentiary electronic documents may include, but are not limited to, invoices, receipts, and the like.
- the web sources 150 store at least requirements for data reporting (e.g., for reporting and claiming VAT refunds). The requirements may be stored in the form of, for example, rules. The web sources 150 may further store data utilized to generate reports such as, but not limited to, tillable reporting forms (e.g., a tillable VAT reclaim form). Different web sources 150 may store different reporting requirements and forms (e.g., reporting requirements or forms for different countries). As a non-limiting example, the web source 140-1 may store regulatory requirements for VAT reporting in France. As another non-limiting example, the web source 140-8 may store VAT reclaim forms utilized for reporting VAT reclaims in Italy.
- tillable reporting forms e.g., a tillable VAT reclaim form
- Different web sources 150 may store different reporting requirements and forms (e.g., reporting requirements or forms for different countries).
- the web source 140-1 may store regulatory requirements for VAT reporting in France.
- the web source 140-8 may store VAT reclaim forms utilized for reporting VAT reclaims in Italy.
- the report generator 120 is configured to generate a template based on transaction parameters identified using machine vision in an electronic document. In a further embodiment, the report generator 120 is configured to compare the template to at least one reporting requirement to determine if a transaction represented by the data of the template is qualified (e.g., for a VAT reclaim). In yet a further embodiment, the report generator 120 is configured to generate qualified reporting data based on the template when it is determined that the transaction is qualified.
- the generated qualified reporting data may include, but is not limited to, an electronic document (e.g., an electronic document including a completed VAT reclaim form), data evidencing the transaction (e.g., an electronic document including a receipt or invoice related to the transaction), or both.
- the qualified reporting data may be sent to, e.g., a reporting authority (for example, an appropriate tax authority).
- a reporting authority for example, an appropriate tax authority.
- the report generator 120 is configured to create datasets based on electronic documents including data that is at least partially unstructured (e.g., unstructured data, semi-structured data, or structured data having an unknown structure).
- the report generator 120 may be further configured to utilize optical character recognition (OCR) or other image processing to determine data in the electronic document.
- OCR optical character recognition
- the report generator 120 is configured to analyze the created datasets to identify transaction parameters related to transactions indicated in the electronic documents. In another embodiment, the report generator 120 may be configured to determine whether the created datasets are eligible for reclaim based on, e.g., whether the dataset meets at least one predetermined constraint.
- the report generator 120 is configured to create a template based on the created datasets.
- the template is a structured dataset including the identified transaction parameters.
- the created template is utilized as the potential reporting template.
- Fig. 2 is an example schematic diagram of the report generator 120 according to an embodiment.
- the report generator 120 includes a processing circuitry 410 coupled to a memory 215, a storage 220, an optical character recognition (OCR) processor 230, and a network interface 240.
- OCR optical character recognition
- the components of the report generator 120 may be communicatively connected via a bus 250.
- the processing circuitry 210 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 215 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 220.
- the memory 215 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 processing circuitry 210, cause the processing circuitry 210 to perform the various processes described herein. Specifically, the instructions, when executed, cause the processing circuitry 210 to perform automatic generation of reporting data based on an electronic document, as described herein.
- the storage 220 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 OCR processor 230 may include, but is not limited to, a feature and/or pattern recognition unit (RU) 235 configured to identify patterns, features, or both, in unstructured data sets. Specifically, in an embodiment, the OCR processor 230 is configured to identify at least characters in the unstructured data. The identified characters may be utilized to create a validation dataset including data required for validation of a transaction.
- RU feature and/or pattern recognition unit
- the network interface 240 allows the report generator 120 to communicate with the enterprise system 130, the database 140, the web sources 150, or a combination of, for the purpose of, for example, retrieving data, storing data, and the like.
- Fig. 3 is an example flowchart 300 illustrating a method for generating reporting data based on electronic documents according to an embodiment. In an embodiment, the method may be performed by the report generator 120.
- a dataset is created based on an electronic document including information related to a transaction.
- the electronic document may include, but is not limited to, unstructured data, semi-structured data, structured data with structure that is unanticipated or unannounced, or a combination thereof.
- S310 may further include analyzing the electronic document using optical character recognition (OCR) to determine data in the electronic document, identifying key fields in the data, identifying values in the data, or a combination thereof.
- OCR optical character recognition
- analyzing the dataset may include, but is not limited to, determining transaction parameters such as, but not limited to, at least one entity identifier (e.g., a consumer enterprise identifier, a merchant enterprise identifier, or both), information related to the transaction (e.g., a date, a time, a price, a type of good or service sold, etc.), or both.
- entity identifier e.g., a consumer enterprise identifier, a merchant enterprise identifier, or both
- information related to the transaction e.g., a date, a time, a price, a type of good or service sold, etc.
- analyzing the dataset may also include identifying the transaction based on the dataset.
- S330 it is determined, based on the analysis, whether the created dataset is eligible for reporting and, if so, execution continues with S340; otherwise, execution terminates.
- S330 may include determining whether the created dataset meets at least one predetermined constraint.
- a dataset may be eligible for reporting if, e.g., the dataset meets the at least one predetermined constraint.
- predetermined constraints may include, but are not limited to, requirements on types of information needed for validation, accuracy requirements, or a combination thereof. For example, if an electronic document does not include a country for the merchant enterprise in a transaction or a price of the transaction, successful reporting may not be possible. Determining whether the transaction is eligible for reporting may reduce use of computing resources by only reporting using datasets meeting minimal requirements.
- S330 may further include determining at least one constraint based on the created dataset.
- determining the at least one constraint may include searching in at least one database based on the created dataset (e.g., using a location of the merchant enterprise indicated in the created dataset).
- S330 may also include analyzing at least one reporting requirements electronic document (e.g., a VAT reclaim form) to determine the at least one constraint. The analysis may further include performing OCR or other image processing on each reporting requirements electronic document.
- the at least one constraint may require that the dataset include a price, at least one good or service, and a location to be eligible.
- additional data, replacement data, or both may be retrieved from at least one data source and included in the created dataset.
- the merchant's name can be extracted from a governmental database based on other information indicated in the invoice.
- execution continues with S340.
- a template is created based on the analyzed dataset.
- the template may be, but is not limited to, a data structure including a plurality of fields.
- the fields may include the identified transaction parameters.
- the fields may be predefined.
- Creating templates from electronic documents allows for faster processing due to the structured nature of the created templates. For example, query and manipulation operations may be performed more efficiently on structured datasets than on datasets lacking such structure. Further, organizing information from electronic documents into structured datasets, the amount of storage required for saving information contained in electronic documents may be significantly reduced. Electronic documents are often images that require more storage space than datasets containing the same information. For example, datasets representing data from 100,000 image electronic documents can be saved as data records in a text file. A size of such a text file would be significantly less than the size of the 100,000 images.
- a plurality of reporting requirements is obtained based on the template.
- S350 may include selecting at least one data source from which the reporting requirements can be obtained.
- the selection may be based on the template.
- the at least one reporting requirement may include one or more rules for determining potential reporting parameters.
- the at least one reporting requirement may include a rule for calculating an amount for a VAT reclaim based on one or more transaction parameters.
- S350 includes retrieving the at least one reporting requirement from at least one data source (e.g., a database of a regulatory authority that establishes requirements for VAT reclaims).
- the at least one reporting requirement may be retrieved based on at least a portion of the template.
- Each potential reporting parameter is a parameter that may be requested or otherwise reported. As a non-limiting example, if a location indicated in a "location" field of the template is France, reporting requirements may be obtained from a server of a French tax authority.
- S350 may include retrieving at least one reporting electronic document such as, but not limited to, an electronic document including a VAT reclaim request form.
- S350 includes determining the at least one reporting requirement by analyzing, via machine imaging, the retrieved at least one reporting electronic document.
- S360 based on the obtained reporting requirements and the created template, it is determined if the transaction indicated in the template is qualified and, if so, execution continues with S370; otherwise, execution terminates.
- S360 includes comparing data in the template to data in the reporting requirements.
- the transaction may be qualified if each of the reporting requirements is met.
- a transaction may be qualified based on reporting requirements from a German tax authority if the template includes the location "Germany", purchased products belonging to a list of predetermined VAT-reclaim eligible products, and an indication that the buyer is from a country other than Germany.
- S370 when it is determined that the transaction is qualified, qualified reporting data is generated.
- S370 includes generating a reporting electronic document including data meeting the obtained reporting requirements.
- S370 may also include retrieving an electronic document to be completed.
- S370 may include generating, using an electronic document including a blank VAT reclaim form and the created template, a completed VAT reclaim form.
- the retrieved electronic document (e.g., the blank VAT reclaim form) may be structured to allow for insertion of particular information.
- the retrieved electronic document may be completed based on such structure.
- S370 may further include obtaining at least one evidentiary electronic document related to the transaction.
- S370 may include querying, using data of the template, at least one data source storing information related to transactions.
- an electronic document including a receipt for a purchase may be retrieved from a merchant server of a merchant of the transaction by querying the merchant server using a transaction identifier of the template.
- Fig. 4 is an example flowchart S310 illustrating a method for creating a dataset based on an electronic document 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.
- 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
- 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. As an example, 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.
- a cleaning process is performed to ensure that the information is accurately presented. For example, if the OCR would result in 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.
- a structured dataset is generated.
- the generated dataset includes the identified key fields and values.
- 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.
- any reference to an element herein using a designation such as "first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations are generally used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in some manner. Also, unless stated otherwise, a set of elements comprises one or more elements.
- the phrase "at least one of” followed by a listing of items means that any of the listed items can be utilized individually, or any combination of two or more of the listed items can be utilized. For example, if a system is described as including "at least one of A, B, and C," the system can include A alone; B alone; C alone; A and B in combination; B and C in combination; A and C in combination; or A, B, and C in combination.
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201662307497P | 2016-03-13 | 2016-03-13 | |
US15/361,934 US20170154385A1 (en) | 2015-11-29 | 2016-11-28 | System and method for automatic validation |
PCT/US2017/014874 WO2017160403A1 (en) | 2016-03-13 | 2017-01-25 | System and method for automatically generating reporting data based on electronic documents |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3430540A1 true EP3430540A1 (en) | 2019-01-23 |
EP3430540A4 EP3430540A4 (en) | 2019-10-09 |
Family
ID=59850546
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP17767105.4A Withdrawn EP3430540A4 (en) | 2016-03-13 | 2017-01-25 | System and method for automatically generating reporting data based on electronic documents |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP3430540A4 (en) |
CN (1) | CN109219809A (en) |
WO (1) | WO2017160403A1 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110516219A (en) * | 2019-08-27 | 2019-11-29 | 上海美吉生物医药科技有限公司 | A kind of method and system based on the production report of product collection |
CN111107154B (en) * | 2019-12-23 | 2022-12-09 | 医渡云(北京)技术有限公司 | Data reporting method and device |
CN111340038B (en) * | 2020-05-20 | 2020-08-21 | 四川新网银行股份有限公司 | Disposable image data acquisition method for MOCK test |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7827079B2 (en) * | 2003-06-30 | 2010-11-02 | Ebay Inc. | Method and system for assessing and reporting VAT charges for network-based marketplace services |
US7607078B2 (en) * | 2005-07-06 | 2009-10-20 | International Business Machines Corporation | Paper and electronic recognizable forms |
US20070168382A1 (en) * | 2006-01-03 | 2007-07-19 | Michael Tillberg | Document analysis system for integration of paper records into a searchable electronic database |
US8774516B2 (en) * | 2009-02-10 | 2014-07-08 | Kofax, Inc. | Systems, methods and computer program products for determining document validity |
CN102654874A (en) * | 2011-03-02 | 2012-09-05 | 顾菊林 | Bill data management method and system |
CN103121324B (en) * | 2013-02-06 | 2015-09-16 | 心医国际数字医疗系统(大连)有限公司 | A kind of medical imaging concentrates the system of printing |
CN105243117B (en) * | 2015-09-28 | 2019-03-12 | 四川长虹电器股份有限公司 | A kind of data processing system and method |
-
2017
- 2017-01-25 CN CN201780027071.2A patent/CN109219809A/en active Pending
- 2017-01-25 WO PCT/US2017/014874 patent/WO2017160403A1/en active Application Filing
- 2017-01-25 EP EP17767105.4A patent/EP3430540A4/en not_active Withdrawn
Also Published As
Publication number | Publication date |
---|---|
CN109219809A (en) | 2019-01-15 |
WO2017160403A1 (en) | 2017-09-21 |
EP3430540A4 (en) | 2019-10-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10546351B2 (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 | |
US20170193608A1 (en) | System and method for automatically generating reporting data based on electronic documents | |
US20170323006A1 (en) | System and method for providing analytics in real-time based on unstructured electronic documents | |
US11138372B2 (en) | System and method for reporting based on electronic documents | |
US20170169292A1 (en) | System and method for automatically verifying requests based on electronic documents | |
US20180011846A1 (en) | System and method for matching transaction electronic documents to evidencing electronic documents | |
US20190236127A1 (en) | Generating a modified evidencing electronic document including missing elements | |
US20170323157A1 (en) | System and method for determining an entity status based on unstructured electronic documents | |
EP3494495A1 (en) | System and method for completing electronic documents | |
EP3430540A1 (en) | System and method for automatically generating reporting data based on electronic documents | |
US20170161315A1 (en) | System and method for maintaining data integrity | |
US20180046663A1 (en) | System and method for completing electronic documents | |
US10387561B2 (en) | System and method for obtaining reissues of electronic documents lacking required data | |
WO2017142615A1 (en) | System and method for maintaining data integrity | |
US20180101745A1 (en) | System and method for finding evidencing electronic documents based on unstructured data | |
US20170169519A1 (en) | System and method for automatically verifying transactions based on electronic documents | |
WO2017142618A1 (en) | Automatic verification of requests based on electronic documents | |
WO2018132655A2 (en) | System and method for optimizing reissuance of electronic documents | |
WO2017201012A1 (en) | Providing analytics in real-time based on unstructured electronic documents | |
WO2018027130A1 (en) | System and method for reporting based on electronic documents | |
WO2018027133A1 (en) | Obtaining reissues of electronic documents lacking required data | |
WO2018048512A1 (en) | Matching transaction electronic documents to evidencing electronic | |
WO2017160372A1 (en) | System and method for automatically verifying transactions based on electronic documents |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20181011 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06F 17/30 20060101AFI20170922BHEP Ipc: G06Q 30/00 20120101ALI20170922BHEP |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20190909 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06Q 20/04 20120101ALI20190903BHEP Ipc: G06Q 20/40 20120101ALI20190903BHEP Ipc: G06Q 20/42 20120101AFI20190903BHEP Ipc: G06Q 40/00 20120101ALI20190903BHEP Ipc: G06Q 20/38 20120101ALI20190903BHEP Ipc: G06Q 30/04 20120101ALI20190903BHEP Ipc: G06F 16/00 20190101ALI20190903BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20200603 |